Description of problem: I had just run an update and then re-booted. Up popped the error message. Version-Release number of selected component: blueman-2.1-0.8.alpha2.fc27 Additional info: reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.6-300.fc27.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) Traceback (most recent call last): File "/usr/bin/blueman-applet", line 42, in <module> BluemanApplet() File "/usr/lib/python3.6/site-packages/blueman/main/Applet.py", line 23, in __init__ self.Manager = Bluez.Manager() File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 16, in __call__ cls._instance = super().__call__(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 38, in __init__ self.__bus_name, '/', None, None, None) GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) Local variables in innermost frame: self: <Manager.Manager object at 0x7f5deadef678 (blueman+bluez+Manager+Manager at 0x55c579bbd260)> __class__: <class 'blueman.bluez.Manager.Manager'>
Created attachment 1370477 [details] File: backtrace
Created attachment 1370478 [details] File: cgroup
Created attachment 1370479 [details] File: cpuinfo
Created attachment 1370480 [details] File: environ
Created attachment 1370481 [details] File: mountinfo
Created attachment 1370482 [details] File: namespaces
Created attachment 1370483 [details] File: open_fds
Similar problem has been detected: Started computer and logged in. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.7-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: I just logged in after doing a package update, and a notification popped up saying that blueman had failed. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.8-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
*** Bug 1532317 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Happens at login. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.11-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: fedora 27 on virtualbox on mac. Just upgraded from Fedora 25. Logged in. Typed "su". Bug. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.13-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Shows up in my bug report, 42 occurances. reporter: libreport-2.9.3 crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.6-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Fedora 27 under virtualbox on a Mac. Booted, logged in, blueman failed. There was also an SE Linux complaint at the same time. May be related. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.13-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
*** Bug 1541018 has been marked as a duplicate of this bug. ***
*** Bug 1541219 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This problem occurs on every system startup. I do not have bluetooth adapter in my PC. reporter: libreport-2.9.3 crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.16-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Just has been an ongoing problem with this application for the last past 2 weeks. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.18-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: This happened on booting (immediately after updating from Fedora 26 to Fedora 27). reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.15.8-300.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 10169
Similar problem has been detected: It appears everytime after graphical log-in. System is after dnf system upgrade from Fedora 25 to Fedora 27 through Fedora 26. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.15.8-300.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: started blueman-adapters from the main menu. Abrt triggered all of a sudden reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.15.7-300.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1001
Similar problem has been detected: This error occurred after a reboot and console login (mate). reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.16.7-200.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 9777
*** Bug 1582868 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I did nothing I can think of specifically . reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.16.9-200.fc27.i686 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Crashed on startup reporter: libreport-2.9.5 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.14.6-300.fc27.x86_64 package: blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
*** Bug 1601474 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Rebooted the system. The error occurred immediately after login. reporter: libreport-2.9.3 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet kernel: 4.18.16-100.fc27.x86_64 package: 1:blueman-2.1-0.8.alpha2.fc27 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20) runlevel: N 5 type: Python3 uid: 1000
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.