Description of problem: Attempt to open bluetooth manager from Applications menu Version-Release number of selected component: blueman-2.1-0.6.alpha1.fc26 Additional info: reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.11.3-300.fc26.armv7hl runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/blueman/main/Manager.py", line 86, in on_dbus_name_vanished self.Applet.disconnect(self._applet_sig) AttributeError: 'Blueman' object has no attribute 'Applet' Local variables in innermost frame: name: 'org.bluez' _connection: <Gio.DBusConnection object at 0xb49636c0 (GDBusConnection at 0x81016858)> self: <Manager.Blueman object at 0xb672b148 (blueman+main+Manager+Blueman at 0x8108b190)>
Created attachment 1290113 [details] File: backtrace
Created attachment 1290114 [details] File: cgroup
Created attachment 1290115 [details] File: cpuinfo
Created attachment 1290116 [details] File: environ
Created attachment 1290117 [details] File: mountinfo
Created attachment 1290118 [details] File: namespaces
Created attachment 1290119 [details] File: open_fds
Similar problem has been detected: No idea, i just tryd to open up bluetooth manager and there was this error reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.11.7-300.fc26.x86_64 package: blueman-2.1-0.5.alpha1.fc26 reason: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Got this reporting bug while desktop is launched. Simply to say after OS is loaded. reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.11.9-300.fc26.x86_64 package: blueman-2.1-0.5.alpha1.fc26 reason: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' runlevel: N 5 type: Python3 uid: 1001
Similar problem has been detected: Started Blueman reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.11.9-300.fc26.x86_64 package: blueman-2.1-0.5.alpha1.fc26 reason: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: I tried to set up a device reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.11.10-300.fc26.x86_64 package: blueman-2.1-0.5.alpha1.fc26 reason: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' runlevel: N 5 type: Python3 uid: 1000
Similar problem has been detected: Just upgraded from fedora to 25, rebooted and logged in. reporter: libreport-2.9.1 cmdline: python3.6 /usr/bin/blueman-manager crash_function: on_dbus_name_vanished exception_type: AttributeError executable: /usr/bin/blueman-manager kernel: 4.13.15-200.fc26.x86_64 package: blueman-2.1-0.5.alpha1.fc26 reason: Manager.py:86:on_dbus_name_vanished:AttributeError: 'Blueman' object has no attribute 'Applet' runlevel: N 5 type: Python3 uid: 1000
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.