Bug 607577 - [abrt] crash in rhythmbox-0.12.8-4.fc13: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in rhythmbox-0.12.8-4.fc13: Process /usr/bin/rhythmbox was kille...
Status: CLOSED DUPLICATE of bug 638821
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox   
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:af738075b5d5e66399c06e0cc49...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-24 12:19 UTC by Patrick Pichon
Modified: 2010-11-09 13:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 13:34:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (46.42 KB, text/plain)
2010-06-24 12:19 UTC, Patrick Pichon 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Patrick Pichon 2010-06-24 12:19:06 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rhythmbox '/home/support/.gvfs/Pipiche\xe2\x80\x99s iPhone'
component: rhythmbox
crash_function: rb_ipod_static_playlist_source_get_itdb_playlist
executable: /usr/bin/rhythmbox
global_uuid: af738075b5d5e66399c06e0cc49a052642f37643
kernel: 2.6.33.5-124.fc13.x86_64
package: rhythmbox-0.12.8-4.fc13
rating: 4
reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Patrick Pichon 2010-06-24 12:19:09 UTC 
Created attachment 426546 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:34:50 UTC 

*** This bug has been marked as a duplicate of bug 638821 ***
Comment 3 Karel Klíč 2010-11-09 13:34:50 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #638821.

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