[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-www
Subject:    Re: Grrrrrrrrrrrrrrrrr.
From:       Dirk Mueller <mueller () kde ! org>
Date:       2004-03-19 23:59:40
Message-ID: 200403200059.40792.mueller () kde ! org
[Download RAW message or body]

On Friday 19 March 2004 22:14, Gary G. Taylor wrote:

> First, the bug reporter in KDE doesn't work.

Thats really hard to believe, as we get currently over new 600 bugreports a 
week. But as you didn't even mention the error message, there is hardly any 
help possible. 



> to tell you that the damn thing keeps crashing and I'm getting tired of
> this crap?!
> KDE 3.1.4 (KDE 3.1.3) (Mandrake Linux Cooker i586 - Cooker)

It has never occured to you that Mandrake Cooker  is not the most stable way 
to use a Linux system?

>
> 0x40f97656 in waitpid () from /lib/i686/libpthread.so.0
> #0  0x40f97656 in waitpid () from /lib/i686/libpthread.so.0
> #1  0x40683fda in KCrash::defaultCrashHandler(int) ()
>    from /usr/lib/libkdecore.so.4
> #2  <signal handler called>
> #3  0x40cbeb1a in QString::QString(QString const&) ()
>    from /usr/lib/qt3/lib/libqt-mt.so.3
> #4  0x4068ba8e in KURL::url(int, int) const () from
> /usr/lib/libkdecore.so.4

These kind of crashes usually indicate binary incompatibilities. You should 
check if all your packages are up to date and consistent. This is a problem 
when using an unstable development platform like cookier. 

Did you upgrade glibc, libstdc++, gcc or Qt lately ? or updated KDE without 
the other packages?


Dirk

_______________________________________________
kde-www mailing list
kde-www@kde.org
https://mail.kde.org/mailman/listinfo/kde-www
[prev in list] [next in list] [prev in thread] [next in thread]