Bug 149193 - Media device add formats problem
Summary: Media device add formats problem
Status: RESOLVED DUPLICATE of bug 151806
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-25 14:09 UTC by Unknown
Modified: 2007-11-08 05:32 UTC (History)
1 user (show)

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 Unknown 2007-08-25 14:09:37 UTC 
Version:           1.4.7 (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

I am not sure the problem is within Amarok or something it uses.
The system running is openSUSE 10.2 with most of the latest updates (Amarok 1.4.7).
The problem did not exist in June.

When adding a device: "Generic Audio Player" (whether the actual device connected or not) it refuses to add certain (file)formats. Only mp3 and wma work correctly (although my devices can handle ogg, mp3 and ogg, mp3, wma respectively). The refused formats most often start with "&" or has it in somewhere within the name. For example: "&ogg", "ap&e".
In approximately June I could add ogg without problem and it worked until now. But when entering options and removing "ogg" and trying to add it again, it would become "&ogg" and thus not work.

I can get around the problem by manually editing ~/.kde/share/config/amarokrc
Comment 1 Jeff Mitchell 2007-08-25 15:14:13 UTC 
I just added a new device (tried it out with an old one too) and selected ape and ogg and mp4 from the drop down list as file formats.  No ampersand anywhere, even after closing Amarok and restarting...I checked in the amarokrc file too.
Comment 2 Unknown 2007-08-26 11:24:00 UTC 
The porblem for me is, that I don't know what part of my system is creating this.  It shows up in Amarok so I thought I tell you here, and someone more experienced might be able to recreate it or figure out whats causing it.

Thank you.
Comment 3 Jeff Mitchell 2007-08-26 15:01:34 UTC 
We don't know either...
Comment 4 Adam Sparks 2007-10-23 01:44:50 UTC 
This says resolved but I'm having this exact issue with KDE 3.5.8 on my openSUSE 10.3 installation currently.  If it's resolved what do I need to do to resolve it?
Comment 5 Unknown 2007-10-24 10:13:01 UTC 
It is not resolved. I have this still. With a completely fresh installation of openSUSE 10.3 it works fine, but the first patchest (that came within days of the release) breaks this wheter you allow the installation to install the patches or you update your system later. I use locale en_US.UTF-8 if that has anything to do with it?
Comment 6 Unknown 2007-10-24 10:19:22 UTC 
I think Bug 150367 (http://bugs.kde.org/show_bug.cgi?id=150367)is a duplicate of this one. Though I don't know how to mark it as such or even if I am allowed to do that.
Comment 7 Jonathan M. Prigot 2007-11-08 05:28:25 UTC 
Bug 151806 seems to show progress in this matter.
Comment 8 Seb Ruiz 2007-11-08 05:32:16 UTC 
reopening to close properly
Comment 9 Seb Ruiz 2007-11-08 05:32:54 UTC 

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