abrt 1.0.8 detected a crash.
cmdline: python /usr/lib/hamster-applet/hamster-applet --oaf-activate-iid=OAFIID:Hamster_Applet_Factory --oaf-ior-fd=63
comment: sorry, i've no idea when or why this happened.
reason: applet.py:75:msg:GError: 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.
release: Fedora release 12 (Constantine)
applet.py:75:msg:GError: 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/lib/python2.6/site-packages/hamster/applet.py", line 481, in refresh_hamster
File "/usr/lib/python2.6/site-packages/hamster/applet.py", line 512, in check_user
self.notify.msg(msg, self.edit_cb, self.switch_cb)
File "/usr/lib/python2.6/site-packages/hamster/applet.py", line 75, in msg
GError: 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:
body: u'Working on <b>admin</b>'
self: <hamster.applet.Notifier object at 0xb7152cec>
edit_cb: <bound method HamsterApplet.edit_cb of <hamster.applet.HamsterApplet object at 0xb777dbac>>
notify: <pynotify.Notification object at 0xb716175c (NotifyNotification at 0x9b86010)>
switch_cb: <bound method HamsterApplet.switch_cb of <hamster.applet.HamsterApplet object at 0xb777dbac>>
Created attachment 408099 [details]
This appears to be a problem not with hamster-applet but with your message bus.
Are you still experiencing this problem?
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12'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 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.