** Changed in: gnome-keyring
Status: Unknown => Fix Released
** Changed in: gnome-keyring
Importance: Unknown => Critical
--
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,
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(
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.
Concerning my previous comment, I have add a similar comment in #458501 has it
concern gnome-screensaver and not gnome-keyring.
--
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, wh
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 gno
** Branch linked: lp:ubuntu/gnome-keyring
--
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
ubuntu-bugs@lists.ubuntu.com
Solved for me with the last updates.
Best regards
2010/3/8 Willem Kan
>
> 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
It still does not work for me.
Best regards
2010/3/8 Willem Kan
>
> 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 w
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
I can also confirm that this has been fixed.
--
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
ubuntu-bugs@lists.ubuntu.c
Fix confirmed, thank you!
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
Confirming its fixed with 2.29.90git20100218-0ubuntu4
On Mon, Mar 8, 2010 at 3:13 PM, jam wrote:
> Thanks
>
> 2010/3/8 Launchpad Bug Tracker <524...@bugs.launchpad.net>
>
> > This bug was fixed in the package gnome-keyring -
> > 2.29.90git20100218-0ubuntu4
> >
> > ---
> > gnome-keyri
Thanks
2010/3/8 Launchpad Bug Tracker <524...@bugs.launchpad.net>
> 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 c
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 t
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Triaged => Fix Committed
--
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
Vish: I am getting a little bit of disk activity, what would be the best
way to record what is happening?
--
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 Ubu
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
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notification because you are
No idea, I cannot enter the system.
Best regards.
2010/3/7 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 c
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.
--
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
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
I'm experiencing this on Lenovo 3000 V200, realtime kernel, fully
updated as of Sat Mar 6 14:03:18 CET 2010.
--
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
I am experiencing this on my Toshiba laptop, all updates for 10.04 ran
up until now (March 6 2010)
--
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.
-
100% reproducible for me with no special PAM configuration, just
Ubuntu's default authentication against local passwd.
--
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 subs
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.
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Incomplete => Triaged
--
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 mai
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.
** Attachment added: "gdb-keyring.txt"
http:/
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.
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Triaged => Incomplete
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/
I'm experiencing this on two machines.
--
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
ubuntu-bugs@lists.ubuntu.com
htt
** Tags removed: amd64 i386
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.
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 pass
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).
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?
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notification because you are
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
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notific
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
There is a stacktrace from a duplicate added upstream now
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Incomplete => Triaged
--
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 Ubunt
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?
--
starts eating cpu when trying to unlock screen
https://bugs.launchpad.net/bugs/524860
You received this bug notification because yo
Gathered an strace of gnome-keyring-daemon. I replaced my password with
a placeholder of "aaaAa00" (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
s
Could you get a stracktrace of gnome-keyring-daemon while hanging? I got
the issue once there but not since
--
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 U
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 y
** Also affects: gnome-keyring (Ubuntu Lucid)
Importance: High
Status: Triaged
--
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-
** Summary changed:
- Locked out at lockscreen
+ starts eating cpu when trying to unlock screen
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-keyring (Ubuntu)
Milestone: None => lucid-alpha-3
** Changed in: gnome-keyring (Ubuntu)
Mileston
41 matches
Mail list logo