Bug 173856 - Composer always reset to Unknown
Summary: Composer always reset to Unknown
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-29 20:26 UTC by Christoph Lange
Modified: 2008-10-29 20:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Lange 2008-10-29 20:26:00 UTC 
Version:           1.90 (using 4.1.2 (KDE 4.1.2), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.24-tuxonice-r4

Maybe this is the same as Bug 172896.  I have a multi-artist album, where all tracks have the same artist, but different composers.  I'm sure that when I ripped the CD (with grip), both the artist and the composer were set correctly, as I have ripped many albums successfully with the same grip configuration.  Now, amarok displays the composer as "unknown" in the dialog "edit track details".  When I go there, enter the composer for a track, and save the track, the value is not actually saved.  When I open the track details editor next, it's again reset to "unknown".  The actual music files (Ogg Vorbis) are untouched, though.
Comment 1 Lydia Pintscher 2008-10-29 20:39:36 UTC 
Please test this with beta 3 which is soon to be released. Until then we are going to assume it is the same problem as in the bug report you mentioned. If it is still a problem there please reopen this report.


Thank you for your report.