TC 5 blueman compiled for wrong libraries

[gerald_clark]

Core 5.4 and blueman.
blueman-applet is looking for libnotify.so.1.
Libnotify is libnotify.so.4

[Juanito]

blueman recompiled and posted for tc-5.x - I couldn't get it to work though...

[gerald_clark]

It looks like notify-python.tcz is the culprit.

[Juanito]

Yeah - I was compiling on tc-6.x so I thought the problem was that pygobject needs libffi5. pygobject-2* will not compile with the gobject-introspection in tc-6.x and pygobject-3* will not work with blueman.

It seem that notify-python-0.1.1 will not compile with anything newer than libnotify-0.5 (the tc-5.x version is 0.7.5) - maybe you could package up libnotify from tc-4.x as libnotify5 and try that?

[Juanito]

I know blueman was working for me in tc-4.x - I just tried to double-check, but it seems my laptop is too recent to boot tc-4.x 

Blueman fails in the same way on both tc-5.x/6.x - from the look of it the problem could be either dbus or pulseaudio.

Until recently blueman was long dead, but it seems to be re-starting in git aimed at gtk3/bluez5 - I'll take a look.

Code: [Select]

Load (/usr/local/lib/python2.7/site-packages/blueman/main/PluginManager.py:68)
['Services', 'PulseAudioProfile']
ERROR:dbus.proxies:Introspect error on org.blueman.Applet:/: dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/local/bin/blueman-applet exited with status 1
Traceback (most recent call last):
  File "/usr/local/bin/blueman-manager", line 301, in <module>
    Blueman()
  File "/usr/local/bin/blueman-manager", line 64, in __init__
    self.Plugins.Load()
  File "/usr/local/lib/python2.7/site-packages/blueman/main/PluginManager.py", line 98, in Load
    __import__(self.module_path.__name__ + ".%s" % plugin, None, None, [])
  File "/usr/local/lib/python2.7/site-packages/blueman/plugins/manager/PulseAudioProfile.py", line 30, in <module>
    if not "PulseAudio" in a.QueryPlugins():
  File "/usr/local/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/local/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/local/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBu.ception: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/local/bin/blueman-applet exited with status 1
_________
save (/usr/local/lib/python2.7/site-packages/blueman/plugins/config/File.py:117)
Saving config
Exception AttributeError: "'NoneType' object has no attribute 'Bus'" in <bound method File.__del__ of <File object at 0xb62ca7d4 (blueman+plugins+ConfigPlugin+ConfigPlugin at 0x9541560)>> ignored


[Juanito]

I compiled blueman-1.99 from git and posted to the tc-6.x repo.

It scans and finds bluetooth devices, but segfaults when I try to pair.

@gerald_clark if you're OK with it, I'll remove blueman from the tc-5.x repo as I don't believe it's (easily) fixable - just let me know.

[gerald_clark]

It's OK with me. 

[Juanito]

I found libnotify still depended on libffi5 - recompiled version now posted in tc-6.x repo.

..and blueman will now pair with bluetooth headphones and (after setting the headphones to "audio sink" in blueman and using pavucontrol to swap the audio output to the headphones) I can use xmms-pulse to play music to the headphones.

However, when trying to pair with an iPhone or a TV - where blueman generates a random pin to be entered on the other device - blueman still segfaults.

[Juanito]

It's OK with me.

blueman removed from tc-5.x repo

[gerald_clark]

I now have music playing to my Phillips Bluetooth stereo through Core 6.  Thanks.

[Juanito]

Great 

The blueman site mentions notification-daemon as a runtime dep, but I haven't seen any added functionality when it's running...

[gerald_clark]

Perhaps it is used to popup a dialog when a file transfer to the computer is requested.

[Juanito]

In fact blueman requires notification-daemon to pair with an intelligent device (i.e. laptop, iPhone, etc) as it pops-up a message about the pairing pin code and asks for confirmation to go ahead.