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: __new__ exception_type: dbus.exceptions.DBusException executable: /usr/bin/blueman-applet interpreter: python3-3.6.6-1.fc28.x86_64 kernel: 4.17.7-200.fc28.x86_64 runlevel: 3 5 type: Python3 uid: 1000 Truncated backtrace: bus.py:122:__new__:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /run/user/1000/bus: Connection refused 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 29, in __init__ self.DbusSvc = DbusService("org.blueman.Applet", "/") File "/usr/lib/python3.6/site-packages/blueman/main/DbusService.py", line 15, in __init__ self.bus = bus() File "/usr/lib64/python3.6/site-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib64/python3.6/site-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib64/python3.6/site-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /run/user/1000/bus: Connection refused Local variables in innermost frame: mainloop: None address_or_type: 0 cls: <class 'dbus._dbus.SessionBus'>
Created attachment 1470832 [details] File: backtrace
Created attachment 1470833 [details] File: cgroup
Created attachment 1470834 [details] File: cpuinfo
Created attachment 1470835 [details] File: environ
Created attachment 1470836 [details] File: mountinfo
Created attachment 1470837 [details] File: namespaces
Created attachment 1470838 [details] File: open_fds
Seeing this error on linux version 4.18.17-100.fc27.x86_64 #1 SMP Mon Nov 5 19:05:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux This bug goes back to at least FC26 and early 2017. I tried a few possible fixes but they did not fix this issue. Is the latest python compiler being distrubuted? I show "python3-testing" installed as part of fc27. The most recent version of python is version 3.6 [root@BRSINC-01Fed bluetooth]# blueman-applet blueman-applet version 2.1.alpha1 starting 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 29, in __init__ self.DbusSvc = DbusService("org.blueman.Applet", "/") File "/usr/lib/python3.6/site-packages/blueman/main/DbusService.py", line 15, in __init__ self.bus = bus() File "/usr/lib64/python3.6/site-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib64/python3.6/site-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib64/python3.6/site-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. python3 version audit-libs-python3.x86_64 2.8.3-1.fc27 @updates libpeas-loader-python3.x86_64 1.22.0-1.fc27 @fedora libselinux-python3.x86_64 2.7-3.fc27 @updates libsemanage-python3.x86_64 2.7-3.fc27 @updates newt-python3.x86_64 0.52.20-3.fc27 @fedora policycoreutils-python3.x86_64 2.7-6.fc27 @updates -testing python3.x86_64 3.6.5-1.fc27 @updates -testing python3-IPy.noarch 0.81-20.fc27 @fedora python3-PyXB.noarch 1.2.6-1.fc27 @fedora python3-PyYAML.x86_64 3.12-5.fc27 @fedora python3-abrt.x86_64 2.10.7-1.fc27 @updates python3-abrt-addon.x86_64 2.10.7-1.fc27 @updates python3-asn1crypto.noarch 0.23.0-1.fc27 @updates python3-augeas.noarch 0.5.0-9.fc27 @fedora python3-beautifulsoup4.noarch 4.6.0-2.fc27.1 @updates -testing python3-bind.noarch 32:9.11.4-3.P2.fc27 @updates -testing
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.