** Attachment added: Backtrace
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/847484/+attachment/3460646/+files/gdb-quassel.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847484
Last day I was halt asleep and I didn't read the line where you request me a
new backtrace and Xorg logs.
I have just attached them, I don't see anything strange in the Xorg logs, and I
hope the quassel backtrace to be useful.
If you think I need to install more debugging symbols to have a
** Attachment added: Xorg logs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/847484/+attachment/3460647/+files/Xorg.0.log.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/847484
I know the cause and have a fix pending, thanks for the information.
It has to do with how QWidget's setfullscreen behaves with regards to
KDE's toggle action system. Quassel currently does not follow the KDE
fullscreen toggle actions documentation in that one should use its
functions to turn
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
Hello, this bug is still present in Kubuntu 12.10, when I set Quassel to
fullscreen, the X server becomes completely crazzy .
Using Intel graphics card.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
New backtrace and Xorg.log please.
Also, the X server becomes completely crazzy . define crazy please.
Also, what does it do actually 'go crazy' or 'crash', that is a rather profound
difference.
Also, does memory/cpu usage change drastically when this happens?
** Changed in: quassel (Ubuntu)
Okay, I have done some new tests, in two totally different computers, one with
Intel graphics card and the other with ATI/AMD graphics card.
With X server to becomes crazy I mean, all windows starting to flash and being
totally unresponsive for instance.
An important discovery is that the bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to quassel in Ubuntu.
https://bugs.launchpad.net/bugs/847484
Title:
quassel crashed with SIGSEGV in _IO_vfprintf_internal()
To manage notifications about this
