Bug 675569

Summary: [abrt] wammu-0.30.1-3.fc14: gtk_file_system_model_sort: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: patrick.guio
Component: wammuAssignee: Xavier Lamien <lxtnow>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bugs.michael, lxtnow
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:84aa99b6f69df7e5760979cadc0e0584822cae4d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-06 10:13:41 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 patrick.guio 2011-02-06 18:09:25 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/wammu
comment: I was trying how to figure out changing the fileencoding of the backup file for mesgs
component: wammu
crash_function: gtk_file_system_model_sort
executable: /usr/bin/python
kernel: 2.6.35.10-74.fc14.i686.PAE
package: wammu-0.30.1-3.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1297015672
uid: 500

How to reproduce
-----
1. Wammu was running but not active window
2.
3.
Comment 1 patrick.guio 2011-02-06 18:09:27 UTC 
Created attachment 477320 [details]
File: backtrace
Comment 2 patrick.guio 2011-02-17 09:31:48 UTC 
Package: wammu-0.30.1-3.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Wammu was running but not active window
2.
3.


Comment
-----
I was trying how to figure out changing the fileencoding of the backup file for mesgs
Comment 3 Michael Schwendt 2011-06-06 10:13:41 UTC 

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