Bug 675569 - [abrt] wammu-0.30.1-3.fc14: gtk_file_system_model_sort: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] wammu-0.30.1-3.fc14: gtk_file_system_model_sort: Process /usr/bin/pyth...
Keywords:
Status: CLOSED DUPLICATE of bug 603781
Alias: None
Product: Fedora
Classification: Fedora
Component: wammu
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:84aa99b6f69df7e5760979cadc0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-06 18:09 UTC by patrick.guio
Modified: 2011-06-06 10:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-06 10:13:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (30.05 KB, text/plain)
2011-02-06 18:09 UTC, patrick.guio 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.