Ilya, all I've seen some Qt3 crashes lately. The latest was in kalazium. I have seen a few others and I wonder if we are not having an issue with Qt3 sneaking in. The 11.4 builds have been superb with very few problems. I think this is a problem with the new gcc and Qt3. IIRC, from Trinity, when there were objects defined as (for example): QString::QString(QString const&) () The newer gcc would cause errors. If I recall, it required a syntax change removing the first class reference 'QString::' in order to be compatible with gcc 4.5+. I don't know if this is the issue here, but it looks similar. To reproduce this crash, just open kalazium and pick, for example, Ti (titanium), then choose "Spectrum" and finally choose "Export Spectrum as Image", you will then get the crash on the 'save'. The full crash I got was: System configuration startup check disabled. [Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007fa2fe72d540 in QString::QString(QString const&) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #6 0x00000000004203c2 in ?? () #7 0x000000000042065c in ?? () #8 0x0000000000416d54 in ?? () #9 0x00007fa2fe4d7b84 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #10 0x00007fa2fe4d7c6c in QObject::activate_signal(int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #11 0x00007fa2fe503a48 in QWidget::event(QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00007fa2fe485185 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x00007fa2fe4854c8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00007fa2fef7e4fe in KApplication::notify (this=0x7fff0e5bcb40, receiver=0xc91bf0, event=0x7fff0e5bc4e0) at kdecore/kapplication.cpp:552 #15 0x00007fa2fe430d66 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00007fa2fe42fb91 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x00007fa2fe43ebb2 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00007fa2fe496bf1 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00007fa2fe496b42 in QEventLoop::exec() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #20 0x0000000000441ba2 in ?? () #21 0x00007fa2fd8b0bfd in __libc_start_main () from /lib64/libc.so.6 #22 0x00000000004162a9 in ?? () #23 0x00007fff0e5bcdc8 in ?? () #24 0x000000000000001c in ?? () #25 0x0000000000000007 in ?? () #26 0x00007fff0e5be54d in ?? () #27 0x00007fff0e5be555 in ?? () #28 0x00007fff0e5be55e in ?? () #29 0x00007fff0e5be566 in ?? () #30 0x00007fff0e5be56c in ?? () #31 0x00007fff0e5be574 in ?? () #32 0x00007fff0e5be57e in ?? () #33 0x0000000000000000 in ?? () Let me know if anyone else has seen anything similar with segfaults and the QString::QString(QString const&) () type reference causing it. Also, if you have any more information or need anything else, please let me know and I'll be happy to help. (Thanks again Ilya!) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org