Bug 81720

Summary: Crash when trying to add new Widget File
Product: [Applications] kdevelop Reporter: Paul Campbell <paul>
Component: generalAssignee: KDevelop Developers <kdevelop-devel>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 3.0.3   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Paul Campbell 2004-05-17 01:42:42 UTC
Version:           3.0.3 (using KDE KDE 3.2.2)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 3.3.1
 
OS:                Linux

To repeat ( on my system anyway ).

1. Open KDevelop
2. Create new KDE Simple Application (all default).
3. New File.
4. Widget (.ui) called anything.
5. Click OK.
6. Click OK in target requester.
7 **CRASH**

I have tried this 10 times, same thing.  I upgrade from 3.0.2 to 3.0.3 and same thing.  I deleted configs and confirmed it wasn't NFS drive problems, always crashes.

Backtrace:
(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 4138)]
[New Thread 32769 (LWP 4182)]
[New Thread 32770 (LWP 4194)]
0x417d01fa in waitpid () from /lib/libpthread.so.0
#0  0x417d01fa in waitpid () from /lib/libpthread.so.0
#1  0x40d3e0ba in KCrash::defaultCrashHandler ()
   from /usr/local/kde/lib/libkdecore.so.4
#2  0x417ce8e5 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x413d60e9 in QString::QString ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#5  0x0806e127 in PartController::editDocument ()
#6  0x4277663a in FileCreatePart::openCreatedFile ()
   from /usr/local/kde/lib/kde3/libkdevfilecreate.so
#7  0x42775f32 in FileCreatePart::slotNewFile ()
   from /usr/local/kde/lib/kde3/libkdevfilecreate.so
#8  0x4277a72b in FileCreatePart::qt_invoke ()
   from /usr/local/kde/lib/kde3/libkdevfilecreate.so
#9  0x4110ec9c in QObject::activate_signal ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#10 0x4110ead4 in QObject::activate_signal ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#11 0x40a769bb in KAction::activated () from /usr/local/kde/lib/libkdeui.so.4
#12 0x40a7638f in KAction::slotActivated ()
   from /usr/local/kde/lib/libkdeui.so.4
#13 0x40a76bc1 in KAction::qt_invoke () from /usr/local/kde/lib/libkdeui.so.4
#14 0x4110ec9c in QObject::activate_signal ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#15 0x4143fa0a in QSignal::signal () from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#16 0x41128a6f in QSignal::activate ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#17 0x41212425 in QPopupMenu::mouseReleaseEvent ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#18 0x41144657 in QWidget::event () from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#19 0x410b333f in QApplication::internalNotify ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#20 0x410b2a41 in QApplication::notify ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#21 0x40cab0dc in KApplication::notify ()
   from /usr/local/kde/lib/libkdecore.so.4
#22 0x4104a205 in QETWidget::translateMouseEvent ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#23 0x4104828d in QApplication::x11ProcessEvent ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#24 0x4105ef01 in QEventLoop::processEvents ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#25 0x410c5526 in QEventLoop::enterLoop ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#26 0x410c53d8 in QEventLoop::exec ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#27 0x410b3581 in QApplication::exec ()
   from /usr/local/qt-3.3.1/lib/libqt-mt.so.3
#28 0x08062858 in main ()
Comment 1 Paul Campbell 2004-05-17 01:56:22 UTC
I have discovered that "if" I choose Open With...  QT Designer (after adding that to my KMenu) that this crash doesn't happen.

I haven't marked it RESOLVED as I don't think KDevelop should simply crash when this is not done.
Comment 2 Jens Dagerbo 2004-05-20 14:30:14 UTC
Dupe. See other report for workarounds until 3.0.4 is out.

*** This bug has been marked as a duplicate of 79794 ***