I'm currently seeing this under Ubuntu 14.10.
In my case, however, the issue is somewhat worse than that originally
reported. Regardless of whether the guest image is idle or not, the
keyboard in such guest becomes unreliably unresponsive exactly X minutes
after (re)entering such guest, where:
* Unreliably unresponsive means a seemingly random loss of roughly half of
all keyboard input (as in the original report).
* X is the currently configured inactivity time in the Ubuntu host
(defaulting to 10 minutes), after which the host screen is blanked or a host
screensaver run.
Interestingly, this is correctable in the same manner as that originally
reported. To reiterate, when a guest keyboard becomes unresponsive:
1. Return to the Ubuntu host from the guest VirtualBox image (e.g., by hitting
Right-Ctrl).
2. At such point, Ubuntu immediately performs inactivity handling (e.g., screen
blanking, screensaver running).
3. Stop such blanking or screensaver (e.g., by hitting any key).
4. Return to the guest VirtualBox image from the Ubuntu host (e.g., by clicking
in the VirtualBox window for such guest).
This is may not necessarily be a gnome-screensaver issue. I'm currently
running Cinnamon 2.2 as provided by the canonical (horrible pun
intended) 14.10 Ubuntu repositories. While I do have both cinnamon-
screensaver and gnome-screensaver installed, the prior appears to
currently take precedence.
Intuitively, this feels like a lower-level upstream issue. My
suspicions are that VisualBox is failing to notify the host X11 of the
activity state of guest images *AND* that VisualBox is failing to
preempt guest images on guest inactivity with the host X11 inactivity
handler (e.g., screen blanking, screensaver running).
It may be pertinent to note that the guest in question is OS X 10.6.8
(Snow Leopard). Due to licensing concerns, Oracle has yet to offer a
Guest Additions ISO for OS X VirtualBox guests, thus preventing use of
Seamless Mode under such guests. Seamless Mode displays application
windows running under guests as native windows running under the host,
and is available for all non-OS X guests. Since virtualization of OS X
is non-trivial (to say the least), most VirtualBox users are likely to
run guests under the blatantly superior Seamless Mode.
Does any this matter? Possibly not. My deepest suspicion, however, is
that VirtualBox only fails to notify the host X11 of the activity state
of guest images *NOT* in Seamless Mode – which would, of course, always
be the case for OS X guests and only rarely the case for non-OS X
guests. This could explain the lack of concurring reports for this bug.
(Or this could explain nothing at all.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/490434
Title:
keyboard input less responsive after screensaver fails to activate
because of VirtualBox
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/490434/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
