Version: 3.2 beta 2 (using KDE KDE 3.1.94) Installed from: Compiled From Sources Compiler: default compiler of redhat linux 9.0 OS: Linux in human words: the event: 1.) just opened quanta -> loaded the project -> worked on the code -> then pressed vpl editor -> ( vpl displayed all the content with out the style sheet) -> modified the code -> clicked on the vpl editor again and it crashed (signal 11)! (see the details below) 2.) relaunched quanta -> project was already loaded->then I tried closed the message window on the bottom to get some space on the workspace -> then clicked vpl editor icon on the tool bar -> bang quabta crashes! this happens all the time. installation stuff: compiled from source , with --prefix=/kde --enable-final --disable-debug running kde 3.1.94 compiled with the same options. path settings : [siraj@tuxcer siraj]$ cat .bashrc # .bashrc # User specific aliases and functions # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi export QTDIR=/usr/lib/qt-3.2 export KDEDIR=/kde export LD_LIBIRARY_PATH=$KDEDIR/lib export PATH=$KDEDIR/bin:$QTDIR/bin:$PATH [siraj@tuxcer siraj]$ final comment: all the other kde apps )3.1.94 works fine only quanta is playing games.! help! thanks some thing that you guys should understand: the backtrace [New Thread 1100874848 (LWP 20923)] 0xffffe410 in ?? () #0 0xffffe410 in ?? () #1 0x40dc87b3 in KCrash::defaultCrashHandler(int) () from /kde/lib/libkdecore.so.4 #2 <signal handler called> #3 0x4144e599 in QString::QString(QString const&) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #4 0x08085557 in QuantaCommon::tagFromDTD(DTDStruct*, QString const&) () #5 0x0817291e in TagAttributeTree::setCurrentNode(Node*) () #6 0x08174b30 in EnhancedTagAttributeTree::setCurrentNode(Node*) () #7 0x080ec70c in KafkaWidget::khtmlMouseReleaseEvent(khtml::MouseReleaseEvent*) () #8 0x403d1a65 in KHTMLPart::customEvent(QCustomEvent*) () from /kde/lib/libkhtml.so.4 #9 0x4117a092 in QObject::event(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #10 0x41120bd5 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #11 0x411202bc in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #12 0x40d57998 in KApplication::notify(QObject*, QEvent*) () from /kde/lib/libkdecore.so.4 #13 0x403a8e0e in KHTMLView::viewportMouseReleaseEvent(QMouseEvent*) () from /kde/lib/libkhtml.so.4 #14 0x41287c5b in QScrollView::eventFilter(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #15 0x403a9bbf in KHTMLView::eventFilter(QObject*, QEvent*) () from /kde/lib/libkhtml.so.4 #16 0x4117a189 in QObject::activate_filters(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #17 0x4117a0da in QObject::event(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #18 0x411b0d46 in QWidget::event(QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #19 0x41120bd5 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #20 0x41120395 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #21 0x40d57998 in KApplication::notify(QObject*, QEvent*) () from /kde/lib/libkdecore.so.4 #22 0x410bb687 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #23 0x410b8f60 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #24 0x410ce8e7 in QEventLoop::processEvents(unsigned) () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #25 0x41133f3f in QEventLoop::enterLoop() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #26 0x41133dfc in QEventLoop::exec() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #27 0x41120e30 in QApplication::exec() () from /usr/lib/qt-3.2/lib/libqt-mt.so.3 #28 0x080ad282 in main () #29 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6
I've fixed a bug with the same backtrace, so i hope yours is fixed :-) If not, could you bring me a testcase please?
Subject: Re: vpl editor crashes with sig 11 when when clicked and also when trying to close it > ------- I've fixed a bug with the same backtrace, so i hope yours is fixed > :-) If not, could you bring me a testcase please? In that case you should close the bug and the reporter can reopen if it's still reproducible. This is because: - we don't have a real quality testing team - reporters tend to not answer if there is no problem. ;-) Andras
Ok, so closing it ;-) BTW the changes have only been commited in the quanta_be branch! I'll port it ASAP in HEAD.