Bug 619177 - [abrt] crash in gwibber-1:2.31.2-7.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gwibber-1:2.31.2-7.fc13: raise: Process /usr/bin/python was k...
Status: CLOSED DUPLICATE of bug 618425
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:383ddd02454fb8ff446884fc603...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-28 19:09 UTC by Aioanei Rares
Modified: 2010-07-29 17:49 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-07-29 17:49:47 UTC

Attachments (Terms of Use)
File: backtrace (35.37 KB, text/plain)
2010-07-28 19:09 UTC, Aioanei Rares
no flags Details

Description Aioanei Rares 2010-07-28 19:09:16 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/gwibber-service
component: gwibber
crash_function: raise
executable: /usr/bin/python
global_uuid: 383ddd02454fb8ff446884fc6038fd91e315b71f
package: gwibber-1:2.31.2-7.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1.Try to ctrl+q gwibber, who seems undying 
2.After few attempts to quit gwibber, python crashes.

Comment 1 Aioanei Rares 2010-07-28 19:09:19 UTC
Created attachment 435108 [details]
File: backtrace

Comment 2 Tom "spot" Callaway 2010-07-28 19:12:42 UTC
Do you have the "minimize to tray on close" option selected in preferences?

Comment 3 Aioanei Rares 2010-07-29 16:47:16 UTC
Yes, unchecking it solves the problem (ctrl+q works), but it ain't ok, since ctrl+q should exit gwibber regardless and that option should make the app stay in tray on alt+f4, not exit completely. My 0.02$ .

Comment 4 Tom "spot" Callaway 2010-07-29 17:49:26 UTC
No, you're right. I'm just trying to close duplicate bugs. :)

Comment 5 Tom "spot" Callaway 2010-07-29 17:49:47 UTC

*** This bug has been marked as a duplicate of bug 618425 ***

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