SUMMARY *** In Wayland, Falkon won't show up if you fire it with a custom keyboard shortcut set in Settings. In a X session Falkon will launch correctly. *** STEPS TO REPRODUCE 1. Open 'Settings' (or fire the kcm module, kcmshell5 kcm_keys). 2. Set a custom keyboard shortcut to fire Falkon (in my case, [Meta][F]. 3. In Wayland, Press that shortcut to launch Falkon. OBSERVED RESULT Falkon won't show up, though it is launched (ps aux shows it is indeed running, but for some reason its window won't show up). In the Wayland log (.local/share/sddm/wayland-session.log) won't show anything telling (at least for me), but some lines saying Omitting both --window and --windowclass arguments is not recommended Got an error Got an error A new Falkon window will successfully show up if you press your custom keyboard shortcut once Falkon has been launched with another method (Kickoff, krunner...). EXPECTED RESULT Falkon will show up when firing any custom keyboard shortcut you set for it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.15.13-gentoo KDE Plasma Version: 21.12.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2
Having being able to upgrade to Plasma 6.1, I can confirm this was fixed somehow and I can launch Falkon with a custom keyboard shortcut again. Marking this as resolved.