Bug 149194 - Kontact crashes with signal 11 on startup since last distribution update (Gutsy Gibbon)
Summary: Kontact crashes with signal 11 on startup since last distribution update (Gut...
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-25 14:15 UTC by Myriam Schweingruber
Modified: 2007-09-05 16:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
crash report 2007-08-25 (1.26 KB, text/plain)
2007-08-25 14:17 UTC, Myriam Schweingruber 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Myriam Schweingruber 2007-08-25 14:15:38 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    Ubuntu Packages

after an update to the latest tribe release, Kontact crashes on startup with signal 11
Comment 1 Myriam Schweingruber 2007-08-25 14:17:05 UTC 
Created attachment 21479 [details]
crash report 2007-08-25
Comment 2 Pino Toscano 2007-08-25 14:38:58 UTC 
Please provide a better backtrace of this crash, read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports for more info about that.
Comment 3 DWhite 2007-08-29 20:02:37 UTC 
As installed from the Kubuntu tribe CD, I had the same crash on my machine.  I noticed that kontact, kmail, basket, etc was installed, but not kdepim.  After I installed the full kdepim everything works fine - suspect ubuntu is missing something in the install.
Comment 4 DWhite 2007-08-29 21:50:11 UTC 
further note - after installing kdepim, kontact starts and works but will eventually crash with SIGSEVG.  This and the backtrace has been reported to ubuntu.
Comment 5 Thomas McGuire 2007-09-05 16:20:21 UTC 
>After I installed the full kdepim everything works fine - suspect ubuntu is missing something in the install. 
Closing this bug report then, as this seems to be an Ubuntu issue.