My system thinks Konqueror is the default browser despite that not being true. I bisected it to: commit fbe3e5bf8327497703adf7c064f3c7aa6cfe54e2 (refs/bisect/bad) Author: David Faure <faure@kde.org> Date: Mon Mar 9 01:24:10 2020 +0100 KSycoca: avoid hitting an assert when writing a full path into mimeapps.list This isn't really standard anyway, but I happened to do that in a unittest to remove the need for extending search paths... and any code rebuilding sycoca would then hit ASSERT: "(*it2).service()->offset() != 0" in file kbuildservicefactory.cpp, line 402 STEPS TO REPRODUCE 1. kbuildsycoca5 2. kcmshell5 componentchooser OBSERVED RESULT Wrong browser EXPECTED RESULT Correct browser. Reverting the aforementioned commit fixes it. ADDITIONAL INFORMATION (Is this an attempt to get people to use Konqueror again? :p)
I'm also seeing a million of these warnings: kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "org.kde.kolourpaint.desktop" kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "org.kde.ark.desktop" kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "org.kde.gwenview.desktop" kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "org.kde.kolourpaint.desktop" kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "krita_qimageio.desktop" kf5.kservice.sycoca: "/home/kaiuwe/.config/mimeapps.list" specifies external service (ex: absolute path), this isn't supported: "google-chrome-unstable.desktop"
What about this? :(