FWIW quassel basically drowns xorg in silly requests which then renders xorg (or drivers) in a state where it in fact goes crazy. Since it is only semi-related to the issue reported I removed an xorg affectness. Most likely that however happens due to stack exhaustion where xlib then starts reading corrupted memory or something equally random. Should it be a reproducible with some simple xlib test program that shoudl be reported separately as the presented bug is really about quassel not following KDE's toggle action documentation.
FWIW quassel basically drowns xorg in silly requests which then renders xorg (or drivers) in a state where it in fact goes crazy. Since it is only semi-related to the issue reported I removed an xorg affectness. Most likely that however happens due to stack exhaustion where xlib then starts reading corrupted memory or something equally random. Should it be a reproducible with some simple xlib test program that shoudl be reported separately as the presented bug is really about quassel not following KDE's toggle action documentation.