Version-Release number of selected component: gwibber-3.4.2-4.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: /usr/bin/python /usr/bin/gwibber-accounts kernel: 3.6.11-1.fc17.x86_64 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/gwibber-accounts", line 125, in <module> : accounts.GwibberAccountManager(selected_account=selected_account, condition=condition, message=message) : File "/usr/lib/python2.7/site-packages/gwibber/accounts.py", line 60, in __init__ : self.services = json.loads(self.gwibber.GetServices()) : File "/usr/lib/python2.7/site-packages/gwibber/lib/__init__.py", line 39, in GetServices : return self.service.GetServices() : 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 0x1d75710> :args: () :utf8_strings: False :bus_name: 'com.Gwibber.Service' :get_args_opts: {'byte_arrays': False, 'utf8_strings': False} :object_path: '/com/gwibber/Service' :timeout: -1.0 :signature: None :dbus_interface: 'com.Gwibber.Service' :message: <dbus.lowlevel.MethodCallMessage object at 0x7f46f8e2cfc0> :method: 'GetServices' Potential duplicate bug: 701303
Created attachment 676336 [details] File: executable
Created attachment 676337 [details] File: environ
Created attachment 676338 [details] File: dso_list
Created attachment 676339 [details] File: smolt_data
Created attachment 676340 [details] File: core_backtrace
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.