Hi everyone,

I've just installed amarok 2.6 on my ubuntu 12.04 (Precise Pangolin) and I have the following problem: a full rescan of my collection never completes (I left it working for a whole night and the number of tracks did not change). Is there a memory limit which I'm not aware of (I have a collection of 35G, roughly)? I also tried to scan the collection not all in one go, but a smaller amount of albums at a time, to limit the amount of memory needed for the scan. Unfortunately, the same problem arose when about 5500 tracks where already added to the collection: no new tracks could be added.
Is there a solution to this problem? Please let me know if you need further details.
I may as well add that I've also tried to populate a playlist with my entire collection, and this made amarok crash (I have not copied the report, but I can repete the experience, if necessary).

I have to admit that I had this problem with all previous 2.n releases of amarok and resorted to downgrade to amarok 1.4 which did not have this annoying issue. Unfortunately, downgrading amarok on Precise seems to be a hard task, so I'd like to know if I can fix my problem with amarok 2.6 instead.
Thanks a lot for your help and sorry if this was discussed before and I could not find it.

this is the amarok --nofork --debug output:
amarok: [ScanManager] Collection scanner crashed, restart count is 2
kmimetype filetype guessing failed for /home/***************/****.ra
kmimetype filetype guessing failed for /home/***************/****.ra
amarok: [ScanManager] Collection scanner crashed, restart count is 3
kmimetype filetype guessing failed for /home**************/*********.ra
kmimetype filetype guessing failed for /home/*******************/********.ra
*** glibc detected *** /usr/bin/amarokcollectionscanner: corrupted double-linked list: 0x0941cbd0 ***

You should run the amarokcollectionscanner separately, there might be a corrupted file causing the issue. please see --help for the available options.

Thanks a lot for your reply. I think I've solved my problem now which in fact was double (I believe).

On the one hand amarok did not like some files in my collection: the files themselves where not corrupted, they just where in RealAudio format and apparently amarok cannot handle them, so I just converted them into mp3s.
On the other one, given the size of the collection I followed the suggestion that I found here:
http://digitizor.com/2010/05/27/how-to- ... in-amarok/
which certainly sped up the scanning.

Trying to create a playlist containing the entire collection still makes amarok to crash, but that's not really important to be honest.

Anyway, thanks again for your help

The instructions in that link are wrong as those apply for Amarok 1.x, not for Amarok 2.x which uses mysql embedded by default.

As for loading an entire collection in the playlist: Amarok was never designed to handle this, that is what the Dynamic Playlist and the Automated Playlist Generator are there for.

Then I guess the mysql had a problem because even skipping the problematic files I could not scan all the collection before purging and reinstalling it.

I'm using Amarok 2.6 on Slackware64 14.0.

When the Amarok GUI scans my collection it goes ok for a while, bu then it freezes (i.e. I cannot interact with any element of the GUI). I keep seeing the HDD light blinking, indicating the scan is still running. I wait for it stop blinking, but Amarok continues freezed, so I have to manually kill its process with root.

If I run "amarokcollectionscanner", it goes ok, and creates a good XML file with the library.
The messages of error it outputs are the following (I've supressed the repeated errors):

Code: Select all

TagLib: A frame of unsupported or unknown type 'CM1' has been discarded
TagLib: A frame of unsupported or unknown type 'XXX' has been discarded
TagLib: ID3v2.4 no longer supports the frame type XXX.  It will be discarded from the tag.
TagLib: A picture frame must contain at least 5 bytes.
TagLib: A private frame must contain at least 2 bytes.
TagLib: ASF: Not an ASF file.
TagLib: MPEG::Header::parse() -- First byte did not match MPEG synch.
TagLib: MPEG::Header::parse() -- Invalid sample rate.
TagLib: MPEG::Properties::read() -- Could not find a valid last MPEG frame in the stream.
TagLib: MPEG::Properties::read() -- Page headers were invalid.
TagLib: String::prepare() - Invalid UTF16 string.
TagLib: String::prepare() - Unicode conversion error.
kmimetype filetype guessing failed for /home/user/music/XXX.mod

I think the problem is that the Amarok GUI is not being able to handle one of these errors.
Does anyone have a clue about what might be happening?

Thank you.

Did you check if you have the taglib dependencies installed and Amarok is compiled with it? Also it would be interesting to run amarok with gdb and get a backtrace when it freezes, please see also http://techbase.kde.org/Development/Tut ... sh_reports. Please make a bug report with the output in http://bugs.kde.org

Mamarok wrote:Did you check if you have the taglib dependencies installed and Amarok is compiled with it? Also it would be interesting to run amarok with gdb and get a backtrace when it freezes, please see also http://techbase.kde.org/Development/Tut ... sh_reports. Please make a bug report with the output in http://bugs.kde.org

I have taglib-1.7.2 and taglib-extras-1.0.1.
The weird thing is that it doesn't crash, it only freezes the interface, so a backtrace report is not doable.
Altough, if I run with --debug, i can get the last comands before it freeze:

Code: Select all

BEGIN: void ScanManager::checkScannerVersion()
END__: void ScanManager::checkScannerVersion() [Took: 0.062s]
BEGIN: void ScanManager::checkForDirectoryChanges()
  BEGIN: virtual void ScanManager::requestIncrementalScan(const QString&)
    [ScanManager] addDirToList for ""
    BEGIN: virtual void ScannerJob::run()
    END__: virtual void ScanManager::requestIncrementalScan(const QString&) [Took: 0s]
    BEGIN: DirWatchJob::DirWatchJob(QObject*, Collections::DatabaseCollection*)
    END__: DirWatchJob::DirWatchJob(QObject*, Collections::DatabaseCollection*) [Took: 0s]
  END__: void ScanManager::checkForDirectoryChanges() [Took: 0s]
  BEGIN: virtual void DirWatchJob::run()
    [ScanManager] ScannerJob: got count: 1167
    BEGIN: virtual void SqlScanResultProcessor::commit()
      BEGIN: void SqlScanResultProcessor::urlsCacheInit()
      END__: void SqlScanResultProcessor::urlsCacheInit() [Took: 0.14s]
      BEGIN: virtual void SqlScanResultProcessor::deleteDeletedDirectories()
      END__: virtual void SqlScanResultProcessor::deleteDeletedDirectories() [Took: 0.01s]
    END__: virtual void SqlScanResultProcessor::commit() [Took: 0.63s]
    [ScanManager] ScannerJob finished
  END__: virtual void ScannerJob::run() [Took: 1.5s]

Do you think I should make a bug report with that information?

Of course you can do a backtrace, did you read the page I suggested? When it freezes you interrupt it with Ctrl+C and then run

Code: Select all

thread apply all bt

And again: this does not belong to the forum but needs to be reported in the bugtracker.