Version: (using KDE 4.3.1) OS: Linux Installed from: openSUSE RPMs If I run (with no other konsole running) konsole --name "foo" then the WM_CLASS property is set (properly) as : WM_CLASS(STRING) = "foo", "Konsole" but If I already have a konsole running, then starting "konsole --name foo" won't set the WM_CLASS: WM_CLASS(STRING) = "Qt-subapplication", "Konsole" What's weird, is that if the command line is executed from a running konsole, then the --name switch will work. the bug is only triggered when the command line is run from elsewhere (I use a ""link to application" icon on the desktop). If there are no other konsole running, then launching the konsole --name foo via the icon WILL set the WM_CLASS property... but after that, the other konsole started from the regular menu (without the --name switch) will have the wrong WM_CLASS (foo)
Sorry the bug title has been cut by the wizard...
Hello, I suspect this is a side-effect of Konsole being a single-process application by default, that is there is only one 'konsole' process which runs all of the Konsole windows. The exception is when a new konsole instance is started from a terminal, in which case a new process is used so that the new Konsole instances inherits the environment from its parent terminal.
*** This bug has been marked as a duplicate of bug 189184 ***