bluetooth-wizard hangs after the connection has been created: #0 0x000000398fc0e100 in __read_nocancel () from /lib64/libpthread.so.0 #1 0x00000039a240bdca in gnome_keyring_socket_read_all () from /usr/lib64/libgnome-keyring.so.0 #2 0x00000039a240be57 in gnome_keyring_socket_read_buffer () from /usr/lib64/libgnome-keyring.so.0 #3 0x00000039a2406a62 in ?? () from /usr/lib64/libgnome-keyring.so.0 #4 0x00000039a2406ec7 in gnome_keyring_find_items_sync () from /usr/lib64/libgnome-keyring.so.0 #5 0x00000039a240732c in gnome_keyring_find_itemsv_sync () from /usr/lib64/libgnome-keyring.so.0 #6 0x00007f7eb7ba8134 in nm_gconf_migrate_0_7_keyring_items () from /usr/lib64/gnome-bluetooth/plugins/libnma.so #7 0x00007f7eb7ba3123 in nm_gconf_get_all_connections () from /usr/lib64/gnome-bluetooth/plugins/libnma.so #8 0x00007f7eb7bad7d6 in ?? () from /usr/lib64/gnome-bluetooth/plugins/libnma.so #9 0x00007f7eb7bad8e3 in ?? () from /usr/lib64/gnome-bluetooth/plugins/libnma.so #10 0x0000003990c3938e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #11 0x0000003990c3cd78 in ?? () from /lib64/libglib-2.0.so.0 #12 0x0000003990c3d1c5 in g_main_loop_run () from /lib64/libglib-2.0.so.0 #13 0x0000003ce5b49887 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #14 0x0000000000407963 in main () NetworkManager-gnome-0.8.0-0.2.git20100129.fc13.x86_64 NetworkManager-openvpn-0.7.996-4.git20090923.fc12.x86_64 NetworkManager-0.8.0-0.2.git20100129.fc13.x86_64 NetworkManager-vpnc-0.7.996-4.git20090921.fc12.x86_64 NetworkManager-glib-0.8.0-0.2.git20100129.fc13.x86_64 NetworkManager-pptp-0.7.997-2.git20100120.fc12.x86_64 gnome-keyring-2.28.2-2.fc12.x86_64
I've seen this sometimes on F12 and rawhide; it seems theres some keyring issues. I don't think this is related to nm-applet or anything else.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 584500 has been marked as a duplicate of this bug. ***
I believe the problem I am seeing in bug 584500 is the same. gnome-keyring-daemon is deadlocked on a pthread mutex; see the backtrace in attachment 408139 [details]. This happens several times a day and causes Evolution to hang without warning when it initiates a background check for mail. (Evolution should probably mitigate that by accessing the keyring asynchronously, but for now it doesn't.) If I kill gnome-keyring-daemon, it is restarted automatically and the applications are able to proceed.
I haven't seen the problem in a while. Perhaps it is fixed in gnome-keyring-2.30.3-1.fc13?
(In reply to comment #5) > I haven't seen the problem in a while. Perhaps it is fixed in > gnome-keyring-2.30.3-1.fc13? There's been a massive rewrite in 2.30, porting gnome-keyring to dbus. Differences in behaviour are to be expected, solving some old issues.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.