Bug 1222113 - [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.
Summary: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.syste...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 19:16 UTC by Christian Stadelmann
Modified: 2015-05-15 21:03 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-15 19:20:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output of journalctl of the message itself and some lines before and after (19.72 KB, text/plain)
2015-05-15 19:16 UTC, Christian Stadelmann
no flags Details

Description Christian Stadelmann 2015-05-15 19:16:25 UTC
Created attachment 1026019 [details]
output of journalctl of the message itself and some lines before and after

Description of problem:
On a machine with bluetooth permanently disabled I see this error message printed to journal every few hours:

dbus[976]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
dbus[976]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory.
pulseaudio[2447]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.

Version-Release number of selected component (if applicable):
pulseaudio, pulseaudio-module-bluetooth 6.0-2.fc22
dbus 1:1.8.16-1.fc22
bluez, bluez-libs 5.29-2.fc22
gnome-bluetooth, gnome-bluetooth-libs 1:3.16.1-1.fc22

How reproducible:
on this hardware: several times per day

Steps to Reproduce:
just log in to your gnome session (X11 or wayland). It will happen on login.

Additional info:
See attached log

Comment 1 Rex Dieter 2015-05-15 19:20:11 UTC
If you choose to forcibly disable bluez5 service, I'd recommend you then also
* remove pulseaudio-module-bluetooth rpm
or
* comment out the entries in /etc/pulse/default.pa that refer to module-bluetooth-* stuff

Comment 2 Christian Stadelmann 2015-05-15 21:03:53 UTC
Sorry for wasting your time. I didn't remember I disabled bluetooth.service, I thought I just disabled it in gnome shell / gnome-contol-center.


Note You need to log in before you can comment on or make changes to this bug.