[apport] kicker crashed with SIGSEGV in XConnectionNumber()

Bug #94635 reported by Lafa
22
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: kdebase

I rebooted the machine get this right after log in to kde on a fresh reboot

ProblemType: Crash
Architecture: i386
Date: Wed Mar 21 19:24:07 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/kicker
Package: kicker 4:3.5.6-0ubuntu16
PackageArchitecture: i386
ProcCmdline: kicker --nocrashhandler
ProcCwd: /home/lafa
ProcEnviron:
 PATH=/home/lafa/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 XConnectionNumber () from /usr/lib/libX11.so.6
 QEventLoop::QEventLoop () from /usr/lib/libqt-mt.so.3
 QApplication::eventLoop () from /usr/lib/libqt-mt.so.3
 QApplication::exit () from /usr/lib/libqt-mt.so.3
 ?? () from /usr/lib/libkdeinit_kicker.so
Uname: Linux lafa-desktop 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Lafa (luis-alves) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in kdebase:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XConnectionNumber (dpy=0x805c6b8) at ../../src/Macros.c:42
QEventLoop (this=0x805c6b8, parent=0x8056a88, name=0xb7439cf1 "default event loop") at kernel/qeventloop.cpp:107
QApplication::eventLoop () at kernel/qapplication.cpp:2730
QApplication::exit (retcode=0) at kernel/qapplication.cpp:2779
sighandler () at /build/buildd/kdebase-3.5.6/./kicker/kicker/core/main.cpp:54

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
James Sparenberg (james-linuxrebel) wrote :

Didn't know which of these to attach to . But I have been experiencing similar problems with near constant crashes of kicker. Then I noticed that when kicker crashed the systray applet would come back in a "damaged" state with only half of it's icons or worse.

So I created a new panel small that only holds systray. Not a single crash since then. If I put another applet in that panel, or if I move the applet to my other panel. It crashes. Further testing in that PCLinuxOS just updated to kde3.8. Low and behold the exact same behavior. Constant kicker crashes, I moved the systray off and sure enough, the crashes have stopped. I plan on checking upstream for bug reports. But it does seem to be connected to systray and related to kde3.8.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This isn't an issue in Kubuntu Intrepid (8.10) since Kicker is no more. (replaced by Plasma)
Thanks for the bug report, and thanks for your interest to help Kubuntu!

Changed in kdebase:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.