Arch Linux

Garret

Member

From: Palermo, Italy

Registered: 2006-07-09

Posts: 172

Blueman doesn't show at startup even with bluetooth daemon started

I use archlinux x86_64 with these packages:
bluez 4.69
blueman 1.21

I start the bluetooth daemon at startup putting it inside /etc/rc.conf

On LXDE I configured the autostart config file with this command:

@blueman-applet

But I don't see the applet on the system tray when I start the LXDE session.

Trying to load it manually I get this and the icon continues not showing up:

[garret@laptop ~]$ blueman-applet
** Message: pygobject_register_sinkfunc is deprecated (GtkWindow)
** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible)
** Message: pygobject_register_sinkfunc is deprecated (GtkObject)
Loading configuration plugins
_________
<module> (/usr/lib/python2.6/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf
Using file config backend
there is an instance already running
_________
save (/usr/lib/python2.6/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 0x141e5f0 (blueman+plugins+ConfigPlugin+ConfigPlugin at 0x10b08e0)>> ignored

I found that if I manually restart the bluetooth daemon the blueman-applet appears on the system tray:

[garret@laptop ~]$ sudo /etc/rc.d/bluetooth start
Password:
:: Starting bluetooth subsystem: bluetoothd [DONE]

So after this operation the blueman-applet takes place on the system tray.

Now I want the blueman-applet load at startup.

Did you experienced this issue?

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Blueman doesn't show at startup even with bluetooth daemon started

start dbus

---

Give what you have. To someone, it may be better than you dare to think.

Garret

Member

From: Palermo, Italy

Registered: 2006-07-09

Posts: 172

Re: Blueman doesn't show at startup even with bluetooth daemon started

start dbus

In my rc.conf I have the hal daemon too. I read that with hal the dbus daemon it's not necessary.

shemz

Member

Registered: 2010-04-23

Posts: 135

Re: Blueman doesn't show at startup even with bluetooth daemon started

Start the applet with some delay to allow loading of the daemon and Lxpanel.

Put this in your openbox autostart instead:

(sleep 15s && blueman-applet) &

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Blueman doesn't show at startup even with bluetooth daemon started

Make sure you have sufficient rights (e.g. your desktop environment should be launched through ck-launch-session). You also might want to check this topic.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Garret

Member

From: Palermo, Italy

Registered: 2006-07-09

Posts: 172

Re: Blueman doesn't show at startup even with bluetooth daemon started

Make sure you have sufficient rights (e.g. your desktop environment should be launched through ck-launch-session). You also might want to check this topic.

I start LXDE with ck-launch-session
I added the

session optional pam_ck_connector.so

to /etc/pam.d/login as they say in that topic but it doesn't work for me

Start the applet with some delay to allow loading of the daemon and Lxpanel.
Put this in your openbox autostart instead:

(sleep 15s && blueman-applet) &

I tried this solution too without results