@Secret300 @kde I think KDE neon has editions for testing KDE software
@skullgiver @raptir haven't tested it yet but the Firefox 121 (released Dec 19th) release notes said it defaults to Wayland when possible now
@MJBrune @Ashiette I tried doing it as quickly as I can and it didn't work the first time (result appeared what looks like about 0.1-0.2s later) but it did work in subsequent attempts (even when looking for other apps)
CPU: i5-1135G7
If you look for an app and then for a different app, does it find it quickly? I suspect it might be reading the .desktop files lazily (meaning it only reads them the first time you look for something)
Edit: nvm ksycoca is there to prevent that
@InverseParallax @semperverus if I understood https://yuenhoe.com/blog/2012/08/associating-firefox-profiles-with-kde-activities/ correctly, it uses a protocol called XSMP which programs need to support, but for me it only ever changed things inside plasmashell so either not a lot of programs support XSMP or XSMP doesnt work on Wayland. I think it would be more useful if it integrated Flatpak and snap, and used them to mount a different config directory based on the activity an app was launched it but idk if that would work well
@voracread I think ~/.config is the standard config file location on Linux (for apps that follow XDG standards) so it should also have config files for non-kde apps