With python-xlib and the randr extension, certain events are not reported to applications as their event code is not correctly registered. Those events actually share a event code and they are differentiated with a sub-code. With my patch, events are correctly reported. I provided the patch also to upstream. Reproducible: Always
Created attachment 345476 [details, diff] Xlib-ext-randr-outputevent.patch
Created attachment 345478 [details, diff] ebuild patch
Is there a bug/patch tracker where we can keep track of upstream on this issue?
Created attachment 345488 [details, diff] randr-parse-outputinfo.patch This is another patch that fixes the parsing of responses. I'm talking with them in their IRC channel.
Ok, just let us know if/when they actually commit the patches.
Created attachment 347432 [details, diff] python-xlib-0.15_rc1-fix-randr-subevents.patch Okay, the attached patch got accepted upstream a week ago, see http://sourceforge.net/p/python-xlib/code/160/ . The last part of the patch is necessary for the 0.15_rc1 version as the parsing of the response was already patched in trunk. Since then, there were only commits to improve the infrastructure for subevents, afaik. In case someone's interested, it's required for my daemon that configures X and PA if a new display is plugged in (https://github.com/anyc/anyc-overlay/tree/master/app-misc/mplugd).
Ah, got the commit for the last part of my patch: http://sourceforge.net/p/python-xlib/code/146/
I presume all patches made it to 0.23.
