2.2 -> 2.2.1 causes track loss in local collection

[novosirj]

Bugzilla from mitchell at kde.org wrote:
> 
> On 11/30/2009 4:05 PM, Christian Kreibich wrote:
>> On Mon, 2009-11-30 at 11:25 -0800, Eric Altendorf wrote:
>>> Weird.  I used 2.2 briefly when I upgraded to Karmic, and all the
>>> tracks that were perpetually missing under 2.1 re-appeared.  So I
>>> thought the long-standing DB bug had finally been fixed in 2.2.
>> 
>> Interesting. I just did a full collection scan using
>> 
>>   amarok --nofork --debug
>> 
>> and I'm noticing an error on a humongous SQL query:
>> 
>>   amarok:      [ERROR!] GREPME MySQL query failed! Duplicate entry
>> '-1-./[my collection path]/New/Various/bandits - catch me (' for key
>> 'urls_id_rpath_temp'  on  "INSERT INTO urls_temp VALUES ([...]"
>> 
>> The query continues with seemingly every single track physically located
>> in my collection folder, including those tracks that no longer appear in
>> the collection browser. Would an error in this query explain a failing
>> collection re-scan?
> 
> Yes, it could. It would be useful if you pasted more of the humongous
> SQL query. Perhaps you could save your debug output and email it to me?
> 
> Please be sure to run "amarok --debug" twice -- that is, run it once,
> close Amarok, then run it again (so the debug output starts at the
> beginning of Amarok loading) and do the scan.

I have had the same problem an have output from a debug run like this. Would
you like me to e-mail that as well? I am also running 2.2.1 under *ubuntu. 
-- 
View this message in context: http://old.nabble.com/2.2--%3E-2.2.1-causes-track-loss-in-local-collection-tp26569949p26735466.html
Sent from the Amarok - Main mailing list archive at Nabble.com.