On Tuesday 03 April 2001 22:08, Jonathan Terhorst wrote:
> I'm having major problems with qt-2.3.0, xf 4.0.3, and the latest kde-2.1.1 
> rpms on mandrake 7.2. Namely, anytime I try to fire up a KDE app with 
> QT_XFT=1 it crashes as follows:
> 
> [jonathan@spe-94-93 bin]$ QT_XFT=1 konqueror &
> [2] 28829
> [jonathan@spe-94-93 bin]$ KCrash: crashing.... crashRecursionCounter = 2
> KCrash: Application Name = konqueror path = <unknown>
> 
> This is true for basically every binary in every KDE package, including the 
> desktop stuff itself - so KDE won't even start up (!).
> 
> Without setting QT_XFT it starts up fine, albeit without antialiasing. On the 
> other hand I can start up the QT designer, licq, and other non-KDE apps that 
> link to QT using QT_XFT=1 and I get purty anti-aliased fonts. So the problem 
> lies somewhere with KDE itself. Could someone point me in the right direction 
> as far as debugging goes? As shown above I'm not even getting a stack trace 
> when it crashes. I'd like to help out and find this bug which a lot of people 
> seem to be experiencing. Thanks,

Recompile qt with -debug, kdelibs with --enable-debug, start konqueror using
QT_XFT=1 konqueror --nocrashhandler
and you should get a valid core dump (then gdb konqueror core, "bt").
Make sure to "ulimit -c unlimited" first.
Not sure why you don't get a stacktrace in drkonqi though.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<