On 01/01/2015 10:49 PM, Michele Calgaro wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On 01/02/2015 10:21 AM, Sl�vek Banko wrote:
>> On Friday 02 of January 2015 01:26:38 Dave wrote:
>>> I've noticed a problem with Amarok. I seems it cannot scan and catalog into the database any more than 12607
>>> music files. Does not matter if it's with SQLite or MySQL. the progress bar climbs to 13 percent and never
>>> advances eventually disappears, showing a partial collection list. it does stop indexing but there are over
>>> 60,000 files in the music directory. I can use the files tab and "grab the music directory" and drag to playlist,
>>> and about 40 mins later all files show up in playlist, and they do play and have tag info, but collection tab
>>> doesn't show all that are in the playlist. Doesn't seem to leave any clue in a log file. All files have the same
>>> owner:group and attributes.
>>>
>>> amarok-1.14.10 in Trinity-3.5.13.2 on Debian Wheezy
>>>
>>  From my Amarok - TDE 3.5.13.2 on Squeeze (sqlite) and Wheezy (mysql):
>>
>> 13577 tracks 431 artists 1996 albums 168 genres
>>
>> You can try to add artists or albums to the collection gradually? And watch if jams occur on any particular file.
>>
> Other more advanced option: run amarok from gdb, make sure you pass the --nofork option before running amarok, do your
> import as usual. When amarok get stuck, press Ctrl-C in gdb, type "thread apply all bt" and see if it is stuck somewhere.
>
Turns out that Sl�vek Banko had the best clue. One hosed file deleted, 
and problem solved.  Hard to find 1 out of 68,000 files. One letter of 
the alphabet at a time... Thank you