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

qubes-gui-daemon 4.1.22 breaks seamless mode in Windows 7 qubes #7643

Closed
GWeck opened this issue Jul 22, 2022 · 10 comments · Fixed by QubesOS/qubes-gui-daemon#110
Closed

qubes-gui-daemon 4.1.22 breaks seamless mode in Windows 7 qubes #7643

GWeck opened this issue Jul 22, 2022 · 10 comments · Fixed by QubesOS/qubes-gui-daemon#110
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: gui-virtualization C: windows-vm 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. r4.1-bookworm-stable r4.1-bullseye-stable r4.1-buster-stable r4.1-centos-stream8-stable r4.1-dom0-stable r4.1-fc34-stable r4.1-fc35-stable r4.1-fc36-stable

Comments

@GWeck
Copy link

GWeck commented Jul 22, 2022

Qubes OS release

R4.1.1

Brief summary

If dom0 is updated from the current-testing repository, qubes-gui-daemon is upgraded from version 4.1.21 to version 4.1.22. After this, any window of a Windows 7 VM running in seamless mode is empty.

Steps to reproduce

Update dom0 from the current-testing repository and observe that the version of qubes-gui-daemon has changed. Then start some application in a Windows 7 VM running QWT 4.1.68.

Expected behavior

The window of this application should show its content as it did before.

Actual behavior

The window just shows the border created by Qubes and is empty.

Additional context

Downgrading qubes-gui-daemon to its previous version via sudo qubes-dom0-update --action=downgrade qubes-gui-daemon restores the previous correct behavior.

Is there a way to stop the update of just this one component, even if the current-testing repository for dom0 is activated?

@GWeck GWeck added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug labels Jul 22, 2022
@marmarek
Copy link
Member

Can you enable debugging for this VM ("debug" property) and share /var/log/qubes/guid.<vmname>.log?

@DemiMarie
Copy link

This is almost certainly due to QubesOS/qubes-gui-daemon@b3bd97c.

@GWeck
Copy link
Author

GWeck commented Jul 22, 2022

@marmarek As far as I can see it, that log is empty.

Hopefully, the issue is solved now. It went in the direction that @DemiMarie described, which I suspected, too.

Thanks a lot for your quick and competent help !!!

@andrewdavidwong andrewdavidwong added C: gui-virtualization C: windows-vm diagnosed Technical diagnosis has been performed (see issue comments). pr submitted A pull request has been submitted for this issue. labels Jul 22, 2022
@andrewdavidwong andrewdavidwong added this to the Release 4.1 updates milestone Jul 22, 2022
@qubesos-bot
Copy link

Automated announcement from builder-github

The package gui-daemon has been pushed to the r4.1 testing repository for the CentOS centos-stream8 template.
To test this update, please install it with the following command:

sudo yum update --enablerepo=qubes-vm-r4.1-current-testing

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-gui-daemon_4.1.23-1 has been pushed to the r4.1 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 buster-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
Copy link

Automated announcement from builder-github

The component gui-daemon (including package qubes-audio-daemon-4.1.23-1.fc32) has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@GWeck
Copy link
Author

GWeck commented Jul 26, 2022

Hi - I checked the new version. Everything o.k. Thanks again!

@qubesos-bot
Copy link

Automated announcement from builder-github

The package gui-daemon has been pushed to the r4.1 stable repository for the CentOS centos-stream8 template.
To install this update, please use the standard update command:

sudo yum update

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The package qubes-gui-daemon_4.1.23-1+deb10u1 has been pushed to the r4.1 stable repository for the Debian template.
To install this update, please use the standard update command:

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

Changes included in this update

@qubesos-bot
Copy link

Automated announcement from builder-github

The component gui-daemon (including package qubes-audio-daemon-4.1.23-1.fc32) has been pushed to the r4.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@andrewdavidwong andrewdavidwong added the affects-4.1 This issue affects Qubes OS 4.1. label Aug 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. C: gui-virtualization C: windows-vm 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. r4.1-bookworm-stable r4.1-bullseye-stable r4.1-buster-stable r4.1-centos-stream8-stable r4.1-dom0-stable r4.1-fc34-stable r4.1-fc35-stable r4.1-fc36-stable
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants