[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: GNOME screensaver's abnormal behaviour



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Camaleón <noelamac@gmail.com> writes:

> On Tue, 03 Aug 2010 10:48:34 +0200, Merciadri Luca wrote:
>
>> I have a random GNOME screensaver, a default one, on this computer
>> (debian Lenny w. kernel 2.6.26-2-686-bigmem).
>> 
>> It gets `paused' by pressing Esc, and is `de-paused' by pressing Esc
>> again. Left click does the same effect as pushing Esc, but right click
>> lets me get out of it. I am sometimes unable to get out of it, and I
>> need to restart the X-server, or go to another tty. I'm pretty sure that
>> this behaviour is not normal, and I would like to know what would cause
>> it, and if anybody has ever got the same problems. I looked at the
>> different logs, but found nothing interesting. Most of the time, simply
>> moving the mouse gets me out of the screensaver, but, in other cases,
>> moving the mouse gives nothing, and the situation is the one I describe
>> with Esc and right click.
>
> There are some bugs¹ for "gnome-screensaver". Take a look and check if 
> any of them fits into yours.
>
> OTOH, you can:
>
> 1/ Review your "/var/log/Xorg.0.log" and "~./xsession-errors"
Done. The former gives mainly

SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled

when the latter gives nothing interesting.

> 2/ Try with a fixed screensaver
Done. It majoritarly happens with `Pop art squares.'

> 3/ Try with no screensaver at all, just use display power manager options 
> to dim the screen and render it black.
Sometimes stalls too. (Old memories, though.) :(

> And verify if it's still reproducible.
See above.

> Are you using any power saving (suspend to ram or suspend to disk) 
> settings?
No.

> Are you using VGA proprietary drivers?
Looks so:

==
[...]
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.0
	Module class: X.Org Video Driver
[...]
(II) NVIDIA dlloader X Driver  173.14.09  Wed Jun  4 23:47:25 PDT 2008
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[...]
(--) NVIDIA(0): Connected display device(s) on GeForce 8400 GS at PCI:1:0:0:
(--) NVIDIA(0):     Samsung SyncMaster (CRT-1)
(--) NVIDIA(0):     Samsung SyncMaster (DFP-0)
(--) NVIDIA(0): Samsung SyncMaster (CRT-1): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Dual Link TMDS
(II) NVIDIA(0): Display Devices found referenced in MetaMode: CRT-1, DFP-0
(II) NVIDIA(0): Assigned Display Devices: CRT-1, DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0):    
(II) NVIDIA(0):     "CRT:nvidia-auto-select+1680+0,DFP:nvidia-auto-select+0+0"
(II) NVIDIA(0):     "CRT:1280x1024+0+0,DFP:NULL"
(II) NVIDIA(0):     "CRT:1280x1024+1680+0,DFP:nvidia-auto-select+0+0"
==

But they are mainly used for CUDA capability, aren't they?

>
> ¹
> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=gnome-screensaver;dist=unstable
Checked.
- -- 
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- -- 

Laugh and the world laughs with you ... Cry and you will find no one
  with tears.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAkxYFH8ACgkQM0LLzLt8MhyXCgCgkiirxP4W8uRNMtGVz+Ql1LxG
x9sAn0WTFS+7PB5YOU4SsaUV46DIvMdD
=dKHJ
-----END PGP SIGNATURE-----


Reply to: