I encountered a strange kstart behaviour when I try to start applications on a different desktop than the current one: With KDE5 applications it works as expected, "kstart --desktop 2 <application>" switches to the new desktop and the application window appears on that desktop. It doesn't matter if I invoke that command from a launcher or krunner or konsole. But with KDE4- and non-KDE applications it behaves different (e.g. Amarok or Gimp): If I invoke the full command from konsole or krunner kstart switches the desktop it behaves as expected, no difference to starting a Plasma 5 app. But invoking any launcher (via kickoff, krunner, quicklaunch, single launcher in panel or on desktop) , the desktop switches to the target desktop, the application gets launched (I see the gimp splash therefore I now it is started on the target desktop) - and then the desktop switches back to where I have executed the launcher and opens the application window on that desktop. As the command does work as expected when typed in konsole or krunner but not when executed via a launcher and the latter only with applications that don't belong to KDE5 I guess it's not really a kstart problem. But I didn't know where else to report. The funny thing is - it did work as expected in KDE4 so it's obviously not a problem of the non-KDE apps. Reproducible: Always Expected Results: The desktop shouldn't switch back to the primary one after the desktop number was set by kstart, even if an application launcher maybe reports it was launched from another desktop.
*Might* be https://git.reviewboard.kde.org/r/127153/ but if there's no (active) window on the current desktop (because the splash doesn't activate or is just gone on the spot) when the "runner" calls (back) focus, that request will still be honored. I can't test or inspect the behavior, though. @Christoph I'm only providing phase-out support, but am no longer using KDE (or Qt, for that matter) so please don't rely on me. I'll oc. fix bugs in my styles etc., but that's it.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!