Apologies for all the typos in the text of the previous message; I was
somewhat distracted while writing it up. Most importantly, I wrote
"0x200", where I meant "0x2000" (2**29). I'm still not
clear on why 0x3fff isn't accepted, as that should fit into a
32-bit integer (it will be ne
The following patch works around the problem for me. The real problem
is twofold:
1. Java is generating __NET_WM_STATE messages with very large X atom
numbers for data[2], that do not correspond to real atoms. I'm not
sure if this is legal or not, or what the numbers might mean if it
i
2 matches
Mail list logo
