Bug 278076

Summary: Kontact crashes when entering OpenVPN Session
Product: [Applications] kontact Reporter: Thomas Kraeuter <kraeutert>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: 4.4.11   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Thomas Kraeuter 2011-07-19 10:32:52 UTC
Application: kontact (4.4.11)
KDE Platform Version: 4.6.3 (4.6.3)
Qt Version: 4.7.3
Operating System: Linux 2.6.38.8-35.fc15.x86_64 x86_64
Distribution: "Fedora release 15 (Lovelock)"

-- Information about the crash:
- What I was doing when the application crashed:
After entering a VPN Session Kontact crashes when fetching mails.
Same during the VPN Session.
Same after exiting VPN Session.
Reboot is necessary.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x272f050, res=<optimized out>) at /usr/src/debug/kdepim-4.4.11.1/kmail/actionscheduler.cpp:675
#7  0x0000003e091d55a8 in KMail::ActionScheduler::filterMessage (this=0x272f050) at /usr/src/debug/kdepim-4.4.11.1/kmail/actionscheduler.cpp:648
#8  0x0000003e091d59c4 in KMail::ActionScheduler::qt_metacall (this=0x272f050, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff96f50140) at /usr/src/debug/kdepim-4.4.11.1/x86_64-redhat-linux-gnu/kmail/actionscheduler.moc:130
#9  0x0000003ded36ceba in QMetaObject::activate (sender=0x27373f0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278
#10 0x0000003ded3707a9 in QObject::event (this=0x27373f0, e=<optimized out>) at kernel/qobject.cpp:1181
#11 0x0000003df03b7444 in notify_helper (e=0x7fff96f50840, receiver=0x27373f0, this=0x1841b10) at kernel/qapplication.cpp:4462
#12 QApplicationPrivate::notify_helper (this=0x1841b10, receiver=0x27373f0, e=0x7fff96f50840) at kernel/qapplication.cpp:4434
#13 0x0000003df03bc2d1 in QApplication::notify (this=0x7fff96f50b40, receiver=0x27373f0, e=0x7fff96f50840) at kernel/qapplication.cpp:4341
#14 0x0000003df1241806 in KApplication::notify (this=0x7fff96f50b40, receiver=0x27373f0, event=0x7fff96f50840) at /usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kapplication.cpp:311
#15 0x0000003ded35a1ac in QCoreApplication::notifyInternal (this=0x7fff96f50b40, receiver=0x27373f0, event=0x7fff96f50840) at kernel/qcoreapplication.cpp:731
#16 0x0000003ded386b52 in sendEvent (event=0x7fff96f50840, receiver=<optimized out>) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x184d5a0) at kernel/qeventdispatcher_unix.cpp:604
#18 0x0000003ded384384 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 0x0000003de42427ed in g_main_dispatch (context=0x18439e0) at gmain.c:2441
#20 g_main_context_dispatch (context=0x18439e0) at gmain.c:3014
#21 0x0000003de4242fc8 in g_main_context_iterate (context=0x18439e0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3092
#22 0x0000003de424325c in g_main_context_iteration (context=0x18439e0, may_block=1) at gmain.c:3155
#23 0x0000003ded384d0f in QEventDispatcherGlib::processEvents (this=0x18413f0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#24 0x0000003df0459fde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207
#25 0x0000003ded3596c2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x0000003ded3598bf in QEventLoop::exec (this=0x7fff96f50ad0, flags=...) at kernel/qeventloop.cpp:201
#27 0x0000003ded35da07 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#28 0x000000000040375c in main (argc=1, argv=0x7fff96f51128) at /usr/src/debug/kdepim-4.4.11.1/kontact/src/main.cpp:226

Possible duplicates by query: bug 269389, bug 269166, bug 269054, bug 268849, bug 268818.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-07-19 10:43:05 UTC

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