Description of problem: Create a .abw file, browse for it in Dolphin, click on it and it opens in Konqueror web browser. Version-Release number of selected component (if applicable): How reproducible: Created a new account, made a new .adw file, results the same Steps to Reproduce: 1. Install Mageia 5, and get updates 2. Install abiword from repo 3. Reproducible: Steps to Reproduce:
Originally reported via forums: https://forums.mageia.org/en/viewtopic.php?f=7&t=10179 mime type seems to be correctly defined, but still - konqueror opens up. $ kmimetypefinder test.abw application/x-abiword (accuracy 100) $ xdg-open test.abw will open konqueror. Interesting fact, for some reason GNOME will show kde4-kate as default application, even when kate only displays that file as xml. $ LC_ALL=C gvfs-mime --query application/x-abiword Default application for 'application/x-abiword': kde4-kate.desktop Registered applications: abiword.desktop libreoffice-writer.desktop wine-extension-xml.desktop firefox.desktop kde4-rekonq.desktop kde4-kfmclient_html.desktop google-chrome.desktop monodevelop.desktop wine-extension-txt.desktop wine-extension-ini.desktop calibre-gui.desktop calibre-ebook-viewer.desktop pluma.desktop mousepad.desktop juffed.desktop kde4-okularApplication_txt.desktop kde4-kate.desktop kde4-kwrite.desktop Recommended applications: abiword.desktop libreoffice-writer.desktop "kcmshell4 filetypes" lists konqueror, kate, kwrite, libreoffice writer and okular all above abiword.
CC: (none) => doktor5000Assignee: bugsquad => shlomif
@ Joel, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
CC: (none) => marja11
(In reply to Marja van Waes from comment #2) > @ Joel, > > Thank you for having taken the needed time to report this issue! > > Did this bug get fixed? If so, please change it's status to RESOLVED - FIXED > one note for the future is that it should be "its" rather than "it's".
No reply, so closing as OLD @ Joel ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
Status: NEW => RESOLVEDResolution: (none) => OLD