ben-grande
commented
1 month ago I have encountered this also. I believe the Dom0 package libappindicator-gtk3 is the problem. The package libayatana-appindicator-gtk3 is not available on Fedora 37 but is on Fedora 38 and beyond. But I cannot be certain until there is a new release on Dom0 based on newer Fedora. I am using KDE and notify-send works normally.
The important part of the log below is:
org.kde.knotifications: WaitForName: Service was not registered within timeoutdom0 dbus-daemon[1671947]: [session uid=1000 pid=1671945] Activating service name='org.freedesktop.Notifications' requested by ':1.46' (uid=1000 pid=1686899 comm="python3 -- /usr/share/qubes-video-companion/sender")
dom0 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
dom0 kernel: audit: type=1131 audit(1717076210.324:27842): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dom0 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dom0 audit: BPF prog-id=5156 op=UNLOAD
dom0 audit: BPF prog-id=5155 op=UNLOAD
dom0 kernel: audit: type=1334 audit(1717076210.345:27843): prog-id=5156 op=UNLOAD
dom0 kernel: audit: type=1334 audit(1717076210.345:27844): prog-id=5155 op=UNLOAD
dom0 kernel: audit: type=1334 audit(1717076210.345:27845): prog-id=5154 op=UNLOAD
dom0 audit: BPF prog-id=5154 op=UNLOAD
dom0 qvc.ScreenShare+-disp8849[1686954]: Traceback (most recent call last):
dom0 qvc.ScreenShare+-disp8849[1686954]: File "/usr/share/qubes-video-companion/sender/screenshare.py", line 81, in <module>
dom0 qvc.ScreenShare+-disp8849[1686954]: screenshare = ScreenShare()
dom0 qvc.ScreenShare+-disp8849[1686954]: ^^^^^^^^^^^^^
dom0 qvc.ScreenShare+-disp8849[1686954]: File "/usr/share/qubes-video-companion/sender/screenshare.py", line 24, in __init__
dom0 qvc.ScreenShare+-disp8849[1686954]: self.main(self)
dom0 qvc.ScreenShare+-disp8849[1686954]: File "/usr/share/qubes-video-companion/sender/service.py", line 154, in main
dom0 qvc.ScreenShare+-disp8849[1686954]: self.start_service(target_domain, remote_domain)
dom0 qvc.ScreenShare+-disp8849[1686954]: File "/usr/share/qubes-video-companion/sender/service.py", line 51, in start_service
dom0 qvc.ScreenShare+-disp8849[1686954]: Notify.Notification.new(app, msg, icon).show()
dom0 qvc.ScreenShare+-disp8849[1686954]: gi.repository.GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached (24)
dom0 plasma_waitforname[1686959]: org.kde.knotifications: WaitForName: Service was not registered within timeout
dom0 dbus-daemon[1671947]: [session uid=1000 pid=1671945] Activated service 'org.freedesktop.Notifications' failed: Process org.freedesktop.Notifications exited with status 1
How to file a helpful issue
Qubes OS release
R4.2
Brief summary
If I try to screenshare with fc37 dom0 as the sender, I get error messages and it won't work.
Steps to reproduce
qubes-video-companion screenshareand select dom0 as the sender.Expected behavior
It works.
Actual behavior
In dom0 journal:
Commenting out
Notify.Notification.new(app, msg, icon).show()fixed this for me. But this probably shouldn't be a solution so this still needs diagnosis.See https://forum.qubes-os.org/t/qubes-video-companion-unable-to-share-dom0s-screen/20607 .