Description of problem: 1. Install XFCE desktop with netinst DVD for rawhide. 2. Input username and password on login screen. 3. A notification will be displayed that an error occurred for Blueman. Version-Release number of selected component: blueman-2.1-0.3.alpha1.fc26 Additional info: reporter: libreport-2.8.0 cmdline: python3 /usr/bin/blueman-applet executable: /usr/bin/blueman-applet kernel: 4.8.0-0.rc7.git4.1.fc26.x86_64 pkg_vendor: Fedora Project runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: Manager.py:40:_init:GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.bluez: Timeout was reached (24) Traceback (most recent call last): File "/usr/bin/blueman-applet", line 27, in <module> BluemanApplet() File "/usr/lib/python3.5/site-packages/blueman/main/Applet.py", line 33, in __init__ self.Manager = Bluez.Manager() File "/usr/lib/python3.5/site-packages/blueman/bluez/Manager.py", line 30, in __new__ cls._instance._init(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blueman/bluez/Manager.py", line 40, in _init self.__bus_name, '/', None, None, None) GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.bluez: Timeout was reached (24) Local variables in innermost frame: __class__: <class 'blueman.bluez.Manager.Manager'> self: <Manager.Manager object at 0x7f999b5c35e8 (blueman+bluez+Manager+Manager at 0x55f61a3226a0)>
Created attachment 1205169 [details] File: backtrace
Created attachment 1205170 [details] File: environ
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.