gnome-screensaver wirdness
Dmitry Morozovsky
on a couple of my workstations, after portupgrading, I've found that
gnome-screensaver after activating renders X unusable, as it shows desktop with
password dialog box for fraction of second, then blanks it back. Killing
gnome-xscreensaver from other console helps, but it does not seem for me to be
a solution.
previously, I found it would be glitches with hald/dbus, and step-by-step
shutdown of these services and then starting them helped, but now it's not the
case: even reboot does not fix this.
Any hints? Thanks!
--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***
------------------------------------------------------------------------
Robert Noland
> Dear colleagues,
>
> on a couple of my workstations, after portupgrading, I've found that
> gnome-screensaver after activating renders X unusable, as it shows desktop with
> password dialog box for fraction of second, then blanks it back. Killing
> gnome-xscreensaver from other console helps, but it does not seem for me to be
> a solution.
>
> previously, I found it would be glitches with hald/dbus, and step-by-step
> shutdown of these services and then starting them helped, but now it's not the
> case: even reboot does not fix this.
>
> Any hints? Thanks!
I see this periodically when doing port updates. I think that it has to
do with re-installing either gnome-screensaver or consolekit. A reboot
has always solved it for me.
robert.
--
Robert Noland <rno...@FreeBSD.org>
FreeBSD
Joe Marcus Clarke
Actually, it's gdm. Every time gdm gets updated, you need to logout of
GNOME, restart gdm, then log back in.
Joe
--
PGP Key : http://www.marcuscom.com/pgp.asc
Dmitry Morozovsky
JMC> > > on a couple of my workstations, after portupgrading, I've found that
JMC> > > gnome-screensaver after activating renders X unusable, as it shows desktop with
JMC> > > password dialog box for fraction of second, then blanks it back. Killing
JMC> > > gnome-xscreensaver from other console helps, but it does not seem for me to be
JMC> > > a solution.
JMC> > >
JMC> > > previously, I found it would be glitches with hald/dbus, and step-by-step
JMC> > > shutdown of these services and then starting them helped, but now it's not the
JMC> > > case: even reboot does not fix this.
JMC> > >
JMC> > > Any hints? Thanks!
JMC> >
JMC> > I see this periodically when doing port updates. I think that it has to
JMC> > do with re-installing either gnome-screensaver or consolekit. A reboot
JMC> > has always solved it for me.
JMC>
JMC> Actually, it's gdm. Every time gdm gets updated, you need to logout of
JMC> GNOME, restart gdm, then log back in.
Well, this scheme helped all the times before, but now it at least seems it
does not. I'll try to test it again after returning home and report back the
results.
Stephen Montgomery-Smith
> On Tue, 9 Jun 2009, Joe Marcus Clarke wrote:
>
> JMC> > > on a couple of my workstations, after portupgrading, I've found that
> JMC> > > gnome-screensaver after activating renders X unusable, as it shows desktop with
> JMC> > > password dialog box for fraction of second, then blanks it back. Killing
> JMC> > > gnome-xscreensaver from other console helps, but it does not seem for me to be
> JMC> > > a solution.
> JMC> > >
> JMC> > > previously, I found it would be glitches with hald/dbus, and step-by-step
> JMC> > > shutdown of these services and then starting them helped, but now it's not the
> JMC> > > case: even reboot does not fix this.
> JMC> > >
> JMC> > > Any hints? Thanks!
> JMC> >
> JMC> > I see this periodically when doing port updates. I think that it has to
> JMC> > do with re-installing either gnome-screensaver or consolekit. A reboot
> JMC> > has always solved it for me.
> JMC>
> JMC> Actually, it's gdm. Every time gdm gets updated, you need to logout of
> JMC> GNOME, restart gdm, then log back in.
>
> Well, this scheme helped all the times before, but now it at least seems it
> does not. I'll try to test it again after returning home and report back the
> results.
>
> Thanks!
I thought I would chime in with a "me too." I updated ports yesterday,
then rebooted the machine. I only observed this when the screen saver
is password locked.
Iván Zaera Avellón
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�n Zaera Avell�n <iza...@gmail.com>
Date: Tue, Jun 9, 2009 at 5:33 PM
Subject: Re: gnome-screensaver wirdness
To: Dmitry Morozovsky <ma...@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
Dmitry Morozovsky
IZA> I sent this mail to Dmitry yesterday but got no confirmation from him,
IZA> so I'm sending it again to the list. I have googled a bit and some
IZA> Linux distro have also this problem (at least Kubuntu, Debian and
IZA> OpenSUSE that I know).
IZA>
IZA> Can anybody experiencing the problem try to change the screensaver to
IZA> a non-OpenGL and try again. Also I remember that, although the lock
IZA> dialog didn't appear, I could type my password and unlock the screen.
Well, for me it does not: my screensaver is "blank screen"
Dmitry Morozovsky
DM> JMC> > > on a couple of my workstations, after portupgrading, I've found that
DM> JMC> > > gnome-screensaver after activating renders X unusable, as it shows desktop with
DM> JMC> > > password dialog box for fraction of second, then blanks it back. Killing
DM> JMC> > > gnome-xscreensaver from other console helps, but it does not seem for me to be
DM> JMC> > > a solution.
DM> JMC> > >
DM> JMC> > > previously, I found it would be glitches with hald/dbus, and step-by-step
DM> JMC> > > shutdown of these services and then starting them helped, but now it's not the
DM> JMC> > > case: even reboot does not fix this.
DM> JMC> > >
DM> JMC> > > Any hints? Thanks!
DM> JMC> >
DM> JMC> > I see this periodically when doing port updates. I think that it has to
DM> JMC> > do with re-installing either gnome-screensaver or consolekit. A reboot
DM> JMC> > has always solved it for me.
DM> JMC>
DM> JMC> Actually, it's gdm. Every time gdm gets updated, you need to logout of
DM> JMC> GNOME, restart gdm, then log back in.
DM>
DM> Well, this scheme helped all the times before, but now it at least seems it
DM> does not. I'll try to test it again after returning home and report back the
DM> results.
Well, for two contemporary RELENG_7/i386 machines I confirm than ewen after
portupgrade -f gdm gnome-screensaver consolekit
and subsequent reboot, activating screensaver leads to the effect described
earlier.
Both machines use VESA X driver, if it's important.