close 368291 thanks 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? We do include a number of XIM fixes in our Qt packages; > it's possible we already have the fix.
After having a look at the qt3.3.6-diff.gz and finding that you include immodule-qt3 without mentioning this _anywhere_ in installed documentation I tried to reproduce with QT_IM_MODULE set to simple as well as xim - no luck. Maybe something changed in the meantime in kdevelop code. Thus closing the bug report (and eventually opening a new one wrt immodule-stuff) Anyway I'll keep an eye out for similar errors and reopen the bug if I find a safe way to reproduce the crashes... Thanks, Andreas -- Make a wish, it might come true. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
