On Sat 2014.08.30 at 20:51 +0200, Julian Andrej wrote:
I encountered a problem either with cwm or tabbeb
(http://tools.suckless.org/tabbed/). If I use cwm as my window manager
and start tabbed with an XEmbed supported application like xterm, surf
or st (e.g. tabbed xterm -into) and then I resize the window of
tabbed.
Before doing something else with the application inside tabbed I try
to close the instance with CTRL+Q (which is inherited from tabbed to
close the application). The result is cwm crashing and i'll be greeted
by the xdm login window.
Unfortunately there is no relevant (imho) output to the Xorg logs.
Does the problem exist for others and how can I further debug it?
This was pointed out to me the other day.
I'm not a user of tabbed, but what I've found is that tabbed actually tries to
XKillClient the cwm menu window, which is, well, bad.
When one does a mouse resize with cwm, we map and reparent the menu window and
draw the little geometry and resize arrow icons, then after we're done,
reparent out and then unmap. tabbed sees the map, decides to manage the
client; however tabbed doesn't look for UnmapNotify events thus when we unmap,
tabbed still thinks it should manage it - and when it tries to close its list
of windows, it attempts to close the menu window, though since it's not really
there, it uses a hammer to kill it (XKillClient).
One could call this a bug in tabbed. However, one might also think that cwm
should create and destroy the menu window each time it is needed, as opposed
to creating once, then mapping and unmapping as needed. I don't know of other
window managers that do this, so ymmv. Might be worth doing the
create/drestoy for the menu window in cwm anyway, but I would also ask
upstream of tabbed since other things might be mapping and unmapping without
destroying.
Thanks,
Okan
