After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 752881 - Gnome shell completely ignores notification settings.
Gnome shell completely ignores notification settings.
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2015-07-26 11:07 UTC by Hussam Al-Tayeb
Modified: 2021-07-05 14:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
telepathyClient: Use protocol-specific policy (1.10 KB, patch)
2015-07-26 17:16 UTC, Florian Müllner
committed Details | Review

Description Hussam Al-Tayeb 2015-07-26 11:07:29 UTC
Gnome shell doesn't respect notification settings.
I changed the setting in gnome-control-center to not show notifications on the lock screen. it still shows notifications on the lock screen.
I set it not to show notifications from empathy at all but it still shows them both in the message tray and the lock screen.
Comment 1 André Klapper 2015-07-26 16:49:14 UTC
Which distribution?
Comment 2 Hussam Al-Tayeb 2015-07-26 17:00:52 UTC
Arch Linux.
The notifications are mostly from empathy/polari.
Another observation is: When I clear the Polari notifications (nickserv stuff), they immediately reappear. I have to restart gnome-shell, then clear them to make them permanently disappear for that session.

Does each application have to respect the notification settings or does gnome-shell filter what appears and what doesn't appear?
Comment 3 Florian Müllner 2015-07-26 17:14:57 UTC
I cannot reproduce this - the global "Lock Screen Notifications" switch works as expected, as does Empathy's corresponding setting for the shell's built-in chat notifications. Both global and app-specific banner settings work here, and so does disabling empathy notifications altogether (which also apply to gnome-shell's built-in chat).
Comment 4 Florian Müllner 2015-07-26 17:16:12 UTC
Created attachment 308181 [details] [review]
telepathyClient: Use protocol-specific policy

Since commit 79c04c93e4cb2, we launch Polari instead of Empathy when
activating a chat notification for an IRC channel. It therefore makes
sense to follow Polari's notification policy for those notifications
rather than Empathy's.

Drive-by fix to pick a more appropriate policy for built-in chat notifications.
Comment 5 Florian Müllner 2015-07-26 17:23:21 UTC
(In reply to Hussam Al-Tayeb from comment #2)
> Another observation is: When I clear the Polari notifications (nickserv
> stuff), they immediately reappear.

Those are not really polari notifications, but built-in chat notifications - see bug 747991.

> I have to restart gnome-shell, then clear
> them to make them permanently disappear for that session.

It should go away if you close the conversation in polari (or empathy for non-irc protocols).


> Does each application have to respect the notification settings or does
> gnome-shell filter what appears and what doesn't appear?

gnome-shell enforces the policy for applications (and its own notifications, which this issue is about)
Comment 6 Florian Müllner 2015-08-05 15:22:46 UTC
Comment on attachment 308181 [details] [review]
telepathyClient: Use protocol-specific policy

Attachment 308181 [details] pushed as 58905bd - telepathyClient: Use protocol-specific policy
Comment 7 Simón 2016-02-09 10:22:07 UTC
I have the same problem with Lollypop (https://github.com/gnumdk/lollypop). But the problem appears when I reactivate the session after a screen lock. There is a issue closed (in github) related to this: https://github.com/gnumdk/lollypop/issues/373
Comment 8 GNOME Infrastructure Team 2021-07-05 14:17:07 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.