On Thu, Oct 25, 2012, Matthew D. Fuller wrote about "Re: [ctwm] serious bug of xterm on ctwm": > On Thu, Oct 25, 2012 at 12:20:21PM +0200 I heard the voice of > Nadav Har'El, and lo! it spake thus: > > > > Anybody ever see this bug? > > Can't say that I have (and I also have xterm 285, and have no troubles > from it). Maybe you could poke at "xwininfo -root -tree" or something > to see if there's a hint about where a window should be but isn't?
The "missing" window that supposedly ctwm put up and disappeared is 0x80000b. It's not listed in xwininfo -root -tree. All of ctwm's children appear to have the 0x14.... ids. But I've found something even more curious - if I remove this property, $ xprop -root -remove _NET_SUPPORTING_WM_CHECK xterm returns to working. But restarting ctwm, doesn't return this property. So perhaps I was wrong, and ctwm isn't at all the one which adds this wrong property for me? It appears (?) that ctwm adds _WIN_SUPPORTING_WM_CHECK, but NOT _NET_SUPPORTING_WM_CHECK. So now I'm left wondering - what is adding this wrong _NET_SUPPORTING_WM_CHECK? Very strange... -- Nadav Har'El | Thursday, Oct 25 2012, 9 Heshvan 5773 n...@math.technion.ac.il |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |My opinions may have changed, but not the http://nadav.harel.org.il |fact that I am right.
