Summary: | Opening URLs doesn't respect mimeapps.list and is buggy | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Martin <spleefer90> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | a.samirh78, jgrulich, kdelibs-bugs, meven29, nate |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=100016 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin
2019-01-22 12:41:03 UTC
Are we talking about opening URLs from Flatpak/Snap applications? No, I have Telegram installed as a normal system app through pacman. It looks like KDE adds definitions into ~/.config/mimeapps.list when you select a hardcoded app to open URLs in, and does not remove when switching back to the default option, so reproducing this without deleting them manually is probably impossible. With the definitions everything works just fine: [Default Applications] x-scheme-handler/http=firefox.desktop; x-scheme-handler/https=firefox.desktop; In that case it's not xdg-desktop-portal-kde issue, but probably KRun? Yep, it's in KRun. Here, have a patch: https://phabricator.kde.org/D18778 This looks like a configuration issue. Most distros set a web browser (you can check in the componentchooser kcm) to open http and https links. Can you reproduce this issue with a new user account? text/html is the mimetype for html files x-scheme-handler/http is the "meta" mimetype that designate an application to open an "http://" url. So that is what you need to setup a browser. Also when manually editing mimeapps.list rather than using kcmshell5 componentchooser, you will need to run kbuildsycoca5 and kdeinit5 to refresh the configuration cache (or close the session). I think this is not really a bug. |