Bug 298128 - Kontact crashes after crash of korgac
Summary: Kontact crashes after crash of korgac
Status: RESOLVED DUPLICATE of bug 272236
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-14 16:24 UTC by Philipp
Modified: 2012-04-17 14:59 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 Philipp 2012-04-14 16:24:51 UTC
Application: kontact (4.4.11)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.2.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (wheezy)

-- Information about the crash:
By starting Kontact and waiting for a few minutes, the korganizer reminder (korgac) crashes reproducibly. From time to time Kontact itself crashes as well afterwards.

This is happening since I sync my calendar and addressbook via kdepim-caldav (1.2.0-1) and kdepim-carddav (0.3.0-1) to an OwnCloud 3.0 server.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f56e2503475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f56e25066f0 in *__GI_abort () at abort.c:92
#8  0x00007f56e253d26b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007f56e25be077 in *__GI___fortify_fail (msg=0x7f56e261bd48 "longjmp causes uninitialized stack frame") at fortify_fail.c:32
#10 0x00007f56e25be009 in ____longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/____longjmp_chk.S:86
#11 0x00007f56e25bdf73 in __longjmp_chk (env=0x7f56c3afece0, val=1) at ../setjmp/longjmp.c:40
#12 0x00007f56c38a5195 in alarmfunc (sig=<optimized out>) at hostip.c:515
#13 <signal handler called>
#14 0x00007f56e259ecc3 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=999) at ../sysdeps/unix/sysv/linux/poll.c:87
#15 0x00007f56dbf875d8 in g_main_context_poll (n_fds=9, fds=0x15abf80, timeout=999, context=0x7b2480, priority=<optimized out>) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3391
#16 g_main_context_iterate (context=0x7b2480, block=<optimized out>, dispatch=1, self=<optimized out>) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3071
#17 0x00007f56dbf87a99 in g_main_context_iteration (context=0x7b2480, may_block=1) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3139
#18 0x00007f56e2ceae2f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#19 0x00007f56e3752eee in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtGui.so.4
#20 0x00007f56e2cbf492 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0x00007f56e2cbf68f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0x00007f56e2cc3837 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#23 0x00000000004038ac in main (argc=1, argv=0x7fffb16ad708) at ../../../kontact/src/main.cpp:226

This bug may be a duplicate of or related to bug 272236.

Possible duplicates by query: bug 281476, bug 272236.

Reported using DrKonqi
Comment 1 Christophe Marin 2012-04-17 14:59:23 UTC

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