Plasma no longer recognizes HTML files after Perl updates

[guido-pe]

On monday, I ran emerge -uvaDN world on my computer, which ended up merging 181 packages, most of them related to Perl. Ever since then, Plasma will no longer properly recognize HTML files. When I view the file properties, the MIME-type of those files is given as "application/x-extension-html". I never checked what mimetype it was before, but I'm assuming it was probably "text/html", since that would be the correct mimetype for HTML.

This has a number of negative consequences for me:

- Neither icons nor previews are shown for HTML files any more.

- When I click on an HTML file, it is opened in a hex editor (okteta) instead of a text editor.

- Most importantly for me, I can no longer open HTML files in editable mode inside of kdevelop.

These things all worked earlier on monday, and then broke in the middle of a session, after emerge finished. As far as I can tell, only HTML files are affected, all other filetypes are still recognized just as before.

By manually adding a text editor to the new "application/x-extension-html" file type, I can still edit them in a text editor, but most of the defaults or special behavior that exists for HTML files is just gone or broken.

There is a file /usr/share/mime/text/html.xml on my computer that really looks like it ought to work. According to its mtime, it was definitely written during that round of updates on monday, and then again today after another round of updates, along with most other files in that directory. However, equery belongs comes up with nothing. (Presumbly because it was locally auto-generated after the install of another packages.)

I am out of ideas how to deal with that. Does anybody have any ideas what might be going on here or how to diagnose that further?

[sam_]

There's a chance this is bug 913854. Could you try dev-perl/MIME-tools-5.510.0-r1 please?

FWIW, /usr/share/mime/text/html.xml is handled by update-mime-database from x11-misc/shared-mime-info.

EDIT: Came across your(?) post on the KDE forums too at https://discuss.kde.org/t/kdevelop-suddenly-will-only-open-html-files-in-read-only-mode/4767 - I also came across some bits at https://community.kde.org/Baloo#Top_bugs_and_feature_requests which are helpful in understanding which components are at play here in KFileMetadata and some known issues with it.

If the issues continue, please try to run file on a HTML file, as well as kmimetypefinder and share their output in full.

[guido-pe]

[sam_]

Happy to have helped & thanks for the conclusion!