Well, In my case .xsession-errors says:
"xscreensaver-command: no screensaver is running on display :0.0" I think I'm getting this because I'm not running gnome-session (too buggy still for me), just the gnome panel. Since the screen saver is actually run by gnome-session the panel then complains. However, even if I run the control center and enable the screen server it won't start. Why on earth do we need gnome-session running to automatically start the screen server? Go fig! If I run gnome-seesion, locking the screen works well. -- Pedro I. Sanchez David Coe wrote: > > For me, the panel's error messages go to .xsession-errors; they > probably do for you too. > > I have the same problem, and see this when I click 'Lock screen': > > sh: xscreensaver-command: command not found > > I guess that's why it recommends xscreensaver. > > Personally I prefer xtrlock, so I just added a launcher for it > to my panel. Maybe there's also a way to configure what > 'Lock screen' starts. > > "Pedro Sanchez" <[EMAIL PROTECTED]> wrote: > > > > I installed the deb gnome 1.0 files for slink but the "lock screen" > > option in the panel does nothing. Does gnome write errors somewhere?
