starts eating cpu when trying to unlock screen

[Vish]

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

[Takyoji (takyoji)]

As a sidenote, I've been able to get around this by killing the gnome-screensaver application from a command line in another terminal. However gnome-keyring-daemon seems to be using nearly 100% CPU power. Trying to open the "Passwords and Encryption Keys" dialog (after bypassing the screensaver password prompt) returns an error of "Couldn't communicate with the key ring daemon" in the status bar of the "Passwords and Encryption Keys" dialog.

Hopefully this additional information helps with debugging the issue.

[Robert B (robertbub)]

Kill'ing -9 (SIGKILL) gnome-keyring-daemon also breaks out of the gnome-screensaver.

[Vish (vish)]

Bumping to "high" , since the default is to 'lock screen when system is idle' and users are getting locked out.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

Could you get a stracktrace of gnome-keyring-daemon while hanging? I got the issue once there but not since

[Takyoji (takyoji)]

Gathered an strace of gnome-keyring-daemon. I replaced my password with a placeholder of "aaaaaaaAaaaaaaaaa00" (same length and form of the password used).

"read(14, "", 8) = 0" is repeated indefinitely throughout the log (a total of 32MB in just a few seconds), thus has been truncated to a more sane size.

[Sebastien Bacher (seb128)]

thank you for your efforts, could you get a gdb stacktrace as described in the wikipage indicated before though rather than strace log which is a different thing?

[Sebastien Bacher (seb128)]

There is a stacktrace from a duplicate added upstream now

[Rafael Gattringer (rafael.gattringer)]

Perhaps this bug has to do with the PAM configuration.

Related bugs in Gnome
https://bugzilla.gnome.org/buglist.cgi?quicksearch=screensaver+password

Gnome FAQ
http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#Why_does_the_screensaver_unlock_dialog_always_think_my_password_is_invalid.3F

[Usama Akkad (damascene)]

I think it has relation to this bug:
Password works in virtual terminal but not in Gnome screensaver
https://bugs.edge.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/435928

[Bernhard (b.a.koenig)]

DId anybody see those messages in mono (e.g. docky) which say:

[Error 17:09:09.373] gnome-keyring-daemon could not be reached!

Is this related to this bug?

[Vish (vish)]

Well , this bug is frustrating.

Upstream has marked bug as incomplete since :
"
> Unfortunately, that stack trace is missing some elements that will help a lot
> to solve the problem. In particular, I need a stack trace of all threads, and
> not just one (in this case the signal handling thread).
"

I have narrowed down the bug to
- Only happens for auto-login users. [when users enter password in policykit
dialogue to unlock keyring]
- Does not happen when user enters password anywhere else [in the vt or during
session login.]

Since this bug is tricky , i have not been able to get a full gdb.
- if i start gdb from session in a terminal , i cant get back to session unless
i kill the daemon. [which does not give the fully required gdb]
- if i start the keyring gdb from a vt earlier[user has to enter password to
login to the vt session] , then the bug wont happen! Since i have entered the
password before starting keyring-daemon.

It seems that user needs ssh access to system to get a full gdb. [I'm not sure
I'll be able to get this done , hope someone else who has ssh access can do it]

If someone can do this it would be nice.
They have to remove the 3 instances of the gnome-keyring from the startup applications to start the gnome-keyring-daemon gdb and have to use the components as args. [i think since this was how i was trying to get it done]

[gmoore777 (guy-moore)]

I've had this problem on 3 different machines with 3 different users on 64-bit LucidLynx.
I have built out these machines within the last 2 weeks.
All 3 have ActiveDirectory logins (leveraging likewise-open). We do not use auto logins.
They had noticed that their screen was locked, entered a password, and have waited over 30 minutes.
ssh-ing in, and running top, we see that the gnome keyring-d is at 99%. If we kill that process,
then the terminal lock screen seems to refresh itself, and now a password will unlock the screen
immediately, as it should. I have 2 other machines that I personally use at work, they were built out
 with LucidLynx long before the 3 mentioned in the above(one in december, one in january),
  and I never had a problem as described.
I'm willing to try to narrow this down, but I would have to have one of those 3 developers assist me
and that may be unlikely.

[Jordan Bradley (jordan-w-bradley)]

I'm experiencing this on two machines.

[Vish (vish)]

I'm marking the bug as incomplete since this bug still needs a complete stack trace of all threads for the upsream devs to work on.

[markh (mark-howson)]

Here's a backtrace taken by the wiki instructions. No auto login here but we are using PAM krb to auth against active directory. Not sure if the trace helps, let me know if I should do something differently - the bug seems fairly reproducible here.

[Victor Costan (costan)]

I have a Dell mini 10 experiencing this problem. If it helps, I can give developers full SSH access to it. The machine doesn't have important data / software, so I'm OK with any experiments.

[Martin Pool (mbp)]

100% reproducible for me with no special PAM configuration, just Ubuntu's default authentication against local passwd.

[Willem Kan (wrkan-deactivatedaccount)]

I am experiencing this on my Toshiba laptop, all updates for 10.04 ran up until now (March 6 2010)

[Dominik Sauer (dominik-sauer)]

I'm experiencing this on Lenovo 3000 V200, realtime kernel, fully updated as of Sat Mar 6 14:03:18 CET 2010.

[Vish (vish)]

Upstream wants to know:
> Is there high hard disk activity from the gnome-keyring-daemon during this
> period as well?

I dont have high disk activity, only high CPU usage..
If anyone is noticing high disk-activity do comment upstream. It seems I'm the only one subscribed there , and others have different scenarios. So if you are noticing different patterns do mention it upstream.

[Kjell L. (lkjell)]

The problem seems to be fixed for me. However there are other problems with the keyring so I will make new bug report on those issue.

[jam (jamontagnon-gmail)]

No idea, I cannot enter the system.
Best regards.

2010/3/7 Vish <email address hidden>

> Upstream wants to know:
> > Is there high hard disk activity from the gnome-keyring-daemon during
> this
> > period as well?
>
> I dont have high disk activity, only high CPU usage..
> If anyone is noticing high disk-activity do comment upstream. It seems I'm
> the only one subscribed there , and others have different scenarios. So if
> you are noticing different patterns do mention it upstream.
>
> --
> 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: Triaged
> Status in “gnome-keyring” source package in Lucid: Triaged
>
> 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

[Kjell L. (lkjell)]

If it is possible maybe try to backup the keyrings and delete to see if it is not the crufts that is holding you back. They are located at ~/.gnome2/keyrings

[IKT (ikt)]

Vish: I am getting a little bit of disk activity, what would be the best way to record what is happening?

[Launchpad Janitor (janitor)]

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 address hidden> Mon, 08 Mar 2010 10:53:47 +0100

[jam (jamontagnon-gmail)]

Thanks

2010/3/8 Launchpad Bug Tracker <email address hidden>

> 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 address hidden> 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

[Omer Akram (om26er)]

Confirming its fixed with 2.29.90git20100218-0ubuntu4

On Mon, Mar 8, 2010 at 3:13 PM, jam <email address hidden> wrote:

> Thanks
>
> 2010/3/8 Launchpad Bug Tracker <email address hidden>
>
> > 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 address hidden> 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 se...

[Rafael Gattringer (rafael.gattringer)]

Fix confirmed, thank you!

[Vitaly (vbabiy86)]

I can also confirm that this has been fixed.

[Willem Kan (wrkan-deactivatedaccount)]

Yes, fixed also at my side, thanks!

_________________________________________________________________
Een netbook met Windows 7? Hier vind je alles dat je moet weten.
www.windows.nl/netbook

[jam (jamontagnon-gmail)]

It still does not work for me.
Best regards

2010/3/8 Willem Kan <email address hidden>

>
> Yes, fixed also at my side, thanks!
>
>
> _________________________________________________________________
> Een netbook met Windows 7? Hier vind je alles dat je moet weten.
> www.windows.nl/netbook
>
> --
> 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

[jam (jamontagnon-gmail)]

Solved for me with the last updates.
Best regards

2010/3/8 Willem Kan <email address hidden>

>
> Yes, fixed also at my side, thanks!
>
>
> _________________________________________________________________
> Een netbook met Windows 7? Hier vind je alles dat je moet weten.
> www.windows.nl/netbook
>
> --
> 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

[David Sauvage (pariakanet)]

using Ubuntu 10.04 (x86 32 bits, dell inspiron 510m), and :
gnome-keyring 2.92.92.is.2.30.1-ubuntu2
gnome-screensaver 2.30.0-0ubuntu2
the problem still happen (that is after the screen is locked automatically by gnome-screensaver, when i enter my password to unlock the session, cpu is 100% on gnome-screensaver, and it stays displaying checking ...).

As i noticed the cpu consumption on gnome-screensaver and not gnome-keyring may be i should report elsewhere ?

I consider this bug critical for the end user.

Note : after i kill -9 the process for the first time, the problem do not appear anymore when unlocking the session ...

do not hesitate to ask some details as i can reproduce this bug (known to me since 9.10)

[David Sauvage (pariakanet)]

Concerning my previous comment, I have add a similar comment in #458501 has it concern gnome-screensaver and not gnome-keyring.

[Jordan Bradley (jordan-w-bradley)]

I'm not sure if this is the same as David Sauvage's problem, but when I close the lid on my laptop it goes to sleep. When I open the lid and power up my laptop, I am asked for my password. Unless I type my password very fast, the unlock screen stalls and I can't enter my password for a few seconds.

[David Sauvage (pariakanet)]

I can confirm that the problem occur when two instances of gnome-screensaver are launched by the system. For my part, the fact that 2 gnome-screensaver instances are launch at startup is unknown and appears randomly.

using a console :
$ pstree -p | grep gnome-screen
        |-gnome-screensav(XXXX)───{gnome-screensav}(YYYY)
        |-gnome-screensav(ZZZZ)
$ kill -9 ZZZZ

then do ALT+F7 to come back to your X session.

As my system have only been upgraded Ubuntu release to another (for several years), may be there are corrupted config files that launched two instances of gnome-screensaver, that is at the origin of the conflict and cpu outage ...

I think #181065 and #458501 are duplicated bugs of this one.