Bug 148903 - Kontact crashes when starting up, it causes signal 11
Summary: Kontact crashes when starting up, it causes signal 11
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-16 21:49 UTC by Kyle
Modified: 2007-08-16 22:22 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 Kyle 2007-08-16 21:49:22 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

In kde 4 beta 1 on ubuntu gutsy, when i try to start kontact it crashes with signal 11.
Backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1259702592 (LWP 9288)]
0xffffe410 in ?? ()
[Current thread is 0 (process 9288)]

Thread 1 (Thread -1259702592 (LWP 9288)):
#0  0xffffe410 in ?? ()
#1  0xbfc7d8c8 in ?? ()
#2  0xb5a60ff4 in ?? () from /lib/tls/i686/cmov/libc.so.6
#3  0xbfc7d8b4 in ?? ()
#4  0xb59ade90 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#5  0xb59adcc7 in sleep () from /lib/tls/i686/cmov/libc.so.6
#6  0xb7b21e70 in KCrash::startDrKonqi (argv=0xbfc7f988, argc=17)
    at /build/buildd/kde4libs-3.92.0/kdeui/util/kcrash.cpp:354
#7  0xb7b22515 in KCrash::defaultCrashHandler (sig=11)
    at /build/buildd/kde4libs-3.92.0/kdeui/util/kcrash.cpp:275
#8  0xffffe420 in ?? ()
#9  0x0000000b in ?? ()
#10 0x00000033 in ?? ()
#11 0x00000000 in ?? ()
#0  0xffffe410 in ?? ()
Comment 1 Thomas McGuire 2007-08-16 22:22:53 UTC
Read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to get a better backtrace.

Also, try the lastest SVN version. Kontact did not start up until recently, but now it does for me so I assume this has been fixed.

If you have the lastest SVN version with a better backtrace, please reopen.