This is still an issue, even if nobody's looking at it...
** Changed in: gnome-screensaver (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/587743
Title:
cannot
Please open a new bug then this was closed almost a year ago. Use
'ubuntu-bug gnome-screensaver' to do so, thanks.
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for gnome-screensaver (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is decidedly not a fix, just a workaround for others who come here
with the same issue. Provided ssh access is available to the VNC host in
question, ssh in (using the username of the session to be resumed).
export DISPLAY=:0
gnome-screensaver-command -d
NOTE: As with any VNC, x11vnc will
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? Do you get the same with latest Lucid packages or in Maverick?
Thanks in
Hello,
I'm using latest lucid, and it is still a problem. I've started using
the built-in vnc service (Remote Desktop), which allows virtual logon,
but not the first time. Let me be clear: when the computer first boots,
and no one has logged in yet, it will NOT let me login via vnc. However,
once
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49417197/Dependencies.txt
** Attachment added: GconfGnomeLockdown.txt
http://launchpadlibrarian.net/49417198/GconfGnomeLockdown.txt
** Attachment added: GconfGnomePowerManager.txt
