[Bug 1001055] New: bluetooth service fails
http://bugzilla.opensuse.org/show_bug.cgi?id=1001055 Bug ID: 1001055 Summary: bluetooth service fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jdelvare@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I see the following error messages in my logs at boot time: dbus[1036]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' systemd[1]: Starting Bluetooth service... bluetoothd[2254]: Bluetooth daemon 5.35 dbus[1036]: [system] Successfully activated service 'org.bluez' systemd[1]: Started Bluetooth service. bluetoothd[2254]: Failed to access management interface bluetoothd[2254]: Adapter handling initialization failed systemd[1]: bluetooth.service: main process exited, code=exited, status=1/FAILURE systemd[1]: Unit bluetooth.service entered failed state. pulseaudio[1956]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) This is only a minor annoyance for me as there is no bluetooth hardware on this machine. However I believe the service should not fail in that case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001055 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seyfried@b1-systems.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1001055 http://bugzilla.opensuse.org/show_bug.cgi?id=1001055#c3 Stefan Seyfried <seife@novell.slipkontur.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Stefan Seyfried <seife@novell.slipkontur.de> --- Closing as this is an cosmetic issue. And even though I like to fix these, the long time of no action clearly shows that it will not happen for this one :-) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com