Bug 190589 - "Rescan Collection" destroys database
Summary: "Rescan Collection" destroys database
Status: RESOLVED DUPLICATE of bug 186169
Alias: None
Product: amarok
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.0.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-25 03:59 UTC by h.i.m
Modified: 2009-04-25 09:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description h.i.m 2009-04-25 03:59:14 UTC
Version:           2.0.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I imported one of my music folders in amarok, which worked quite well. Most of the titles were display at the right place. (album, genre, etc)

After pressing the "Rescan Collection" button. A lot of albums dissapeared. I tried to restart, but it didnt help. So i first deleted the amarok config files in ./kde/share/config with no positive result. And then i deleted the ./kde/share/apps/amarok which just works after restarting amarok the collection was complete again.

To reproduce the bug i tried it again and the result was. you can guess, a destroyed collection. 

this time i only deleted the "collection_scan.files", "collection_scan.log", "dynamic.xml" and "my.cnf" and the "mysqle"-folder.

restarted, works again.

So we have to look for the bug in one of these files or the folder.
If it is possible, then i try to upload the "working" and the "destroyed" collection_scan file.

I noticed one thing. The file"collection_scan.files" is identical both in destroyed and working. So we have to check the "mysqle"-folder. --> direct hit!

After deleting the "mysqle"-folder it started to work again.

Please tell me, which file in "mysqle/mysql" could be the interesting one.
I want to help to resolve this bug.


H.i.M
Comment 1 Myriam Schweingruber 2009-04-25 09:27:32 UTC

*** This bug has been marked as a duplicate of bug 186169 ***