Hi Marc,

>Does this happen to you every time?
Yes

>Is the gnome-screensaver daemon running after you login?
yes,  it seems so:
* 1644 ?        00:00:00 gnome-screensav

*a...@alex-laptop:~$ ps -A | grep -e gnome
 1468 ?        00:00:00 gnome-keyring-d
 1483 ?        00:00:01 gnome-session
 1567 ?        00:00:01 gnome-settings-
 1588 ?        00:00:02 gnome-panel
 1621 ?        00:00:00 gnome-volume-co
 1622 ?        00:00:00 polkit-gnome-au
 1626 ?        00:00:01 gnome-power-man
* 1644 ?        00:00:00 gnome-screensav
* 3093 ?        00:00:01 gnome-terminal
 3094 ?        00:00:00 gnome-pty-helpe


>If you lock the screen manually with Ctrl-Alt-L, does it lock properly?
Yes, it is. Lock screen appears as it should be.


>Could you please take a look at the following debugging page and include
here the relevant information?

Done.

Regards,
Alex


On Tue, Feb 16, 2010 at 8:17 PM, Marc Deslauriers <
marc.deslauri...@ubuntu.com> wrote:

> Thanks for the bug report.
>
> Does this happen to you every time?
>
> Is the gnome-screensaver daemon running after you login?
> If you lock the screen manually with Ctrl-Alt-L, does it lock properly?
>
> Could you please take a look at the following debugging page and include
> here the relevant information?
>
> https://wiki.ubuntu.com/DebuggingScreenLocking
>
>
>
> ** Package changed: mobile-meta (Ubuntu) => gnome-screensaver (Ubuntu)
>
> ** Changed in: gnome-screensaver (Ubuntu)
>       Status: Confirmed => Incomplete
>
> ** Changed in: gnome-screensaver (Ubuntu)
>     Assignee: (unassigned) => Alexey Anufriev (alexey-a-anufriev)
>
> --
> Resuming from hibernate does not initiate authorisation process
> https://bugs.launchpad.net/bugs/369359
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gnome-screensaver” package in Ubuntu: Incomplete
>
> Bug description:
> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
> About Ubuntu.
> release 9.04 (jaunty)
> kernel linux 2.6.28-11-generic
> gnome 2.26.1
>
>
> 2) The version of the package you are using, via 'apt-cache policy
> packagename' or by checking in Synaptic.
> Package files:
>  100 /var/lib/dpkg/status
>     release a=now
>  500 http://security.ubuntu.com jaunty-security/multiverse Packages
>     release v=9.04,o=Ubuntu,a=jaunty-security,l=Ubuntu,c=multiverse
>     origin security.ubuntu.com
>  500 http://security.ubuntu.com jaunty-security/universe Packages
>     release v=9.04,o=Ubuntu,a=jaunty-security,l=Ubuntu,c=universe
>     origin security.ubuntu.com
>  500 http://security.ubuntu.com jaunty-security/restricted Packages
>     release v=9.04,o=Ubuntu,a=jaunty-security,l=Ubuntu,c=restricted
>     origin security.ubuntu.com
>  500 http://security.ubuntu.com jaunty-security/main Packages
>     release v=9.04,o=Ubuntu,a=jaunty-security,l=Ubuntu,c=main
>     origin security.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty-updates/multiverse Packages
>     release v=9.04,o=Ubuntu,a=jaunty-updates,l=Ubuntu,c=multiverse
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty-updates/universe Packages
>     release v=9.04,o=Ubuntu,a=jaunty-updates,l=Ubuntu,c=universe
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty-updates/restricted Packages
>     release v=9.04,o=Ubuntu,a=jaunty-updates,l=Ubuntu,c=restricted
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty-updates/main Packages
>     release v=9.04,o=Ubuntu,a=jaunty-updates,l=Ubuntu,c=main
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty/multiverse Packages
>     release v=9.04,o=Ubuntu,a=jaunty,l=Ubuntu,c=multiverse
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty/universe Packages
>     release v=9.04,o=Ubuntu,a=jaunty,l=Ubuntu,c=universe
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty/restricted Packages
>     release v=9.04,o=Ubuntu,a=jaunty,l=Ubuntu,c=restricted
>     origin fi.archive.ubuntu.com
>  500 http://fi.archive.ubuntu.com jaunty/main Packages
>     release v=9.04,o=Ubuntu,a=jaunty,l=Ubuntu,c=main
>     origin fi.archive.ubuntu.com
>
>
> 3) What you expected to happen
> expected result: authorization process after resume from hibernation.
>
> 4) What happened instead
> actual result: ubuntu returns to the same view (e.g. firefox browser view)
>
> 5. Steps:
> - start ubuntu
> - open firefox, go to google.com
> - put ubuntu to hibernation
> - resume from hibernate
>
> 6. HW: ASUS EEPC 1000H
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/369359/+subscribe
>


-- 
Regards,
Alexey

-- 
Resuming from hibernate does not initiate authorisation process
https://bugs.launchpad.net/bugs/369359
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to