Bug 101991

Summary: konq: changing file association for .avi changes .ogg association
Product: [Unmaintained] kio Reporter: missive
Component: generalAssignee: David Faure <faure>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description missive 2005-03-20 17:00:52 UTC 
Version:           3.4.0 (using KDE 3.4.0, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.11-gentoo-r4

I am using the "Open with->Other" then selected "remember application association for this type of file"

I changed the association for .ogg files to open with noatun.

Later I double-clicked on a .avi (video) file and it also opened with noatun. Hmm...

So I changed the association for .avi files to kmplayer. Now when I double-click on a .ogg file, those also open in mplayer.

I want to open .ogg files in noatun and .avi files in kmplayer.
Comment 1 David Faure 2005-06-17 21:20:31 UTC 
Don't you have a different mimetype for those two types of files?
By default *.avi is video/x-ms-wmv.desktop and *.ogg is application/ogg,
so changing one shouldn't affect the other. Unless you have modified the default extensions in the "File Types Associations" control module, or your distributor has done something with the mimetypes...
Comment 2 missive 2005-06-18 03:10:49 UTC 
My .ogg files seem to be using audio/vorbis.
the .avi files are using video/x-msvideo.

If I switch them using the properties window, I can get each to be correct, but there is something strange going on with the other method.

I can get each to use the correct player, but they seem to be linked somehow.

Switching .ogg to Noatun (using the "open with other... remember..." method) will also switch the .avi association.
Comment 3 David Faure 2009-02-18 01:54:33 UTC 
All redone differently in KDE4, using mimeapps.list. Haven't heard of that bug happening there -- please reopen the bug if you can still experience this with KDE 4.