Version-Release number of selected component: blueman-2.0.4-1.fc25 Additional info: reporter: libreport-2.7.0 cmdline: python3 /usr/bin/blueman-applet executable: /usr/bin/blueman-applet kernel: 4.6.0-0.rc2.git4.1.fc25.x86_64 reproducible: Not sure how to reproduce the problem runlevel: unknown type: Python3 uid: 1000 Truncated backtrace: connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out Traceback (most recent call last): File "/usr/lib64/python3.5/site-packages/dbus/bus.py", line 175, in activate_name_owner return self.get_name_owner(bus_name) File "/usr/lib64/python3.5/site-packages/dbus/bus.py", line 361, in get_name_owner 's', (bus_name,), **keywords) File "/usr/lib64/python3.5/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.bluez': no such name During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/blueman-applet", line 121, in <module> BluemanApplet() File "/usr/bin/blueman-applet", line 63, in __init__ self.Plugins.Load() File "/usr/lib/python3.5/site-packages/blueman/main/PluginManager.py", line 90, in Load __import__(self.module_path.__name__ + ".%s" % plugin, None, None, []) File "/usr/lib/python3.5/site-packages/blueman/plugins/applet/DBusService.py", line 12, in <module> from blueman.main.applet.BluezAgent import AdapterAgent File "/usr/lib/python3.5/site-packages/blueman/main/applet/BluezAgent.py", line 23, in <module> from blueman.bluez.Agent import Agent, AgentMethod File "/usr/lib/python3.5/site-packages/blueman/bluez/Agent.py", line 48, in <module> class Agent(dbus.service.Object): File "/usr/lib/python3.5/site-packages/blueman/bluez/Agent.py", line 56, in Agent @AgentMethod File "/usr/lib/python3.5/site-packages/blueman/bluez/Agent.py", line 38, in AgentMethod if BlueZInterface.get_interface_version()[0] < 5: File "/usr/lib/python3.5/site-packages/blueman/bluez/BlueZInterface.py", line 16, in get_interface_version obj = dbus.SystemBus().get_object('org.bluez', '/') File "/usr/lib64/python3.5/site-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib64/python3.5/site-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib64/python3.5/site-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib64/python3.5/site-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib64/python3.5/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out Local variables in innermost frame: method: 'StartServiceByName' timeout: -1.0 signature: 'su' object_path: '/org/freedesktop/DBus' bus_name: 'org.freedesktop.DBus' kwargs: {} get_args_opts: {'byte_arrays': False} self: <dbus._dbus.SystemBus (system) at 0x7f214a9d2d58> message: <dbus.lowlevel.MethodCallMessage path: /org/freedesktop/DBus, iface: org.freedesktop.DBus, member: StartServiceByName dest: org.freedesktop.DBus> args: ('org.bluez', 0) byte_arrays: False dbus_interface: 'org.freedesktop.DBus'
Created attachment 1145809 [details] File: backtrace
Created attachment 1145810 [details] File: environ
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
*** Bug 1331775 has been marked as a duplicate of this bug. ***
I have the same thing. bluetooth-applet crashes on every login into gnome-shell. It seems that the underlying cause is bluez not starting, but the applet should not crash even if that happens. Jul 24 15:55:42 bupkis dbus-daemon[980]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Jul 24 15:55:42 bupkis pulseaudio[2146]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: 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. Jul 24 15:55:42 blueman.desktop[2465]: blueman-applet version 2.1.alpha1 starting Jul 24 15:55:42 python3[2465]: detected unhandled Python exception in '/usr/bin/blueman-applet' Jul 24 15:55:43 blueman.desktop[2465]: Traceback (most recent call last): Jul 24 15:55:43 blueman.desktop[2465]: File "/usr/bin/blueman-applet", line 27, in <module> Jul 24 15:55:43 blueman.desktop[2465]: BluemanApplet() Jul 24 15:55:43 blueman.desktop[2465]: File "/usr/lib/python3.6/site-packages/blueman/main/Applet.py", line 33, in __init__ Jul 24 15:55:43 blueman.desktop[2465]: self.Manager = Bluez.Manager() Jul 24 15:55:43 blueman.desktop[2465]: File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 30, in __new__ Jul 24 15:55:43 blueman.desktop[2465]: cls._instance._init(*args, **kwargs) Jul 24 15:55:43 blueman.desktop[2465]: File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 40, in _init Jul 24 15:55:43 blueman.desktop[2465]: self.__bus_name, '/', None, None, None) Jul 24 15:55:43 blueman.desktop[2465]: GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedes Jul 24 15:55:43 bupkis abrt-notification[2732]: Process 2465 (blueman-applet) of user 1001 encountered an uncaught GLib.GError exception Version-Release number of selected component (if applicable): blueman-2.1-0.5.alpha1.fc26.x86_64 gnome-shell-3.24.2-1.fc26.x86_64 Additional info: There's no bluetooth hardware on this machine. $ systemctl status dbus-org.bluez.service bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) Ah, OK: bluetooth.service has ConditionPathIsDirectory=/sys/class/bluetooth, and this directory does not exist on my system. So the service is not even attempted to start, which is OK, because there's no hardware. So the applet should just handle this properly. This is affecting multiple people. It'd be great if this could get some attention from the maintainers.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.