| Summary: | Local collection shows ???? instead of names | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | snvv101 |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | alex.merry, ashl1future |
| Priority: | NOR | ||
| Version: | 2.0.96 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
snvv101
2009-05-12 16:04:42 UTC
The encodings on the temporary tables and the real tables in the MySQL collection are being set differently, and this seems to be causing some problems. I guess we should be forcing the collations on the temporary tables to be the same as the real tables. I don't know if it helps you to further diagnose the issue, but when I removed default-character-set = utf8 in /etc/mysql/my.cnf and I dropped the old amarok database and I created a new one, the problem "solved". That's means we cannot use our old amarok database. Regards. Confirm this on 2.1.1 After force rescanning by Amarok, Amarok show me randomly ??? in name, artist or song. It's for japanese and russian lang but not at all tracks. I read that problem with creation DB in Amarok. Is this problem present now because you modifing your DB schema or change working with DB in Amarok? The situation with 2.1.1 is much worse than before. It destroy even the newly created DB. I reverted back to 2.0.96 to solve the problem. (other versions from 2.0.96 to just before 2.2.1 worked just fine but I use 2.0.96 because I could not find them for my debian system. I read about bug when downgrading Amarok (lost some files in collection). This bug presents in Amarok 2.1.1 and I want to read a comment from developers. I think this problem linked with problem (Bad search with match case). As you can find a bug with the letter of one of developer (I think he is) which explain this bug. He says that problem in conversation with Latin1 encoding in DB and UTF8 encoding string adding to the table in DB. Duplicate of this bug: http://bugs.kde.org/show_bug.cgi?id=191871 No. This is not a duplicate bug of 191871. In 191871 case the problem was consisted across all tags and next (svn) versions solve the problem. In 2.1.1 it destroys some tags. Some other tags are not shown at all, and in general something is really messed with the scanner in the latest version. Maybe related to this: http://bugs.kde.org/show_bug.cgi?id=189527#c12 *** This bug has been marked as a duplicate of bug 189527 *** (In reply to comment #9) > > *** This bug has been marked as a duplicate of bug 189527 *** No, it is not, that other bug is about special characters in the file path, not about id3 tags... This is solved for me in 2.2-SVN, r985453, build 23.6.2009 |