Application: kalarm (2.4.8) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.3 Operating System: Linux 2.6.31.13-131 i686 Distribution: "Pardus 2009.2 Geronticus eremita" -- Information about the crash: I put one alarm as a hourly bell. It was working fine. This is the first time it crashed. I just started up the system and it crashed. I'm using Pardus distro. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault [KCrash Handler] #6 0xb767bb01 in KAEventData::clearRecur (this=0xb765bee8) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/cal/kaeventdata.cpp:2737 #7 0xb767bbd8 in KAEventData::checkRecur (this=0xb765bee8) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/cal/kaeventdata.cpp:2766 #8 0xb7682d6e in KAEventData::alarm (this=0xb765bee8, type=REMINDER_ALARM) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/cal/kaeventdata.cpp:1603 #9 0xb7683954 in KAEventData::nextAlarm (this=0xb758c0b0, prevType=MAIN_ALARM) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/cal/kaeventdata.cpp:1710 #10 0x080d159a in nextAlarm (al=<value optimized out>, this=<value optimized out>) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/./cal/kaeventdata.h:349 #11 nextAlarm (al=<value optimized out>, this=<value optimized out>) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/build/kalarm/../../kalarm/kaevent.h:153 #12 KAlarmApp::handleEvent (al=<value optimized out>, this=<value optimized out>) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/kalarmapp.cpp:1057 #13 0x080d35d4 in KAlarmApp::processQueue (this=0x9cfa1c8) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/kalarm/kalarmapp.cpp:709 #14 0x080d5d6d in KAlarmApp::qt_metacall (this=0x9cfa1c8, _c=InvokeMetaMethod, _id=440, _a=0xbfcc0a08) at /var/pisi/kdepim-4.4.6-33/work/kdepim-4.4.6/build/kalarm/kalarmapp.moc:111 #15 0xb5a4c250 in QMetaObject::metacall (object=0xb758bf00, cl=InvokeMetaMethod, idx=32, argv=0xbfcc0a08) at kernel/qmetaobject.cpp:237 #16 0xb5a5baf0 in QMetaObject::activate (sender=0x9e31b58, m=0xb5b5d188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #17 0xb5a63005 in QSingleShotTimer::timeout (this=0x9e31b58) at .moc/release-shared/qtimer.moc:82 #18 0xb5a6314c in QSingleShotTimer::timerEvent (this=0x9e31b58) at kernel/qtimer.cpp:308 #19 0xb5a581c4 in QObject::event (this=0x9e31b58, e=0xbfcc0fa0) at kernel/qobject.cpp:1212 #20 0xb5c84dfc in QApplicationPrivate::notify_helper (this=0x9cfd588, receiver=0x9e31b58, e=0xbfcc0fa0) at kernel/qapplication.cpp:4324 #21 0xb5c8c88a in QApplication::notify (this=0x9cfa1c8, receiver=0x9e31b58, e=0xbfcc0fa0) at kernel/qapplication.cpp:3728 #22 0xb6a3be71 in KApplication::notify (this=0x9cfa1c8, receiver=0x9e31b58, event=0xbfcc0fa0) at /var/pisi/kdelibs-4.4.5-79/work/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302 #23 0xb5a46cfe in QCoreApplication::notifyInternal (this=0x9cfa1c8, receiver=0x9e31b58, event=0xbfcc0fa0) at kernel/qcoreapplication.cpp:726 #24 0xb5a77e6c in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617 #26 0xb5a74562 in timerSourceDispatch (source=0x9d00300) at kernel/qeventdispatcher_glib.cpp:184 #27 0xb44ac53c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #28 0x09cff694 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Reported using DrKonqi
Did it crash almost as soon as you logged in, or was there a pause of a minute or so before it crashed? Did you see the KAlarm main window display before the crash? (Of course, if it wasn't visible when you logged out, you wouldn't see it at login.) Could you please attach your alarm calendar file. It will be in $HOME/.kde/share/apps/kalarm/calendar.ics, or $HOME/.kde4/share/apps/kalarm/calendar.ics. You can edit the alarm message texts in the calendar for privacy, if you like.
it didn't crash as soon as i logged in. The desktop wallpaper came, then the plasma toolbar on the top, then it crashed. i saw the system tray icon before crash. Although i did not load the kalarm main window before shutting it down the last time so i did not see it this time. I have attached the calendar file Thank You very much. I really appreciate your help. *Kranthi Kumar Katikala* <http://www.google.com/profiles/kranthi.t2000> (ThCbe) On Fri, Nov 12, 2010 at 10:56 PM, David Jarvie <djarvie@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=256652 > > > > > > --- Comment #1 from David Jarvie <djarvie kde org> 2010-11-12 14:56:16 --- > Did it crash almost as soon as you logged in, or was there a pause of a > minute > or so before it crashed? Did you see the KAlarm main window display before > the > crash? (Of course, if it wasn't visible when you logged out, you wouldn't > see > it at login.) > > Could you please attach your alarm calendar file. It will be in > $HOME/.kde/share/apps/kalarm/calendar.ics, or > $HOME/.kde4/share/apps/kalarm/calendar.ics. You can edit the alarm message > texts in the calendar for privacy, if you like. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
The attachment hasn't appeared. Please go to the bug report at https://bugs.kde.org/show_bug.cgi?id=256652 and use "Add an attachment" there.
Created attachment 53361 [details] /.kde4/share/apps/kalarm/calendar.ics
I see that the calendar file contains no alarms. If your alarms are configured to be archived, the alarm which crashed should be in $HOME/.kde4/share/apps/kalarm/expired.ics - if so, can you please attach that file.
Created attachment 53365 [details] /.kde4/share/apps/kalarm/expired.ics
Do you remember if you had done any system package updates just before this crash happened? Does the crash still happen? (If not, have you updated KAlarm's version since the bug report?)
I'm really sorry, i don't remember it. But now the crash doesn't happen. *Kranthi Kumar Katikala* <http://www.google.com/profiles/kranthi.t2000> (ThCbe) On Sun, Jun 5, 2011 at 10:25 PM, David Jarvie <djarvie@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=256652 > > > > > > --- Comment #7 from David Jarvie <djarvie kde org> 2011-06-05 18:55:48 --- > Do you remember if you had done any system package updates just before this > crash happened? Does the crash still happen? (If not, have you updated > KAlarm's > version since the bug report?) > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
The crash trace indicates what seems to be an 'impossible' crash, which suggests that it may be due to an update which installed inconsistent library packages, which would have been fixed by later system updates. Because it seems likely to be due to some packaging bug, and the fact that the crash no longer occurs, I'm marking this issue as invalid. Thank you for reporting it, nonetheless.
Sure. Thanks *Kranthi Kumar Katikala* <http://www.google.com/profiles/kranthi.t2000> (ThCbe) On Wed, Jun 8, 2011 at 6:33 PM, David Jarvie <djarvie@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=256652 > > > David Jarvie <djarvie@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |INVALID > > > > > --- Comment #9 from David Jarvie <djarvie kde org> 2011-06-08 15:03:32 --- > The crash trace indicates what seems to be an 'impossible' crash, which > suggests that it may be due to an update which installed inconsistent > library > packages, which would have been fixed by later system updates. Because it > seems > likely to be due to some packaging bug, and the fact that the crash no > longer > occurs, I'm marking this issue as invalid. > > Thank you for reporting it, nonetheless. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >