Bug 616111 - [abrt] crash in awn-extras-applets-0.4.0-17.fc13: messagehandler.py:126:__init__:GError: 0 is not a valid notification ID
Summary: [abrt] crash in awn-extras-applets-0.4.0-17.fc13: messagehandler.py:126:__ini...
Alias: None
Product: Fedora
Classification: Fedora
Component: awn-extras-applets
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:854b86df
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-19 17:22 UTC by mhyp666
Modified: 2011-06-29 13:16 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2011-06-29 13:16:34 UTC

Attachments (Terms of Use)
File: backtrace (1.07 KB, text/plain)
2010-07-19 17:22 UTC, mhyp666
no flags Details

Description mhyp666 2010-07-19 17:22:46 UTC
abrt 1.1.1 detected a crash.

architecture: i686
cmdline: python /usr/share/avant-window-navigator/applets/battery/battery.py --uid=1279319857 --window=46137387 --panel-id=1
component: awn-extras-applets
executable: /usr/share/avant-window-navigator/applets/battery/battery.py
package: awn-extras-applets-0.4.0-17.fc13
reason: messagehandler.py:126:__init__:GError: 0 is not a valid notification ID
release: Fedora release 13 (Goddard)

messagehandler.py:126:__init__:GError: 0 is not a valid notification ID

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/awn/extras/awnlib.py", line 1059, in callback_wrapper
  File "/usr/share/avant-window-navigator/applets/battery/battery.py", line 253, in check_status_cb
  File "/usr/share/avant-window-navigator/applets/battery/messagehandler.py", line 42, in evaluate
  File "/usr/share/avant-window-navigator/applets/battery/messagehandler.py", line 86, in evaluate
  File "/usr/share/avant-window-navigator/applets/battery/messagehandler.py", line 39, in set_next
    self.__state = state(self)
  File "/usr/share/avant-window-navigator/applets/battery/messagehandler.py", line 126, in __init__
GError: 0 is not a valid notification ID

Local variables in innermost frame:
self: <messagehandler.VisibleErrorState instance at 0x92afb8c>
handler: <messagehandler.MessageHandler instance at 0x92afacc>

Comment 1 mhyp666 2010-07-19 17:22:49 UTC
Created attachment 432964 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-01 13:26:20 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 3 Bug Zapper 2011-06-29 13:16:34 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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