Notify-send hangs in newer templates

[tasket]

Qubes OS version
R4.0
Affected component(s) or functionality
fedora-30
debian-10

Brief summary
The notify-send command hangs for nearly a minute without displaying a message.

To Reproduce
In a domU shell, run notify-send HELLO

Expected behavior
Message is displayed in a popup window and command returns in a short period of time.

Actual behavior
There is a 50sec delay and no message display.

Additional context
Log from debian-10:

Jun 02 14:20:28 personal-net dbus-daemon[896]: [session uid=1000 pid=896] Activating service name='org.freedesktop.Notifications' requested by ':1.25' (uid=1000 pid=2114 comm="notify-send HI ")
Jun 02 14:21:28 personal-net org.freedesktop.Notifications[896]: org.kde.knotifications: WaitForName: Service was not registered within timeout
Jun 02 14:21:28 personal-net dbus-daemon[896]: [session uid=1000 pid=896] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1

Related issues
VPN startup suffering 1min 40sec delay:
tasket/Qubes-vpn-support#40

[tasket]

I tried installing mate-notification-daemon as suggested in issue #4098 but it didn't help.

[marmarek]

I've seen this before, which was the reason for QubesOS/qubes-app-linux-split-gpg@42ac505. But your report proves it isn't isolated issue for that particular installation. The error message is exactly the same.

[marmarek]

Can you give some more details how to reproduce it? I've tried both fedora-30 (and -minimal) and debian-10 and it works for me there... Some specific package installed? Or maybe removed?

[tasket]

I thought it always occurred, but now I see that in my unmodified fedora-30 template, I must have Qubes-vpn-support configured to run in order to trigger it.

If I comment-out the notify-send lines in qubes-vpn-ns and qubes-vpn-setup and restart the vm, the vpn client will start normally and I can use notify-send from the cli with no hanging. So running notify-send during startup from my service scripts is triggering the problem on fedora-30.

The debian-10 template is upgraded from 9 and heavily modified, with the most significant change being Gnome replaced with KDE. Here the notify-send command will hang even with all extra Qubes services disabled, and regardless of vm class. Its possible that something else is trying to use notify-send or something similar during startup. Perhaps later I'll try installing the pre-release debian-10 template.

[tasket]

Here is a log from fedora-30:

Jun 04 17:59:41 VPN2 systemd[571]: Starting D-Bus User Message Bus...
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Service file '/usr/share/dbus-1/services/org.freedesktop.mate.Notifications.service' is n
ot named after the D-Bus name 'org.freedesktop.Notifications'.
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.UserPrompter.serv
ice' is not named after the D-Bus name 'org.gnome.evolution.dataserver.UserPrompter0'.
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.AddressBook.servi
ce' is not named after the D-Bus name 'org.gnome.evolution.dataserver.AddressBook9'.
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Calendar.service'
 is not named after the D-Bus name 'org.gnome.evolution.dataserver.Calendar7'.
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Sources.service' 
is not named after the D-Bus name 'org.gnome.evolution.dataserver.Sources5'.
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is dep
recated and ignored
Jun 04 17:59:41 VPN2 dbus-broker-launch[772]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is dep
recated and ignored
Jun 04 17:59:41 VPN2 systemd[571]: Started D-Bus User Message Bus.
Jun 04 17:59:41 VPN2 dbus-broker-lau[772]: Ready
Jun 04 17:59:41 VPN2 systemd[571]: Created slice dbus\x2d:1.2\x2dorg.freedesktop.Notifications.slice.
Jun 04 17:59:41 VPN2 systemd[571]: Started dbus-:1.2-org.freedesktop.Notifications@0.service.
Jun 04 17:59:41 VPN2 mate-notification-daemon[784]: Unable to init server: Could not connect: Connection refused
Jun 04 17:59:41 VPN2 mate-notificati[784]: cannot open display: 
Jun 04 17:59:41 VPN2 systemd[571]: dbus-:1.2-org.freedesktop.Notifications@0.service: Succeeded.
Jun 04 17:59:42 VPN2 qubes-gui[424]: Ok, somebody connected.
Jun 04 17:59:42 VPN2 qubes-gui[424]: Connection to local X server established.

Notice the X server starts after the 'notifications' messages. When this happens, notify-send cannot be used for a very long time (if it works at all).

[tasket]

FYI, a debian-9-to-10 template I upgraded without KDE has no notify-send hanging problem.

[tasket]

A recent Fedora 30 update appears to have fixed the issue.

[fepitre]

I'm still having the issue with updated Fedora 30. Any try of 'notify-send' is hanging.

[marmarek]

Do you see similar messages in journalctl?