Bug#366558: xnest: Xnest should set the WM_CLASS property

To: Christophe Troestler <Christophe.Troestler@umh.ac.be>
Cc: 366558@bugs.debian.org
Subject: Bug#366558: xnest: Xnest should set the WM_CLASS property
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
Date: Sun, 18 Feb 2007 12:09:27 +0100
Message-id: <[🔎] 45D833E7.7000101@ens-lyon.org>
Reply-to: 366558@bugs.debian.org, 366558@bugs.debian.org

Hi Christoph,

I tried to reproduce your problem with Xnest not setting the WM_CLASS
property, but I couldn't. Both 1:1.0.2-8 and current 2:1.1.1-17 seem to
set WM_CLASS correctly. To reproduce, I run Xnest, then run xterm inside
it, then run xprop in this xterm and click on the xterm window, it
returns WM_CLASS=Xterm as it should. Could you check this bug with
latest Xorg/Etch or tell me how to reproduce the problem? Thanks.

Brice

Reply to:

Follow-Ups:
- Bug#366558: xnest: Xnest should set the WM_CLASS property
  - From: Christophe TROESTLER <debian00@tiscali.fr>

Prev by Date: Bug#325181: xnest: Resets mouse acceleration and speed
Next by Date: Bug#341536: marked as done (xnest does not propagate window manager events)
Previous by thread: Processed: Bug#325181: xnest: Resets mouse acceleration and speed
Next by thread: Bug#366558: xnest: Xnest should set the WM_CLASS property
Index(es):
- Date
- Thread