Bug 583024 - [abrt] crash in amarok-utils-2.3.0-5.fc12: Process /usr/bin/amarokcollectionscanner was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in amarok-utils-2.3.0-5.fc12: Process /usr/bin/amarokcollections...
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:597c54ec4ac55e05caa8b4583c0...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-16 13:29 UTC by santiago angel
Modified: 2010-12-03 15:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 15:49:29 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (4.44 KB, text/plain)
2010-04-16 13:29 UTC, santiago angel
no flags Details

Description santiago angel 2010-04-16 13:29:37 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/amarokcollectionscanner -p -r --savelocation /home/santiago/.kde/share/apps/amarok/ /music/Download /music/Ready /music/Shared /music/genres
component: amarok
executable: /usr/bin/amarokcollectionscanner
package: amarok-utils-2.3.0-5.fc12
rating: 4
reason: Process /usr/bin/amarokcollectionscanner was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

scannning a music collection of about 22K mp3's

How to reproduce
1.scan music
2.the music collection has around 22K mp3's

Comment 1 santiago angel 2010-04-16 13:29:39 UTC
Created attachment 407100 [details]
File: backtrace

Comment 2 santiago angel 2010-04-16 23:43:16 UTC
top output:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                                                        
66666 user      20   0 8340m 6.8g 1300 D  5.6 87.1  11:54.80 amarokcollectio

Comment 3 santiago angel 2010-04-17 00:03:32 UTC
bug in ubuntu:


Comment 4 santiago angel 2010-04-17 00:03:57 UTC
upstream bug:


Comment 5 Steven M. Parrish 2010-05-05 11:54:08 UTC
This is an issue which needs to be addressed by the upstream developers.  Please file a report at http://bugs.kde.org  once that is done please add the upstream bug information to this report.  We will monitor the upstream report for a resolution. 


Comment 6 Bug Zapper 2010-11-03 16:59:12 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 7 Bug Zapper 2010-12-03 15:49:29 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.

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