FS#37645 - [blueman] Blueman utilities stopped working after change to bluez5
Attached to Project:
Community Packages
Opened by Vlad Seghete (vlsd) - Tuesday, 05 November 2013, 01:23 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 26 November 2013, 09:46 GMT
Opened by Vlad Seghete (vlsd) - Tuesday, 05 November 2013, 01:23 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 26 November 2013, 09:46 GMT
|
Details
Now that blueman depends on bluez5 it is not possible to
open blueman-applet or blueman-manager anymore. For example,
this is a typical error:
on_dbus_name_owner_change (/usr/bin/blueman-applet:100) org.bluez owner changed to :1.2 _________ Run (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:216) Function on_manager_state_changed on AuthAgent Failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py", line 220, in Run ret = getattr(inst, function)(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blueman/plugins/applet/AuthAgent.py", line 49, in on_manager_state_changed adapters = self.Applet.Manager.ListAdapters() File "/usr/lib/python2.7/site-packages/blueman/bluez/utils.py", line 28, in warp raise errors.parse_dbus_error(exception) DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist More details in this thread https://bbs.archlinux.org/viewtopic.php?pid=1345376 |
This task depends upon
Closed by Sergej Pupykin (sergej)
Tuesday, 26 November 2013, 09:46 GMT
Reason for closing: Won't fix
Additional comments about closing: bluez4 is gone from repos, so blueman removed from community too, but I will put it back when it become bluez5 compatible
Tuesday, 26 November 2013, 09:46 GMT
Reason for closing: Won't fix
Additional comments about closing: bluez4 is gone from repos, so blueman removed from community too, but I will put it back when it become bluez5 compatible
This 'org.bluez.Manager' interface has been removed from bluez5, see http://www.bluez.org/bluez-5-api-introduction-and-porting-guide/
"One of the most notable of these removals is the old org.bluez.Manager interface. In BlueZ 5 there does not exist anything that would correspond to this"
So currently blueman should depend on bluez4, not on bluez (=bluez5)
Related github issue: https://github.com/cschramm/blueman/issues/13 "Port to bluez5"
pacman -Sdd bluez4
This did fix blueman. - Please revert the dependency to bluez4.