https://bugs.kde.org/show_bug.cgi?id=361602
Bug ID: 361602
Summary: strange behaviour on switching desktops with non-KDE5
applications
Product: kstart
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: l.lu...@kde.org
Reporter: bugzi...@kerridis.de
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.
--
You are receiving this mail because:
You are watching all bug changes.
