[Bug 436400] [NEW] bluetooth dialogs take 100% cpu and do not show up

[Oded Arbel]

Public bug reported:

Binary package hint: gnome-bluetooth

I'm not sure when this started happening, but with current Karmic
(everything up to date as of 2 hours ago and the system was rebooted
after the update), when I try to access any GNOME bluetooth dialog
(specifically the "new device" wizard or the preferences) then the
process that was created takes up 100% as can be seen in the system
monitor - and does not show up.

I've waited several minutes and it doesn't seem to be getting anywhere.
Attaching strace or ltrace to either process shows nothing, so my guess
is that it is stuck in some infinite loop somewhere. I don't have
debugging symbols installed (can't find gnome-bluetooth-dbg), but
attaching gdb and 'stepi'ing through the program I can see it is stuck
in some g_slist_find() :

---8<---
0x00007faa5690f450 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f453 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f456 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f458 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f45b in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f45d in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f475 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fdf in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fe2 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fe4 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fe6 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fe8 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fd0 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fd7 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fda in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f450 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f453 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f456 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f458 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f45b in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f45d in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa5690f475 in g_slist_find () from /usr/lib/libglib-2.0.so.0
0x00007faa56919fdf in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
---8<---
and so on ad nauseaum. 

GDB's backtrace says this:
---8<---
 (gdb) backtrace
#0  0x00007faa5690f458 in g_slist_find () from /usr/lib/libglib-2.0.so.0
#1  0x00007faa56919fdf in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
#2  0x00007faa59c4eb4c in bluetooth_client_get_type () from /usr/lib/libgnome-bluetooth.so.7
#3  0x00007faa59c4f515 in bluetooth_client_new () from /usr/lib/libgnome-bluetooth.so.7
#4  0x00007faa59c53885 in ?? () from /usr/lib/libgnome-bluetooth.so.7
#5  0x00007faa56dad927 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
#6  0x00007faa56d927ec in ?? () from /usr/lib/libgobject-2.0.so.0
#7  0x00007faa56d937e1 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#8  0x00007faa58c382ad in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#9  0x00007faa58c392f9 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x00007faa58c3acf3 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00007faa568f8504 in g_markup_parse_context_parse () from /usr/lib/libglib-2.0.so.0
#12 0x00007faa58c39071 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x00007faa58c38a9f in gtk_builder_add_from_file () from /usr/lib/libgtk-x11-2.0.so.0
#14 0x00000000004079ba in main ()
---8<---

Any help will be appreciated. I don't mind resetting all the
configuration and starting from scratch if it will make it work, I'm
just not sure how to do it - there is not .config/gnome-bluetooth or
.gnome-bluetooth. I assume all the configuration is in gconf, so I'm
loath to touch that without explicit instructions.

** Affects: gnome-bluetooth (Ubuntu)
     Importance: Undecided
         Status: New

-- 
bluetooth dialogs take 100% cpu and do not show up
https://bugs.launchpad.net/bugs/436400
You received this bug notification because you are a member of
Bluetooth, which is subscribed to gnome-bluetooth in ubuntu.