diff options
| author | Anselm R Garbe <anselm@garbe.us> | 2009-08-16 21:39:24 +0100 |
|---|---|---|
| committer | Anselm R Garbe <anselm@garbe.us> | 2009-08-16 21:39:24 +0100 |
| commit | cba6b211c2ab1564d818fa7dac85b71ba5663e0d (patch) | |
| tree | cca235470d7e765f42f58cad9a7c517b32237595 /dwm.1 | |
| parent | 42750a621b3f0786e7fa3d7c9533c03c2a3d189d (diff) | |
applied nsz's dwm.1 patch, also added wmname
Diffstat (limited to 'dwm.1')
| -rw-r--r-- | dwm.1 | 16 |
1 files changed, 11 insertions, 5 deletions
@@ -149,11 +149,17 @@ code. This keeps it fast, secure and simple. .SH BUGS Java applications which use the XToolkit/XAWT backend may draw grey windows only. The XToolkit/XAWT backend breaks ICCCM-compliance in recent JDK 1.5 and early -JDK 1.6 versions, because it assumes a reparenting window manager. As a workaround -you can use JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or you -can set the following environment variable (to use the older Motif -backend instead): -.BR AWT_TOOLKIT=MToolkit . +JDK 1.6 versions, because it assumes a reparenting window manager. Possible workarounds +are using JDK 1.4 (which doesn't contain the XToolkit/XAWT backend) or setting the +environment variable +.BR AWT_TOOLKIT=MToolkit +(to use the older Motif backend instead) or running +.B xprop -root -f _NET_WM_NAME 32a -set _NET_WM_NAME LG3D +or +.B wmname LG3D +(to pretend that a non-reparenting window manager is running that the +XToolkit/XAWT backend can recognize) or when using OpenJDK setting the environment variable +.BR _JAVA_AWT_WM_NONREPARENTING=1 . .P GTK 2.10.9+ versions contain a broken .BR Save\-As |