Blueman manager won't start after update.

eduardosm · 2013-11-02 16:09:01

After updating blueman to 20131021git-2 and bluez to 5.9, I can't start the blueman manager. I can only see the applet icon, but most of the options (device list, send file...) don't work at all. Sending a file from another device to my computer doesn't work either. If I try to open blueman-manager from the console I get:

Loading configuration plugins
_________
<module> (/usr/lib/python2.7/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf 
Using file config backend
_________
Load (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:68)
['PulseAudioProfile', 'Services'] 
_________
__load_plugin (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:142)
loading <class 'blueman.plugins.manager.Services.Services'> 
_________
__load_plugin (/usr/lib/python2.7/site-packages/blueman/main/PluginManager.py:142)
loading <class 'blueman.plugins.manager.PulseAudioProfile.PulseAudioProfile'> 
_________
pa_context_event (/usr/lib/python2.7/site-packages/blueman/main/PulseAudioUtils.py:306)
1 
blueman-manager version 1.23 starting
There is an instance already running
_________
save (/usr/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 0x20735a0 (blueman+plugins+ConfigPlugin+ConfigPlugin at 0x1ca7320)>> ignored

I'm running XFCE.

TheSaint · 2013-11-02 18:11:00

blueman wants bluez4, don't you know it?
Even pacman will note that the dependency is broken.

eduardosm · 2013-11-02 18:19:13

TheSaint wrote:

blueman wants bluez4, don't you know it?
Even pacman will note that the dependency is broken.

Not true anymore: https://www.archlinux.org/packages/comm … 4/blueman/
I had to remove bluez4 and install bluez to update blueman.

drhill1 · 2013-11-02 18:29:53

Having read your post, I've just checked mine after the blueman/bluez upgrade and am having the same problem, so it's not just you. I haven't a clue as to a fix though, sorry.

Joel · 2013-11-02 23:20:06

I'm having the same issue:

1.- After upgrade, the icon shows on system notification tray
2.- Can't open any dialog window from tray icon, except the "about dialog"
3.- runing "blueman-manager" from the terminal I get the same text as the poster eduardosm.

after googling seems that the error was about dbus and ck-launch-session, maybe the updated blueman needs to use the systemd thing?

eduardosm · 2013-11-02 23:43:27

Joel wrote:

I'm having the same issue:
1.- After upgrade, the icon shows on system notification tray
2.- Can't open any dialog window from tray icon, except the "about dialog"
3.- runing "blueman-manager" from the terminal I get the same text as the poster eduardosm.

after googling seems that the error was about dbus and ck-launch-session, maybe the updated blueman needs to use the systemd thing?

That topic is from 2011 and consolekit deprecated (only available on AUR). I haven't heard about integration of blueman with systemd. Probably we will have to wait for a bugfix and downgrade until then.

KlipperKyle · 2013-11-04 02:10:09

Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py", line 92, in timeout
self.adapter_state = self.get_adapter_state()
File "/usr/lib/python2.7/site-packages/blueman/plugins/applet/PowerManager.py", line 98, in get_adapter_state
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)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't exist

Judging by the error messages, it looks like bluez 5's dbus interfaces are different. (I'm not 100% sure because I'm not a dbus wiz.)

Right now, I have reverted to the text based bluetoothctl command. <https://wiki.archlinux.org/index.php/Bl … ith_bluez5>

Obviously, another alternative is to downgrade blueman to 1.23-10.

lervag · 2013-11-04 13:43:01

I also have this problem, but I am not able to use the bluetoothctl command either. I get the following output with bluetoothctl:

---> bluetoothctl 
[NEW] Controller B0:05:94:F2:59:6D vsl136 [default]
[NEW] Device 00:18:09:1C:B7:80 MDR-1RBT
[bluetooth]# connect 00:18:09:1C:B7:80 
Attempting to connect to 00:18:09:1C:B7:80
Failed to connect: org.bluez.Error.Failed

I hope this is a bug that will be fixed quickly.

KlipperKyle · 2013-11-04 15:21:42

lervag wrote:

I also have this problem, but I am not able to use the bluetoothctl command either. I get the following output with bluetoothctl:
---> bluetoothctl 
[NEW] Controller B0:05:94:F2:59:6D vsl136 [default]
[NEW] Device 00:18:09:1C:B7:80 MDR-1RBT
[bluetooth]# connect 00:18:09:1C:B7:80 
Attempting to connect to 00:18:09:1C:B7:80
Failed to connect: org.bluez.Error.Failed
I hope this is a bug that will be fixed quickly.

Are you sure your adapters are on? By default, bluez 5 turns your bluetooth adapters off. (If you run hciconfig from the bluez-utils package, you will see "DOWN" in the output if an adapter is off.)

So, there are two ways to turn it on:

sudo hciconfig hci0 up

Or

bluetoothctl
power on

I added a udev rule to turn on bluetooth adapters automatically. Then, devices can connect automatically. <https://bbs.archlinux.org/viewtopic.php?id=166362>

lervag · 2013-11-04 16:02:10

Thanks for the tip, however, I had already made sure that my adapter was turned on. When I run hciconfig, it says "UP RUNNING PSCAN".

To make things more clear, here is the output from bluetoothctl slightly more verbose:

---> bluetoothctl
[NEW] Controller B0:05:94:F2:59:6D vsl136 [default]
[NEW] Device 00:18:09:1C:B7:80 MDR-1RBT
[bluetooth]# show
Controller B0:05:94:F2:59:6D
...	Powered: yes ...
[bluetooth]# connect 00:18:09:1C:B7:80 
Attempting to connect to 00:18:09:1C:B7:80
[CHG] Device 00:18:09:1C:B7:80 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 00:18:09:1C:B7:80 Connected: no

Last edited by lervag (2013-11-04 16:06:16)

vlsd · 2013-11-05 01:29:19

I assume this is a blueman bug. I submitted a bug report here https://bugs.archlinux.org/index.php?do … k_id=37645

Edit: Since this was completely breaking bluetooth for me, I managed to get a workaround for my headset using pulseaudio-git, gnome-bluetooth and bluetoothctl. In short, I installed pulseaudio with bluez5 support, paired with bluetooth-wizard and connected using bluetoothctl. I put full details in a blog post here. Hope this helps someone!

Edit2: make sure your controller's power is on. I just spent half an hour thinking I broke something when in fact the controller was turned off by default at startup.

Last edited by vlsd (2013-11-15 20:25:24)

dna · 2013-11-12 09:29:18

I got the same issue. Instead of installing all this gnome-*** stuffs I simply installed bluez4 from extra instead of bluez and it worked fine.
Cheers

vlsd · 2013-11-12 16:22:10

dna wrote:

I got the same issue. Instead of installing all this gnome-*** stuffs I simply installed bluez4 from extra instead of bluez and it worked fine.
Cheers

This used to work before blueman started erroneously depending on bluez instead of bluez4. Did you force the replacement of bluez with bluez4 despite dependencies?

dojero · 2013-11-13 16:25:50

It's strange to me that this is such a difficult problem with Arch. It's the first time I've experienced this kind of thing without a proper solution. The major mistake, I think, was to move in the repositories from bluez4 to bluez(5) when bluez5 isn't ready for use yet. At a minimum, it's not ready and will (apparently) never be ready for ALSA. While pulseaudio is not listed as a dependency for bluez, it actually is.

For those of us who don't want to use pulse audio and would prefer to stay with alsa, bluez isn't an option. Simply add bluez to the IgnorePkg and stay with bluez4. You'll be asked if you want to skip blueman upgrade when you try a general update (pacman -Syu), and you simply say yes. Then your reliable bluez4 and blueman will continue to work with alsa and your bluetooth devices.

asdil12 · 2013-11-18 14:16:40

To get blueman working again, run:

pacman -Sdd bluez4
systemctl restart bluetooth

lervag · 2013-11-18 15:00:19

Thank you, this worked for me!

Although, it really does not look like a permanent solution. It seems to me that there are two issues that should be fixed:

1. blueman should depend on bluez4, not bluez
2. blueman should be updated so that it is compatible with bluez5 (bluez), and only then should the dependency be changed to bluez

vlsd · 2013-11-18 20:13:21

I figured out why I couldn't pair with bluetoothctl before. The agent needs to be turned on before pairing and then both pairing and connecting work well. No need to gnome-***

tchebb · 2015-06-05 22:14:32

Sorry to revive this old thread, but it's the top result on Google for the blueman-manager error

There is an instance already running

This is caused by a stale cache file, and can be fixed by running

rm ~/.cache/blueman-manager-*

WorMzy · 2015-06-05 22:52:17

Hi tchebb, welcome to the Arch Linux forums. Thank you for sharing that, but I think that hint would be better placed on the wiki.

I'm going to close this thread now, since it's quite old.

https://wiki.archlinux.org/index.php/Fo … bumping.22

Closing.

Arch Linux

#1 2013-11-02 16:09:01

Blueman manager won't start after update.

#2 2013-11-02 18:11:00

Re: Blueman manager won't start after update.

#3 2013-11-02 18:19:13

Re: Blueman manager won't start after update.

#4 2013-11-02 18:29:53

Re: Blueman manager won't start after update.

#5 2013-11-02 23:20:06

Re: Blueman manager won't start after update.

#6 2013-11-02 23:43:27

Re: Blueman manager won't start after update.

#7 2013-11-04 02:10:09

Re: Blueman manager won't start after update.

#8 2013-11-04 13:43:01

Re: Blueman manager won't start after update.

#9 2013-11-04 15:21:42

Re: Blueman manager won't start after update.

#10 2013-11-04 16:02:10

Re: Blueman manager won't start after update.

#11 2013-11-05 01:29:19

Re: Blueman manager won't start after update.

#12 2013-11-12 09:29:18

Re: Blueman manager won't start after update.

#13 2013-11-12 16:22:10

Re: Blueman manager won't start after update.

#14 2013-11-13 16:25:50

Re: Blueman manager won't start after update.

#15 2013-11-18 14:16:40

Re: Blueman manager won't start after update.

#16 2013-11-18 15:00:19

Re: Blueman manager won't start after update.

#17 2013-11-18 20:13:21

Re: Blueman manager won't start after update.

#18 2015-06-05 22:14:32

Re: Blueman manager won't start after update.

#19 2015-06-05 22:52:17

Re: Blueman manager won't start after update.

Board footer