bluetooth-wizard will not run - assertion failure

[Matthew Woerly]

Binary package hint: gnome-bluetooth

Running bluetooth-wizard gives me this:

$ bluetooth-wizard

(bluetooth-wizard:4558): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-wizard:4558): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

ProblemType: Bug
Architecture: amd64
Date: Mon Sep 14 12:38:49 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-bluetooth 2.27.90-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
SourcePackage: gnome-bluetooth
Uname: Linux 2.6.31-10-generic x86_64

[Alexander Sack (asac)]

this is interesting. we dropped symbolic-functions ... which was supposed to be ok now.

[Alexander Sack (asac)]

do you have an up-to-date system? please ensure that libgnome-bluetooth* has the same version as gnome-bluetooth package.

[icb410 (ian-berke)]

My system is up-to-date as far as I can tell and I have this problem too:

ian@ubulaptop:~$ apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.27.90-0ubuntu1
  Candidate: 2.27.90-0ubuntu1
  Version table:
 *** 2.27.90-0ubuntu1 0
        500 http://mirrors.rit.edu karmic/main Packages
        100 /var/lib/dpkg/status

ian@ubulaptop:~$ apt-cache policy libgnome-bluetooth7
libgnome-bluetooth7:
  Installed: 2.27.90-0ubuntu1
  Candidate: 2.27.90-0ubuntu1
  Version table:
 *** 2.27.90-0ubuntu1 0
        500 http://mirrors.rit.edu karmic/main Packages
        100 /var/lib/dpkg/status

[icb410 (ian-berke)]

I get a similar message with bluetooth-properties:

ian@ubulaptop:~$ bluetooth-properties

** (bluetooth-properties:12151): WARNING **: Could not open RFKILL control device, please verify your installation

(bluetooth-properties:12151): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-properties:12151): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

These commands start and peg the CPU near 100% until I kill them. The bluetooth-sendto dialogue seems to work ok.

Ian

[Alexander Sack (asac)]

ok. readding workaround for this bug. the underlying issue that should bring the real fix is bug 429950.

[Alexander Sack (asac)]

This bug was fixed in the package gnome-bluetooth - 2.27.90-0ubuntu2

---------------
gnome-bluetooth (2.27.90-0ubuntu2) karmic; urgency=low

  * fix LP: #427020 - bluetooth-wizard crashes on load; we backout dropping
    -Bsymbolic-functions hack from debian/rules in last upload

 -- Alexander Sack <email address hidden> Tue, 15 Sep 2009 12:35:26 +0200

[buzz (buzz2)]

With the current gnome-bluetooth version i still get this failure. So for me its not fixed.

gnome-bluetooth:
  Installiert: 2.28.0-0ubuntu1
  Kandidat: 2.28.0-0ubuntu1
  Versions-Tabelle:
 *** 2.28.0-0ubuntu1 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[Matjam (chrome)]

I get the same problem.

chrome@neutron:~$ apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        100 /var/lib/dpkg/status
     2.27.8-0ubuntu1 0
        500 http://au.archive.ubuntu.com karmic/main Packages
chrome@neutron:~$ apt-cache policy libgnome-bluetooth7
libgnome-bluetooth7:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        100 /var/lib/dpkg/status
     2.27.8-0ubuntu1 0
        500 http://au.archive.ubuntu.com karmic/main Packages

Note: the error about RFKILL can be fixed by running as root with sudo. Permissions problems with the device?

strace shows this:

open("/dev/rfkill", O_RDWR) = -1 EACCES (Permission denied)

crw-r--r-- 1 root root 10, 63 2009-09-23 08:48 /dev/rfkill

This may be two separate bugs.

[Alexey Kotlyarov (koterpillar)]

Not fixed here either. ^C is mine, both times processes ate 100% CPU.

alex@flower2:~$ LANG=C apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        400 http://ru.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
alex@flower2:~$ LANG=C apt-cache policy libgnome-bluetooth7
libgnome-bluetooth7:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        400 http://ru.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
alex@flower2:~$ bluetooth-properties

** (bluetooth-properties:2830): WARNING **: Could not open RFKILL control device, please verify your installation
** (bluetooth-properties:2830): DEBUG: Unhandled UUID 831c4071-7bc8-4a9c-a01c-15df25a4adbc (0x831c4071)

(bluetooth-properties:2830): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-properties:2830): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
^C
alex@flower2:~$ bluetooth-wizard
** (bluetooth-wizard:2831): DEBUG: Unhandled UUID 831c4071-7bc8-4a9c-a01c-15df25a4adbc (0x831c4071)

(bluetooth-wizard:2831): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-wizard:2831): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
^C

[Rachel Greenham (rachel-strangenoises)]

The fix appears to still not be released. I'm also getting this on a freshly installed and upgraded asus 1008HA. Opening bluetooth-properties (Preferences on the applet) just hangs, taking up 100% CPU and outputting this:

rachel@siren:/$ bluetooth-properties

** (bluetooth-properties:2045): WARNING **: Could not open RFKILL control device, please verify your installation

(bluetooth-properties:2045): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-properties:2045): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

<end>

Definitely up to date; just updated literally right before trying it again this morning.

rachel@siren:/$ apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
rachel@siren:/$ apt-cache policy libgnome-bluetooth7
libgnome-bluetooth7:
  Installed: 2.28.0-0ubuntu1
  Candidate: 2.28.0-0ubuntu1
  Version table:
 *** 2.28.0-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[Vitali Kulikou (sabotatore)]

I have the same:

$ bluetooth-wizard

(bluetooth-wizard:7244): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-wizard:7244): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

AND

$ bluetooth-properties

** (bluetooth-properties:7447): WARNING **: Could not open RFKILL control device, please verify your installation

(bluetooth-properties:7447): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-properties:7447): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

And 100% load processor.

[sim (simll)]

the same bug

[icb410 (ian-berke)]

I get slightly different error message about being unable to open a library:

$ bluetooth-properties

** (bluetooth-properties:19667): WARNING **: error opening /usr/lib/gnome-bluetooth/plugins/libnma.so: libnm-glib-vpn.so.0: cannot open shared object file: No such file or directory

** (bluetooth-properties:19667): WARNING **: Could not open RFKILL control device, please verify your installation

(bluetooth-properties:19667): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-properties:19667): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
^C

The libraries are present.

[Dan Andreșan (danyer)]

@icb410,
libnm-glib-vpn.so.0 is a different (temporary) issue, I guess if you update you will not see it again.

excepting that line, all the other messages are exactly like in comment 12.

[Paolo Stivanin (polslinux)]

gnome-bluetooth doesn't work, i have the same problems!

[Eugene Crosser (crosser)]

I see the same messages from bluetooth-wizard and bluetooth-properties and after that both programs busyloop. I ran under gdb and hit Ctrl-C, see below

$ apt-cache policy gnome-bluetooth
gnome-bluetooth:
  Installed: 2.28.0-0ubuntu1

$ gdb /usr/bin/bluetooth-wizard
GNU gdb (GDB) 6.8.91.20090918-cvs-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/bluetooth-wizard...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/bluetooth-wizard
[Thread debugging using libthread_db enabled]

(bluetooth-wizard:2267): GLib-GObject-WARNING **: cannot register existing type `BluetoothClient'

(bluetooth-wizard:2267): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
^C
Program received signal SIGINT, Interrupt.
0x00007ffff489dfe8 in g_once_init_enter_impl () from /usr/lib/libglib-2.0.so.0
(gdb) bt
#0 0x00007ffff489dfe8 in g_once_init_enter_impl ()
   from /usr/lib/libglib-2.0.so.0
#1 0x00007ffff7bd2b4c in bluetooth_client_get_type ()
   from /usr/lib/libgnome-bluetooth.so.7
#2 0x00007ffff7bd3515 in bluetooth_client_new ()
   from /usr/lib/libgnome-bluetooth.so.7
#3 0x00007ffff7bd7885 in ?? () from /usr/lib/libgnome-bluetooth.so.7
#4 0x00007ffff4d31927 in g_type_create_instance ()
   from /usr/lib/libgobject-2.0.so.0
#5 0x00007ffff4d167ec in ?? () from /usr/lib/libgobject-2.0.so.0
#6 0x00007ffff4d177e1 in g_object_newv () from /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff6bbc2ad in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00007ffff6bbd2f9 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x00007ffff6bbecf3 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x00007ffff487c504 in g_markup_parse_context_parse ()
   from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff6bbd071 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x00007ffff6bbca9f in gtk_builder_add_from_file ()
   from /usr/lib/libgtk-x11-2.0.so.0
#13 0x00000000004079ba in main ()
(gdb)

[Eugene Crosser (crosser)]

Is Bug #436049 related to this one?

[Dan Andreșan (danyer)]

Bug #436049 is marked as a duplicate of this one

[Alexander Sack (asac)]

uploaded new package to my ppa: https://edge.launchpad.net/~asac/+archive/ppa ... will be available in a few hours. Please upgrade gnome-bluetooth and libgnome-bluetooth7 to version 2.28.0-0ubuntu2~asac from there and confirm that it helps. Thanks.

[Alexey Kotlyarov (koterpillar)]

Works for me.

[Eugene Crosser (crosser)]

Helps me, too

[Vitali Kulikou (sabotatore)]

Works for me.

[Alexander Sack (asac)]

Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading gnome-bluetooth_2.28.0-0ubuntu2.dsc: done.
  Uploading gnome-bluetooth_2.28.0-0ubuntu2.diff.gz: done.
  Uploading gnome-bluetooth_2.28.0-0ubuntu2_source.changes: done.
Successfully uploaded packages.

[Launchpad Janitor (janitor)]

This bug was fixed in the package gnome-bluetooth - 2.28.0-0ubuntu2

---------------
gnome-bluetooth (2.28.0-0ubuntu2) karmic; urgency=low

  * debian/rules: code is still not good for -Bsymbolic-functions; strip
    it from LDFLAGS to prevent type problems LP: #429523

 -- Alexander Sack <email address hidden> Fri, 25 Sep 2009 01:09:43 +0200

[k_laci (laszlokaroly)]

What about the RFKILL issue? 2.28.0-0ubuntu2 did not solve this problem for me. Some weeks ago it worked fine, now I cannot switch bluetooth on/off from the applet, only from the command line with sudo.

bluetooth-applet &
** (bluetooth-applet:4172): WARNING **: Could not open RFKILL control device, please verify your installation

[Սահակ (petrosyan)]

RFKILL issue is bug #436694

[k_laci (laszlokaroly)]

Thanks. Fedora's udev rule works for me.

[gpothier (gpothier)]

It seems this bug reappeared in Maverick. I installed Maverick from alpha1 media and then installed all the updates. I get the exact same message as in the original bug description. I had no problem with bluetooth in Lucid.

[Ahmed Kamal (kim0)]

I'm on Maverick and bluetooth is not working for me neither. I'm getting that error message too

[Pete Goodall (pgoodall)]

Rather than use the Karmic bug I filed a new one. Should probably comment further there if you are seeing this problem on Maverick. Bug #597117