[Bug 847484] Re: quassel crashed with SIGSEGV in _IO_vfprintf_internal()

[Rafael Belmonte]

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 only occurs when Quassel window is maximized and then you put it in full-screen. Then X server freezes screen image and becomes totally unresponsive to mouse or keyboard events (or in rare occasions, it becomes a little crazy). At this point, with Intel graphics computer, I can jump to a tty and restart kdm service to can use X server again. But in the ATI graphics computer, going to tty causes a total system hang, resulting in a dark but flashing screen, Alt + Impr + k does nothing, but Alt + Impr + b hardly reboots the system.
While X server was frozen, I have take a look at CPU and memory usage with top command, and I did not see any strange.

Can't you reproduce the bug? Can I give any other valuable debug
information or backtrace?

** Changed in: quassel (Ubuntu)
       Status: Incomplete => New

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/847484/+subscriptions