Bug 677832 - [abrt] rhythmbox-0.13.1-1.fc14: IA__gtk_tree_model_get_valist: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.1-1.fc14: IA__gtk_tree_model_get_valist: Process /usr/b...
Keywords:
Status: CLOSED DUPLICATE of bug 649149
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:efb3755908f7664501e3f6f9591...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 00:58 UTC by pmvr
Modified: 2012-03-20 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:45:04 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (34.19 KB, text/plain)
2011-02-16 00:58 UTC, pmvr
no flags Details

Description pmvr 2011-02-16 00:58:55 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: IA__gtk_tree_model_get_valist
executable: /usr/bin/rhythmbox
kernel: 2.6.35.6-45.fc14.i686
package: rhythmbox-0.13.1-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297817518
uid: 500

How to reproduce
-----
1.Crash qhen open the rytmbox

Comment 1 pmvr 2011-02-16 00:58:58 UTC
Created attachment 478994 [details]
File: backtrace

Comment 2 pmvr 2011-03-10 19:51:28 UTC
Package: rhythmbox-0.13.1-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Start the Rythmbox
2.
3.

Comment 3 abrt-bot 2012-03-20 16:45:04 UTC
Backtrace analysis found this bug to be similar to bug #649149, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649149, bug #657713, bug #667355, bug #667880

This comment is automatically generated.

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


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