https://bugzilla.novell.com/show_bug.cgi?id=299730#c11
--- Comment #11 from Akhil Laddha 2007-10-15 00:06:44 MST ---
Comment#8 point (2)
In OpenSUSE 10.3 GM,again i noticed that gnome-keyring-daemon is taking 100%
CPU.
Scenario - Maiden account creation in Evolution asked me to enter password for
default keyring.After entering password,it started taking 100% CPU.It was
taking continuously.
If you feel that provided information is sufficient, please reopen other wise
let it be like in same state.
(gdb) thread apply all bt
Thread 2 (Thread 0xb7aeeb90 (LWP 7072)):
#0 0x08051038 in find_in_each_keyring (keyring=0x80768a0, data=0xb7aee2c4) at
gkr-daemon-ops.c:1734
#1 0x08058302 in gkr_keyrings_foreach (func=0x8050fb0 ,
data=0xb7aee2c4)
at gkr-keyrings.c:493
#2 0x08051265 in op_find (packet=0x807a58c, result=0x807a5a0, req=0xb7aee350)
at gkr-daemon-ops.c:1780
#3 0x0804e93b in client_worker_main (user_data=0x807a580) at
gkr-daemon-io.c:426
#4 0x0805c7ab in async_worker_thread (data=0x807a600) at gkr-async.c:193
#5 0xb7dcbfef in g_thread_create_proxy (data=0x80765c8) at gthread.c:635
#6 0xb7f38192 in start_thread () from /lib/libpthread.so.0
#7 0xb7d0702e in clone () from /lib/libc.so.6
Thread 1 (Thread 0xb7c438d0 (LWP 3878)):
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7f3ec1e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2 0xb7f3aa58 in _L_mutex_lock_86 () from /lib/libpthread.so.0
#3 0xb7f3a47d in pthread_mutex_lock () from /lib/libpthread.so.0
#4 0x0805c1f9 in lock_step_poll_func (ufds=0x8071c70, nfsd=4, timeout=-1) at
gkr-async.c:88
#5 0xb7dabef5 in g_main_context_iterate (context=0x806e3e8, block=1,
dispatch=1, self=0x806b668) at gmain.c:2996
#6 0xb7dac2a7 in g_main_loop_run (loop=0x80718b0) at gmain.c:2898
#7 0x0804dda4 in main (argc=1, argv=0xbff267b4) at gkr-daemon.c:318
#0 0xffffe410 in __kernel_vsyscall ()
Comment#8 point (1)
https://bugzilla.novell.com/show_bug.cgi?id=332390
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.