Bug 368911 - Konsole re-uses EWMH -name when it reuses a process
Summary: Konsole re-uses EWMH -name when it reuses a process
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: single-process (show other bugs)
Version: 16.08.1
Platform: Gentoo Packages Linux
: NOR minor
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-16 20:12 UTC by temporalabstraction
Modified: 2020-11-01 06:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description temporalabstraction 2016-09-16 20:12:30 UTC
When a konsole window has been created with the `-name` option to give it an EWMH name and a new window is spawned which re-uses the process (which is apparently automatic if not spawned from a terminal) the new window will obtain the EWMH name already given via `-name` to the other process. A current workaround is simply spawning with `--separate` in which case the bug does not occur.

Reproducible: Always

Steps to Reproduce:
1. kill all existing konsole sessions
2. spawn a new konsole with `-name foo`
3. spawn another konsole session without any `-name` argument

An easy way to do it is using a hotkey daemon of some kind and just bind the `konsole -name foo` and  `konsole` commands to two different hotkeys, this is the exact scenario that caused the bug for me. 

Actual Results:  
The second konsole window will get the EWMH window name `foo`

Expected Results:  
The second window should get the EWMH name `konsole`
Comment 1 Justin Zobel 2020-11-01 05:37:06 UTC
Thanks for the report and apologies for the delayed response.

I've just tested this on the latest konsole and cannot reproduce the issue.

xprop confirms both have different names.
Comment 2 Justin Zobel 2020-11-01 05:37:22 UTC
Can you please confirm if this is still an issue for you?
Comment 3 temporalabstraction 2020-11-01 06:21:20 UTC
(In reply to Justin Zobel from comment #2)
> Can you please confirm if this is still an issue for you?

I tried to reproduce my own bug, and can no longer reproduce it, following my own steps.