kontact crashed with SIGSEGV

[tomaggio]

Binary package hint: kdepim

lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
kontact kmail 4:4.1.3-0ubuntu1~intrepid2
I tried to receive my emails but kmail did#nt use kwallet and asked for my password. So i closed kontact. Then kwallet asked for my password. Then i started kontact and it crashed.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Disassembly: 0x7f62a7905fd5:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/kontact
NonfreeKernelModules: fglrx
Package: kontact 4:4.1.3-0ubuntu1~intrepid2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/kontact
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdepim
Stacktrace: #0 0x00007f62a7905fd5 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: kontact crashed with SIGSEGV
Uname: Linux 2.6.27-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[tomaggio (joli64)]

Argh and lost all my pop and imap accounts settings

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Richard Birnie (rbirnie-deactivatedaccount)]

Thanks for reporting this. Has this only occurred once or is it reproducible?

Can we just clarify the steps that lead to the crash:
1) Try to receive mail. By clicking 'check mail'?
2) Kmail shows a pop-up asking for username and password information
3) Closed Kontact. Did you actually enter the password or just click cancel and then close the application?
4) After you closed kontact a kwallet pop-up appears asking for your password. Did you enter your password?
5) Start Kontact and observe a crash.

Is this correct?
There are now packages available for KDE4.1.4 and 4.2rc1. Do you see this issue with either of those versions? If the crash is occurring repeatedly could you install the package kdepim-dbg so that we can get a more informative backtrace.

[tomaggio (joli64)]

Hi; I've installed kontact 4:4.1.4-0ubuntu1~intrepid1 from the proposed repository a few day's ago. So i tried to reproduce this behaviour. But i couldn't. It seems that it's fixed.
Greets Tom

[Jonathan Thomas (echidnaman)]

Great! Thanks for testing.