https://bugs.kde.org/show_bug.cgi?id=446199
--- Comment #7 from Erwan David <k...@rail.eu.org> --- (In reply to Erwan David from comment #6) > (In reply to S. Christian Collins from comment #5) > > Until it's fixed, does anybody know a workaround for this bug? > > I just use a & after the kstart5 command in my scripts. It lets the kstart > process running, but otherwise it works. Sorry I answered for the wrong bug... For this one, I use wmctrl after kstart. The touchy part is that you must wait long enough for the window to have appeared -- You are receiving this mail because: You are watching all bug changes.
