they are switches for electron apps, as some of them default to run under X11. so for e.g. element, it should be flatpak run im.riot.Riot --enable-features=UseOzonePlatform,WebRTCPipeWireCapturer --ozone-platform=wayland.

you can check if all your apps are using wayland by running xlsclients in terminal while you got them open; an empty response means all wayland.

if you’ve installed flatpak recently, say F40 onward, it should default to user. if it’s an old install then your flatpaks are system-wide. there isn’t a downside for either case per se, but user being the default for the future prevents potential issues.

my issue is, when I need to edit a .desktop file (to include ozon flags and whatnot) for a system-wide flatpak app, plasma doesn’t edit the app’s .desktop file but incorrectly inserts a symlink to the user-wide version (which doesnt exist). there are ways around that, like removing the symlink and manually copying the file from /var/lib/flatpak/wherever to ~/.local/share/applications/ and editing it there, but then plasma doesn’t pick up the change immediately so this works better for me.

no help to you, but a heads-up to anybody yet to deploy disks in such a scenario: always use encryption by way of LUKS2. you can set it up easily to unlock it on boot by a key file on the boot drive, thumb drive, TPM and such. so when a drive gets sold, RMA’d, etc., you got none of these issues.

source: sold my old drives recently and the shred procedure took ages. the new ones are encrypted so none of that shit no more.