sys-gui-gpu Failed to execute qubes.WindowUpdater in dom0

Kenny606 commented 2 years ago

Qubes OS release

Qubes 4.1 , Xen 4.14.4 , Kernel 5.10.104.fc32 qubes x86_x64 dom0, Fedora-34 and Fedora-34-xfce templates up to date.

Brief summary

Whenever a vm’s starts or shuts down I see an error notification: “Failed to execute qubes.WindowUpdater (from somevm-xx to dom0)”

Steps to reproduce

Simply perform any action that results in a VM starting or shutting down, each action will product the error.

Expected behavior

VM's do start and shutdown so expected behavior the qubes.WindowsUpdater to execute I guess.

Actual behavior

The mentioned error notification appears during every startup or shutdown while in the GUI domain.

DemiMarie commented 2 years ago

WindowUpdater should be directed to the GUIVM, not dom0. This is either a GUI agent issue or a qrexec policy issue.

Kenny606 commented 2 years ago

WindowUpdater should be directed to the GUIVM, not dom0. This is either a GUI agent issue or a qrexec policy issue.

If this helps

default_guivm = sys-gui-gpu
default_audiovm = sys-gui-gpu
sys-gui-gpu guivm = "" (all other vm's use default setting)
sys-gui-gpu audiovm = dom0 as specified in another issue, a resolution which worked (all other vm's use default setting)

If there are any log files I can provide that would help let me know.

Thanks everyone for your hard work on this project. I'm still pretty early breaking in Qubes but I love the idea and design :)

-Kenny

marmarek commented 2 years ago

The call should be redirected via policy here: https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/blob/master/qvm/template-gui.jinja#L26

Can you verify if you have this line in the policy? I assume you meant qubes.WindowIconUpdater service. If that's really qubes.WindowUpdater, then the service name is wrong somewhere (but I don't see from where it would come).

There should be icon-receiver process running in sys-gui-gpu. Do you have it? It's started from /etc/xdg/autostart/qubes-icon-receiver.desktop`.

Kenny606 commented 2 years ago

Your correct it was qubes.WindowIconUpdater, sorry.

Confirmed icon sender and receiver files exist in sys-gui-gpu. Both contain just one line Waitforsession=1 I believe it was.

I also verified in dom0 all policies from line 15 to 48 including qubes.WindowIconUpdater exist and match in /etc/qubes/policy.d/50-gui-sys-gui-gpu.policy

Geblaat commented 2 years ago

The call should be redirected via policy here: https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/blob/master/qvm/template-gui.jinja#L26

Can you verify if you have this line in the policy? I assume you meant qubes.WindowIconUpdater service. If that's really qubes.WindowUpdater, then the service name is wrong somewhere (but I don't see from where it would come).

There should be icon-receiver process running in sys-gui-gpu. Do you have it? It's started from /etc/xdg/autostart/qubes-icon-receiver.desktop`.

I have the same issue with qubes.WindowIconUpdater in hybrid sys-gui. qubes.WindowIconUpdater * @tag:guivm-{{ vmname }} dom0 allow target={{ vmname }} does exist in the policy file. There is an icon-receiver file in /etc/xdg/autostart/qubes-icon-receiver.desktop, but when using ps -e to show running processes, I only see icon-sender running, not icon-receiver.

ClaraCrazy commented 2 years ago

having the exact same issue as @Geblaat . Anyone got a solution for this?

Kenny606 commented 2 years ago

Your correct it was qubes.WindowIconUpdater, sorry.

Confirmed icon sender and receiver files exist in sys-gui-gpu. Both contain just one line Waitforsession=1 I believe it was.

I also verified in dom0 all policies from line 15 to 48 including qubes.WindowIconUpdater exist and match in /etc/qubes/policy.d/50-gui-sys-gui-gpu.policy

From: Marek Marczykowski-Górecki @.***> Sent: Tuesday, April 19, 2022 8:02 PM To: QubesOS/qubes-issues Cc: Author Subject: Re: [QubesOS/qubes-issues] sys-gui-gpu Failed to execute qubes.WindowUpdater in dom0 (Issue #7454)

This Message originated outside your organization.

The call should be redirected via policy here: https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/blob/master/qvm/template-gui.jinja#L26 https://github.com/QubesOS/qubes-mgmt-salt-dom0-virtual-machines/blob/master/qvm/template-gui.jinja#L26

Can you verify if you have this line in the policy? I assume you meant qubes.WindowIconUpdater service. If that's really qubes.WindowUpdater, then the service name is wrong somewhere (but I don't see from where it would come).

There should be icon-receiver process running in sys-gui-gpu. Do you have it? It's started from /etc/xdg/autostart/qubes-icon-receiver.desktop`.

— Reply to this email directly, view it on GitHubhttps://github.com/QubesOS/qubes-issues/issues/7454#issuecomment-1103317790, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARQU2LQRHAFNMU4Z56YLLPDVF5JQRANCNFSM5TUXWZIA. You are receiving this because you authored the thread.Message ID: @.***>

Disclaimer: The information in the Email and/or attachment(s) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521. It may be confidential and/or privileged and is intended solely for the person or entity to which it is addressed. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you have received it in error. The review, dissemination, copying, or taking of any action based on the contents thereof is strictly prohibited. If you have received this Email in error, please advise the sender by reply Email and then delete it and any attachment(s) from your system immediately. Thank you.

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

ZYousef commented 8 months ago

I'm using sys-gui-gpu - Qubes OS R4.2 - with icon-sender running in GuiVM, however whenever a new domain runs their icon-sender I see the following error few time then it exists

icon-sender: running: ['qrexec-client-vm', 'dom0', 'qubes.WindowIconUpdater ']
icon-sender: process exited too soon, waiting 5 seconds and retrying 
icon-sender: disconnecting from X

I can confirm that dom0 redirect qubes.WindowIconUpdater calls to GuiVM and icon-receiver.sock exists

QubesOS / qubes-issues