blueman-manager times out: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

[mathew]

Binary package hint: blueman

$ blueman-manager
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
Loading configuration plugins
Using gconf config backend
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:104)
org.bluez owner changed to :1.8
Using gconf config backend
ERROR:dbus.proxies:Introspect error on org.blueman.Applet:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 576, in msg_reply_handler
    reply_handler(*message.get_args_list(**get_args_opts))
  File "/usr/bin/blueman-manager", line 132, in on_bluez_name_owner_changed
    if not self.Applet.GetBluetoothStatus():
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

^CTraceback (most recent call last):
  File "/usr/bin/blueman-manager", line 296, in <module>
    Blueman()
  File "/usr/bin/blueman-manager", line 179, in __init__
    gtk.main()
KeyboardInterrupt

Similar problem with blueman-applet. Which is probably why starting it from the GUI menu does nothing, no window appears.

$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
$ apt-cache policy blueman
blueman:
  Installed: 1.21-4.1
  Candidate: 1.21-4.1
  Version table:
 *** 1.21-4.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

# locate canberra
/etc/X11/Xsession.d/52libcanberra-gtk-module_add-to-gtk-modules
/usr/lib/libcanberra-0.25
/usr/lib/libcanberra.so.0
/usr/lib/libcanberra.so.0.2.4
/usr/lib/libcanberra-0.25/libcanberra-alsa.so
/usr/share/doc/libcanberra0
/usr/share/doc/libcanberra0/README.Debian
/usr/share/doc/libcanberra0/README.gz
/usr/share/doc/libcanberra0/changelog.Debian.gz
/usr/share/doc/libcanberra0/copyright
/var/lib/dpkg/info/libcanberra-gtk-module.list
/var/lib/dpkg/info/libcanberra-gtk0.list
/var/lib/dpkg/info/libcanberra-gtk0.postrm
/var/lib/dpkg/info/libcanberra0.list
/var/lib/dpkg/info/libcanberra0.md5sums
/var/lib/dpkg/info/libcanberra0.postinst
/var/lib/dpkg/info/libcanberra0.postrm
/var/lib/dpkg/info/libcanberra0.shlibs
/var/lib/dpkg/info/libcanberra0.symbols

[Daniel Hahler (blueyed)]

Do you still experience this problem?

If so, please provide the output of
  cat /etc/X11/Xsession.d/52libcanberra-gtk-module_add-to-gtk-modules

It looks that you had libcanberra-gtk-module installed, but then removed it (but not purged it).

This way the above file (/etc/X11/Xsession.d/52libcanberra-gtk-module_add-to-gtk-modules) has been left, which add canberra-gtk-module to GTK_MODULES.

You can fix the (rather cosmetic) error by e.b. pruning the package: "sudo dpkg -P canberra-gtk-module".

[Daniel Hahler (blueyed)]

The command for pruning should be:
  sudo dpkg -P libcanberra-gtk-module

[Daniel Hahler (blueyed)]

The real error here however appears to be that "blueman-manager" cannot connect to your DBus.

[Daniel Hahler (blueyed)]

Please provide any feedback regarding the canberra-module issue at bug 689434.

Thanks.