I needed to rebuild my collection database, but the scanning process is broken. Using amarokcollectionscanner, I found that it does a segfault because it tries to scan text files inside my music folders containing my flac files. Isn't it supposed to skip those kind of text files? Thanks for any help

It certainly does for me, how did you run amarokcollectionscanner, what options did you specify? Also what extensions do these files have? I have several CUE files in my music folders that are nothing more than text files and the scanner has no problem with that.

Also it would be a good diea to always specify the extact Amarok version you are running, and what options. Ideally the Diagnostics file holds all this information, you can just copy & paste it. You can find it in the Help menu.

The option I use are

Code: Select all

amarokcollectionscanner -ris /media/multimedia/CD-BU/CDs/ > amarokcollectionscanner_batchfullscan.xml

It crashed again and Ubuntu decided to create a report automatically:

Code: Select all

 ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: amarok-utils 2:2.8.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sat Mar 29 07:45:59 2014
ExecutablePath: /usr/bin/amarokcollectionscanner
InstallationDate: Installed on 2014-02-13 (43 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: amarokcollectionscanner -ris /media/username/CD-BU/CDs/
SegvAnalysis:
 Segfault happened at: 0x7fb0d544ce3e <__memcpy_sse2_unaligned+46>:   movdqu -0x10(%rsi,%rdx,1),%xmm8
 PC (0x7fb0d544ce3e) ok
 source "-0x10(%rsi,%rdx,1)" (0x101033697) not located in a known VMA region (needed readable region)!
 destination "%xmm8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: amarok
StacktraceTop:
 TagLib::ByteVector::replace(TagLib::ByteVector const&, TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const&, TagLib::ID3v2::Header*) const () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::Tag::parse(TagLib::ByteVector const&) () from /usr/lib/x86_64-linux-gnu/libtag.so.1
 TagLib::ID3v2::Tag::read() () from /usr/lib/x86_64-linux-gnu/libtag.so.1
Title: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace()
UpgradeStatus: Upgraded to trusty on 2014-02-14 (42 days ago)
UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo

It might be that errors on text files during the scanning process are unrelated to the crash.

The crash is in Taglib, and you seem to have a rather uncommon file ending there, that is not recognized, maybe check that again? AFAIK "xmm8" is not an existingMIME type.

Mamarok wrote:The crash is in Taglib, and you seem to have a rather uncommon file ending there, that is not recognized, maybe check that again? AFAIK "xmm8" is not an existingMIME type.

Thank you for your reply, where do I need to look for this xmm8 thing? Just a simple file extension search?

You can locate the folder by running amarokcollectionscanner: do not use the -s option, and check the resulting xml file, it tells you which file causes the crash and where it is.

Thanks for your help, I'm trying your suggestion, but either there are too many files like this, or there must be something seriously broken in taglib. Mine it's a collection build up over the past 8 years and amarok never gave me such problems while scanning, now it seems the problem is within even old directories untouched for years. It's becoming hellish.

In a laptop of mine, with Debian "almost" Wheezy and some Sid (multimedia codecs) there is amarok 2.5 and it is able to scan my collection flawlessy.