Opened 8 years ago
Closed 7 years ago
#16469 closed defect (fixed)
Unresponsive after sleep
| Reported by: | Don Hughes | Owned by: | |
|---|---|---|---|
| Component: | host support | Version: | VirtualBox 5.1.14 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
After upgrading to VB 5.1.14 I have had mouse and keyboard problems.
Host: SuSE Leap 64 Bit Default 4.1.36 Kernel Guests: Various
1) If the system is idle long enough for one of the guests to go to sleep, the entire system stops accepting any input. I can not use any of the controls on the VBox Manager, the window manager (openBox), or any of the guest machines - either applications running in the guest, or any of the VBox decorations. The only option is to ssh to the box and kill the VBox threads. On restart, all of the machines that were running are now in an aborted state
2) With the VBox manager running I can no longer use the mouse right-click on an open spot on the desktop to bring up the window manager menu. If I close VBox manager, the mouse right-click again works.
Everything was working in 5.1.12
However, on another server I am only having the 2nd issue. This 2nd machine only ever has 1 guest running at a time and only has a single processor.
Attachments (2)
Change History (9)
by , 8 years ago
| Attachment: | VBoxSVC.log added |
|---|
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Has not reoccurred since reverting to 5.1.12, though it may take another day to be sure.
comment:3 by , 8 years ago
In that case when you return to 5.1.14 please try what I said with (not) keyboard capturing.
comment:4 by , 8 years ago
Happened with 5.1.12.
Happens with no keyboard capturing (5.1.12 or 5.1.14), but with no capturing I get the following message if I click on the X in the upper right of the guest after the guest stops responding:
"Oracle VM Virtual Box does not seem to be responding...."
The kernel and systemctl were upgraded at the same time as VirtualBox. VBox recompiled after kernel change.
by , 8 years ago
comment:5 by , 8 years ago
VB seemed to be capturing all of the mouse clicks (keystrokes?) and not passing them on. I could do nothing with any of the quests, and could not access the window manager. This made the guests appear to be unresponsive. If I terminated VB, I could then access the window manager, but, of course, all of the guests aborted.
This appears to be fixed in 5.1.26.
A couple of questions: does this still happen if you re-install 5.1.12<1>? And if you disable automatic keyboard capturing and make sure that none of the virtual machines have the keyboard captured can you still reproduce this?