Application that crashed: korganizer Version of the application: 4.3.0 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.30-ice x86_64 What I was doing when the application crashed: When adding an event to a calendar in remote file calendar resource (which points to a local file using the file:// protocol), korganizer sometimes crashes. After restarting korganizer, the event has not been added, but ususally it's possible to add it without a crash. Using korganizer 4.3 from arch linux packages. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [KCrash Handler] #5 0x00007f528bd82187 in KCal::IncidenceBase::uid () from /usr/lib/libkcal.so.4 #6 0x00007f5284515231 in KOEventViewer::changeIncidenceDisplay () from /usr/lib/libkorganizer_eventviewer.so.4 #7 0x00007f528b6f0907 in CalendarView::incidenceAdded () from /usr/lib/libkorganizerprivate.so.4 #8 0x00007f528b6f6c79 in CalendarView::qt_metacall () from /usr/lib/libkorganizerprivate.so.4 #9 0x00007f528a7fde0c in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0x00007f528af67e4f in KOrg::IncidenceChangerBase::incidenceAdded () from /usr/lib/libkorganizer_interfaces.so.4 #11 0x00007f528b77a375 in IncidenceChanger::addIncidence () from /usr/lib/libkorganizerprivate.so.4 #12 0x00007f528b702ec7 in KOEventEditor::processInput () from /usr/lib/libkorganizerprivate.so.4 #13 0x00007f528b701056 in KOIncidenceEditor::slotButtonClicked () from /usr/lib/libkorganizerprivate.so.4 #14 0x00007f528c4346a9 in KDialog::qt_metacall () from /usr/lib/libkdeui.so.5 #15 0x00007f528c4e8d10 in KPageDialog::qt_metacall () from /usr/lib/libkdeui.so.5 #16 0x00007f528b701e20 in KOIncidenceEditor::qt_metacall () from /usr/lib/libkorganizerprivate.so.4 #17 0x00007f528b703380 in KOEventEditor::qt_metacall () from /usr/lib/libkorganizerprivate.so.4 #18 0x00007f528a7fde0c in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #19 0x00007f528a80093e in QSignalMapper::mapped () from /usr/lib/libQtCore.so.4 #20 0x00007f528a801b30 in QSignalMapper::map () from /usr/lib/libQtCore.so.4 #21 0x00007f528a801da0 in QSignalMapper::qt_metacall () from /usr/lib/libQtCore.so.4 #22 0x00007f528a7fde0c in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #23 0x00007f528a294017 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4 #24 0x00007f5289ff5b2b in ?? () from /usr/lib/libQtGui.so.4 #25 0x00007f5289ff773b in ?? () from /usr/lib/libQtGui.so.4 #26 0x00007f5289ff7985 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4 #27 0x00007f5289ce3810 in QWidget::event () from /usr/lib/libQtGui.so.4 #28 0x00007f5289c94e2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #29 0x00007f5289c9bf41 in QApplication::notify () from /usr/lib/libQtGui.so.4 #30 0x00007f528c4bdff6 in KApplication::notify () from /usr/lib/libkdeui.so.5 #31 0x00007f528a7e8d0c in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #32 0x00007f5289c9b810 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #33 0x00007f5289d01714 in ?? () from /usr/lib/libQtGui.so.4 #34 0x00007f5289d00409 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #35 0x00007f5289d285fc in ?? () from /usr/lib/libQtGui.so.4 #36 0x00007f52834f1dbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #37 0x00007f52834f5568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #38 0x00007f52834f5690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #39 0x00007f528a8111d6 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #40 0x00007f5289d27dde in ?? () from /usr/lib/libQtGui.so.4 #41 0x00007f528a7e7612 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #42 0x00007f528a7e79e4 in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #43 0x00007f528a7e9b99 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #44 0x00000000004085e2 in _start () This bug may be a duplicate of or related to bug 176991 Reported using DrKonqi
Indeed, this a duplicate of bug 176991. Thanks *** This bug has been marked as a duplicate of bug 176991 ***