dialog with error "org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.blueman.Mechanism: Permission denied" displayed after login

Bug #1542723 reported by Karl-Philipp Richter
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After login a dialog with error `org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.blueman.Mechanism: Permission denied` is displayed. It doesn't seem to relate to any error because bluetooth functions fine and it's unhelpful because it doesn't contain instructions what to do.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: bluetooth 5.35-0ubuntu2
Uname: Linux 4.3.0-040300-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 6 21:42:53 2016
InstallationDate: Installed on 2013-10-17 (842 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO IdeaPad U410
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-040300-generic root=UUID=8c488557-8173-43a2-a3a8-df0a24695c08 ro rootflags=subvol=ubuntu-main-root quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to wily on 2015-11-19 (79 days ago)
dmi.bios.date: 09/25/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 65CN90WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: 31900003WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo U410
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65CN90WW:bd09/25/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr31900003WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410:
dmi.product.name: IdeaPad U410
dmi.product.version: Lenovo U410
dmi.sys.vendor: LENOVO
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 84:A6:C8:63:22:B5 ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING PSCAN ISCAN
  RX bytes:1822601 acl:3765 sco:0 events:286 errors:0
  TX bytes:8558 acl:199 sco:0 commands:72 errors:0

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems like an issue with blueman which is not installed by default with Ubuntu

affects: bluez (Ubuntu) → blueman (Ubuntu)
Revision history for this message
Terrance (kato223) wrote :

I just had this error, and I was able to correct it.

This error is because of incorrect permissions to the dbus-daemon-launch-helper

To fix it:

sudo chmod 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper

sudo chown root:messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
Tom Fields (udzelem) wrote :

*bump* Still present in Ubuntu 18.10.

Revision history for this message
Tom Fields (udzelem) wrote :

I too can confirm this is an issue when installing the blueman application.

Revision history for this message
Fabiouch (fabiouch) wrote :

Had the same error message on my computer today;
it seems like blueman crashes during session start when it can't reach dbus.
Afterwards, blueman simply restarts as user and starts everything it needs in the userspace too, so everything SEEM to work normally...

You can fix this with `sudo apt-get install --reinstall dbus`

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.