Bug 129226 - amarok: directory icons start amarok (cause: amarok.desktop)
Summary: amarok: directory icons start amarok (cause: amarok.desktop)
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: Final
Hardware: All Other
: P2 - High : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL: http://bugs.kde.org/show_bug.cgi?id=1...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 22:04 UTC by Pascal Bleser
Modified: 2007-07-12 10:16 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Bleser 2005-10-18 22:04:26 UTC 
http://bugs.kde.org/show_bug.cgi?id=114595

"After installing Amarok , some desktop icons when clicked start Amaork such as
MY Computer, Network,Office (Open Office Org),and Trash . Home and Printer do not .
Uninstalled Amarok and icons functions return to normal behaviour."
"inode/directory caused strange behavior of .desktop files on SUSE Linux 10.0
with KDE 3.4.3"

Patch, in amarok.desktop:
-MimeType=audio/basic;application/x-ogg;application/ogg;audio/x-vorbis;audio/vorbis;audio/x-oggflac;audio/oggflac;audio/x-flac;audio/flac;audio/x-mp3;audio/mp3;audio/x-mpeg-url;audio/mpeg-url;audio/x-mpegurl;audio/mpegurl;audio/x-wav;audio/wav;audio/x-mod;audio/mod;audio/x-scpls;audio/scpls;audio/x-sid;audio/sid;audio/x-aiff;audio/aiff;audio/x-mid;audio/mid;audio/x-midi;audio/midi;inode/directory;
+#don't add inode/directory to mimetypes it leads to misbehavior
+MimeType=audio/basic;application/x-ogg;audio/x-vorbis;audio/x-oggflac;audio/x-flac;audio/x-mp3;audio/x-mpeg-url;audio/x-wav;audio/x-mod;audio/x-aiff;audio/x-mid;audio/x-midi;
Comment 1 Dirk Mueller 2005-10-19 07:07:10 UTC 
this mime type is not included in the suse 10.0 package of amarok. 
so did you actually see any misbehaviour?
Comment 2 Marco Röben 2005-10-19 07:45:15 UTC 
I've encountered the same problem after upgrading Amarok 1.3.1 on SL 10.0 to Amarok 1.3.3 from the KDE supplementary directory. The same problem occured with the Amarok Version from the guru package repository (just as an extra piece of information). Sorry, that I cannot report more detailed information, just downgraded to 1.3.1.
Comment 3 Pascal Bleser 2005-10-19 07:58:59 UTC 
I just forwarded the kde.org bug as it was reported by an amarok developer on the #openSUSE IRC channel and he didn't feel like creating himself an account on the Novell bugzilla.

Note that the person who originally reported the bug could very well have encountered that one when using my amarok RPMs for SUSE (I'm the maintainer of the "guru" repository). Also, from what Maro reports above (comment #2), it seems like the patch from the stock 10.0 amarok RPM didn't make it into the KDE supplemental package.

Dirk, I will check the SUSE 10.0 amarok RPM, mine and possible also the KDE supplemental RPM to see which ones are affected by the bug (apparently, the stock 10.0 amarok RPM isn't, as you have stated in comment #1).
Maybe you could forward the bug to the KDE supplemental amarok maintainer for him to check whether his source RPM includes that patch ?
Comment 4 Dirk Mueller 2005-10-19 09:22:20 UTC 
well, anyway, I fixed supplementary.