Bug 216626

Summary: Window class (WM_CLASS) not set via the command line switch "konsole --name foo" if konsole is already running
Product: [Applications] konsole Reporter: Frederic <frederic>
Component: generalAssignee: Konsole Bugs <konsole-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: adaptee, robertknight
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Frederic 2009-11-29 11:39:49 UTC 
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)
Comment 1 Frederic 2009-11-29 11:42:08 UTC 
Sorry the bug title has been cut by the wizard...
Comment 2 Robert Knight 2009-11-30 00:15:31 UTC 
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.
Comment 3 Jekyll Wu 2011-08-02 20:00:23 UTC 

*** This bug has been marked as a duplicate of bug 189184 ***