Bug 1010088 - [abrt] wicd-gtk-1.7.2.4-6.fc19: connection.py:651: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 ...
Summary: [abrt] wicd-gtk-1.7.2.4-6.fc19: connection.py:651:call_blocking:DBusException...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wicd
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0b59b9ff6889ecc663cf7206ca4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-19 23:19 UTC by Cory
Modified: 2020-01-17 04:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:15:27 UTC
Type: ---
Embargoed:
hexkrak: needinfo-


Attachments (Terms of Use)
File: backtrace (1.32 KB, text/plain)
2013-09-19 23:19 UTC, Cory
no flags Details
File: environ (1.36 KB, text/plain)
2013-09-19 23:19 UTC, Cory
no flags Details

Description Cory 2013-09-19 23:19:03 UTC
Description of problem:
Occured after login as the desktop was initializing.

Version-Release number of selected component:
wicd-gtk-1.7.2.4-6.fc19

Additional info:
reporter:       libreport-2.1.7
cmdline:        /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --tray
dso_list:       dbus-python-1.1.1-5.fc19.x86_64
executable:     /usr/share/wicd/gtk/wicd-client.py
kernel:         3.10.11-200.fc19.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
connection.py:651: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/share/wicd/gtk/gui.py", line 407, in update_statusbar
    daemon.UpdateState()
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, 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.SystemBus (system) at 0x1e2ab30>
args: ()
object_path: '/org/wicd/daemon'
signature: ''
bus_name: dbus.UTF8String(':1.5')
get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
timeout: -1.0
kwargs: {}
dbus_interface: 'org.wicd.daemon'
message: <dbus.lowlevel.MethodCallMessage path: /org/wicd/daemon, iface: org.wicd.daemon, member: UpdateState dest: :1.5>
method: 'UpdateState'

Comment 1 Cory 2013-09-19 23:19:06 UTC
Created attachment 800224 [details]
File: backtrace

Comment 2 Cory 2013-09-19 23:19:08 UTC
Created attachment 800225 [details]
File: environ

Comment 3 David Cantrell 2014-09-25 20:03:46 UTC
Is the wicd service enabled and NetworkManager disabled?  The client speaks to wicd-daemon and that needs to be running before you run it.

Comment 4 Fedora End Of Life 2015-01-09 19:54:11 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 5 Fedora End Of Life 2015-02-17 17:15:27 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


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