Bug 655695 - [abrt] sound-juicer-2.32.0-2.fc14: IA__gtk_tree_model_get_valist: Process /usr/bin/sound-juicer was killed by signal 11 (SIGSEGV)
Summary: [abrt] sound-juicer-2.32.0-2.fc14: IA__gtk_tree_model_get_valist: Process /us...
Keywords:
Status: CLOSED DUPLICATE of bug 658089
Alias: None
Product: Fedora
Classification: Fedora
Component: sound-juicer
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3584615ddbbb15d7be9a335acdd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-22 07:31 UTC by Jim Shipman
Modified: 2012-03-30 11:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 11:32:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (37.78 KB, text/plain)
2010-11-22 07:31 UTC, Jim Shipman 		no flags Details
View All

Description Jim Shipman 2010-11-22 07:31:36 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: sound-juicer
component: sound-juicer
crash_function: IA__gtk_tree_model_get_valist
executable: /usr/bin/sound-juicer
kernel: 2.6.35.6-48.fc14.x86_64
package: sound-juicer-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/sound-juicer was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290410597
uid: 500

How to reproduce
-----
1. Start an extraction
2. Open preferenced while the extraction is going on.
3. Crash
Comment 1 Jim Shipman 2010-11-22 07:31:38 UTC 
Created attachment 461935 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 11:32:19 UTC 
Backtrace analysis found this bug to be similar to bug #658089, closing as duplicate.

Bugs which were found to be similar to this bug: bug #554906, bug #566567, bug #579197, bug #598623, bug #625243, bug #636599, bug #658089, bug #666592, bug #678455

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 658089 ***
Note You need to log in before you can comment on or make changes to this bug.