After upgrades last week, gnome-screensaver fails

[Kevin Oberman]

> From: Joe Marcus Clarke <marcus at marcuscom.com>
> Date: Mon, 08 Jun 2009 16:47:37 -0400
> Sender: owner-freebsd-gnome at freebsd.org
> 
> On Mon, 2009-06-08 at 10:08 +0000, knowtree at aloha.com wrote:
> > > > From: Joe Marcus Clarke <marcus at marcuscom.com>
> > > > Date: Mon, 08 Jun 2009 12:23:40 -0400
> > > > 
> > > > On Mon, 2009-06-08 at 08:40 -0700, Kevin Oberman wrote:
> > > > > Since a ports upgrade last week (while on vacation), something broke on
> > > > > multiple systems in the gnome-screensaver. All ports are now current and
> > > > > I have no other problems, but the screensaver keeps locking me out of my
> > > > > system.
> > > > > 
> > > > > The system locks normally, but it just puts up the background pattern
> > > > > and draws the input box to allow the entry of the password. Then it goes
> > > > > back to black (My screensaver is "Blank Screen".) Pressing a key
> > > > > repeats, but it does not accept input, so I can't unlock the display.
> > > > 
> > > > This happens after gdm is upgraded.  You will need to logout, restart
> > > > gdm, then log back in.
> > > 
> > > I don't think so. I don't run gdm. I 'startx'. And, at least one system,
> > > my laptop, has re-booted multiple times since the upgrades.
> > 
> > I have this, and I run gdm and have rebooted several times. To break in,
> > <Ctrl> <Alt> F1, logon as myself, ps -A | grep saver, then kill it. <Ctrl>
> > <Alt> F9 to get back into Gnome. I now have my screen saver turned off.
> 
> Sorry, I can't reproduce.  Everything works just fine for me on RELENG_7
> and -CURRENT.  Check the console or ~/.xsession-errors for any more
> clues.

A couple of added data point. I was going to use ktrace to look at where
things were failing, so I re-started gnome-screensaver. The problem no
longer was there. It runs fine. This makes me suspicious that it may be
related to session initialization and timing which will make it a real
bear to track down.

Oh, and nothing of interest on the console or in ~/.xession-errors. One
system has no .xsession-errors file and the mtime on the other is
10-Nov-2006. Is the file still really used?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751