Summary: | x11-misc/xscreensaver-4.23-r1/4.24 - new-login USE flag has no effect | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fab <netbox253> |
Component: | Current packages | Assignee: | Desktop Misc. Team <desktop-misc> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
xscreensaver output emerge --info |
Description
Fab
2006-08-31 07:50:03 UTC
Created attachment 95555 [details]
emerge --info
Forgot to mention that I'm currently running xscreensaver from gnome.
Created attachment 95626 [details]
xscreensaver output
I ran the following commands, output is in the attached file :
$ xscreensaver-command -exit
$ script log.txt
$ xscreensaver -verbose -no-capture &
==> locked screen
==> give password
$ xscreensaver-command -exit
$ exit
Does 5.00 work? (In reply to comment #3) > Does 5.00 work? > Will try as soon as possible (emerge -e system && emerge -e world rules...) Created attachment 96046 [details]
emerge --info
With 5.00-r1 it does not work :(
Attached file : new emerge --info after upgrade to gcc-4.1.
Found following URI : http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=336590 [quote] The problem basically was that '/usr/bin/' is not anymore in the path of xscreensaver... as it is stated in /etc/X11/app-defaults/XScreensaver-nogl, the "new login" button will not appear if the command in 'newLoginCommand' option doesn't exists. The default value for that option is 'gdmflexiserver -l', if you simply change that (in your ~/.xscreensaver) to '/usr/bin/gdmflexiserver -l' then the famous button is back!. [/quote] Will try as soon as possible... (In reply to comment #6) > Will try as soon as possible... Please reopen then. Yes, I know : I didn't forget this bug. I'm currently approximately 1000 kilometers away from this computer, so it's not easy to test the screensaver :-) Normally, I would be there in approximately 1 or 2 month, I'll reopen when I would have more infos, and if the bug doesn't occurs anymore, I'll close it. Thanks. |