Bug 860071

Summary: [abrt] rhythmbox-2.97-1.fc17: metadata_cb: Process /usr/bin/rhythmbox was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: anon.leipzig
Component: rhythmboxAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:3ccf4ed3fb07a0e45cd302ff0fecb9ac59a5b632
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 21:04:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description anon.leipzig 2012-09-24 21:04:00 UTC
Description of problem:
The problem occured when I reopened rhythmbox after it didn't recognice a cd of mine.

Version-Release number of selected component:
rhythmbox-2.97-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        rhythmbox
crash_function: metadata_cb
kernel:         3.5.4-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (5 frames)
: #4 metadata_cb at rb-audiocd-source.c
: #8 g_signal_emit_by_name at gsignal.c
: #9 fire_signal_idle at sj-metadata-getter.c
: #13 g_main_context_iteration at gmain.c
: #14 g_application_run at gapplication.c

Comment 1 anon.leipzig 2012-09-24 21:04:02 UTC
Created attachment 616724 [details]
File: core_backtrace

Comment 2 anon.leipzig 2012-09-24 21:04:04 UTC
Created attachment 616725 [details]
File: environ

Comment 3 anon.leipzig 2012-09-24 21:04:06 UTC
Created attachment 616726 [details]
File: backtrace

Comment 4 anon.leipzig 2012-09-24 21:04:08 UTC
Created attachment 616727 [details]
File: limits

Comment 5 anon.leipzig 2012-09-24 21:04:11 UTC
Created attachment 616728 [details]
File: cgroup

Comment 6 anon.leipzig 2012-09-24 21:04:17 UTC
Created attachment 616729 [details]
File: maps

Comment 7 anon.leipzig 2012-09-24 21:04:19 UTC
Created attachment 616730 [details]
File: dso_list

Comment 8 anon.leipzig 2012-09-24 21:04:23 UTC
Created attachment 616731 [details]
File: var_log_messages

Comment 9 anon.leipzig 2012-09-24 21:04:24 UTC
Created attachment 616732 [details]
File: open_fds

Comment 10 Fedora End Of Life 2013-07-03 20:45:01 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2013-07-31 21:04:51 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.