Summary: | KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype ... differs in case | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Rex Dieter <rdieter> |
Component: | kdecore | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | a.samirh78, christoph, Dieter, emrecio, eric.brunet, freekdekruijf, gamesh.g, hardy.heroin, hpj, hrvoje.senjan, peer.frank, quazgar, sergio, simonandric5 |
Priority: | NOR | ||
Version: | 4.14.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=88004 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rex Dieter
2015-01-28 16:15:32 UTC
marking confirmed, it's easily reproducible. *** Bug 343579 has been marked as a duplicate of this bug. *** So in the meantime the workaround is something like this? sudo sed -i 's:macroEnabled:macroenabled:g' /usr/share/mime/subclasses (In reply to OpenSUSE User #314 from comment #3) > So in the meantime the workaround is something like this? > > sudo sed -i 's:macroEnabled:macroenabled:g' /usr/share/mime/subclasses Seems to be...;-) WORKS for me, thanks! openSUSE 13.2 KDE 4.14.6 shared-mime-info-1.4-2.4.1.x86_64 Also works for me. Can this be applied upstream? (In reply to Daniel Hornung from comment #5) > Also works for me. Can this be applied upstream? I second this. It's a pain to apply it every update cycle. PING! Could everyone be so kind to give her/his/its vote, please? Voting won't help, but an acceptable patch to fix the code would. Hint: manually modifying subclasses is not acceptable So, if I see the problem correctly, KStandardDirs::locate should provide a case insensitive search as well, and then the correct MimeType should be chosen by KMimeTypeRepository? bump?? Still an issue after so long? (In reply to EMR_Kde from comment #11) > bump?? Still an issue after so long? Yes. Sadly, after _every_ update with any mimetype related stuff I have to repeate the above step. Sorry. Same here. Bump?? Still an issue after so long? (Again) Seems to be fixed with current Tumbleweed, at least for me. Could be closed?! Please re-open if one can reproduce this with the current KF 6 based release, thanks. This seems to be fixed for me there. |