THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added:
FS#790 - Handling windows from Java applications User who did this - Uli Schlachter (psychon) ---------- What you describe sounds like 4 different bug reports to me, not just a single one. This will mean stuff gets mixed up and this report gets closed when only some of this is handled. Also, could you give some hints on how to reproduce this? 1. I just start $RANDOM_JAVA_APP three times, notices that the class looks fine and then close this as WORKSFORME? Also, awesome uses xcb-util's xcb_get_wm_class_*() functions here, so if there is a bug, it's either in java or xcb-util, not in awesme. 2. Could you paste the xprop output for some random java window? I'm interested in the WM_PROTOCOLS property. Besides that, I kinda doubt that there is such a generic bug on our side that only bites java apps.... 3. Hm, this sounds like a good bug report. It's clearly described how to reproduce. I'll give it a try once I get access to some java runtime environment again. 4. Works everywhere else. No idea what java is smoking here. Any hints on how to reproduce? In case you didn't notice: I don't have java on any of my boxes and I usually try to reproduce these bugs via X11 forwarding with ssh to the university. For some reason (wrong phase of moon?) java doesn't accept any keyboard input here, so it might be a little difficult for me to look into this. ---------- More information can be found at the following URL: http://awesome.naquadah.org/bugs/index.php?do=details&task_id=790#comment2172 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to [email protected].
