Bug 1337686 - [abrt] blueman: connection.py:651:call_blocking: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 ...
Summary: [abrt] blueman: connection.py:651:call_blocking:dbus.exceptions.DBusException...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:bc39a9662115e9db0fe70a0f949...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-19 19:51 UTC by Giulio 'juliuxpigface'
Modified: 2016-05-23 20:04 UTC (History)
4 users (show)

Fixed In Version: blueman-2.0.4-2.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-23 20:04:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (3.46 KB, text/plain)
2016-05-19 19:52 UTC, Giulio 'juliuxpigface'
no flags Details
File: environ (1.34 KB, text/plain)
2016-05-19 19:52 UTC, Giulio 'juliuxpigface'
no flags Details

Description Giulio 'juliuxpigface' 2016-05-19 19:51:58 UTC
Description of problem:
1. Started a brand new Xfce session.
2. Chose to start with an empty panel.
3. Added an additional panel.
4. Received a notify about this crash.

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

Additional info:
reporter:       libreport-2.7.0
cmdline:        python3 /usr/bin/blueman-applet
executable:     /usr/bin/blueman-applet
kernel:         4.5.4-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
connection.py:651:call_blocking: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.

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/AuthAgent.py", line 9, in <module>
    import blueman.main.applet.BluezAgent as BluezAgent
  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.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.

Local variables in innermost frame:
object_path: '/org/freedesktop/DBus'
timeout: -1.0
message: <dbus.lowlevel.MethodCallMessage path: /org/freedesktop/DBus, iface: org.freedesktop.DBus, member: StartServiceByName dest: org.freedesktop.DBus>
signature: 'su'
self: <dbus._dbus.SystemBus (system) at 0x7f67a9fc76d0>
get_args_opts: {'byte_arrays': False}
dbus_interface: 'org.freedesktop.DBus'
byte_arrays: False
method: 'StartServiceByName'
bus_name: 'org.freedesktop.DBus'
args: ('org.bluez', 0)
kwargs: {}

Potential duplicate: bug 1279365

Comment 1 Giulio 'juliuxpigface' 2016-05-19 19:52:05 UTC
Created attachment 1159654 [details]
File: backtrace

Comment 2 Giulio 'juliuxpigface' 2016-05-19 19:52:07 UTC
Created attachment 1159655 [details]
File: environ

Comment 3 Raphael Groner 2016-05-19 20:09:03 UTC
Thanks for your report.
Can you retry with 2.0.4-2 from updates-testing? We saw several issues with dbus/systemd.

Comment 4 Fedora Update System 2016-05-19 20:10:52 UTC
blueman-2.0.4-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4162d4878a

Comment 5 Giulio 'juliuxpigface' 2016-05-19 20:54:42 UTC
As noted in Bodhi, I can confirm it fixes the issue here.

Comment 6 Fedora Update System 2016-05-21 01:35:06 UTC
blueman-2.0.4-2.fc24 has been pushed to the Fedora 24 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-4162d4878a

Comment 7 Fedora Update System 2016-05-23 20:04:48 UTC
blueman-2.0.4-2.fc24 has been pushed to the Fedora 24 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.