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 618932 - gnome-screensaver crashes in KVM
gnome-screensaver crashes in KVM
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: daemon
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-17 20:57 UTC by Chris Coulson
Modified: 2014-08-20 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
xtrace log (72.14 KB, text/x-log)
2010-05-17 20:58 UTC, Chris Coulson
  Details
Output of gnome-screensaver --debug --no-daemon (2.61 KB, text/plain)
2010-05-17 20:58 UTC, Chris Coulson
  Details
/0001-Don-t-crash-when-the-XF86VM-extension-doesn-t-allow-.patch (2.13 KB, patch)
2010-05-17 21:05 UTC, Chris Coulson
none Details | Review

Description Chris Coulson 2010-05-17 20:57:32 UTC
gnome-screensaver crashes with an unhandled X error when trying to lock the screen in KVM. I've attached the xtrace log and output of "gnome-screensaver --debug --no-daemon"

The debug log shows the fade type being set to FADE_TYPE_GAMMA_RAMP in check_gamma_extension, due to the presence of the XF86VM extension. The xtrace log shows XF86VidModeGetGammaRampSize in gamma_fade_setup return a size of zero, at which point the fade type is changed to FADE_TYPE_GAMMA_NUMBER. XF86VidModeGetGamma then successfully returns the current gamma value.

However, when trying to set the gamma in xf86_whack_gamma, XF86VidModeSetGamma causes a BadValue error on the first iteration (as shown in xtrace), even though all the values are sane. This appears to be not handled properly on KVM, and with no way of knowing this beforehand, the error should be trapped correctly.

This behaviour seems to have changed in a recent X server version. Previously, this only worked because XF86VidModeSetGamma completed successfully in KVM, despite not actually changing the gamma value.
Comment 1 Chris Coulson 2010-05-17 20:58:01 UTC
Created attachment 161274 [details]
xtrace log
Comment 2 Chris Coulson 2010-05-17 20:58:26 UTC
Created attachment 161275 [details]
Output of gnome-screensaver --debug --no-daemon
Comment 3 Chris Coulson 2010-05-17 21:05:16 UTC
Created attachment 161276 [details] [review]
/0001-Don-t-crash-when-the-XF86VM-extension-doesn-t-allow-.patch
Comment 4 William Jon McCann 2010-06-21 21:47:29 UTC
Dave, any thoughts on this?
Comment 5 William Jon McCann 2010-06-29 17:35:47 UTC
Chris, can you provide any details about which versions are subject to this?  I'm not able to reproduce right now.  Thanks.
Comment 6 Ritesh Khadgaray ( irc:ritz) 2010-11-02 11:17:06 UTC
Hi @William

  I belive, this bug is specific to ubuntu due to patch from https://bugzilla.gnome.org/show_bug.cgi?id=610294 .
Comment 7 Ritesh Khadgaray ( irc:ritz) 2010-11-02 11:33:08 UTC
Also, in xf86_whack_gamma, add trap to gdk_flush. This should fix the issue, when using vnc based display.
Comment 8 Bastien Nocera 2014-08-20 20:23:25 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.