SUMMARY On Wayland, when launching an application from simple application launcher, the menu launcher or KRunner, plasma instead launches the previously-selected application. For example: On first logging in, using the Simple Menu to launch Dolphin does nothing. After attempting to launch Dolphin, using the Simple Menu to launch Kate instead launches Dolphin. Then, attempting to launch Konsole instead launches Kate. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520
I can verify that this bug is valid. It is happening in the Plasma Wayland session on my Surface Pro 4 and ASUS ROG Strix GL702VM laptops. I actually came here to submit the same bug report. It only started happening when KDE Frameworks 5.83.0 was released. It also occurs when launching applications from the Application Dashboard, Latte Dock, and from Krunner. I updated to 5.22.1 this afternoon, and it does not fix the issue. Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 ASUS ROG Strix Laptop: Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 1060/PCIe/SSE2 Surface Pro 4 Laptop: Kernel Version: 5.12.10-surface (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15.6 GiB of RAM Graphics Processor: Mesa Intel HD Graphics 520
I can also reproduce this. Changing status to Confirmed Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.3 Kernel Version: 5.4.0-74-generic (64-bit) Graphics Platform: Wayland Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics Memory: 7.7 GiB of RAM Graphics Processor: AMD CEDAR
This bug is fixed 4 days ago, but it seems that the fix was not included in the plasma-framework 5.83.0 package. https://bugs.kde.org/show_bug.cgi?id=438313
*** This bug has been marked as a duplicate of bug 438313 ***