Confirming its fixed with 2.29.90git20100218-0ubuntu4

On Mon, Mar 8, 2010 at 3:13 PM, jam <[email protected]> wrote:

> Thanks
>
> 2010/3/8 Launchpad Bug Tracker <[email protected]>
>
> > This bug was fixed in the package gnome-keyring -
> > 2.29.90git20100218-0ubuntu4
> >
> > ---------------
> > gnome-keyring (2.29.90git20100218-0ubuntu4) lucid; urgency=low
> >
> >  * debian/patches/05_git_no_read_looping.patch:
> >    - git change to "Fix problems with EINTR and EAGAIN handling", fix
> > issues
> >      where the unlock screen hangs on checking (lp: #524860)
> >  -- Sebastien Bacher <[email protected]>   Mon, 08 Mar 2010 10:53:47
> +0100
> >
> > ** Changed in: gnome-keyring (Ubuntu Lucid)
> >        Status: Fix Committed => Fix Released
> >
> > --
> > starts eating cpu when trying to unlock screen
> > https://bugs.launchpad.net/bugs/524860
> > You received this bug notification because you are a direct subscriber
> > of a duplicate bug.
> >
> > Status in GNOME keyring services: Unknown
> > Status in “gnome-keyring” package in Ubuntu: Fix Released
> > Status in “gnome-keyring” source package in Lucid: Fix Released
> >
> > Bug description:
> > Binary package hint: gnome-keyring
> >
> > Everytiime I lock the screen , I cannot return to session.  When I enter
> > the password gdm stays at "checking..." and just remains.
> >
> > I have to use SysRq+ALT+K  to exit from the freeze state.  :(
> >
> > Its either from today's update > gnome-keyring (2.28.2-0ubuntu1) to
> > 2.29.90git20100218-0ubuntu1
> >
> > I also notice gnome-keyring-daemon using high cpu when i enter the
> session.
> > [I'm not sure if this is gtk-csd related but it has been happening after
> > today's update and a restart]
> >
> > ProblemType: Bug
> > Architecture: i386
> > CheckboxSubmission: 6c350872f0b430ef8235c693ed2354c1
> > CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
> > Date: Sat Feb 20 16:50:26 2010
> > DistroRelease: Ubuntu 10.04
> > InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
> > Package: gnome-keyring 2.29.90git20100218-0ubuntu1
> > ProcEnviron:
> >  LANG=en_US.utf8
> >  SHELL=/bin/bash
> > ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
> > SourcePackage: gnome-keyring
> > Uname: Linux 2.6.32-13-generic i686
> >
> > To unsubscribe from this bug, go to:
> > https://bugs.launchpad.net/gnome-keyring/+bug/524860/+subscribe
> >
>
>
> --
> Jean-Antoine
>
> --
> starts eating cpu when trying to unlock screen
> https://bugs.launchpad.net/bugs/524860
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME keyring services: Unknown
> Status in “gnome-keyring” package in Ubuntu: Fix Released
> Status in “gnome-keyring” source package in Lucid: Fix Released
>
> Bug description:
> Binary package hint: gnome-keyring
>
> Everytiime I lock the screen , I cannot return to session.  When I enter
> the password gdm stays at "checking..." and just remains.
>
> I have to use SysRq+ALT+K  to exit from the freeze state.  :(
>
> Its either from today's update > gnome-keyring (2.28.2-0ubuntu1) to
> 2.29.90git20100218-0ubuntu1
>
> I also notice gnome-keyring-daemon using high cpu when i enter the session.
> [I'm not sure if this is gtk-csd related but it has been happening after
> today's update and a restart]
>
> ProblemType: Bug
> Architecture: i386
> CheckboxSubmission: 6c350872f0b430ef8235c693ed2354c1
> CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
> Date: Sat Feb 20 16:50:26 2010
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
> Package: gnome-keyring 2.29.90git20100218-0ubuntu1
> ProcEnviron:
>  LANG=en_US.utf8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
> SourcePackage: gnome-keyring
> Uname: Linux 2.6.32-13-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-keyring/+bug/524860/+subscribe
>

-- 
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to