[Linux-disciples] Re: Linux-disciples Digest, Vol 11, Issue 7

karl sokol fritzsokol at yahoo.com
Wed Dec 15 15:42:45 EST 2004


Thanks Adam.  This is actually on my desktop with Suse.  the town of Franklin Grove has approved getting wireless infrastructure, so I will hang tight with the annoyance until I am online and can upgrade to Debian unstable.

linux-disciples-request at lists.bostoncoop.net wrote:


Message: 1
Date: Sat, 11 Dec 2004 12:02:08 -0500
From: Adam Rosi-Kessel 
Subject: Re: [Linux-disciples] Strange 'crash' when exiting a program
To: linux-disciples at lists.bostoncoop.net
Message-ID: <20041211170208.GA29332 at bostoncoop.net>
Content-Type: text/plain; charset="us-ascii"

Are you running Debian? Unstable? KDE has been through some hard times
but I believe recent versions don't do this anymore. If you're running
Debian Testing you might have a slightly outdated version where this
hasn't been fixed yet.

You might also check the bug tracking sytsem (http://bugs.debian.org) to
see if his has been reported for any of the packages you are using.

On Fri, Dec 10, 2004 at 10:56:25AM -0800, Karl Sokol wrote:
> I continuously get a crash error when I close a KDE
> application or stop the screen saver with a window
> that says ?the application unknown (katomic) crashed
> and caused a signal 11 (SIGSEGV). KDE apps 'crash'
> when I close them in other window managers as well. 
> It does not happen on non-kde apps like gimp or xine. 
> 
> 
> The backtrace gives:
> 
> 
> (no debugging symbols found)...(no debugging symbols
> found)...
> 
> --------- {this repeats a bunch of times}
> 
> (no debugging symbols found)...(no debugging symbols
> found)...[New Thread 16384 (LWP 16595)]
> 
> (no debugging symbols found)...(no debugging symbols
> found)...
> 
> ----------{ and repeats a bunch more}
> 
> 0x41195a86 in waitpid () from
> /lib/i686/libpthread.so.0
> #0 0x41195a86 in waitpid () from
> /lib/i686/libpthread.so.0
> #1 0x40681d30 in KCrash::defaultCrashHandler(int) ()
> from /opt/kde3/lib/libkdecore.so.4
> #2 0x4119496c in __pthread_sighandler () from
> /lib/i686/libpthread.so.0
> #3 
> #4 0x40f12bea in glXChannelRectSyncSGIX () from
> /usr/lib/libGL.so.1
> #5 0x08060168 in ?? ()
> #6 0x40f44540 in ?? () from /usr/lib/libGL.so.1
> #7 0x08060168 in ?? ()
> #8 0x40f14ed6 in glXChannelRectSyncSGIX () from
> /usr/lib/libGL.so.1
> #9 0x08060168 in ?? ()
> #10 0x08060168 in ?? ()
> #11 0x41166a88 in __JCR_LIST__ () from
> /usr/X11R6/lib/libX11.so.6
> #12 0x080694d0 in ?? ()
> #13 0x410809ea in XCloseDisplay () from
> /usr/X11R6/lib/libX11.so.6
> #14 0x409a68f2 in qt_cleanup() () from
> /usr/lib/qt3/lib/libqt-mt.so.3
> #15 0x40a1353c in QApplication::~QApplication() ()
> from /usr/lib/qt3/lib/libqt-mt.so.3
> #16 0x406148e3 in KApplication::~KApplication() ()
> from /opt/kde3/lib/libkdecore.so.4
> #17 0x0805469a in main ()
> 
> 
> The log is always identical except for the 0x000000000
> #s and the last couple of lines sometimes change. For
> example:
> 
> #16 0x406b5bb3 in KApplication::~KApplication() ()
> from /opt/kde3/lib/libkdecore.so.4
> #17 0x0806b409 in BaseFactory::~BaseFactory() ()
> #18 0x08065107 in main ()
> 
> Any ideas on how to squelch this annoyance, or at
> least get better debugging info?
> 
> 
> =====
> Grace and peace,
> Karl
> 




Grace and peace,
Karl
		
---------------------------------
Do you Yahoo!?
 The all-new My Yahoo! – What will yours do?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.bostoncoop.net/pipermail/linux-disciples/attachments/20041215/aaa06be0/attachment.htm


More information about the Linux-disciples mailing list