Right after resuming from suspend to ram, anything X related like moving windows, focusing windows, etc is very unresponsive. Everything is very sluggish for around 10s or 20s, while the cpu usage of the X process is very high. This also happens when switching back from a virtual terminal (ctr-alt-f1 then ctr-alt-f7). Problem started happening with version 0.5.5 I've done a bisect of the code between 0.5.4.3 and 0.5.5 and found this commit to be the cause: 0aab3c4 Reset xkb config when new keyboard is detected Reverting that commit on top of 0.5.6 makes the problem go away.
Well, yes - that commit does exactly what's advertised, i.e., it resets XKB settings whenever it gets a new keyboard notification signal, as happens to be the case upon resume. Without this, the plugin will be losing its settings just as it used to. As for the time it takes to restore the settings, there isn't much I can think of to speed this up; it takes pretty much the same time as, say, changing the settings through xkb-plugin's Configure dialog (it might take a bit more since X seems to be sending multiple X-new-device notifications.
Fair enough. My problem is that this reset is very disruptive. It keeps X running at full speed for a few seconds making things very unresponsive. I'm talking about several seconds latency between a mouse click and things happening. Could it be that the reset is exposing an underlying bug somewhere else. Any ideas how to debug it?
Ditto. I'm experienceing the same issue, only in my case the unresponsiveness, sluggishness, and slow time to usability is on the order of ten seconds. It is really annoying for anyone (like me) who uses multiple x sessions and routinely toggles between virtual terminals. Please consider raising the priority of this bug because of the following written on the homepage of the xfce website (emphasis added): "Xfce is a lightweight desktop environment for UNIX-like operating systems. It aims to be --FAST-- and low on system resources". BTW, I vaguely remember, and I could be wrong, that way back on the xfce4.6 desktop the plugin never did lose its settigns.