This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
** Tags added: bluez-classic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/297635
Title:
Any user can manage bluetooth devices
To manage notifications about this bug go to:
** Tags added: intrepid
--
Any user can manage bluetooth devices
https://bugs.launchpad.net/bugs/297635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Baptiste,
I think the D-BUS configuration is alright. We certainly don't want to
remove at_console, this would break it for any normal user, too.
What we could do is to have bluez use PolicyKit instead of just relying
on the very coarse at_console D-BUS policy. Then we can remove the bluez
TBH, bluez should probably provide the concept of system and user
connections much like network manager does
--
Any user can manage bluetooth devices
https://bugs.launchpad.net/bugs/297635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry to paste dbus conf from bluetooth:
-8---
policy user=root
allow own=org.bluez/
allow send_destination=org.bluez/
!-- allow root to send to agents --
allow send_interface=org.bluez.Agent/
/policy
!-- allow users at
** Summary changed:
- Guest user can manage bluetooth devices
+ Any user can manage bluetooth devices
--
Any user can manage bluetooth devices
https://bugs.launchpad.net/bugs/297635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
