Bug 668883 - [abrt] rhythmbox-0.13.2-1.fc14: g_object_unref: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] rhythmbox-0.13.2-1.fc14: g_object_unref: Process /usr/bin/rhythmbox wa...
Keywords:
Status: CLOSED DUPLICATE of bug 673001
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:30ee9a07e266aaa05778c427e2a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-11 22:26 UTC by simon
Modified: 2012-03-21 17:54 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:54:54 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.37 KB, text/plain)
2011-01-11 22:26 UTC, simon 		no flags Details
View All

Description simon 2011-01-11 22:26:44 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: rhythmbox
component: rhythmbox
crash_function: g_object_unref
executable: /usr/bin/rhythmbox
kernel: 2.6.35.10-74.fc14.i686
package: rhythmbox-0.13.2-1.fc14
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1294784662
uid: 1804

comment
-----
Playlist file contents (playlist.m3u) reproduces issue;

#EXTM3U
#EXTINF:251,The Title
Music/Missing File.m4a

How to reproduce
-----
1. Attempted to import a playlist file that referenced missing files
2.
3.
Comment 1 simon 2011-01-11 22:26:46 UTC 
Created attachment 472911 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:54:54 UTC 
Backtrace analysis found this bug to be similar to bug #673001, closing as duplicate.

Bugs which were found to be similar to this bug: bug #649270, bug #652466, bug #657955, bug #658454, bug #667068, bug #673001, bug #702397, bug #702604

This comment is automatically generated.

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