Bug 265538 - kontact crahes after login
Summary: kontact crahes after login
Status: RESOLVED DUPLICATE of bug 201275
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-05 18:37 UTC by Vadym Krevs
Modified: 2011-02-06 13:23 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 Vadym Krevs 2011-02-05 18:37:51 UTC
Application: kontact (4.4.10)
KDE Platform Version: 4.5.5 (KDE 4.5.5) "release 1"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

Nothing  actually - just waiting for the login process to finish.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007f60243296d7 in operator bool () at /usr/include/ksharedptr.h:106
#7  KMKernel::config () at /usr/src/debug/kdepim-4.4.10/kmail/kmkernel.cpp:2320
#8  0x00007f602432a431 in KMKernel::slotRunBackgroundTasks (this=0x12bbb80) at /usr/src/debug/kdepim-4.4.10/kmail/kmkernel.cpp:2379
#9  0x00007f6024336f1d in KMKernel::qt_metacall (this=0x12bbb80, _c=QMetaObject::InvokeMetaMethod, _id=44, _a=0x7fffc95934b0) at /usr/src/debug/kdepim-4.4.10/build/kmail/kmkernel.moc:242
#10 0x00007f603e46ba1f in QMetaObject::activate (sender=0x1448690, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3295
#11 0x00007f603e46922e in QObject::event (this=0x1448690, e=0x7fffc9593c50) at kernel/qobject.cpp:1212
#12 0x00007f603d8494d4 in QApplicationPrivate::notify_helper (this=0x641af0, receiver=0x1448690, e=0x7fffc9593c50) at kernel/qapplication.cpp:4302
#13 0x00007f603d851aca in QApplication::notify (this=<value optimized out>, receiver=0x1448690, e=0x7fffc9593c50) at kernel/qapplication.cpp:4185
#14 0x00007f603ed7d876 in KApplication::notify (this=0x7fffc9594090, receiver=0x1448690, event=0x7fffc9593c50) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#15 0x00007f603e457e4c in QCoreApplication::notifyInternal (this=0x7fffc9594090, receiver=0x1448690, event=0x7fffc9593c50) at kernel/qcoreapplication.cpp:726
#16 0x00007f603e4830c9 in sendEvent (this=0x645560) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x645560) at kernel/qeventdispatcher_unix.cpp:618
#18 0x00007f603e47fff8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#20 0x00007f6035aa3a93 in g_main_dispatch (context=0x644520) at gmain.c:1960
#21 IA__g_main_context_dispatch (context=0x644520) at gmain.c:2513
#22 0x00007f6035aa4270 in g_main_context_iterate (context=0x644520, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591
#23 0x00007f6035aa4510 in IA__g_main_context_iteration (context=0x644520, may_block=1) at gmain.c:2654
#24 0x00007f603e48067f in QEventDispatcherGlib::processEvents (this=0x613220, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f603d8ea14e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f603e457292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007f603e457495 in QEventLoop::exec (this=0x7fffc9593fe0, flags=...) at kernel/qeventloop.cpp:201
#28 0x00007f603e45b88b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#29 0x000000000040417e in _start ()

Possible duplicates by query: bug 263052, bug 250828.

Reported using DrKonqi
Comment 1 Christophe Marin 2011-02-06 13:23:26 UTC

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