Bug 789589

Summary: [abrt] rednotebook-1.2.0-1.fc16: journal.py:336:exit:RuntimeError: called outside of a mainloop
Product: [Fedora] Fedora Reporter: Samuel <samuel2>
Component: rednotebookAssignee: Fabian Affolter <mail>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: cwickert, mail
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:1d4ab10508f8e899240ac1d41bba5a2b975fb155
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-25 16:47:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Samuel 2012-02-11 15:35:52 UTC 
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        /usr/bin/python /usr/bin/rednotebook
comment:        i yust just the problem as ever
executable:     /usr/bin/rednotebook
kernel:         3.2.2-1.fc16.i686.PAE
reason:         journal.py:336:exit:RuntimeError: called outside of a mainloop
time:           Sa 11 Feb 2012 09:44:58 CET
uid:            500
username:       samuel

backtrace:
:journal.py:336:exit:RuntimeError: called outside of a mainloop
:
:Traceback (most recent call last):
:  File "/usr/bin/rednotebook", line 12, in <module>
:    rednotebook.journal.main()
:  File "/usr/lib/python2.7/site-packages/rednotebook/journal.py", line 671, in main
:    gtk.main()
:  File "/usr/lib/python2.7/site-packages/rednotebook/util/utils.py", line 121, in signal_handler
:    journal.exit()
:  File "/usr/lib/python2.7/site-packages/rednotebook/journal.py", line 336, in exit
:    gtk.main_quit()
:RuntimeError: called outside of a mainloop
:
:Local variables in innermost frame:
:self: <rednotebook.journal.Journal instance at 0xb771710c>
Comment 1 Fabian Affolter 2012-02-25 16:47:33 UTC 
rednotebook was updated to the latest upstream release. Please check and reopen this bug when the issue still occurs.