Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notification issue of qubes-video-companion-dom0 #8457

Closed
Augsch123 opened this issue Aug 28, 2023 · 1 comment · Fixed by QubesOS/qubes-video-companion#23
Closed

Notification issue of qubes-video-companion-dom0 #8457

Augsch123 opened this issue Aug 28, 2023 · 1 comment · Fixed by QubesOS/qubes-video-companion#23
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: other diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@Augsch123
Copy link

Augsch123 commented Aug 28, 2023

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

  1. Install qubes-video-companion in dom0 and a template qube.
  2. From an app qube, try to qubes-video-companion screenshare and select dom0 as the sender.

Expected behavior

It works.

Actual behavior

In dom0 journal:

dom0 qvc.ScreenShare+-disp6823[12773]: Traceback (most recent call last):
dom0 qvc.ScreenShare+-disp6823[12773]:   File "/usr/share/qubes-video-companion/sender/screenshare.py", line 81, in <module>
dom0 qvc.ScreenShare+-disp6823[12773]:     screenshare = ScreenShare()
dom0 qvc.ScreenShare+-disp6823[12773]:                   ^^^^^^^^^^^^^
dom0 qvc.ScreenShare+-disp6823[12773]:   File "/usr/share/qubes-video-companion/sender/screenshare.py", line 24, in __init__
dom0 qvc.ScreenShare+-disp6823[12773]:     self.main(self)
dom0 qvc.ScreenShare+-disp6823[12773]:   File "/usr/share/qubes-video-companion/sender/service.py", line 157, in main
dom0 qvc.ScreenShare+-disp6823[12773]:     self.start_service(target_domain, remote_domain)
dom0 qvc.ScreenShare+-disp6823[12773]:   File "/usr/share/qubes-video-companion/sender/service.py", line 51, in start_service
dom0 qvc.ScreenShare+-disp6823[12773]:     Notify.Notification.new(app, msg, icon).show()
dom0 qvc.ScreenShare+-disp6823[12773]: gi.repository.GLib.GError: g-io-error-quark:  Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached (24)

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 .

@Augsch123 Augsch123 added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Aug 28, 2023
@Augsch123 Augsch123 changed the title Notification issue of qubes-video-companion-sender in dom0 Notification issue of qubes-video-companion-dom0 Aug 28, 2023
@andrewdavidwong andrewdavidwong added C: other needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.2 This issue affects Qubes OS 4.2. labels Aug 28, 2023
@ben-grande
Copy link

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 timeout
dom0 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

ben-grande added a commit to ben-grande/qubes-video-companion that referenced this issue May 30, 2024
Only screenshare script requires as of today, but put it in webcam also
for future proof as it doesn't cause any harm.

Assigning variable and declaration made separate due to ShellCheck
warning SC2155.

For: QubesOS/qubes-issues#6426
Fixes: QubesOS/qubes-issues#8457
Fixes: QubesOS#15
ben-grande added a commit to ben-grande/qubes-video-companion that referenced this issue May 31, 2024
Only screenshare script requires as of today, but put it in webcam also
for future proof as it doesn't cause any harm.

Assigning variable and declaration made separate due to ShellCheck
warning SC2155.

For: QubesOS/qubes-issues#6426
Fixes: QubesOS/qubes-issues#8457
Fixes: QubesOS#15
@andrewdavidwong andrewdavidwong added diagnosed Technical diagnosis has been performed (see issue comments). pr submitted A pull request has been submitted for this issue. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: other diagnosed Technical diagnosis has been performed (see issue comments). P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. pr submitted A pull request has been submitted for this issue. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants