Hide Forgot
abrt version: 2.0.1 executable: /usr/bin/gwibber cmdline: /usr/bin/python /usr/bin/gwibber component: gwibber kernel: 2.6.38.4-20.fc15.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. uid: 500 package: gwibber-3.0.0.1-1.fc15 username: matt architecture: x86_64 os_release: Fedora release 15 (Lovelock) time: 1304345047 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", line 87, in <module> client.Client() File "/usr/lib/python2.7/site-packages/gwibber/client.py", line 623, in __init__ self.w = GwibberClient() File "/usr/lib/python2.7/site-packages/gwibber/client.py", line 40, in __init__ self.model = gwui.Model() File "/usr/lib/python2.7/site-packages/gwibber/gwui.py", line 51, in __init__ self.services = json.loads(self.daemon.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 0xf6ea70> 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 0x10ad240> method: 'GetServices'
Created attachment 496272 [details] File: backtrace
Package: gwibber-3.0.0.1-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- i will only start gwibber...
Package: gwibber-3.0.0.1-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Crash occured by simply launching gwibber on Fedora 15. Gwibber does not launch (as non-root user).
Package: gwibber-3.1.0-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- started gwibber in Fedora 15
Package: gwibber-3.1.0-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Started gwibber
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I was reauthorizing Identi.ca.
Package: gwibber-3.1.0-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Starting up Gwibber
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Started the program.
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- chose app icon, never opened, abrt popped up
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- tried to open, gui never opened but popup notifications repeated themselves over and over
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- i opened gwibber and tried to make a post
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- opened gwibber
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- im not sure what went wrong tbh i wasnt actually using it at that moment
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- im not really sure what happened this time, gwibber seems to crash a ot for no reason
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- opened gwibber from a cold boot
Package: gwibber-3.1.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- Gwibber supposedly comes up when I boot. It didn't.
Package: gwibber-3.1.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- At boot up, gwibber never showed.
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- hit refresh
Package: gwibber-3.1.0-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- 1) Click Gwibber --> Quit
Package: gwibber-3.1.0-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- updated yum with no errors, and opened gwibber
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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