Bug 211005 - kalarm crash while start after upgrade
Summary: kalarm crash while start after upgrade
Status: CLOSED DUPLICATE of bug 210552
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-18 20:51 UTC by Mariusz Pluciński
Modified: 2010-09-02 12:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mariusz Pluciński 2009-10-18 20:51:58 UTC
Application that crashed: kalarm
Version of the application: 2.2.7
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.31custom1 x86_64
Distribution: "Fedora release 11 (Leonidas)"

 -- Backtrace:
Application: KAlarm (kalarm), signal: Segmentation fault
[KCrash Handler]
#5  AlarmCalendar::atLoginAlarms (this=0x0) at /usr/src/debug/kdepim-4.3.1/kalarm/alarmcalendar.cpp:1383
#6  0x000000000049dd5e in KAlarmApp::processQueue (this=0x1a0eb80) at /usr/src/debug/kdepim-4.3.1/kalarm/kalarmapp.cpp:673
#7  0x000000000049f1fc in KAlarmApp::qt_metacall (this=0x1a0eb80, _c=QMetaObject::InvokeMetaMethod, _id=29193728, _a=0x7fff485760c0)
    at /usr/src/debug/kdepim-4.3.1/x86_64-redhat-linux-gnu/kalarm/kalarmapp.moc:102
#8  0x00000038933547dc in QMetaObject::activate (sender=0x1b5c090, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x3aabd69e90) at kernel/qobject.cpp:3113
#9  0x00000038933597bf in QSingleShotTimer::timerEvent (this=0x1b5c090) at kernel/qtimer.cpp:298
#10 0x000000389334e7de in QObject::event (this=0x1b5c090, e=0x0) at kernel/qobject.cpp:1075
#11 0x000000389538f69c in QApplicationPrivate::notify_helper (this=0x1a2df90, receiver=0x1b5c090, e=0x7fff485766d0) at kernel/qapplication.cpp:4056
#12 0x00000038953968fe in QApplication::notify (this=0x1a0eb80, receiver=0x1b5c090, e=0x7fff485766d0) at kernel/qapplication.cpp:4021
#13 0x0000003541211b56 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x000000389333f59c in QCoreApplication::notifyInternal (this=0x1a0eb80, receiver=0x1b5c090, event=0x7fff485766d0) at kernel/qcoreapplication.cpp:610
#15 0x0000003893369fc2 in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:572
#17 0x00000038933679ed in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#18 0x000000389223790e in g_main_dispatch (context=<value optimized out>) at gmain.c:1824
#19 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2377
#20 0x000000389223b0e8 in g_main_context_iterate (context=0x1a29520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455
#21 0x000000389223b20a in IA__g_main_context_iteration (context=0x1a29520, may_block=1) at gmain.c:2518
#22 0x0000003893367936 in QEventDispatcherGlib::processEvents (this=0x19e7a90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#23 0x0000003895421f8e in QGuiEventDispatcherGlib::processEvents (this=0x7fff48575fa0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#24 0x000000389333ded2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 36}) at kernel/qeventloop.cpp:149
#25 0x000000389333e2a4 in QEventLoop::exec (this=0x7fff48576970, flags={i = 0}) at kernel/qeventloop.cpp:201
#26 0x0000003893340439 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#27 0x0000000000458523 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdepim-4.3.1/kalarm/main.cpp:126
Warning: the current language does not match this frame.

This bug may be a duplicate of or related to bug 185633

Reported using DrKonqi
Comment 1 David Jarvie 2009-10-18 20:55:18 UTC

*** This bug has been marked as a duplicate of bug 210552 ***