Bug 680631 - [abrt] rhythmbox-0.13.3-1.fc14: g_type_check_instance_is_a: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.3-1.fc14: g_type_check_instance_is_a: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 705028
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4cca2cc7826c29e621d8a9972e5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 15:00 UTC by François Pelletier
Modified: 2012-03-21 17:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:45:52 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (57.79 KB, text/plain)
2011-02-26 15:00 UTC, François Pelletier 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description François Pelletier 2011-02-26 15:00:23 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 59174 bytes
cmdline: rhythmbox
comment: This is the first time I encounter this bug. I opened it again after the crash and everything was okay
component: rhythmbox
Attached file: coredump, 183881728 bytes
crash_function: g_type_check_instance_is_a
executable: /usr/bin/rhythmbox
kernel: 2.6.35.11-83.fc14.x86_64
package: rhythmbox-0.13.3-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298731718
uid: 500

How to reproduce
-----
1. I was on a fresh reboot. I started Rhythmbox after my external hard drive partitions icons apeared on my desktop.
2. Rhythmbox window showed and it begin scanning my external hard drive for changes as usual
3. It crashed after approximately 1000 songs
Comment 1 François Pelletier 2011-02-26 15:00:26 UTC 
Created attachment 481152 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:45:52 UTC 
Backtrace analysis found this bug to be similar to bug #705028, closing as duplicate.

Bugs which were found to be similar to this bug: bug #667612, bug #682411, bug #705028

This comment is automatically generated.

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