Your message dated Wed, 12 May 2010 00:59:07 +0200
with message-id <[email protected]>
and subject line Re: __GL_SYNC_TO_VBLANK=1 & KDE Control center/Screen saver
preview freezes X
has caused the Debian Bug report #285127,
regarding __GL_SYNC_TO_VBLANK=1 & KDE Control center/Screen saver preview
freezes X
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
285127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285127
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nvidia-graphics-drivers
I can reliably trigger the bug by putting "export __GL_SYNC_TO_VBLANK=1" in
~/.bash_profile, logout of the console (runlevel 2), log back in, and startx.
Now that KDE has inherited the environment variable, I can start up its
Control Center, click on Screen Saver, click on one GL screensaver (I
recommend blocktube) so that it's little preview starts up, and click to
another screen saver. X almost entirely freezes, ignoring mouse clicks, key
presses, Ctrl-Alt-Backspace, Ctrl-Alt-F1 (to console); only the magic Sysrq
commands work (such as Sync,Unmount,Boot). I can still move around the mouse
cursor, which is a new X-failure experience for me.
I am running Sarge with kernel-image-2.4.27-1-686-smp, xfree86 4.3.0.dfsg.1-8,
and nvidia driver 1.0-6629. Hardwarewise, my PC is a P4 2.4Ghz with
hyperthreading enabled, an i875pbz motherboard, and an Albatron FX 5700 AGP
video card.
--- End Message ---
--- Begin Message ---
On Friday, 10. December 2004 20:49:23 [email protected] wrote:
...
> I am running Sarge with kernel-image-2.4.27-1-686-smp, xfree86
> 4.3.0.dfsg.1-8, and nvidia driver 1.0-6629. Hardwarewise, my PC is a P4
...
This bug was reported against Debian 3.1 "sarge", the Debian release that
predates oldstable "etch" and is no longer being supported, so I'm closing
this bug now.
If you still experience this problem in the current stable release "lenny" or
in unstable, please open a new bug report.
Andreas
--- End Message ---