grafic problems with FVWM
Brought to you by:
anomie
Menu
▾
▴
#6 grafic problems with FVWM
open-works-for-me
nobody
None
5
2012-09-17
2012-09-16
Anonymous
No
wmudmount allways paints its window on position +0+0 on screen when using with FVWM Window-Manager
Calling wmudmount from command line creates two wmudmount-windows on is painted on top left of the screen without window decorations and the other is painted with decorations elsewhere on screen. Both are usable, but the first window destroys grafical content on the upper left screen.
When using wmudmount with FVWMButtons you need to start FVWMButtons on top left of the screen and make wmudmount the fisrt window to be swallowed otherwise you would have two wmudmount windows with absolutely the same content.
This sounds like GTK bug 139322 (see https://bugzilla.gnome.org/show_bug.cgi?id=139322\), which the GTK folks refuse to fix. FVWMButtons should be updated to recognize windows with WM_CLASS DockApp as dockapps (in addition to windows with initial_state = WithdrawnState) to work around this GTK bug, see http://icculus.org/pipermail/openbox/2010-September/006787.html for details.
In the mean time, you can pass --enable-gtk-withdrawn-hack to ./configure when building wmudmount to have it hack around the GTK bug. When doing this with fvwm 2.5.30 as available from Debian and a configuration based on http://ft.bewatermyfriend.org/comp/fvwm/config.d/fvwmbuttons.html, it seems to swallow fine.
Thanks for looking at the bug report!
Now I tested quite a lot, but without luck. :(
I used fvwm 2.5.30 indeed.
I compiled wmudmount with
(1) --enable-gtk-withdrawn-hack (1)
and with
(2) --disable-gtk-withdrawn-hack (2)
When using the (2) version a window gets painted at the top left of the screen. This window has no borders or anything. Trying to identify this window with FvwmIdent is not possible. For the WindowManager it does not seem to exist!
Of course FvwmButtons is not able to swallow this window. Also its not possible for the WindowManager to modify it (i.e. iconify, change decoration and so on)
When using the (1) version: TWO(!) windows occure. One completely without decoration, this window behaves like the Version (2).
The other window is a regular one. It is decorated by Fvwm it can be iconified, moved and so on. When Identifying this window with FvwmIdent it states it is wmudmount. And of course swallowing is no problem. But the other window (without the border) will not be swallowed, obscures all other windows and can't be moved.
It does not matter if FvwmButtons is used or not. One window of wmudmount stays allways at the top left of the screen. (Sometimes this wmudmount window gets below some other window and then it seems like the swallowing is working, but it is not.)
I adapted mentioned fvwm config but of course it did not matter ...
To me this behaviour seems like, wmudmount is not working properly ...