Bug 619177

Summary: [abrt] crash in gwibber-1:2.31.2-7.fc13: raise: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Aioanei Rares <schaiba>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:383ddd02454fb8ff446884fc6038fd91e315b71f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-29 17:49:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

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
kernel: 2.6.33.6-147.2.4.fc13.x86_64
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.
3.
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 ***