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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847484 Title: quassel crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/847484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
