Bug 208601

Summary:	Some ID3 are not displayed correctly
Product:	[Applications] amarok	Reporter:	snvv101
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	mitchell
Priority:	NOR
Version First Reported In:	2.1.90
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description snvv101 2009-09-26 14:44:34 UTC

Version:           2.1.90 (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Hello,

I just upgraded to Amarok Version 2.1.90 in debian sid, and I have some problems with tags.

My tags are with Greek UTF8 characters and with the previous version worked without any problem.

Now, randomly it shows some tags with ???? while other tags in the same CD are shown correctly. If I correct the tags inside Amarok and rescan db then the same tags are shown as ??? again.

When I play the tracks in Kaffeine then the tags are shown correctly.

I use an external mysql db.

Thank you

Comment 1 Jeff Mitchell 2009-09-26 18:14:41 UTC

Please try current git version. Also, make sure you do a full rescan (Settings->Collection->Rescan Collection). Then close Amarok and re-open it.

Comment 2 Mikko C. 2009-12-05 13:25:12 UTC

2.1.90 is outdated.
Reopen if it still happens with 2.2.1.

Comment 3 Myriam Schweingruber 2009-12-07 00:25:24 UTC

Closing for lack of feedback. Most likely fixed already.

Comment 4 snvv101 2009-12-07 04:29:52 UTC

I did not reported back because I upgraded in Version 2.2.1 and yes it has the same problem.

I have to test it better, in a way my comments to be useful for debug the issue.

For example, when the title is with Latin characters and the artist with Greek, then the artist is not displayed.

And there are still exists that problem with random ????

Till the end of the year I am out of time. Then I will create many bug reports about the issue unless it is fixed.

regards
snvv

Comment 5 Myriam Schweingruber 2009-12-07 11:42:54 UTC

(In reply to comment #4)
> I did not reported back because I upgraded in Version 2.2.1 and yes it has the
> same problem.

Well, you should have reported, definitely. How on earth are we supposed to know what happens on your installation if you don't tell us? If we ask for feedback it's for exactly that reason.
 
> Till the end of the year I am out of time. Then I will create many bug reports
> about the issue unless it is fixed.

Are you serious? One report per item, everything else will be closed as a duplicate. Please don't give me unnecessary work, I already have enough, really.

Also, this is a dupe anyway, I only closed it because *you* did *not* report back.

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