Description of problem: in the time of each system start Version-Release number of selected component: 1:blueman-2.1-0.9.alpha2.fc28 Additional info: reporter: libreport-2.9.5 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet interpreter: python3-3.6.6-1.fc28.x86_64 kernel: 4.17.9-200.fc28.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Chyba při volání StartServiceByName pro 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: Chyba při volání StartServiceByName pro 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 0x7fb51e464678 (blueman+bluez+Manager+Manager at 0x55b37872b700)> __class__: <class 'blueman.bluez.Manager.Manager'>
Created attachment 1471896 [details] File: backtrace
Created attachment 1471897 [details] File: cgroup
Created attachment 1471898 [details] File: cpuinfo
Created attachment 1471899 [details] File: environ
Created attachment 1471900 [details] File: mountinfo
Created attachment 1471901 [details] File: namespaces
Created attachment 1471902 [details] File: open_fds
Similar problem has been detected: every in time of start system. reporter: libreport-2.9.5 cmdline: python3 /usr/bin/blueman-applet crash_function: __init__ exception_type: GLib.GError executable: /usr/bin/blueman-applet interpreter: python3-3.6.6-1.fc28.x86_64 kernel: 4.18.12-200.fc28.x86_64 package: 1:blueman-2.1-0.9.alpha2.fc28 reason: Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Chyba při volání StartServiceByName pro 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 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.