Mailinglist Archive: opensuse-bugs (5220 mails)

< Previous Next >
[Bug 470640] bluez breaks due to dbus security update
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 3 Apr 2009 10:19:52 -0600 (MDT)
  • Message-id: <20090403161952.3494ECC7D0@xxxxxxxxxxxxxxxxxxxxxx>

User novell@xxxxxxxxxxxxxxxx added comment

Bernd Jantzen <novell@xxxxxxxxxxxxxxxx> changed:

What |Removed |Added
CC| |novell@xxxxxxxxxxxxxxxx

--- Comment #38 from Bernd Jantzen <novell@xxxxxxxxxxxxxxxx> 2009-04-03
10:19:51 MDT ---
I had the same problem as described above in openSUSE 10.3. After the update of
bluez-utils to 3.18-13.4 my kbluetooth succeeded to connect again to the
bluetooth adapter. But the password exchange with my mobile phone failed. The
error message in /var/log/messages was as follows:

dbus-daemon: Rejected send message, 1 matched rules; type="method_call",
sender=":1.9" (uid=0 pid=6788 comm="/usr/sbin/hcid -s -f
/etc/bluetooth/hcid.conf ") interface="org.bluez.PasskeyAgent" member="Request"
error name="(unset)" requested_reply=0 destination=":1.12" (uid=
1000 pid=6806 comm="kbluetooth "))

I guess that this type of message is still rejected by the dbus-daemon because
"org.bluez" is neither the sender nor the receiver. And in addition, the sender
is root (uid=0) and not a console-user (so probably the dbus-rules with
at_console="true" do not match).

I only solved this issue by adding the one line at the end of the <policy
user="root"> section in /etc/dbus-1/system.d/bluetooth.conf:

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

(The last line of this policy-section is from me.)
I do not know if this is the best solution. But now the password exchange
between my laptop and the mobile phone works again. Without this additional
line, just with the update of bluez-utils, it did not work.

So, will there be another update to bluez-utils fixing this issue? (For
openSUSE 10.3; maybe this is already fixed for 11.*.)
Shall I mark this bug as "reopened" as long as this issue is not fixed?

Thanks in advance for your help!

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >