Bug 293360

Summary: KAlarm crashes when adding a new alert entry
Product: [Applications] kalarm Reporter: Alexander Stein <alexanders83>
Component: generalAssignee: David Jarvie <djarvie>
Status: CLOSED FIXED    
Severity: crash CC: alex
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 4.8.1
Sentry Crash Report:
Attachments: backtrace from crash after KAlarm start

Description Alexander Stein 2012-02-05 13:34:39 UTC 
Application: kalarm (2.8.0-ak)
KDE Platform Version: 4.8.00 (4.8.0 (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.2.1-gentoo-r2 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
I opened the main window and tried to add a new alert entry from the toolbar. Right after pressing the menu entry KAlarm crashed.

The crash can be reproduced some of the time.

-- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fa6eae63e45 in KAlarmCal::KAEvent::category (this=<optimized out>) at /tmp/portage/kde-base/kdepimlibs-4.8.0/work/kdepimlibs-4.8.0/kalarmcal/kaevent.cpp:1862
#7  0x00000000004871e1 in AlarmCalendar::events (this=0x16f1560, collection=..., type=...) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/alarmcalendar.cpp:1852
#8  0x000000000046b879 in AlarmCalendar::events (this=0x16f1560, s=...) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/alarmcalendar.h:89
#9  0x000000000047343f in EditAlarmDlg::initValues (this=0x1fb6730, event=<optimized out>) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/editdlg.cpp:598
#10 0x000000000047546f in EditAlarmDlg::init (this=0x1fb6730, event=0x0) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/editdlg.cpp:462
#11 0x0000000000478440 in EditDisplayAlarmDlg::EditDisplayAlarmDlg (this=0x1fb6730, Template=<optimized out>, parent=<optimized out>, getResource=<optimized out>) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/editdlgtypes.cpp:125
#12 0x000000000046f35a in EditAlarmDlg::create (Template=false, type=<optimized out>, parent=0x1858c30, getResource=EditAlarmDlg::RES_PROMPT) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/editdlg.cpp:111
#13 0x00000000004e2852 in KAlarm::editNewAlarm (type=<optimized out>, parent=<optimized out>) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/functions.cpp:1111
#14 0x00000000004aaeb4 in MainWindow::qt_metacall (this=0x1749dd0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffe270b560) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0_build/kalarm/mainwindow.moc:156
#15 0x00007fa6e6e2dcff in QMetaObject::activate (sender=0x181bb60, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffe270b560) at kernel/qobject.cpp:3278
#16 0x00007fa6e60fbe12 in QAction::triggered (this=<optimized out>, _t1=false) at .moc/debug-shared/moc_qaction.cpp:263
#17 0x00007fa6e60fbfe2 in QAction::activate (this=0x181bb60, event=<optimized out>) at kernel/qaction.cpp:1257
#18 0x00007fa6e657a023 in QMenuPrivate::activateCausedStack (this=0x18ad570, causedStack=..., action=0x181bb60, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1005
#19 0x00007fa6e658056a in QMenuPrivate::activateAction (this=0x18ad570, action=0x181bb60, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1097
#20 0x00007fa6e7c117a2 in KMenu::mouseReleaseEvent (this=0x181bc50, e=0x7fffe270c3c0) at /tmp/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/kdeui/widgets/kmenu.cpp:464
#21 0x00007fa6e615c1f1 in QWidget::event (this=0x181bc50, event=0x7fffe270c3c0) at kernel/qwidget.cpp:8295
#22 0x00007fa6e6581713 in QMenu::event (this=0x181bc50, e=0x7fffe270c3c0) at widgets/qmenu.cpp:2405
#23 0x00007fa6e6102800 in QApplicationPrivate::notify_helper (this=0x14c0bc0, receiver=0x181bc50, e=0x7fffe270c3c0) at kernel/qapplication.cpp:4481
#24 0x00007fa6e6108510 in QApplication::notify (this=<optimized out>, receiver=0x181bc50, e=0x7fffe270c3c0) at kernel/qapplication.cpp:4042
#25 0x00007fa6e7b49371 in KApplication::notify (this=0x14ac640, receiver=0x181bc50, event=0x7fffe270c3c0) at /tmp/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311
#26 0x00007fa6e6e1714b in QCoreApplication::notifyInternal (this=0x14ac640, receiver=0x181bc50, event=0x7fffe270c3c0) at kernel/qcoreapplication.cpp:787
#27 0x00007fa6e6103c08 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#28 QApplicationPrivate::sendMouseEvent (receiver=0x181bc50, event=0x7fffe270c3c0, alienWidget=0x0, nativeWidget=0x181bc50, buttonDown=0x7fa6e6c9fc78, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3141
#29 0x00007fa6e618d353 in QETWidget::translateMouseEvent (this=0x181bc50, event=<optimized out>) at kernel/qapplication_x11.cpp:4398
#30 0x00007fa6e618b759 in QApplication::x11ProcessEvent (this=0x14ac640, event=0x7fffe270cb70) at kernel/qapplication_x11.cpp:3590
#31 0x00007fa6e61b4532 in x11EventSourceDispatch (s=0x14c3990, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#32 0x00007fa6e02460da in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#33 0x00007fa6e02468e8 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0
#34 0x00007fa6e0246a7f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#35 0x00007fa6e6e452fa in QEventDispatcherGlib::processEvents (this=0x14b0a50, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#36 0x00007fa6e61b41e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007fa6e6e15bb2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#38 0x00007fa6e6e15e34 in QEventLoop::exec (this=0x7fffe270ce80, flags=...) at kernel/qeventloop.cpp:201
#39 0x00007fa6e657db4b in QMenu::exec (this=<optimized out>, p=..., action=<optimized out>) at widgets/qmenu.cpp:2049
#40 0x00007fa6e65c1569 in QToolButtonPrivate::popupTimerDone (this=0x17acd80) at widgets/qtoolbutton.cpp:955
#41 0x00007fa6e65c1ca1 in QToolButton::qt_metacall (this=0x1863fe0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0x7fffe270d120) at .moc/debug-shared/moc_qtoolbutton.cpp:114
#42 0x00007fa6e6e2dcff in QMetaObject::activate (sender=0x1863fe0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#43 0x00007fa6e64f4883 in QAbstractButtonPrivate::emitPressed (this=<optimized out>) at widgets/qabstractbutton.cpp:560
#44 0x00007fa6e64f53bc in QAbstractButton::mousePressEvent (this=0x1863fe0, e=0x7fffe270dd20) at widgets/qabstractbutton.cpp:1096
#45 0x00007fa6e65c1dd8 in QToolButton::mousePressEvent (this=0x1863fe0, e=0x7fffe270dd20) at widgets/qtoolbutton.cpp:712
#46 0x00007fa6e615c73c in QWidget::event (this=0x1863fe0, event=0x7fffe270dd20) at kernel/qwidget.cpp:8291
#47 0x00007fa6e6102800 in QApplicationPrivate::notify_helper (this=0x14c0bc0, receiver=0x1863fe0, e=0x7fffe270dd20) at kernel/qapplication.cpp:4481
#48 0x00007fa6e6108510 in QApplication::notify (this=<optimized out>, receiver=0x1863fe0, e=0x7fffe270dd20) at kernel/qapplication.cpp:4042
#49 0x00007fa6e7b49371 in KApplication::notify (this=0x14ac640, receiver=0x1863fe0, event=0x7fffe270dd20) at /tmp/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311
#50 0x00007fa6e6e1714b in QCoreApplication::notifyInternal (this=0x14ac640, receiver=0x1863fe0, event=0x7fffe270dd20) at kernel/qcoreapplication.cpp:787
#51 0x00007fa6e6103c08 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#52 QApplicationPrivate::sendMouseEvent (receiver=0x1863fe0, event=0x7fffe270dd20, alienWidget=0x1863fe0, nativeWidget=0x1749dd0, buttonDown=0x7fa6e6c9fc78, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3141
#53 0x00007fa6e618d0ef in QETWidget::translateMouseEvent (this=0x1749dd0, event=<optimized out>) at kernel/qapplication_x11.cpp:4464
#54 0x00007fa6e618b759 in QApplication::x11ProcessEvent (this=0x14ac640, event=0x7fffe270e4d0) at kernel/qapplication_x11.cpp:3590
#55 0x00007fa6e61b4532 in x11EventSourceDispatch (s=0x14c3990, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#56 0x00007fa6e02460da in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#57 0x00007fa6e02468e8 in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0
#58 0x00007fa6e0246a7f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#59 0x00007fa6e6e452fa in QEventDispatcherGlib::processEvents (this=0x14b0a50, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#60 0x00007fa6e61b41e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#61 0x00007fa6e6e15bb2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#62 0x00007fa6e6e15e34 in QEventLoop::exec (this=0x7fffe270e7d0, flags=...) at kernel/qeventloop.cpp:201
#63 0x00007fa6e6e1b39b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#64 0x000000000046d9d5 in main (argc=1, argv=0x7fffe270f768) at /tmp/portage/kde-base/kalarm-4.8.0/work/kalarm-4.8.0/kalarm/main.cpp:130

Reported using DrKonqi
Comment 1 David Jarvie 2012-02-06 00:22:32 UTC 
Could you please look at KAlarm's calendar list (use View -> Show Calendars to
see it) and hover over each calendar shown. This will display the calendar's
file location. Do this for each of Active Alarms, Expired Alarms and Alarm
Templates (using the drop-down selector). Do any of the calendars show
duplicate file names, i.e. the same file as another calendar? Do you have just
one calendar in each category?
Comment 2 Alexander Stein 2012-02-06 18:21:49 UTC 
No, there are 3 different one. calendar.ics, expired.ics and template.ics.
I also had another crash with a slightly different backtrace (will attach). This one occured upon KAlarm start where several alarms popped up and I delayed them some hours (think of a ToDo list). I could delay not all alarms before KAlarm crashed, previously I could delay all alarms (about 5 or 6) before crashing. Seems like a timing issue to me.
Comment 3 Alexander Stein 2012-02-06 18:24:17 UTC 
Created attachment 68567 [details]
backtrace from crash after KAlarm start
Comment 4 David Jarvie 2012-02-08 09:42:26 UTC 
*** Bug 293611 has been marked as a duplicate of this bug. ***
Comment 5 David Jarvie 2012-02-19 00:53:55 UTC 
This crash should, I hope, be fixed by commit c55b943be61cded1cedd05e9e6b04612b2d6058c (4.8 branch). If it occurs again after updating to 4.8.1, please reopen it.