Reading the posts above, is there now a working patch for this? If so,
will an updated package be available via the repositories any time soon?
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Has any progress been made on this?
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Agreed, I think a regression would be in order due to the security
implications related to this. I currently have to start the screensaver
manually and then use xset from my Mac to shutdown the displays
remotely.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You
Mine is still random. Sometimes it works, sometimes it doesn't. Still
view this as a security vulnerability.
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
I ran some updates including the proposed repositories and thus far, it
seems like the issue has corrected itself ... I'm not going to call it
just yet, although so far the screensaver has started when it should and
the displays have shutdown when they should. I will continue to monitor
for a few
Well, strike that previous post ... problem is back ... :(
--
gnome-screensaver not functioning
https://bugs.launchpad.net/bugs/411350
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Is there a way to add an option in gdm.conf to tell gdm which display is
the primary (that it should appear on)?
--
gdm 2.26 appears on wrong monitor
https://bugs.launchpad.net/bugs/395314
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I've discovered upon a fresh reboot, if you do not touch gconf at all
and let the system idle. The first instance of the screen saver/power
manager appears to work. Over the course of time, the randomness comes
back and is ultimately followed by nothing working at all. Could we be
looking at a
Due to the security issues involved, is it possible to issue a
regression back down to the known working packages from Jaunty until
this can be resolved? As of now, I have to SSH to all affected Karmic
boxes from my iBook and forcibly shut down the displays. If this is not
possible, could
I am also having this issue and as stated above, view this as a security
issue as I also require the display to auto lock itself in a timely
manner while I am away from my machines. I opened a bug on this myself
yesterday, however I stumbled across this already on going one.
Therefore, I have
*** This bug is a duplicate of bug 411350 ***
https://bugs.launchpad.net/bugs/411350
See bug #411350.
** This bug has been marked a duplicate of bug 411350
gnome-screensaver not functioning
** Package changed: ubuntu = gnome-power-manager (Ubuntu)
** Changed in: gnome-power-manager
Also note, I have the random issue. And by that I mean sometimes
nothing works right, sometimes the screen saver works but not the power
manager, and seldom do both work as they should. Also, a litte output
of my settings per gconf...
Power Manager General Options (Defaults)
Just installed Xvnc4 on hardy (64-bit) and am having this issue as well.
I've even went as far as disabling all plugins in
/apps/gnome_settings_daemon/plugins/ with the result still the same.
I've done a lot of research and it seems this bug is plaguing a lot of
people. Does anyone know if there
13 matches
Mail list logo
