closing the bug then, thanks you.
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete => Fix Released
--
When locking manually, theme setting is ignored, random hack starts
https://bugs.launchpad.net/bugs/162910
You received this bug notification because you are a member of Ubunt
I can confirm that the problem is no longer here (as of 8.04.1)
--
When locking manually, theme setting is ignored, random hack starts
https://bugs.launchpad.net/bugs/162910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I *think* that as of hardy, the settings are taking effect immediately
now. I will verify it and report on Aug 8th when I get access to the
system in question.
--
When locking manually, theme setting is ignored, random hack starts
https://bugs.launchpad.net/bugs/162910
You received this bug notif
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.
--
When locking manually, theme setting is ignored, random
Thanks for your report, That works fine here, May you please run the
gnome-screensaver from the command like this: gnome-screensaver --no-
daemon --debug &>gnome-screensaver-debug.txt and attach that log to the
report? thanks!.
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided =>
The previous attachment is for manually running a second instance of
screensaver, which immediately terminates. Here, there is a "real" run,
with activation and deactivation of the screensaver.
Anyway, my report proved to be misleading. Setting the theme in gnome-
screensaver-preferences *does*
** Attachment added: "gnome-screensaver --no-daemon --debug
&>gnome-screensaver-debug.txt"
http://launchpadlibrarian.net/1043/gnome-screensaver-debug.txt
--
When locking manually, theme setting is ignored, random hack starts
https://bugs.launchpad.net/bugs/162910
You received this bug no
