Bug 293290 - KAlarm crashed on exit
Summary: KAlarm crashed on exit
Status: CLOSED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-04 12:57 UTC by Unknown
Modified: 2020-08-17 23:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.8.1


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2012-02-04 12:57:25 UTC
Application: kalarm (2.8.0-ak)
KDE Platform Version: 4.8.00 (4.8.0 "release 462"
Qt Version: 4.8.0
Operating System: Linux 3.1.9-1.4-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I had had an (expired) alarm before I exited from KAlarm and maybe its notification window was open, too (althogh I'm not sure about the latter). Then I quit from the context menu of its icon on the system tray.
After that it crashed.

-- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fd47c642623 in KAlarmCal::KAEvent::category (this=0x2225810) at /usr/src/debug/kdepimlibs-4.8.0/kalarmcal/kaevent.cpp:1862
#7  0x000000000048b8ad in AlarmCalendar::removeKAEvents (this=0xae30f0, key=148, closing=true, types=...) at /usr/src/debug/kdepim-4.8.0/kalarm/alarmcalendar.cpp:634
#8  0x000000000048bc36 in AlarmCalendar::close (this=0xae30f0) at /usr/src/debug/kdepim-4.8.0/kalarm/alarmcalendar.cpp:495
#9  0x000000000048be23 in AlarmCalendar::~AlarmCalendar (this=0xae30f0, __in_chrg=<optimized out>) at /usr/src/debug/kdepim-4.8.0/kalarm/alarmcalendar.cpp:214
#10 0x000000000048bfd9 in AlarmCalendar::~AlarmCalendar (this=0xae30f0, __in_chrg=<optimized out>) at /usr/src/debug/kdepim-4.8.0/kalarm/alarmcalendar.cpp:215
#11 0x0000000000488736 in AlarmCalendar::terminateCalendars () at /usr/src/debug/kdepim-4.8.0/kalarm/alarmcalendar.cpp:115
#12 0x00000000004a36f9 in KAlarmApp::quitIf (this=0x864480, exitCode=0, force=<optimized out>) at /usr/src/debug/kdepim-4.8.0/kalarm/kalarmapp.cpp:586
#13 0x00000000004a58d5 in KAlarmApp::doQuit (this=0x864480, parent=<optimized out>) at /usr/src/debug/kdepim-4.8.0/kalarm/kalarmapp.cpp:640
#14 0x00007fd47888e4f6 in QObject::event (this=0xb5cf90, e=<optimized out>) at kernel/qobject.cpp:1195
#15 0x00007fd477bfbd84 in notify_helper (e=0x231bc70, receiver=0xb5cf90, this=0x86cb40) at kernel/qapplication.cpp:4550
#16 QApplicationPrivate::notify_helper (this=0x86cb40, receiver=0xb5cf90, e=0x231bc70) at kernel/qapplication.cpp:4522
#17 0x00007fd477c00c03 in QApplication::notify (this=0x864480, receiver=0xb5cf90, e=0x231bc70) at kernel/qapplication.cpp:4411
#18 0x00007fd479570786 in KApplication::notify (this=0x864480, receiver=0xb5cf90, event=0x231bc70) at /usr/src/debug/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311
#19 0x00007fd47887548c in QCoreApplication::notifyInternal (this=0x864480, receiver=0xb5cf90, event=0x231bc70) at kernel/qcoreapplication.cpp:876
#20 0x00007fd478878d2a in sendEvent (event=0x231bc70, receiver=0xb5cf90) at kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x806850) at kernel/qcoreapplication.cpp:1500
#22 0x00007fd4788a4093 in sendPostedEvents () at kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#24 0x00007fd4714ce58d in g_main_dispatch (context=0x86c7d0) at gmain.c:2425
#25 g_main_context_dispatch (context=0x86c7d0) at gmain.c:2995
#26 0x00007fd4714ced88 in g_main_context_iterate (context=0x86c7d0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3073
#27 0x00007fd4714cef59 in g_main_context_iteration (context=0x86c7d0, may_block=1) at gmain.c:3136
#28 0x00007fd4788a44bf in QEventDispatcherGlib::processEvents (this=0x806110, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#29 0x00007fd477c9edee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007fd478874272 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007fd4788744c7 in QEventLoop::exec (this=0x7fff883313a0, flags=...) at kernel/qeventloop.cpp:204
#32 0x00007fd478879025 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#33 0x00000000004518c7 in main (argc=5, argv=0x7fff883322b8) at /usr/src/debug/kdepim-4.8.0/kalarm/main.cpp:130

Reported using DrKonqi
Comment 1 David Jarvie 2012-02-04 16:09:34 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 Unknown 2012-02-05 09:42:28 UTC
There are no duplicates and there's only one calendar in each category:

1. ~/.kde4/data/kalarm (without extension)
2. ~/.kde4/share/apps/kalarm/expired.ics
3. ~/.kde4/share/apps/kalarm/template.ics
Comment 3 David Jarvie 2012-02-07 11:54:55 UTC
Thank you - I'm investigating the crash.

This is not related to the crash - but I notice that the first calendar location is not the default location. Did you choose this location yourself? If not, did you upgrade to this version of kalarm from a previous version, or was it installed for the first time?
Comment 4 Unknown 2012-02-07 18:40:53 UTC
Ok, thank you :)

Yes, I chose this location. I don't know exactly why but I'd deleted all Akonadi-related KAlarm entries and recreated them some time ago. There were no errors I just were trying something.
Comment 5 David Jarvie 2012-02-19 00:53:11 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.
Comment 6 Unknown 2012-02-20 18:20:43 UTC
Thank you for the fix!