konsole repeatedly blows up with an unuseable backtrace

gabriel danstemporaryaccount at yahoo.ca
Thu Mar 25 21:07:02 GMT 2004

i'd report this to bugs.kde.org but the crash handler tells me that the 
backtrace is no good.

here's the deal:  i'm runing multiple konsoles with the dark transparent 
schema.  one on the right side of the screen is rather narrow and is on every 
desktop, while i have another one with multiple tabs spanning the rest of the 
screen on desktop 3 (i have 6).  and occasionally, about twice a day in fact, 
konsole just blows up -- often when i'm not even using it.  but only one of 
them blows up, and it's _always_ the bigger, multi-tabbed one on the left.

this doesn't happen at home, where i keep my box running for days at a time, 
only here @work.  here's the specs on my work box:

	System uname: 2.4.26_pre5-gentoo i686 AMD Athlon(tm) XP 2500+
	Gentoo Base System version
	Autoconf: sys-devel/autoconf-2.59-r3
	Automake: sys-devel/automake-1.8.2
	CFLAGS="-O2 -march=athlon-xp -pipe"
	CXXFLAGS="-O2 -march=athlon-xp -pipe"

i'm running kde 3.2.1 with alsa on an asus board with an nvidia chipset and 
graphics card, and here's the backtrace if it's of any use to anyone:

	(no debugging symbols found)...Using host libthread_db library 
	(no debugging symbols found)...
	(no debugging symbols found)...(no debugging symbols found)...
	(no debugging symbols found)...(no debugging symbols found)...
	(no debugging symbols found)...(no debugging symbols found)...
	0x414d89a8 in waitpid () from /lib/libpthread.so.0
	#0  0x414d89a8 in waitpid () from /lib/libpthread.so.0
	#1  0x40860614 in ?? () from /usr/kde/3.2/lib/libkdecore.so.4
	#2  0x407a6eb0 in KCrash::defaultCrashHandler(int) ()
	   from /usr/kde/3.2/lib/libkdecore.so.4
	#3  0x414d7693 in __pthread_clock_settime () from /lib/libpthread.so.0
	#4  <signal handler called>
	#5  0x404abb5c in KSharedPixmap::x11Event(_XEvent*) ()
	   from /usr/kde/3.2/lib/libkdeui.so.4
	#6  0x40b3689c in QApplication::x11ProcessEvent(_XEvent*) (this=0xbffff110, 
	    event=0xbfffed60) at kernel/qapplication_x11.cpp:3336
	#7  0x40b5446d in QEventLoop::processEvents(unsigned) (this=0x80ef978, 
	    at kernel/qeventloop_x11.cpp:192
	#8  0x40bcfb85 in QEventLoop::enterLoop() (this=0x80ef978)
	    at kernel/qeventloop.cpp:198
	#9  0x40bcfa9e in QEventLoop::exec() (this=0x80ef978)
	    at kernel/qeventloop.cpp:145
	#10 0x40bb89db in QApplication::exec() (this=0xbffff110)
	    at kernel/qapplication.cpp:2741
	#11 0x41824431 in kdemain () from /usr/kde/3.2/lib/libkdeinit_konsole.so
	#12 0x408a39b6 in kdeinitmain () from /usr/kde/3.2/lib/kde3/konsole.so
	#13 0x0804dc95 in ?? ()
	#14 0x00000001 in ?? ()
	#15 0x080601e8 in ?? ()
	#16 0x00000001 in ?? ()
	#17 0x08061ee8 in ?? ()

so if the backtrace is no good, how else can i help the kde folks fix this?  
or is this my bad somehow?

faith sustains us in the hour when reason tells us that we can not continue, 
that the whole of our whole lives is without meaning.
	- brother alwyn macomber, babylon 5 "the deconstruction of falling stars"

This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list