Showing Telegram's notifications on the lock screen

[zolagonano]

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Other (Please describe in detail)

Current Behavior

i3lock shows telegram's notifications(and probably other apps as well) while its locked, which might contain sensitive information.

Expected Behavior

Not showing anything from outside lock screen.

Reproduction Instructions

1. open telegram desktop
2. lock your device
3. send a message to your telegram account, and you'll get the message on the lock screen

Environment

Output of i3lock --version:

i3lock version:  2.14.1 

[stapelberg]

Are you using a compositor like xcompmgr, compton, picom or others? If so, try turning it off.

[zolagonano]

Are you using a compositor like xcompmgr, compton, picom or others? If so, try turning it off.

Yeah i do.
I tried turning them off and it fixed the problem.
but i still need my compositor, is there any fix for that? without having to remove the compositor?

[stapelberg]

I don’t recall if there are better workarounds, but you can wrap i3lock in a script that kills the compositor, invokes i3lock, then restarts the compositor.

[kolayne]

Killing picom didn't work for me. Running Telegram version 4.7.1, i3lock: version 2.14.1

[ssidashov]

I have the same problem, and I have no picom or any other compositor installed. Telegram messages are showed on lock screen. Btw, betterlockscreen has the same problem.
i3lock: version 2.13.c.4

[stapelberg]

I cannot reproduce this problem without a compositor.

I tried it with Telegram’s native notifications and custom notifications. Neither show up on i3lock when not running a compositor.

As soon as I start a compositor, both mechanisms show up.

To double-check whether you’re running a compositor: run notify-send foo via SSH. If the message is visible on i3lock, you’re running a compositor.

i3lock: version 2.13.c.4

This is not a known version number. We have released i3lock 2.13, followed by 2.14. I don’t know what the “c.4” stands for. I suggest you try it with upstream i3lock, without modifications.

[orestisfl]

To double-check whether you’re running a compositor: run notify-send foo via SSH. If the message is visible on i3lock, you’re running a compositor.

Just to propose a way to setup this test without ssh, one can run:

i3lock & sleep 1 && notify-send foo

[ssidashov]

This is not a known version number. We have released i3lock 2.13, followed by 2.14. I don’t know what the “c.4” stands for. I suggest you try it with upstream i3lock, without modifications.

Yes, i'm sorry, this is a version of fork i3lock-color (https://github.com/Raymo111/i3lock-color), which is betterlockscreen dependency in Arch.

[micronull]

The problem is reproduced on version 2.14.1

i3lock & sleep 1 && notify-send foo

With picom turned off, there is no problem.

[tycho-kirchner]

While I prefer using i3lock I wanted to point out that gnome-screensaver is able to hide the notifications, even if a compositor is running. I don't know, how, but it might be worth looking into.

gnome-screensaver-command --lock & sleep 1; notify-send foo

[zolagonano]

aah, this works well thank you. but all this long, i guess the fix to this problem was removing the program itself

…

-------- Original Message --------

On 3/8/25 01:33, Tycho Kirchner wrote: While I prefer using i3lock I wanted to point out that gnome-screensaver is able to hide the notifications, even if a compositor is running. I don't know, how, but it might be worth looking into. gnome-screensaver-command --lock & sleep 1; notify-send foo — Reply to this email directly, [view it on GitHub](#333 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASROZ3YRDFKQWZMZ3FNQUN32TIJU5AVCNFSM6AAAAABYSFPPR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGU2TMOJZGY). You are receiving this because you authored the thread.Message ID: ***@***.***> [tycho-kirchner]tycho-kirchner left a comment [(i3/i3lock#333)](#333 (comment)) While I prefer using i3lock I wanted to point out that gnome-screensaver is able to hide the notifications, even if a compositor is running. I don't know, how, but it might be worth looking into. gnome-screensaver-command --lock & sleep 1; notify-send foo — Reply to this email directly, [view it on GitHub](#333 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASROZ3YRDFKQWZMZ3FNQUN32TIJU5AVCNFSM6AAAAABYSFPPR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGU2TMOJZGY). You are receiving this because you authored the thread.Message ID: ***@***.***>

[tycho-kirchner]

the fix to this problem was removing the program itself

Uh, which program did u remove 😅?

[zolagonano]

i3locks. switched to gnome screensaver, although im not sure if it was an i3locks problem or a compositor problem. but anyways, something had to be removed.

…

-------- Original Message --------

On 3/8/25 01:48, Tycho Kirchner wrote: > the fix to this problem was removing the program itself Uh, which program did u remove 😅? — Reply to this email directly, [view it on GitHub](#333 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASROZ3YFLP5IHN5G6AKCFDT2TILKTAVCNFSM6AAAAABYSFPPR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGU4TSOBSGE). You are receiving this because you authored the thread.Message ID: ***@***.***> [tycho-kirchner]tycho-kirchner left a comment [(i3/i3lock#333)](#333 (comment)) > the fix to this problem was removing the program itself Uh, which program did u remove 😅? — Reply to this email directly, [view it on GitHub](#333 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ASROZ3YFLP5IHN5G6AKCFDT2TILKTAVCNFSM6AAAAABYSFPPR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBXGU4TSOBSGE). You are receiving this because you authored the thread.Message ID: ***@***.***>