Registered Member
|
Not sure how I can provide useful info, please offer suggestions.
Due to collection scan errors I am unable to build catalog my collection. At first it was crashing on non asci characters, then crashing on accented characters, now crashing on file names that are perfectly normal. In total I've scanned my collection of 120K+ files over 50 times! Each time it crashes on a character, searching the entire collection and renaming the files. My systems (I've tried 3 total): Two Fedora Core 6 final and one Fedora Core 7 test, all result in the same errors. I've also tried compiling Amarok from source, same error. This error happens with both sqlite and mysql. I'm happy to help in any manor. Thanks Andy |
Registered Member
|
Just because I tried it again, here is the output:
The character "Würm" is really a "Wurm" and the "u" two little dots above it! Don't have a clue what is wrong with the others! Anyway to configure it to simply skip all files/songs with what it considers bad names? |
Registered Member
|
One more update. Last night I compiled Taglib1.4 from source, no effect, same problem.
|
KDE Developer
|
Same problem as with the Ubuntu package, I think: GCC's stack smashing protection goes haywire. Amarok needs to be rebuild without this option.
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
Thanks Mark, what is the configure option to disable it? I'll test it!
|
KDE Developer
|
Well I don't know. There is some info on wikipedia:
http://en.wikipedia.org/wiki/Stack-smashing_protection
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
mmmmmmm, disabling appears to me more difficult then just a configure option!
Is this change scheduled? Any guesses on the time line? |
KDE Developer
|
We (Amarok) currently can't do anything about it. The best thing you could do is contact your distro packager and point the problem out to him. I think it would be in the best interest of everyone if new packages were made.
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
Well, before I can do that I need to better understand the problem! This isn't an Amarok bug? Its a GCC stack smashing bug?
If so I'd bet the best option would be for an Amarok developer (who truly understands the problem) to contact the maintainer or submit it to Bugzilla. |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]