blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.54" (uid=1000 pid=4182 comm="/usr/bin/python3 /usr/bin/blueman-applet ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=843 comm="/usr/lib/bluetooth/bluetoothd ")

[Eric Schaffner]

Crash occurred at login of fresh Xubuntu install.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: blueman 2.0.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
Uname: Linux 4.8.0-14-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Thu Sep 22 10:22:23 2016
ExecutablePath: /usr/bin/blueman-applet
InstallationDate: Installed on 2016-09-22 (0 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-applet
PythonArgs: ['/usr/bin/blueman-applet']
SourcePackage: blueman
Title: blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.54" (uid=1000 pid=4182 comm="/usr/bin/python3 /usr/bin/blueman-applet ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=843 comm="/usr/lib/bluetooth/bluetoothd ")
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1546873, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.