! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
xfce4-notifyd doesn't log notifications by default
Status:
RESOLVED: INVALID
Product:
Xfce4-notifyd
Component:
general

Comments

Description Marco R. 2020-04-23 17:04:06 CEST
I was testing the Xubuntu daily ISO:
- xubuntu/daily-live/current/focal-desktop-amd64.iso.zsync
- xubuntu/bionic/daily-live/current/bionic-desktop-amd64.iso.zsync

And noticed that by default the xfce4-notifyd (notification panel plugin) comes with notification log disabled. This means that when you receive a notification it won't get logged.

Testcase:
- Boot live desktop
- Open Firefox and go to -> https://www.bennish.net/web-notifications.html
- Click "Authorize" and allow notifications
- Click "Show" to trigger a notification
- After the notification fades out, click the bell icon in the panel

Expected behaviour:
- Clicking the bell icon in the panel shows the notifications triggered by firefox

Actual Behaviour:
- No notifications logged

This can be fixed by activating "Log Notifications" to "Always" inside "Notifications" in "xfce4-settings-manager".

Is this default behaviour correct?

This means that if i'm not paying attention to my screen while receiving a notification, it get lost forever without a chance to review it.

[Also reported as a question on LP: ]
Comment 1 Marco R. 2020-04-23 17:05:43 CEST
Also reported as a question on LP: https://answers.launchpad.net/ubuntu/+source/xfce4-notifyd/+question/690117
Comment 2 Simon Steinbeiss editbugs 2020-04-23 18:23:34 CEST
From an Xfce upstream perspective this is the correct behavior, because we cannot know whether the panel plugin is present and without it, the log is not very accessible and meaningful.

Distributions can decide whether they think it's good to enable the log and with which settings (if you look through the settings dialog you will see that notifications log settings have several conditions as to when to log which applications).

So please report this against the package xubuntu-default-settings on Launchpad instead.
Comment 3 Marco R. 2020-04-23 18:58:36 CEST
Will do, thanks for your reply.
Comment 4 Marco R. 2020-04-24 00:44:54 CEST
On a second round of testing this scenario, I created a new user in my Xubuntu Bionic machine.

- For the Default Xubuntu Session, the xfce4-notifyd plugin gets added to the panel with notification log disabled.
- For the default xfce session, the user gets asked if they want a simple panel or an empty panel, both come without xfce4-notifyd. Once the user adds the xfce4-notifyd to their panel, the file ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml gets created with the non-logging defaults.

On further research i found that this defaults are set in `xfce4-notifyd/xfce4-notifyd/xfce-notify-daemon.c` when you add the xfce4-notifyd plugin to the panel:
- xndaemon->notification_log = xfconf_channel_get_bool(xndaemon->settings, "/notification-log", FALSE);
- xndaemon->log_level_apps = xfconf_channel_get_uint(xndaemon->settings, "/log-level-apps", 0); //0 All,  1 All except blocked, 2 Only blocked

From my perspective as a user i think that notification-log/TRUE and log-level-apps/0 are better defaults because it means i will no lose my notifications if i'm not paying attention.

Would be great if i can hear from a ux collaborator point of view.
Comment 5 Marco R. 2020-04-24 00:49:22 CEST
reply to Marco R. from comment #4)
> (...)
> On further research i found that this defaults are set in
> `xfce4-notifyd/xfce4-notifyd/xfce-notify-daemon.c` when you add the
> xfce4-notifyd plugin to the panel:
> - xndaemon->notification_log = xfconf_channel_get_bool(xndaemon->settings,
> "/notification-log", FALSE);
> - xndaemon->log_level_apps = xfconf_channel_get_uint(xndaemon->settings,
> "/log-level-apps", 0); //0 All,  1 All except blocked, 2 Only blocked
> (...)

PS: Also
- xndaemon->log_level = xfconf_channel_get_uint(xndaemon->settings, "/log-level", 0); // 0 Only during "do not disturb", 1 Always

Bug #16749

Reported by:
Marco R.
Reported on: 2020-04-23
Last modified on: 2020-04-24

People

Assignee:
Simon Steinbeiss
CC List:
0 users

Version

Version:
unspecified

Attachments

Additional information