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

Sometimes (about once a day) windows 7 HVM with seamless GUI disabled can loose control of application windows #2590

Open
tonsimple opened this Issue Jan 17, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@tonsimple

tonsimple commented Jan 17, 2017

Qubes OS version (e.g., R3.2):

3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

Windows 7 HVM with Qubes Tools installed and seamless GUI disabled


Expected behavior:

Application windows are clickable and interactive

Actual behavior:

After several hours of work, application windows (word, excel, photoshop, etc) become non-interactive

"windows interface windows" (start menu, shutdown button) are not affected.

The affected windows programs can be minimized, resized, closed by clicking on the control panel and choosing closed, but items inside window proper (word text and interface, excel cells, etc.) are off limits.

Steps to reproduce the behavior:

Tricky.
Basically, work with word, photoshop, excel, etc. for some time, and with some probability it will happen.

General notes:

No workaround this time, except restart the VM :(

EDITED TO ADD:
Also happens if Seamless GUI is on sometimes (in this case, control is lost completely of all "seamlessed" windows.
Switching between seamless and non-seamless remains possible but does not in any way alleviate the issue


Related issues:

@tonsimple tonsimple changed the title from Sometimes (about once a day) windows 7 HVM with seamless GUI disabled can lose control of application windows to Sometimes (about once a day) windows 7 HVM with seamless GUI disabled can loose control of application windows Jan 17, 2017

@andrewdavidwong andrewdavidwong added this to the Release 3.2 updates milestone Jan 18, 2017

@tonsimple

This comment has been minimized.

Show comment
Hide comment
@tonsimple

tonsimple Jan 21, 2017

Issue also happens in seamless gui mode, happened to me right now in fact...

(switching from seamless to non-seamless and vice versa does not fix anything, issue persists, restart of windows VM is only known "cure")

Issue also happens in seamless gui mode, happened to me right now in fact...

(switching from seamless to non-seamless and vice versa does not fix anything, issue persists, restart of windows VM is only known "cure")

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 21, 2017

Member

Just to make sure: in non-seamless mode some interface parts are working but not application windows?

Member

marmarek commented Jan 21, 2017

Just to make sure: in non-seamless mode some interface parts are working but not application windows?

@tonsimple

This comment has been minimized.

Show comment
Hide comment
@tonsimple

tonsimple Jan 31, 2017

@marmarek
Yes, exactly.
Start button is usually unaffected (which allows for a relatively graceful shutdown)
Certain elements of application window remain "workable" too (for instance, you could close an excel window using the close window button, or minimize it, but you could not select a cell in a spreadsheet, or open any of the excel's own menus)

tonsimple commented Jan 31, 2017

@marmarek
Yes, exactly.
Start button is usually unaffected (which allows for a relatively graceful shutdown)
Certain elements of application window remain "workable" too (for instance, you could close an excel window using the close window button, or minimize it, but you could not select a cell in a spreadsheet, or open any of the excel's own menus)

@vercas

This comment has been minimized.

Show comment
Hide comment
@vercas

vercas May 29, 2017

When this happens, exactly one window (could even be the taskbar) remains useable with the mouse.
Keyboard input works fine.

Sometimes, it happens a few seconds after the VM starts. Other times, a few minutes.

vercas commented May 29, 2017

When this happens, exactly one window (could even be the taskbar) remains useable with the mouse.
Keyboard input works fine.

Sometimes, it happens a few seconds after the VM starts. Other times, a few minutes.

@jaseg

This comment has been minimized.

Show comment
Hide comment
@jaseg

jaseg Jul 1, 2017

I do currently have a Windows 7 vm that is pretty consistently showing this issue mere minutes after boot on my system. Please tell me if there is anything I can do to debug this.

This behavior reminds me of #1599 .

jaseg commented Jul 1, 2017

I do currently have a Windows 7 vm that is pretty consistently showing this issue mere minutes after boot on my system. Please tell me if there is anything I can do to debug this.

This behavior reminds me of #1599 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment