Hi Uli, thanks for following up on this. On Wed, 2011-02-02 at 15:22 +0100, Uli Schlachter wrote: > > > > So it seems there's an unmapped parent window with a 1x1 pixel size. How > > would this affect tiling? > > This is IMHO an ICCCM violation which states[1]: > > "Clients should not rely on transient windows being available to the user when > the transient owner window is not in the Normal state." > > The transient owner window is unmapped which means that awesome isn't managing > it which in turn means that it is in the "withdrawn" state. From my reading of > ICCCM this means that awesome is free to hide that e-Sword window. > > Now for what actually happens: I haven't verified yet, but it looks like this > case triggers a bug and awesome aborts half-way through making that window > visible. Could you check if you get any error messages on awesome standard > error > output? E.g. on Linux: > > ls -l /proc/$(pidof awesome)/fd/2 > > If that points to some file, error messages end up in that file. If this > points > to e.g. "tty1" then error messages are sent to the tty where awesome was > started. > > Cheers, > Uli > > [1] http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.4
I'll presume you meant me to check the xsession errors (I'm running through gdm). Nothing related to awesome there when I start up the wine app, just a common wine-related error (missing winemenubuilder.exe) which is not related. I read through the link you provided, but nothing there seems to me to indicate that awesome should be treating the child window according to the state of the parent window. I can bring this issue back to the wine forum, but first I'd like your confirmation on what exactly is 'wrong' with the current behaviour. If someone with the knowledge volunteers to test the app out I can compress the .wine folder so that it can be run on any machine with wine installed, no setup required. -- To unsubscribe, send mail to [email protected].
