For what it's worth, I'm seeing this issue (100% CPU usage, Gnome
desktop hangs completely on start) with Jaunty installed from http
://old-releases.ubuntu.com/ubuntu/ , running in a chroot under Android
on a Tegra2 tablet %).
--
You received this bug notification because you are a member of
Installing http://old-releases.ubuntu.com/ubuntu/pool/main/g/gnome-
keyring/gnome-keyring_2.28.1-0ubuntu1_armel.deb (using dpkg -i --force-
all) makes desktop not hang on start (like with 2.26.1-0ubuntu1), but
gnome-keyring-daemon still eats 100% CPU.
So, rm
** Changed in: gnome-keyring
Status: Confirmed = Unknown
** Changed in: gnome-keyring
Importance: Unknown = Critical
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of
** Branch linked: lp:ubuntu/gnome-keyring
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs
I am seeing a similar behavior when trying to unlock on Karmic today. I
had to kill the keyring daemon from the console (ctlr+alt+F1). I have
seen it twice today. I am not sure it is relevant here.
Steps to reproduce:
1. Lock the screen - ctrl + alt + 'L'
2. Try to unlock the screen with
setting to fix released status, the issue doesnt show up with recent
upstream and gcc 4.4
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Fix Released
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug
i revisited the issue today and tested the following:
* we noticed that the issue does not show up in karmic so i rebuilt the
2.27 version of gnome keyring in jaunty, the issue returned with the
newer version as well
* i rebuilt the 2.27 source in jaunty with karmics gcc-4.4, the issue
** Changed in: gnome-keyring
Status: New = Confirmed
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
I had uploaded g-k built with -O1 to workaround this bug in jaunty.
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Won't Fix = Fix Released
** Changed in: gnome-keyring (Ubuntu Jaunty)
Assignee: Oliver Grawert (ogra) = Loïc Minier (lool)
--
[arm] gnome-keyring-daemon eating
** Tags added: armel
** Tags removed: arm
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs
** Changed in: gnome-keyring
Status: Incomplete = New
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Triaged = Won't Fix
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
On Tue, Apr 14, 2009 at 12:59:28PM -, Steve Langasek wrote:
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Triaged = Won't Fix
Wasn't this fixed by
gnome-keyring (2.26.0-0ubuntu7) jaunty; urgency=low
* Built with -O1 on armel to workaround a deadlock which is triggerred
On Tue, Apr 14, 2009 at 02:56:58PM +0100, Matt Zimmerman wrote:
On Tue, Apr 14, 2009 at 12:59:28PM -, Steve Langasek wrote:
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Triaged = Won't Fix
Wasn't this fixed by
gnome-keyring (2.26.0-0ubuntu7) jaunty; urgency=low
*
will be fixed with the 2.16.1 update once accepted today
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Fix Committed
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a
This bug was fixed in the package gnome-keyring - 2.26.1-0ubuntu1
---
gnome-keyring (2.26.1-0ubuntu1) jaunty; urgency=low
* New upstream version:
- Fix many problems with the new secure memory allocator.
(lp: #328167, #338158, #352269)
- DBus now automatically starts
Verified fixed.
** Changed in: oem-priority
Status: New = Fix Released
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I confirmed that this issue is still present in gnome-keyring 2.26.1 if
it is built with -O2. Further debugging information relayed upstream.
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Fix Released = Triaged
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I've pushed a gnome-keyring building with -O1 on armel as that was said
to workaround the bug by Michael no IRC.
@Michael: please document your debugging progress here, backtraces, what
you tried etc.
I personally suspect http://bugzilla.gnome.org/show_bug.cgi?id=575247 to
be on the right track
marking the jaunty task as wontfix and un-milestoning as we have a
workaround in place. Of course a cleaner fix is a welcome replacement
though.
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Triaged = Won't Fix
** Changed in: gnome-keyring (Ubuntu Jaunty)
Milestone:
gnome-keyring-daemon hangs in --start and never forks to a --daemonize --login
process
sockets for ssh and pkcs11 dont show up in the socket dir
running gnome-keyring-daemon --daemonize --login from a terminal does not
result in 100% CPU usage but still leaves me without more than
The fix applied to close bug #338158 is confirmed not to fix this bug.
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring
i tested with --start --components=ssh as well as --start
--components=pkcs11, neither of them got further in the process so i
assume its not the fault of the backend components
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received
confirming that the rebuild with -O1 works around the issue
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
I've been working on this bug, and I've done a bisection of uploads of
gnome-keyring to Jaunty. The bug only started occurring with the upload
of 2.25.4.1; 2.25.1 and 2.24 are unaffected. I'm trying now to isolate
the changeset that broke the daemon on ARM.
--
[arm] gnome-keyring-daemon eating
@Ralph, since all of the other reports in this bug are on arm systems,
it's very possible that you have a different bug. Could you file it
separately (use ubuntu-bug /usr/bin/gnome-keyring) and mention the bug
number here? Maybe it will turn out to be the same, but maybe not, and
it's easier to
** Also affects: oem-priority
Importance: Undecided
Status: New
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-keyring
Status: New = Incomplete
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
** Summary changed:
- gnome-keyring-daemon eating 100% CPU at login in Jaunty
+ [arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug notification because you
30 matches
Mail list logo
