Bug 1331600 - [abrt] blueman: connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
Summary: [abrt] blueman: connection.py:651:call_blocking:dbus.exceptions.DBusException...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Don Zickus
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6044a3259e524d3079374430a6e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-29 00:02 UTC by James Caldwell
Modified: 2016-06-23 04:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 04:54:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (3.14 KB, text/plain)
2016-04-29 00:02 UTC, James Caldwell
no flags Details
File: environ (3.54 KB, text/plain)
2016-04-29 00:02 UTC, James Caldwell
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1286296 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 1286296

Description James Caldwell 2016-04-29 00:02:48 UTC
Description of problem:
Booted system, ran dnf update

Version-Release number of selected component:
blueman-2.0.4-1.fc23

Additional info:
reporter:       libreport-2.6.4
cmdline:        python3 /bin//blueman-applet
executable:     /bin/blueman-applet
kernel:         4.4.8-300.fc23.x86_64
runlevel:       N 5
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.4/site-packages/dbus/bus.py", line 175, in activate_name_owner
    return self.get_name_owner(bus_name)
  File "/usr/lib64/python3.4/site-packages/dbus/bus.py", line 361, in get_name_owner
    's', (bus_name,), **keywords)
  File "/usr/lib64/python3.4/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 "/bin//blueman-applet", line 121, in <module>
    BluemanApplet()
  File "/bin//blueman-applet", line 63, in __init__
    self.Plugins.Load()
  File "/usr/lib/python3.4/site-packages/blueman/main/PluginManager.py", line 90, in Load
    __import__(self.module_path.__name__ + ".%s" % plugin, None, None, [])
  File "/usr/lib/python3.4/site-packages/blueman/plugins/applet/DBusService.py", line 12, in <module>
    from blueman.main.applet.BluezAgent import AdapterAgent
  File "/usr/lib/python3.4/site-packages/blueman/main/applet/BluezAgent.py", line 23, in <module>
    from blueman.bluez.Agent import Agent, AgentMethod
  File "/usr/lib/python3.4/site-packages/blueman/bluez/Agent.py", line 48, in <module>
    class Agent(dbus.service.Object):
  File "/usr/lib/python3.4/site-packages/blueman/bluez/Agent.py", line 56, in Agent
    @AgentMethod
  File "/usr/lib/python3.4/site-packages/blueman/bluez/Agent.py", line 38, in AgentMethod
    if BlueZInterface.get_interface_version()[0] < 5:
  File "/usr/lib/python3.4/site-packages/blueman/bluez/BlueZInterface.py", line 16, in get_interface_version
    obj = dbus.SystemBus().get_object('org.bluez', '/')
  File "/usr/lib64/python3.4/site-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib64/python3.4/site-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib64/python3.4/site-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib64/python3.4/site-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib64/python3.4/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:
self: <dbus._dbus.SystemBus (system) at 0x7f031f183f10>
message: <dbus.lowlevel.MethodCallMessage path: /org/freedesktop/DBus, iface: org.freedesktop.DBus, member: StartServiceByName dest: org.freedesktop.DBus>
timeout: -1.0
byte_arrays: False
object_path: '/org/freedesktop/DBus'
get_args_opts: {'byte_arrays': False}
kwargs: {}
args: ('org.bluez', 0)
signature: 'su'
bus_name: 'org.freedesktop.DBus'
method: 'StartServiceByName'
dbus_interface: 'org.freedesktop.DBus'

Potential duplicate: bug 1325728

Comment 1 James Caldwell 2016-04-29 00:02:54 UTC
Created attachment 1152073 [details]
File: backtrace

Comment 2 James Caldwell 2016-04-29 00:02:55 UTC
Created attachment 1152074 [details]
File: environ

Comment 3 James Caldwell 2016-04-30 22:36:25 UTC
Similar problem has been detected:

Booted system

reporter:       libreport-2.6.4
cmdline:        python3 /bin//blueman-applet
event_log:      2016-04-30-18:35:57> ('report_uReport' completed successfully)
executable:     /bin/blueman-applet
kernel:         4.4.8-300.fc23.x86_64
package:        blueman-2.0.4-1.fc23
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
runlevel:       N 5
type:           Python3
uid:            1000

Comment 4 Raphael Groner 2016-05-16 18:56:48 UTC
Similar problem has been detected:

autostart in cinnamon cinnamon-3.0.1-1.fc23.x86_64

reporter:       libreport-2.6.4
cmdline:        python3 /usr/bin/blueman-applet
event_log:      2016-05-16-20:55:14> (»report_uReport« erfolgreich abgeschlossen)
executable:     /usr/bin/blueman-applet
kernel:         4.4.9-300.fc23.x86_64
package:        blueman-2.0.4-1.fc23
reason:         connection.py:651:call_blocking:dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
runlevel:       N 5
type:           Python3
uid:            1000

Comment 5 Fedora Update System 2016-05-18 07:50:00 UTC
blueman-2.0.4-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a82a812d3

Comment 6 Fedora Update System 2016-05-21 02:29:07 UTC
blueman-2.0.4-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a82a812d3

Comment 7 Fedora Update System 2016-06-21 15:51:25 UTC
blueman-2.0.4-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a82a812d3

Comment 8 Raphael Groner 2016-06-21 15:55:45 UTC
No crash with:
bluez-5.39-1.fc23.x86_64
blueman-2.0.4-2.fc23.x86_64

Maybe a bug with old bluez?

Comment 9 Fedora Update System 2016-06-22 02:55:30 UTC
blueman-2.0.4-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8a82a812d3

Comment 10 Fedora Update System 2016-06-23 04:54:00 UTC
blueman-2.0.4-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.