Bug 241753 - korgac crashes [KCal::Calendar::appendAlarms KCal::CalendarLocal::alarms KCal::ResourceCached::alarms]
Summary: korgac crashes [KCal::Calendar::appendAlarms KCal::CalendarLocal::alarms KCal...
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) (show other bugs)
Version: 0.9
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-14 18:03 UTC by Thomas Tanghus
Modified: 2011-06-22 01:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (9.93 KB, text/plain)
2010-06-25 13:06 UTC, Thomas Tanghus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Tanghus 2010-06-14 18:03:04 UTC
Application: korgac (0.9)
KDE Platform Version: 4.4.4 (KDE 4.4.4)
Qt Version: 4.6.3
Operating System: Linux 2.6.34-020634-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
But the backtrace mentions KOrganizer Daemon for some reason..?

 -- Backtrace:
Application: KOrganizer Reminder Daemon (korgac), signal: Aborted
[Current thread is 1 (Thread 0xb3d47730 (LWP 1935))]

Thread 2 (Thread 0xb23bfb70 (LWP 2072)):
#0  0xb7759430 in __kernel_vsyscall ()
#1  0xb605fd33 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95
#2  0xb5ff6697 in _L_lock_9637 () from /lib/tls/i686/cmov/libc.so.6
#3  0xb5ff4ec6 in *__GI___libc_free (mem=0x91c87e8) at malloc.c:3736
#4  0xb61b1741 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#5  0xb637da7a in QEventDispatcherUNIX::unregisterSocketNotifier (this=0x95c0388, notifier=0xb23bf2cc) at kernel/qeventdispatcher_unix.cpp:803
#6  0xb636afb9 in QSocketNotifier::setEnabled (this=0xfffffe00, enable=false) at kernel/qsocketnotifier.cpp:298
#7  0xb637ed11 in QEventDispatcherUNIXPrivate::doSelect (this=0x9139ac8, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:260
#8  0xb637f765 in QEventDispatcherUNIX::processEvents (this=0x95c0388, flags=...) at kernel/qeventdispatcher_unix.cpp:920
#9  0xb634e759 in QEventLoop::processEvents (this=0xb23bf270, flags=) at kernel/qeventloop.cpp:149
#10 0xb634ebaa in QEventLoop::exec (this=0xb23bf270, flags=...) at kernel/qeventloop.cpp:201
#11 0xb624ffc9 in QThread::exec (this=0x8f4f6b8) at thread/qthread.cpp:487
#12 0xb632e1db in QInotifyFileSystemWatcherEngine::run (this=0x8f4f6b8) at io/qfilesystemwatcher_inotify.cpp:248
#13 0xb625297e in QThreadPrivate::start (arg=0x8f4f6b8) at thread/qthread_unix.cpp:248
#14 0xb5d5296e in start_thread (arg=0xb23bfb70) at pthread_create.c:300
#15 0xb6052a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb3d47730 (LWP 1935)):
[KCrash Handler]
#6  0xb7759430 in __kernel_vsyscall ()
#7  0xb5faf651 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0xb5fb2a82 in *__GI_abort () at abort.c:92
#9  0xb5fe649d in __libc_message (do_abort=2, fmt=0xb60baf98 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#10 0xb5ff0591 in malloc_printerr (action=<value optimized out>, str=0x6 <Address 0x6 out of bounds>, ptr=0x95c31c0) at malloc.c:6264
#11 0xb5ff09ea in malloc_consolidate (av=<value optimized out>) at malloc.c:5150
#12 0xb5ff2afd in _int_malloc (av=<value optimized out>, bytes=<value optimized out>) at malloc.c:4370
#13 0xb5ff4f9c in *__GI___libc_malloc (bytes=728) at malloc.c:3660
#14 0xb60102b7 in __tzfile_read (file=0x8ef3ae4 "Europe/Copenhagen", extra=0, extrap=0x0) at tzfile.c:257
#15 0xb600f618 in tzset_internal (always=<value optimized out>, explicit=<value optimized out>) at tzset.c:439
#16 0xb600f85d in __tzset () at tzset.c:592
#17 0xb65a5928 in KSystemTimeZoneBackend::offset (this=0x942c118, caller=0x910ff88, t=1276530818) at ../../kdecore/date/ksystemtimezone.cpp:630
#18 0xb65a465d in KSystemTimeZoneBackend::offsetAtUtc (this=0x942c118, caller=0x910ff88, utcDateTime=...) at ../../kdecore/date/ksystemtimezone.cpp:614
#19 0xb659d630 in KTimeZone::offsetAtUtc (this=0x910ff88, utcDateTime=...) at ../../kdecore/date/ktimezone.cpp:799
#20 0xb65a22d0 in KTimeZone::toZoneTime (this=0x910ff88, utcDateTime=..., secondOccurrence=0xbfed23ef) at ../../kdecore/date/ktimezone.cpp:768
#21 0xb6595218 in KDateTimePrivate::setDtFromUtc (this=0x910ff80, utcdt=...) at ../../kdecore/date/kdatetime.cpp:575
#22 0xb659622f in KDateTime (this=0xbfed255c, dt=..., spec=...) at ../../kdecore/date/kdatetime.cpp:803
#23 0xb659ad27 in KDateTime::addSecs (this=0xbfed26f8, secs=-1) at ../../kdecore/date/kdatetime.cpp:1128
#24 0xb72a9bac in KCal::Calendar::appendAlarms (this=0x8ef2560, alarms=..., incidence=0x951ed28, from=..., to=...) at ../../kcal/calendar.cpp:1087
#25 0xb72afe4f in KCal::CalendarLocal::alarms (this=0x8ef2560, from=..., to=...) at ../../kcal/calendarlocal.cpp:340
#26 0xb73097da in KCal::ResourceCached::alarms (this=0x8ef27e8, from=..., to=...) at ../../kcal/resourcecached.cpp:350
#27 0xb731491e in KCal::CalendarResources::alarms (this=0x8ebd2d0, from=..., to=...) at ../../kcal/calendarresources.cpp:619
#28 0x0805d776 in KOAlarmClient::checkAlarms (this=0x8dfaaf0) at ../../../korganizer/korgac/koalarmclient.cpp:120
#29 0x0805dc2d in KOAlarmClient::qt_metacall (this=0x8dfaaf0, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfed281c) at ./koalarmclient.moc:83
#30 0xb635547a in QMetaObject::metacall (object=0x8dfaaf0, cl=1935, idx=7, argv=0xbfed281c) at kernel/qmetaobject.cpp:237
#31 0xb6363fbb in QMetaObject::activate (sender=0x8dfab0c, m=0xb64655a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#32 0xb63b6327 in QTimer::timeout (this=0x8dfab0c) at .moc/release-shared/moc_qtimer.cpp:134
#33 0xb636be4e in QTimer::timerEvent (this=0x8dfab0c, e=0xbfed2d50) at kernel/qtimer.cpp:271
#34 0xb6360a64 in QObject::event (this=0x8dfab0c, e=0x6) at kernel/qobject.cpp:1212
#35 0xb6873e8c in QApplicationPrivate::notify_helper (this=0x8db1438, receiver=0x8dfab0c, e=0xbfed2d50) at kernel/qapplication.cpp:4302
#36 0xb687aa0e in QApplication::notify (this=0xbfed3040, receiver=0x8dfab0c, e=0xbfed2d50) at kernel/qapplication.cpp:3706
#37 0xb757fffa in KApplication::notify (this=0xbfed3040, receiver=0x8dfab0c, event=0xbfed2d50) at ../../kdeui/kernel/kapplication.cpp:302
#38 0xb635013b in QCoreApplication::notifyInternal (this=0xbfed3040, receiver=0x8dfab0c, event=0xbfed2d50) at kernel/qcoreapplication.cpp:726
#39 0xb637f5c6 in QCoreApplication::sendEvent (this=0x8db6058) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#40 QTimerInfoList::activateTimers (this=0x8db6058) at kernel/qeventdispatcher_unix.cpp:603
#41 0xb637f777 in QEventDispatcherUNIX::processEvents (this=0x8d919e0, flags=...) at kernel/qeventdispatcher_unix.cpp:924
#42 0xb6934e82 in QEventDispatcherX11::processEvents (this=0x8d919e0, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#43 0xb634e759 in QEventLoop::processEvents (this=0xbfed2fa4, flags=) at kernel/qeventloop.cpp:149
#44 0xb634ebaa in QEventLoop::exec (this=0xbfed2fa4, flags=...) at kernel/qeventloop.cpp:201
#45 0xb6353e3f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#46 0xb6873f27 in QApplication::exec () at kernel/qapplication.cpp:3581
#47 0x080520db in main (argc=3, argv=0xbfed3194) at ../../../korganizer/korgac/korgacmain.cpp:85

Possible duplicates by query: bug 230906, bug 214079, bug 208881.

Reported using DrKonqi
Comment 1 Thomas Tanghus 2010-06-25 13:06:23 UTC
Created attachment 48315 [details]
New crash information added by DrKonqi

Again reading news from Akregator and clicking on a link in the planetkde feed (http://slangkamp.wordpress.com/2010/06/25/we-need-more-bug-reports/).
Comment 2 Geoff Madden 2010-07-05 08:13:53 UTC
Ran into a similar problem reading items,which required a login to read or download further info. The actual process of logging on dumped me back to my system login screen,which was successful. but not to the place i was expecting to go HI, this's in regard to Akregator, was trying to login to vote for a particular item in kde look. Hitting the vote button put me in a screen that required login,which is where the problems started.
Comment 3 Sergio Martins 2011-06-22 01:02:22 UTC
Does it still happen with 4.6 ?
Comment 4 Thomas Tanghus 2011-06-22 01:42:50 UTC
(In reply to comment #3)
> Does it still happen with 4.6 ?

No I don't think I have seen this for quite a while. Another one down I guess :-)