Bug 757423

Summary: [abrt] conduit-0.3.17-3.fc15: connection.py:630:call_blocking: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 rep
Product: [Fedora] Fedora Reporter: Jean-Philippe Broussard <jphilippe.broussard>
Component: conduitAssignee: Bernard Johnson <bjohnson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bjohnson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:db317e63ceef696c2f476dd3025053dff4f28740
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 11:32:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: Bug
none
File: event_log
none
File: smolt_data none

Description Jean-Philippe Broussard 2011-11-26 23:52:15 UTC
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        python /usr/bin/conduit
comment:        I don't know
executable:     /usr/bin/conduit
kernel:         3.1.1-2.fc16.x86_64
reason:         connection.py:630:call_blocking: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.
reported_to:    file: Bug
time:           dim. 27 nov. 2011 00:48:58 CET
uid:            1500
username:       jphilippe

Bug:            Text file, 2282 bytes
event_log:      Binary file, 109 bytes
smolt_data:     Text file, 3796 bytes

backtrace:
:connection.py:630:call_blocking: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/bin/conduit", line 23, in <module>
:    app = conduit.Main.Application()
:  File "/usr/lib/python2.7/site-packages/conduit/Main.py", line 141, in __init__
:    if conduitApp.HasGUI():
:  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
:    return self._proxy_method(*args, **keywords)
:  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 140, in __call__
:    **keywords)
:  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
:    message, timeout)
: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:
:byte_arrays: False
:self: <dbus._dbus.SessionBus (session) at 0x7f1afb3c7b30>
:args: ()
:utf8_strings: False
:bus_name: dbus.UTF8String(':1.113')
:get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
:object_path: '/activate'
:timeout: -1.0
:signature: None
:dbus_interface: 'org.conduit.Application'
:message: <dbus.lowlevel.MethodCallMessage object at 0x7f1b059cbfa8>
:method: 'HasGUI'

Comment 1 Jean-Philippe Broussard 2011-11-26 23:52:17 UTC
Created attachment 536950 [details]
File: Bug

Comment 2 Jean-Philippe Broussard 2011-11-26 23:52:19 UTC
Created attachment 536951 [details]
File: event_log

Comment 3 Jean-Philippe Broussard 2011-11-26 23:52:21 UTC
Created attachment 536952 [details]
File: smolt_data

Comment 4 Fedora End Of Life 2013-01-16 11:56:13 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 11:32:18 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.