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

2008-03-28 Thread Brice Goglin
tags 366558 -fixed-upstream thank you On Sun, Feb 18, 2007 at 01:35:46PM +0100, Brice Goglin wrote: > Christophe TROESTLER wrote: > > I am talking about the xnest window itself. Start Xnest and, from a > > xterm not running inside it, issue xprop and click on the Xnest > > window. You get: > >

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

2007-02-18 Thread Brice Goglin
forwarded 366558 https://bugs.freedesktop.org/show_bug.cgi?id=10016 thank you Christophe TROESTLER wrote: > I am talking about the xnest window itself. Start Xnest and, from a > xterm not running inside it, issue xprop and click on the Xnest > window. You get: > > ... > WM_ICON_NAME(STRIN

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

2007-02-18 Thread Christophe TROESTLER
On Sun, 18 Feb 2007, Brice Goglin <[EMAIL PROTECTED]> wrote: > > 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

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

2007-02-18 Thread Brice Goglin
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 re