Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck on alert colour #38

Open
jefferyto opened this issue Nov 18, 2017 · 3 comments
Open

Stuck on alert colour #38

jefferyto opened this issue Nov 18, 2017 · 3 comments
Labels

Comments

@jefferyto
Copy link

Hi,

I'm using the latest version from e.g.o. on Ubuntu 17.10 (GNOME Shell 3.26.1) and my clock is frequently stuck on the alert colour. I've set the blink rate to 0 but the issue is still present if the rate is higher (so it actually blinks).

I believe the trigger is, if I receive a notification and the notification is revoked when the screen is locked, then the clock is stuck on the alert colour. Let me know if there is anything more I should add or try.

Thanks!

@bellini666
Copy link
Owner

Hey @jefferyto . Thanks for reporting the issue.

What do you mean by the notification is revoked when the screen is locked? How to you revoke it while the screen is locked?

@bellini666 bellini666 added the bug label Nov 20, 2017
@jefferyto
Copy link
Author

Applications can call g_application_withdraw_notification() to withdraw sent notifications.

There are also notifications with the transient hint set to true, that do not appear in the message tray after it has been shown. (Though transient notifications do seem to be shown after the screen is unlocked instead of disappearing while the screen is locked.)

I've been testing transient notifications (using notify-send) with the screen locked, and it sometimes triggers this issue (but not always). I haven't figured out how to reliably cause notifications to be withdrawn yet.

@bellini666
Copy link
Owner

hrm, didn't know about g_application_withdraw_notification().

One thing to notice is that the gnome-shell disables all extensions on screen lock and re-enables them on unlock.

This shouldn't be an issue for this extension because, when activated, it would check for notifications and "do its thing" correctly. It shouldn't matter whatever happens in the lockscreen. However, since you are having that issue, there may be something happening that I'm not aware of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants