blueman permissions problem

musicmastamike · 2009-02-18 19:57:16

pacman recently decided to replace bluez-gnome with blueman. That's fine with me. However, whenever I try to start up blueman, I get the following output:

michael@horsepower:~$ blueman-applet 
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
_________
load_plugins (/usr/bin/blueman-applet:115)
['Headset'] 
_________
__setattr__ (/usr/bin/blueman-applet:156)
bt_off False 
_________
__init__ (/usr/bin/blueman-applet:60)
Unable to initialize obex-data-server 
_________
load_nap_settings (/usr/bin/blueman-applet:136)
Loading NAP settings 
_________
on_dbus_name_owner_change (/usr/bin/blueman-applet:220)
org.bluez owner changed to :1.1 
/usr/lib/python2.6/site-packages/blueman/bluez/Manager.py:41: DeprecationWarning: object.__new__() takes no parameters
  cls._instance = super(Manager, cls).__new__(cls, *args, **kwargs)
ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.DBus.Introspectable" member "Introspect" error name "(unset)" destination "org.bluez")
_________
update_menuitems (/usr/lib/python2.6/site-packages/blueman/gui/applet/DiscvManager.py:101)
warning: Adapter is None 
_________
set_nap (/usr/lib/python2.6/site-packages/blueman/main/applet/NetworkManager.py:106)
set nap False 
_________
manager_init (/usr/bin/blueman-applet:179)
org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.bluez.Manager" member "ListAdapters" error name "(unset)" destination "org.bluez") 
_________
manager_init (/usr/bin/blueman-applet:179)
Bluez DBus API not available. Listening for DBus name ownership changes

It seems there are some DBus permissions problems. Can someone help me, please?

killajoe · 2009-02-20 15:27:51

is dbus running?

/etc/rc.d/dbus start

musicmastamike · 2009-02-20 15:35:45

Thanks for the reply. Yes, I have DBus and HAL both running.

musicmastamike · 2009-02-20 15:39:29

Update: It runs fine if I run it as root. Are there any groups I need to put myself in or something of that sort?

Nepherte · 2009-02-20 16:51:41

Did you start the bluetooth service?

musicmastamike · 2009-02-20 16:56:23

Yes, bluetooth is running. As I said, everything is running fine when I start blueman as root, but I shouldn't have to do that....

killajoe · 2009-02-20 22:09:28

group: uucp /dev/ttyS[0-9] /dev/tts/[0-9] Serial & USB devices such as modems,handhelds,RS232/serial ports.

NeoXP · 2009-02-21 19:24:55

killajoe wrote:

group: uucp /dev/ttyS[0-9] /dev/tts/[0-9] Serial & USB devices such as modems,handhelds,RS232/serial ports.

Tried your suggestion, but it didn't help.

As you may have figured out, I have the same problem, only get the same messages when starting blueman-manager.

When I use Wammu to manage my phone, I get a connection. So I assume that bluetooth is working alright.

Any more suggestions?

Last edited by NeoXP (2009-02-21 19:26:23)

musicmastamike · 2009-02-22 15:46:18

Yeah, I concur that adding myself to group uucp doesn't work. Still running as root right now...

walmis · 2009-02-25 15:33:16

<!-- This configuration file specifies the required security policies
     for Bluetooth core daemon to work. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- ../system.conf have denied everything, so we just punch some holes -->

  <policy user="root">
    <allow own="org.bluez"/>
    <allow send_destination="org.bluez"/>
    <allow send_interface="org.bluez.Agent"/>
  </policy>

  <policy at_console="true">
    <allow send_destination="org.bluez"/>
  </policy>

  <policy context="default">
    <deny send_destination="org.bluez"/>
  </policy>

</busconfig>

According to this, i suspect that something is wrong with consolekit, are you using gdm? If not, check this http://wiki.archlinux.org/index.php/Net … er_0.7#KDE

If everything else fails, hack this file it's under /etc/dbus-1/system.d/bluetooth.conf

Last edited by walmis (2009-02-25 15:38:15)

NeoXP · 2009-02-25 15:52:19

@ walmis

Thxs for pointing me in this direction. In the following line:

<policy user="root">

I changed root to my own username and voila... Blueman is working.

walmis · 2009-02-25 16:39:12

That's not a very good solution, because other apps may be broken too. I suggest you try to fix consolekit...

musicmastamike · 2009-02-25 17:09:59

walmis wrote:

That's not a very good solution, because other apps may be broken too. I suggest you try to fix consolekit...

I tried adding ck-launch-session to my autostart.sh before blueman-applet, but that didn't change anything. I'm using Openbox with Slim.

walmis · 2009-02-25 17:13:34

try this:

Install Consolekit and add the following line to /etc/pam.d/ck
session optional pam_ck_connector.so

NeoXP · 2009-02-25 17:21:51

walmis wrote:

That's not a very good solution, because other apps may be broken too. I suggest you try to fix consolekit...

What would be a better solution then? I have no experience with consolekit.

walmis · 2009-02-25 18:43:16

NeoXP wrote:

walmis wrote:
That's not a very good solution, because other apps may be broken too. I suggest you try to fix consolekit...
What would be a better solution then? I have no experience with consolekit.

Either start the session using ck-launch-session or add

 session optional pam_ck_connector.so

to /etc/pam.d

musicmastamike · 2009-02-25 19:41:37

Awesome! Finally got this to work by adding

 session optional pam_ck_connector.so

to /etc/pam.d/slim.

NeoXP · 2009-02-25 20:55:09

musicmastamike wrote:

Awesome! Finally got this to work by adding
 session optional pam_ck_connector.so
to /etc/pam.d/slim.

This worked for me to, thx walmis

JunglePenguin · 2009-03-25 12:40:47

Thanks, it worked for me too.

archbawks · 2013-04-29 15:06:28

walmis wrote:

Either start the session using ck-launch-session or add
 session optional pam_ck_connector.so
to /etc/pam.d

+1

Arch Linux

#1 2009-02-18 19:57:16

blueman permissions problem

#2 2009-02-20 15:27:51

Re: blueman permissions problem

#3 2009-02-20 15:35:45

Re: blueman permissions problem

#4 2009-02-20 15:39:29

Re: blueman permissions problem

#5 2009-02-20 16:51:41

Re: blueman permissions problem

#6 2009-02-20 16:56:23

Re: blueman permissions problem

#7 2009-02-20 22:09:28

Re: blueman permissions problem

#8 2009-02-21 19:24:55

Re: blueman permissions problem

#9 2009-02-22 15:46:18

Re: blueman permissions problem

#10 2009-02-25 15:33:16

Re: blueman permissions problem

#11 2009-02-25 15:52:19

Re: blueman permissions problem

#12 2009-02-25 16:39:12

Re: blueman permissions problem

#13 2009-02-25 17:09:59

Re: blueman permissions problem

#14 2009-02-25 17:13:34

Re: blueman permissions problem

#15 2009-02-25 17:21:51

Re: blueman permissions problem

#16 2009-02-25 18:43:16

Re: blueman permissions problem

#17 2009-02-25 19:41:37

Re: blueman permissions problem

#18 2009-02-25 20:55:09

Re: blueman permissions problem

#19 2009-03-25 12:40:47

Re: blueman permissions problem

#20 2013-04-29 15:06:28

Re: blueman permissions problem

Board footer