KDE Developer
|
Re: Cannot build collection (Collection scan was aborted, since too many problems..)
Thu Dec 28, 2006 12:29 am
I don't know.
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Thu Dec 28, 2006 11:42 pm
Thanks Mark, I have (3) FC6 Final machines. None will build a collection due to this error!
Building Amarok isn't that easy either! Any idea what this error means?
|
Moderator
|
Re: Cannot build collection (Collection scan was aborted, since too many problems..)
Fri Dec 29, 2006 3:44 am
Looks like you are trying to compile amarok with mysql support, but you don't have the mysql-dev package installed.
"There are two theories to arguing with women. Neither one works."
. If men could get pregnant, we'd learn the true meaning of "screaming nancyboy wuss" |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Sat Dec 30, 2006 2:44 am
Dangit, and I checked for that, somehow missed it! Thanks. |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Sat Dec 30, 2006 3:43 am
Well, i compiled fresh, still get the collection scan error. This must be a code problem.
|
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Mon Jan 15, 2007 2:02 am
apoikos, where is this max_restarts variable located at? I'd like to build with it set at 1000+. Thanks |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Tue Jan 16, 2007 7:39 pm
I'm having the same problem, and I have to ask myself: WHY does Amarok absolutely have to abort after 2, 20, or 1000 errors? This makes absolutely no sense to me. Why not simply ask people whether they want to continue scanning after 20 errors? Bonus points for including a "don't ask me again" checkbox. Many people with a collection above a certain size have a lot of MP3's that taglib doesn't like. Telling people to manually delete these files kind of defeats the purpose of having a powerful automated collection manager like Amarok. An even better solution might be to simply skip the current file when something goes wrong, skip the dir if 3 consecutive files go wrong, and prompt the user if 20 consecutive files go wrong. This would leave the user with a fairly complete collection in most cases and still catch fatal errors like a unmounted filesystem (presumably what the limit is designed to detect, correct me if I'm wrong). |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problems..)
Tue Jan 16, 2007 8:00 pm
FiatTux, follow this link, lets see if your problem is the same as mine! Providing the backtrace will help the developers.
Your suggestion is a great idea as well. http://amarok.kde.org/forum/index.php/t ... 558.0.html |
Registered Member
|
Re: Cannot build collection (Collection scan was aborted, since too many problem
Tue Jan 16, 2007 8:17 pm
I'll do that, thanks. Right now my pc is busy compiling a version with MAX_RESTARTS = 1000 though (you can find this value in ./src/scancontroller.h, in case you want to try that).
Also, I had a quick look at the source to see if my suggestion was trivial to implement. It looks as if the message is printed after the scanning process is completely aborted though, so I'm settling for the MAX_RESTARTS tweak for now. I really should be doing other things right now anyway |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]