[SOLVED] - blueman in openbox not working

theta · 2011-07-31 13:20:28

Hi, I recently switched over from gnome to openbox with a fresh install and have kernel 2.6.39. I installed blueman for accesing my phone and bluetooth headphones which were earlier working seamlessly with gnome3. Now I can't seem to get blueman to work. I think I have missed out some optional dependencies
I get the following log in stdout when I start blueman-applet

<module> (/usr/lib/python2.7/site-packages/blueman/main/Config.py:20)
Skipping plugin Gconf
No module named gconf 
Using file config backend
_________
SetAdapter (/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py:300)
None 
ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.13" (uid=1000 pid=1225 comm="/usr/bin/python2 /usr/bin/blueman-assistant ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=825 comm="/usr/sbin/bluetoothd ")
Traceback (most recent call last):
  File "/usr/bin/blueman-assistant", line 399, in <module>
    Assistant()
  File "/usr/bin/blueman-assistant", line 119, in __init__
    self.dev_widget = DeviceSelectorWidget()
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceSelectorWidget.py", line 38, in __init__
    self.List = devlist = DeviceSelectorList(adapter)
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceSelectorList.py", line 49, in __init__
    DeviceList.__init__(self, adapter, data)
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py", line 121, in __init__
    self.SetAdapter(adapter)
  File "/usr/lib/python2.7/site-packages/blueman/gui/DeviceList.py", line 331, in SetAdapter
    except dbus.DBusServiceUnknownError:
AttributeError: 'module' object has no attribute 'DBusServiceUnknownError'
_________
save (/usr/lib/python2.7/site-packages/blueman/plugins/config/File.py:117)
Saving config 
Exception AttributeError: "'DeviceSelectorWidget' object has no attribute 'List'" in <bound method DeviceSelectorWidget.__del__ of <DeviceSelectorWidget object at 0x2695640 (GtkVBox at 0x26d8960)>> ignored
Exception AttributeError: "'NoneType' object has no attribute 'Bus'" in <bound method File.__del__ of <File object at 0x293bfa0 (blueman+plugins+ConfigPlugin+ConfigPlugin at 0x231f880)>> ignored
_________
child_closed (/usr/lib/python2.7/site-packages/blueman/Functions.py:137)
/usr/bin/blueman-assistant closed

I have dbus running but not hal. Is hal a requirement for blueman by any chance or is this a dbus dependency problem, or something else at all?

Last edited by theta (2011-08-04 17:49:35)

Stebalien · 2011-07-31 17:54:50

How are you starting openbox? You need a dbus session bus. If you are using xinit or startx, edit your ~/.xinitrc and change `exec openbox-session` to `exec dbus-launch openbox-session`.

Last edited by Stebalien (2011-07-31 17:56:14)

theta · 2011-07-31 17:59:30

I got it working by doing a simple

sudo blueman-applet

but this wasn't the case with gnome. How do I now get it to work without the sudo. Do I need to add my user to a particular group or change permissions of blueman-applet binary?

theta · 2011-07-31 18:00:49

Sorry Stebalien, was typing when you posted. I will try the 'exec dbus-launch openbox-session' also.

theta · 2011-07-31 18:08:13

Nope that didn't work either.

kmeng · 2011-08-03 22:22:02

does work since version 4.95.
version 4.94 is good.

.:B:. · 2011-08-03 22:35:09

You shouldn't need sudo to get blueman running. Using Openbox myself here, works just fine. Just make sure you launch Openbox the right way - if your login manager supports consolekit, you can just use this:

exec /usr/bin/openbox-session

If not, you need this:

exec ck-launch-session /usr/bin/openbox-session

theta · 2011-08-04 17:49:13

.:B:. wrote:

You shouldn't need sudo to get blueman running. Using Openbox myself here, works just fine. Just make sure you launch Openbox the right way - if your login manager supports consolekit, you can just use this:
exec /usr/bin/openbox-session
If not, you need this:
exec ck-launch-session /usr/bin/openbox-session

Thanks, I wasn't aware about the console kit to authorize sessions as I had been using gnome. This solved my problem.

Arch Linux

#1 2011-07-31 13:20:28

[SOLVED] - blueman in openbox not working

#2 2011-07-31 17:54:50

Re: [SOLVED] - blueman in openbox not working

#3 2011-07-31 17:59:30

Re: [SOLVED] - blueman in openbox not working

#4 2011-07-31 18:00:49

Re: [SOLVED] - blueman in openbox not working

#5 2011-07-31 18:08:13

Re: [SOLVED] - blueman in openbox not working

#6 2011-08-03 22:22:02

Re: [SOLVED] - blueman in openbox not working

#7 2011-08-03 22:35:09

Re: [SOLVED] - blueman in openbox not working

#8 2011-08-04 17:49:13

Re: [SOLVED] - blueman in openbox not working

Board footer