Date: Wed, 10 Jun 2009 09:18:06 +0200 From: =?ISO-8859-1?Q?Iv=E1n_Zaera_Avell=F3n?= <izaera@gmail.com> To: freebsd-ports@freebsd.org Subject: Fwd: gnome-screensaver wirdness Message-ID: <9719a6f50906100018r13cf4904y274e4f21000e1bbb@mail.gmail.com> In-Reply-To: <9719a6f50906090833p3db55671ra7c66409952dd750@mail.gmail.com> References: <alpine.BSF.2.00.0906090403340.9880@woozle.rinet.ru> <9719a6f50906090833p3db55671ra7c66409952dd750@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi all: I sent this mail to Dmitry yesterday but got no confirmation from him, so I'm sending it again to the list. I have googled a bit and some Linux distro have also this problem (at least Kubuntu, Debian and OpenSUSE that I know). Can anybody experiencing the problem try to change the screensaver to a non-OpenGL and try again. Also I remember that, although the lock dialog didn't appear, I could type my password and unlock the screen. If you confirm this error I'm afraid the problem is in the original code for X11 or OpenGL or the screensavers, in which case it wouldn't be a FreeBSD only problem and would have to be corrected in the upstream code. Regards, Ivan ---------- Forwarded message ---------- From: Iv=E1n Zaera Avell=F3n <izaera@gmail.com> Date: Tue, Jun 9, 2009 at 5:33 PM Subject: Re: gnome-screensaver wirdness To: Dmitry Morozovsky <marck@rinet.ru> Hi Dmitry: I'm new to FreeBSD so I don't know the internals of the system, but I'm changing from Debian/Linux and had the same problem some months ago (to add more differences to your case, I had KDE instead of GNOME). In my case it was an interaction between OpenGL, transparency in the video driver, the screensaver and the desktop lock program. The bypass solution I found was to stop using OpenGL screensaver (apart from killing the screen saver or the desktop lock programs from a text console, as you say). I don't know if this can help you because, as I said, my configuration was totally different from yours, but I just wanted to share my solution because the problems looked similar. Hope it helps, Ivan Zaera
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9719a6f50906100018r13cf4904y274e4f21000e1bbb>