Summary: | URGENT amarok deletes mp3s itself ! | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Maciek <wired.leilah> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | k.dummann |
Priority: | NOR | ||
Version First Reported In: | 2.0.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Maciek
2009-10-01 16:24:23 UTC
Hello Maciek, I thing you had pretty bad luck :( At first I must sax 2.0.2 is very very outdated, there were some nasty bugs in there. We are closed to roll out 2.2 and 2.1.1 should have been available thought backports in Jaunty. I can tell you I lost a huge amount of music while hunting this bus and I can tell you. And I can tell you that this problem is not in there anymore. But I don't know if this a report on the same Problem. For me the Music got lost when I tried to "oganaise" my collection. Did you some thing like that? But I thing that this bug is fixed for now, we had no problems since 2.1.80. You should try 2.2 when it is out! cheers Kolja Awww! Right, I forgot to unhash backports in sources.list, so I thought I've got the actual version of Amarok. And yes - I'm pretty sure it happened during the reorganisation, just like in your case. That's true - I had a really bad luck... Oh, well. Sorry to arouse panic.. I guess that's the point. Life's go on and now I have to recollect my mp3s again... So I presume that this bug is solved... See you next time(/bug;)) Maciek Why did you reorganize? There is no need to, it is not a prominent feature, and it tells you on the screen what it is going to do, why did you use it? FWIW, search your local /home folder for folders starting with initials, that's where your files are most likely. Again, this is not a bug, it's a feature but not one you are supposed to use unless you know what you are doing... Sorry for the misunderstanding - I meant that I just ordered amarok to rescan the collection, not to do the whole thing with reorganizing, moving to initials folder etc. Best wishes, Maciek Maciek, then it is impossible that Amarok removed anything. I am sure your music is still there, on the hard disk. But you definitely should upgrade to Amarok 2.2, it was released yesterday. I'm afraid it IS amaroks fault, every signs leads to this, but I'm not going to argue about it. Simply, after scanning the local collection my hard disk says I've got 80gb extra free.... As I said before - I have no sufficient arguments to prove my "impeachment", but if I were you I'll check the code responsible for rescanning the collection once again or maybe, as Kolja said it is fixed till 2.1.80 so I guess our discussion is pointless.,, Take care! Maciek To clarify I just hunted a bug related to the reorganisation of files, nothing to do with scanning. There war a but that moved your files to nowhere in special cases. I never experienced things like that when SCANNING the collection. And I don't think that the code that does scanning touches the files in anyway, it just reads the meta data from it. I wish I could help, so that no one will come across that nasty bug (or how to call it...), where ever the fault lies - I'm pretty sure that even in the hardest mental block I will not remove my music collection by myself... I tried to recreate every step I made, and the only trace I found is that maybe it could have something do to with changing the collection paths - I mean - I've reinstalled Kubuntu, but I left my home folder (with .amaroks-newer than that buggy 2.0.2, .kde etc. configuration files in it). My (separate) mp3 disk has always been mounted in /data but during the re-installation I've chosen /media/data as a place for mounting. So when the installation was over and I had a brand new Kubuntu 9.04, before clicking for the scanning in amarok configuration window I had to 'tick' the proper (/media/data/music) path, but what I've found interesting is that that the old path (/data) was still "ticked" in the collection folders window - this is because of the amarok configuration (which was newer than the originally installed amarok). I've got no idea if it could be any trace, I'm just trying to find out what happened... Sorry for the twisted description of the problem (it is caused because of my not sufficient English skills). Anyway I really do appreciate your commitment. Thank you. But I guess I'll have to deal with this problem by myself. ;) with regards, Maciek |