Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalI use xscope to monitor X11 protocol. I monitor X11 protocol because I try to fix some focus issue with Swing and MPX. I noticed that following packet is transmitted when focus error occurs. How to draw a conclusion from this message? I still don;tdon't know what is invalid. Do you have any idea?
=====EDIT=====
I suppose that there is some error between client (my application) and Window Manager. I think so because there is <WM_PROTOCOLS>.
I use xscope to monitor X11 protocol. I monitor X11 protocol because I try to fix some focus issue with Swing and MPX. I noticed that following packet is transmitted when focus error occurs. How to draw a conclusion from this message? I still don;t know what is invalid. Do you have any idea?
I use xscope to monitor X11 protocol. I monitor X11 protocol because I try to fix some focus issue with Swing and MPX. I noticed that following packet is transmitted when focus error occurs. How to draw a conclusion from this message? I still don't know what is invalid. Do you have any idea?
=====EDIT=====
I suppose that there is some error between client (my application) and Window Manager. I think so because there is <WM_PROTOCOLS>.
I use xscope to monitor X11 protocol. I monitor X11 protocol because I try to fix some focus issue with Swing and MPX. I noticed that following packet is transmitted when focus error occurs. How to draw a conclusion from this message? I still don;t know what is invalid. Do you have any idea?
614.21: 32 bytes <-- X11 Server Read from fd 8 a1 20 c2 0b 07 00 c0 00 68 01 00 00 71 01 00 00 21 9f 6a 01 00 00 00 00 00 00 00 00 00 00 00 00 Event (fd 8): a1 20 c2 0b 07 00 c0 00 68 01 00 00 71 01 00 00 21 9f 6a 01 00 00 00 00 00 00 00 00 00 00 00 00 ..............EVENT: **INVALID** (161) format: 20 sequence number: 0bc2 window: WIN 00c00007 type: ATM 00000168 <WM_PROTOCOLS> data: 71 01 00 00 21 9f : 6a 01 00 00 00 00 : 00 00 00 00 00 00 : 00 00 Have 0 need 32