Application: akonadi_kcal_resource (4.10) KDE Platform Version: 4.10.5 Qt Version: 4.8.2 Operating System: Linux 3.10-3-rt-686-pae i686 Distribution: Debian GNU/Linux testing (unknown.new.testing) -- Information about the crash: - What I was doing when the application crashed: I was trying to create a new calendar which type was traditional. The window after the type appeared but the box of the second page ( after the presentation of calendar creation) was empty, then i clicked next and the bug ocured. - Unusual behavior I noticed: I couldn't manage to create an event in the calendar view, that why i tried anything to correct it and then I tried to create a new calendar (Cf top of that document) - Custom settings of the application: The application was installed on a kali linux (ie: debian stable) updated to debian testing. It was a new installation. the desktop used is Gnome, but kde-full package is installed. The crash can be reproduced every time. -- Backtrace: Application: KDE Calendar (traditional) (akonadi_kcal_resource), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [KCrash Handler] #6 0xb6c7c2b4 in KPageWidgetItem::widget() const () from /usr/lib/libkdeui.so.5 #7 0x0805bd53 in ?? () #8 0xb6b83e53 in ?? () from /usr/lib/libkdeui.so.5 #9 0xb740ecd2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #10 0xb6b94415 in KDialog::user2Clicked() () from /usr/lib/libkdeui.so.5 #11 0xb6b94d28 in KDialog::slotButtonClicked(int) () from /usr/lib/libkdeui.so.5 #12 0xb6b967f8 in ?? () from /usr/lib/libkdeui.so.5 #13 0xb740ecd2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #14 0xb7413fa5 in QSignalMapper::mapped(int) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #15 0xb74141ed in QSignalMapper::map(QObject*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #16 0xb74142fe in QSignalMapper::map() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #17 0xb7414754 in ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #18 0xb740ecd2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #19 0xb67e03ad in QAbstractButton::clicked(bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #20 0xb64e3ddd in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #21 0xb64e462b in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #22 0xb64e48e6 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #23 0xb611dbc2 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #24 0xb64e3ca2 in QAbstractButton::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #25 0xb6585428 in QPushButton::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #26 0xb60c447c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #27 0xb60c9969 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #28 0xb6c44554 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #29 0xb73f654e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #30 0xb60c52df in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #31 0xb614e0d5 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #32 0xb614cb99 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #33 0xb6177614 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #34 0xb563142e in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #35 0xb56317d8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #36 0xb5631898 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #37 0xb742884f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #38 0xb61771fa in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #39 0xb73f501c in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #40 0xb73f5311 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #41 0xb6604a7d in QDialog::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #42 0x080549c0 in _start () Reported using DrKonqi
Which calendar plugin/type are were you using? We have native resources for most types of calendars now so is possible there is a better way than this compatibility resource.
I was trying to create a traditionnal Calendar (KDE Traditionnal if i'm not mistaken). Thanks for your quick answer.
In case you are trying to add a calendar that is contained in a single file, try the iCal resource instead. It was newly written for that use case and does not require old legacy plugins that the "Traditional Calendar" resource uses.
(In reply to comment #3) > In case you are trying to add a calendar that is contained in a single file, > try the iCal resource instead. > It was newly written for that use case and does not require old legacy > plugins that the "Traditional Calendar" resource uses. Thank you, I didn't tryed because I used the legacy one on my previous laptop. In fact, if it works, the path where it's stored didn't mattered. ;) If I had time i'd it fixed by myself, but I am kinda lazy at home :p Maybe not allowing to create new calendars with the old format could be good ?
Yes, we are trying to remove the legacy handlers but I think there is still one plugin we don't have a replacement for yet. Hmm, we could probably blacklist the single file calendar plugin though
(In reply to comment #5) > Yes, we are trying to remove the legacy handlers but I think there is still > one plugin we don't have a replacement for yet. > Hmm, we could probably blacklist the single file calendar plugin though If I have some free time, I'll manage to find it and at least catch the exception to avoid the crash. ^^ It's the minimum I can do and it will make me explore some KDE code °^° Thanks for your help and for supporting such a great and useful software.