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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/847484
Title:
quassel crashed with SIGSEGV in _IO_vfprintf_internal()
Status in “quassel” package in Ubuntu:
New
Status in “xorg-server” package in Ubuntu:
New
Bug description:
Quassel crashed and also made Xorg to crash when I switch to full
screen mode.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: quassel 0.7.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Mon Sep 12 02:31:35 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/quassel
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: /usr/bin/quassel
SegvAnalysis:
Segfault happened at: 0x7fdd526ec522 <_IO_vfprintf_internal+50>: mov
%eax,-0x518(%rbp)
PC (0x7fdd526ec522) ok
source "%eax" ok
destination "-0x518(%rbp)" (0x7fffda001b28) not located in a known VMA
region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: quassel
StacktraceTop:
_IO_vfprintf_internal (s=0x7fffda002050, format=0x7fdd54215e0d
"LANGUAGE=%s", ap=0x7fffda0021c8) at vfprintf.c:245
___vsnprintf_chk (s=0xe88750 "", maxlen=<optimized out>, flags=1,
slen=<optimized out>, format=0x7fdd54215e0d "LANGUAGE=%s", args=0x7fffda0021c8)
at vsnprintf_chk.c:65
___snprintf_chk (s=<optimized out>, maxlen=<optimized out>, flags=<optimized
out>, slen=<optimized out>, format=<optimized out>) at snprintf_chk.c:36
snprintf (__fmt=0x7fdd54215e0d "LANGUAGE=%s", __n=42, __s=<optimized out>)
at /usr/include/x86_64-linux-gnu/bits/stdio2.h:66
KCatalogPrivate::setupGettextEnv (this=0xe71e80) at
../../kdecore/localization/kcatalog.cpp:183
Title: quassel crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
(process:3445): libindicate-WARNING **: Unable to get property data:
GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 1 has no
property named 'icon'
(process:3445): libindicate-WARNING **: Unable to get property data:
GDBus.Error:com.canonical.indicate.NO_SUCH_PROPERTY: Indicator 1 has no
property named 'count'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/847484/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
