Bug 5337 - Set _NET_WM_PID property on X11 window
Summary: Set _NET_WM_PID property on X11 window
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Target Milestone: 4.4.0
Assignee: Henrik Andersson
Keywords: relnotes, samuel_tester
Depends on:
Reported: 2014-11-04 13:57 CET by Peter Åstrand
Modified: 2015-04-23 14:59 CEST (History)
3 users (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2014-11-04 13:57:19 CET
We should set the _NET_WM_PID property on the tlclient and vncviewer windows. Without this property, the IGEL connection manager is not able to terminate our client upon suspend, as reported here:

Comment 1 Peter Åstrand cendio 2014-11-11 11:27:48 CET
Comment 2 Henrik Andersson cendio 2014-12-16 16:44:28 CET
GTK+ uses XSetWMProperties() which sets WM_CLIENT_MACHINE and WM_LOCALE_NAME to proper values.
Comment 3 Henrik Andersson cendio 2014-12-17 15:28:33 CET
Patched added to cenbuild in commit r29737.
Comment 4 Henrik Andersson cendio 2014-12-17 15:29:19 CET
(In reply to comment #3)
> Patched added to cenbuild in commit r29737.

Tested and verified that adding the NET_VM_PID fixes the main issue with IGEL and suspend.
Comment 5 Henrik Andersson cendio 2015-01-12 09:03:10 CET
Using long datatype for pid fixed in commit r29759
Comment 6 Pierre Ossman cendio 2015-04-20 14:02:33 CEST
Committed upstream as r10710.
Comment 7 Samuel Mannehed cendio 2015-04-23 13:44:32 CEST
Reproduced the problem with 4.3.0 on Igel UD3 and verified that it is fixed with build 4588.

$ xprop -name "ThinLinc Client" | grep _NET_WM_PID
Comment 8 Samuel Mannehed cendio 2015-04-23 14:59:19 CEST
[samuel@samuel-80 ~]$ xprop -name "ThinLinc Client" | grep WM_CLIENT_MACHINE
[samuel@samuel-80 ~]$ xprop -name "ThinLinc Client" | grep WM_LOCALE_NAME

Looks good.

Note You need to log in before you can comment on or make changes to this bug.