-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Comments
Can you enable debugging for this VM ("debug" property) and share |
This is almost certainly due to QubesOS/qubes-gui-daemon@b3bd97c. |
@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 !!! |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Hi - I checked the new version. Everything o.k. Thanks again! |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
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 viasudo 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?
The text was updated successfully, but these errors were encountered: