applied nsz's dwm.1 patch, also added wmname - dwm - dynamic window manager
HTML git clone https://git.parazyd.org/dwm
DIR Log
DIR Files
DIR Refs
DIR README
DIR LICENSE
---
DIR commit cba6b211c2ab1564d818fa7dac85b71ba5663e0d
DIR parent 42750a621b3f0786e7fa3d7c9533c03c2a3d189d
HTML Author: Anselm R Garbe <anselm@garbe.us>
Date: Sun, 16 Aug 2009 21:39:24 +0100
applied nsz's dwm.1 patch, also added wmname
Diffstat:
M dwm.1 | 16 +++++++++++-----
1 file changed, 11 insertions(+), 5 deletions(-)
---
DIR diff --git a/dwm.1 b/dwm.1
@@ -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