After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 700661 - KVM interaction with gnome-screensaver/screen modes (keyboard/video/mouse switch as in)
KVM interaction with gnome-screensaver/screen modes (keyboard/video/mouse swi...
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-19 21:02 UTC by Dave Gilbert
Modified: 2014-08-20 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dave Gilbert 2013-05-19 21:02:41 UTC
(I'm forwarding this bug, don't have the hardware/bug myself to report)

There are >20 people reporting a problem on Ubuntu when using a kvm switch and it losing the correct resolution; the reporters have varying video hardware (Intel, and Nvidia) and they're saying it's only affecting Gnome desktops.
The details are a bit sketchy; the screensaver seems to be common among most of them - see the various reports at:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/988290

They're generally reporting that running 'xrandr' sorts it out (with no parameters).

To quote the original reporter:

  I have a machine that shares monitor, keyboard and mouse with a second
  machine via a standard KVM-Switch (USB/VGA). After updating to precise beta 
  yesterday, I noticed that, after having worked with the other machine for a
  while and switching back to the precise machine, screen resolution has 
  changed to 800x600. Just opening "Monitors" from gnome-system-settings 
  restores the original resolution of 1280x1024, you don't need to change 
  anything.

  This is reproducible, if you switch away from the machine long enough (I 
  guess until the screensaver gets invoked) resolution will be changed when you 
  come back. This was not the case with oneiric.

It was originally assigned as an X bug, which got rejected on the basis that it was the kvm not being nice enough to kick the host (which is my reading),
however the fact it's working with other desktops make me a bit confused.

Perhaps doing an randr probe when the screensaver wakes up would solve the problem?

Dave (just triaging some bugs)
Comment 1 Bastien Nocera 2014-08-20 20:23:11 UTC
The screen lock is now implemented directly in gnome-shell, not in
gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x).

If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected.

If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.