Bug 241865 - Kontact crashes at startup
Summary: Kontact crashes at startup
Status: RESOLVED DUPLICATE of bug 235724
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-16 00:01 UTC by Oliver Zimmermann
Modified: 2010-06-16 00:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Zimmermann 2010-06-16 00:01:36 UTC
Application: kontact (4.4.3)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.3
Operating System: Linux 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
Each time Kontact or Kmail is started it crashes right away.

 -- Backtrace:
Application: Kontact (kontact), signal: Aborted
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb5df00cf in raise () from /lib/libc.so.6
#8  0xb5df19e7 in abort () from /lib/libc.so.6
#9  0xb5fe403f in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#10 0xb5fe1d53 in __cxxabiv1::__terminate (handler=0xb5fe3ef0 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#11 0xb5fe1d8f in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#12 0xb5fe1e2a in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#13 0xb6c24330 in QEventLoop::exec (this=0xbf8d0f44, flags=...) at kernel/qeventloop.cpp:214
#14 0xb6c29480 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#15 0xb614eee4 in QApplication::exec () at kernel/qapplication.cpp:3581
#16 0x0804b512 in _start ()

Possible duplicates by query: bug 240694, bug 240373, bug 238940, bug 236782, bug 235724.

Reported using DrKonqi
Comment 1 Nicolas L. 2010-06-16 00:57:01 UTC

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