Summary: | Cannot change file associations through system settings | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Christopher Heiny <christopherheiny> |
Component: | kcm_filetypes | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | metalbrick, pino, sourtooth+ssbugs, vsd497 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christopher Heiny
2009-12-15 00:49:46 UTC
Please run kbuildsycoca4 --noincremental, and try again. I tried it - alas there is no improvement in the behavior. I experienced the same on Kubuntu Karmic. The Ubuntu bug reference is here: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/373253 Does anybody know any workaround that can be followed until the final resolution? Thanks I see: the problem is that audio/m3u is both a subclass (in kde.xml) and an alias (in shared-mime-info >= 0.60). This messes things up. The workaround - which is in fact the right way to configure this, is to set things up for the mimetype audio/x-mpegurl instead. I'll need to double-check that we handle aliases correctly, and then what to do with the "both an alias and a real mimetype" corner case. Fixed by r1097945 in 4.x branch, will be in KDE SC 4.4.2. The commit log should have also said: "Detect aliases that are also known as real types (can happen with 3rd party xml files), to prevent inconsistencies when editing mimetypes." We also removed audio/m3u and other temporary aliases from kde.xml (make sure you have shared-mime-info >= 0.60) This bug happened to me again, which is weird, because I use KDE 4.11 on Kubuntu 13.04. The problem is exactly the same as it described above, any help? (In reply to comment #6) > This bug happened to me again, > which is weird, because I use KDE 4.11 on Kubuntu 13.04. > > The problem is exactly the same as it described above, any help? Yes ,that problem appears again as bug 321706 in KDE SC 4.11. The good news is it is fixed in the upcoming 4.11.1 Glad to hear that. |