qubes-issues icon indicating copy to clipboard operation
qubes-issues copied to clipboard

Dom0 notifications are missing

Open scallyob opened this issue 2 years ago • 7 comments

How to file a helpful issue

Qubes OS release

Qubes 4.2-rc4 (upgrading from 4.1), continues to be a problem after rc5

Brief summary

no notifications from dom0, notifications from other Qubes/VMs work fine

Steps to reproduce

upgrade from 4.1 to 4.2-rc4 and then do things that used to trigger a notification like copying to global clipboard or launching a Qube

Expected behavior

notification shows

Actual behavior

no notifications

If I try to force a notification with notify-send "test" I get error:

 GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

Fixed by creating: /usr/share/dbus-1/services/org.freedesktop.Notifications.service

[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/lib64/xfce4/notifyd/xfce4-notifyd

for more info see: https://forum.qubes-os.org/t/no-notifications-in-qubes-os-4-2/22707/5

scallyob avatar Dec 12 '23 19:12 scallyob

Also happens for a fresh install not only for an upgrade form 4.1 to 4.2.

neoniobium avatar Dec 24 '23 08:12 neoniobium

I can confirm this for the final 4.2 release.

Also, no Qubes OS package requires dbus-x11, which contains dbus-launch and is therefore required to send notifications as root user, but may not be installed. That's another packaging issue imho.

3hhh avatar Dec 31 '23 10:12 3hhh

Fresh install of Qubes OS 4.2.4 I have the same problem still. And same fix worked again.

[using i3wm]

scallyob avatar Apr 07 '25 18:04 scallyob

i am surprised that T:bug was removed from that issue and that this hasn´t been fixed in the first place in the last year, the fix seems easy enough?

or were dom0 notifications disabled on purpose?

h01ger avatar Jun 16 '25 07:06 h01ger

oh, and yes, I also switched to i3, and thinking about it, yes, after installing 4.2 notifications were working.

h01ger avatar Jun 16 '25 07:06 h01ger

Just creating /usr/share/dbus-1/services/org.freedesktop.Notifications.service as described did not fix the issue for me?

h01ger avatar Jun 16 '25 08:06 h01ger

@h01ger:

i am surprised that T:bug was removed from that issue [...]

GitHub introduced a Type field for issues, so it was no longer necessary to have T: labels to represent issue types. Therefore, T: bug was removed from all issues and replaced with the issue type Bug. The replacement may not be obvious because GitHub shows the removal of T: bug on the issue's timeline without showing the addition of the type Bug on the timeline, but you can see it in the Type field on this issue, which is located in the side bar on the right if looking at GitHub on a desktop browser. This was purely an administrative change and has nothing to do with the content of this or any other issue. The same replacement was done with the T: enhancement and T: task labels and their respective issue types (see commit https://github.com/QubesOS/qubes-doc/commit/e1bc45f146c571df58b338f0188c201fa64817f4).

andrewdavidwong avatar Jun 16 '25 20:06 andrewdavidwong

It looks like dunst is one of recommended notification daemons for i3. Just installing the package seems to be enough to get notifications working, it includes relevant systemd/dbus configuration.

marmarek avatar Jun 27 '25 12:06 marmarek

thank you! I can confirm that installing dunst in dom0 brings back notifications with i3!

-- cheers, Holger

⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄

Dance like no one's watching. Encrypt like everyone is.

h01ger avatar Jun 27 '25 12:06 h01ger

Automated announcement from builder-github

The package desktop-linux-i3-settings-qubes has been pushed to the r4.3 testing repository for the Debian template. To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing bookworm-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

qubesos-bot avatar Jun 28 '25 00:06 qubesos-bot

Automated announcement from builder-github

The component desktop-linux-i3-settings-qubes (including package desktop-linux-i3-settings-qubes) has been pushed to the r4.3 testing repository for the Fedora template. To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing

Changes included in this update

qubesos-bot avatar Jun 28 '25 00:06 qubesos-bot

Automated announcement from builder-github

The package desktop-linux-i3-settings-qubes has been pushed to the r4.3 testing repository for the Debian template. To test this update, first enable the testing repository in /etc/apt/sources.list.d/qubes-*.list by uncommenting the line containing trixie-testing (or appropriate equivalent for your template version), then use the standard update command:

sudo apt-get update && sudo apt-get dist-upgrade

Changes included in this update

qubesos-bot avatar Jun 28 '25 00:06 qubesos-bot

Automated announcement from builder-github

The component desktop-linux-i3-settings-qubes (including package desktop-linux-i3-settings-qubes) has been pushed to the r4.3 testing repository for the Fedora template. To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing

Changes included in this update

qubesos-bot avatar Jun 28 '25 00:06 qubesos-bot

Automated announcement from builder-github

The component desktop-linux-i3-settings-qubes (including package desktop-linux-i3-settings-qubes) has been pushed to the r4.3 testing repository for the Fedora template. To test this update, please install it with the following command:

sudo dnf update --enablerepo=qubes-vm-r4.3-current-testing

Changes included in this update

qubesos-bot avatar Jun 28 '25 00:06 qubesos-bot