On 03.06.06 14:34:49, Christopher Martin wrote: > On Saturday 03 June 2006 14:25, you wrote: > > On 03.06.06 13:53:50, Christopher Martin wrote: > > > On Sunday 28 May 2006 17:50, Andreas Pakulat wrote: > > > > The backtrace of kdevelop crashing is attached. I tried to change > > > > the XIM input method with qtconfig from "on the spot" to root but > > > > it didn't help. I first couldn't reproduce this anymore after > > > > playing around a bit, but today it happened again and thus I'm > > > > reporting this. The mailing list thread I opened can be read from > > > > here: > > > > > > > > http://lists.kde.org/?l=kdevelop-devel&m=114878188129406&w=2 > > > > > > > > I'll try to reproduce this with Debian's kdevelop tomorrow. > > > > > > I can't reproduce any crashes here, but I could be simply failing > > > to trigger the right circumstances. > > > > > > Can you confirm that the bug exists using stock Debian packages? > > > Perhaps some more info on how to reproduce it? > > > > kdevelop package from debian works. I will try with a rebuilt qt3.3 > > without xim patches on Monday/Tuesday. > > OK, so if I understand correctly then, Debian isn't really affected by > the crashes? Well, yes and no. The currently included kdevelop doesn't trigger the crash, but at least from my experience the next kdevelop release (3.4.0) will. > We do include a number of XIM fixes in our Qt packages; > it's possible we already have the fix. As far as I understood, these "fixes" are exactly the problem, according to the upstream bugreport a "plain Qt3" won't show these crashes. As I said I'll check with a Qt package without debian XIM patches monday/tuesday. Andreas -- Good day for overcoming obstacles. Try a steeplechase.
Description: PGP signature