https://bugs.kde.org/show_bug.cgi?id=438313
Bug ID: 438313
Summary: Wayland:
Product: plasmashell
Version: 5.22.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: edoubray...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
STEPS TO REPRODUCE
1. Launch a KDE App with launcher or KRunner. eg Dolphin
2. Launch another app. eg Kate
3. and so on. eg launch Okular
OBSERVED RESULT
1. Dolphin does not launch
2. App#1 ie Dolphin, launches (instead of Kate)
3. App#2 ie Kate opens (instead of Okular)
EXPECTED RESULT
Correct app launches on time
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon Testing (based on Ubuntu focal 20.04)
KDE Plasma Version: 5.22.0 (5.22.0+p20.04+tstable+git20210608.1257-0)
KDE Frameworks Version: 5.82.0+p20.04+tunstable+git20210608.0115-0
(kInfoCenter say 5.83.0 for some reason)
Qt Version: 5.15.2+p20.04+tunstable+git20210602.0956-0
(kInfoCenter says 5.15.3 for some reason)
KDE Apps: 21.04.1+p20.04+tstable+git20210608.0108-0
ADDITIONAL INFORMATION
This happens in both:
* the default App Launcher(the new Kickoff named SimpleMenu I think?) and the
* KRunner
It does *not* happen with command-line, even with dbus-launcher / kinit5
It does not happen with all apps, but for sure it does with the kde/wayland
ones.
The app is not just hidden, I see eg gwenview/dolphin doing their startup work
when I launch the next app.
Works normally on Xorg.
--
You are receiving this mail because:
You are watching all bug changes.
