Summary: | Crash closing project from menu | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Steven T. Hatton <hattons> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | Andreas.Schallenberg, AngusCMarch, atzus, basti, bluedzins, edulix, FredericDruide, greatbunzinni, info, jhlaks, joel, kde, metehan, n.bergantino, rpolli, sleepingeliminator, steven_risner, ucbpabe, vdboor, vkrevs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Steven T. Hatton
2004-09-11 08:25:53 UTC
Yeah, this and bug #89052 look like two different ways of hitting the same bug. Steven, what Qt version are you running?! I can see no mention of QXIMInputContext in either latest qt-copy or the Qt-3.3.3 documentation. With the help of google I found this: http://freedesktop.org/pipermail/uim/2004-June/000370.html, which mentions this as new code as late as three months ago. Best I can figure is that you are running on a SuSE-modified Qt, in which case you should report this crash to them. On Saturday 11 September 2004 10:39, Jens Dagerbo wrote: > Steven, what Qt version are you running?! > > I can see no mention of QXIMInputContext in either latest qt-copy or the > Qt-3.3.3 documentation. <nearest suse ftp mirror>/pub/suse/i386/supplementary/KDE/update_for_9.1 > With the help of google I found this: > http://freedesktop.org/pipermail/uim/2004-June/000370.html, which mentions > this as new code as late as three months ago. > > Best I can figure is that you are running on a SuSE-modified Qt, in which > case you should report this crash to them. I'll let them know. Thanks. Yeah, there it is. SuSE's qt3-3.3.3-11.src.rpm comes with a patch that adds the code in question. In other words, this bug report is of no use to us. Closing as INVALID. *** Bug 94294 has been marked as a duplicate of this bug. *** *** Bug 95245 has been marked as a duplicate of this bug. *** *** Bug 96293 has been marked as a duplicate of this bug. *** *** Bug 96293 has been marked as a duplicate of this bug. *** *** Bug 97531 has been marked as a duplicate of this bug. *** *** Bug 103460 has been marked as a duplicate of this bug. *** *** Bug 105472 has been marked as a duplicate of this bug. *** *** Bug 105960 has been marked as a duplicate of this bug. *** *** Bug 110986 has been marked as a duplicate of this bug. *** *** Bug 114029 has been marked as a duplicate of this bug. *** *** Bug 115963 has been marked as a duplicate of this bug. *** *** Bug 116122 has been marked as a duplicate of this bug. *** I had the same problem with several versions of kdevelop. I am running FC4, which uses qt-3.3.4-17.4.fc4.kde With some help from opensuse.org.suse-linux.kde I think I have found a work around. Now, this is for SUSE 9.3 but it should work on other versions of SUSE as well. In SUSE 9.3 it appears that the XIM input method is not defined. Therefore, by setting the INPUT_METHOD to "none" KDevelop stops crashing. In SUSE, this is set by: 1. Yast->System->/etc/sysconfig Editor 2. Then click Search and enter: input method 3. Select INPUT_METHOD 4. Then set the field to "none" (without the quotes) OR 1. Edit /etc/sysconfig/language 2. Change INPUT_METHOD= to INPUT_METHOD="" 3. Save changes then run /sbin/SuSEconfig as root. To ensure that the changes were seen, I restarted X. I was told another tip was to use /usr/lib/qt3/bin/qtconfig and disable XIM in the Interface tab (at the bottom). I haven't tried this yet, but I thought it would be worth mentioning in case it works for someone else. I think I was a little hasty at posting my previous "fix". Turns out setting INPUT_METHOD didn't really fix the problem. I tried using qtconfig to disable XIM support and KDevelop rarely crashes now. I have tested this everyday for about a week. My "fix" was to disable LIBQXIM plugins completely by renaming them. mkdir /usr/lib/qt3/plugins/inputmethods/bad cd /usr/lib/qt3/plugins/inputmethods/bad mv /usr/lib/qt3/plugins/inputmethods/bad/libqxim.lib64-non-mt.so . mv /usr/lib/qt3/plugins/inputmethods/bad/libqxim.lib64.so . mv /usr/lib/qt3/plugins/inputmethods/bad/libqxim.so . Having done that, I have not experienced any crashes closing projects, switching between tabs. *** Bug 117856 has been marked as a duplicate of this bug. *** *** Bug 126303 has been marked as a duplicate of this bug. *** *** Bug 127128 has been marked as a duplicate of this bug. *** *** Bug 128072 has been marked as a duplicate of this bug. *** *** Bug 128620 has been marked as a duplicate of this bug. *** *** Bug 129715 has been marked as a duplicate of this bug. *** I have experienced one crash when closing a file after having deleted the /usr/lib/qt3/plugins/inputmethods/ directory!. This is the back trace - not a very useful one but that's all I can do for now: (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1217542464 (LWP 12161)] [New Thread -1227732048 (LWP 3086)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0x43f14136 in nanosleep () from /lib/tls/i686/cmov/libc.so.6 #2 0x43f13f3c in sleep () from /lib/tls/i686/cmov/libc.so.6 #3 0x4113d70f in ?? () from /usr/lib/libkparts.so.2 #4 0x00000001 in ?? () #5 0x00000000 in ?? () This is my backtrace: KDevelop 3.3.4 running on SuSE 10.0 (x86), qt 3.3.6. Happens very often when I open a single project. When I open the project on startup everything is fine. Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47282119770192 (LWP 21524)] [New Thread 1082132800 (LWP 21757)] [KCrash handler] #5 0x00002b00b5a589a8 in QWidget::topLevelWidget () from /usr/lib/qt3/lib64/libqt-mt.so.3 #6 0x00002b00bc7ca0d6 in QXIMInputContext::setMicroFocus (this=0xffea30, x=27, y=112, h=14, f=0x0) at qximinputcontext_x11.cpp:761 #7 0x00002b00b59a7a64 in QWidget::setMicroFocusHint () from /usr/lib/qt3/lib64/libqt-mt.so.3 #8 0x00002aaaaac26609 in KateViewInternal::updateMicroFocusHint () from /opt/kde3/lib64/kde3/libkatepart.so #9 0x00002aaaaac2a90c in KateViewInternal::updateCursor () from /opt/kde3/lib64/kde3/libkatepart.so #10 0x00002aaaaac2ce5a in KateView::setCursorPositionInternal () from /opt/kde3/lib64/kde3/libkatepart.so #11 0x00002aaaaac50874 in KateView::setCursorPositionReal () from /opt/kde3/lib64/kde3/libkatepart.so #12 0x00002b00b45a8d96 in PartController::editDocumentInternal () from /opt/kde3/lib64/libkdevshell.so.0 #13 0x00002b00b45b61ed in ProjectSession::loadDocument () from /opt/kde3/lib64/libkdevshell.so.0 #14 0x00002b00b45b6238 in ProjectSession::loadDocument () from /opt/kde3/lib64/libkdevshell.so.0 #15 0x00002b00b45b62ed in ProjectSession::qt_invoke () from /opt/kde3/lib64/libkdevshell.so.0 #16 0x00002b00b5a2aa8c in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x00002b00b5d0ec52 in QSignal::signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00002b00b5a435a5 in QSignal::activate () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00002b00b5a49bc8 in QSingleShotTimer::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #20 0x00002b00b59d3a95 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #21 0x00002b00b59d46c7 in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #22 0x00002b00b53db218 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #23 0x00002b00b59ca005 in QEventLoop::activateTimers () from /usr/lib/qt3/lib64/libqt-mt.so.3 #24 0x00002b00b598a4ed in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #25 0x00002b00b59e87a1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #26 0x00002b00b59e864a in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #27 0x00000000004072f7 in main (argc=<value optimized out>, argv=<value optimized out>) at main.cpp:145 The last Backtrace has nothing to do with the original bug. It is a duplicate of a KATE bug fixed in KDE 3.5.4 Ok, thx. Which one? And why it is still in KDevelop 3.3.4? KDevelop only uses KATE, KDevelop does not provide KATE. KATE is part of KDE. So unless you update your KDE to 3.5.4 the bug will not go away. I upgraded everything at the same time. *** Bug 133598 has been marked as a duplicate of this bug. *** *** Bug 134347 has been marked as a duplicate of this bug. *** |