[Bug 268947] Re: kontact crashed with SIGSEGV

2008-10-26 Thread Jonathan Thomas
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on t

[Bug 268947] Re: kontact crashed with SIGSEGV

2008-09-28 Thread Hein van Rensburg
Was busy establishing settings in kmail ( A custom time format) when crash occurred -- kontact crashed with SIGSEGV https://bugs.launchpad.net/bugs/268947 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailin

[Bug 268947] Re: kontact crashed with SIGSEGV

2008-09-17 Thread felix.rommel
Got the same error - it always happens when starting kontact. When I have time I will do a backtrace. The error messages in console when starting kontact: kontact(8762)/kmail KMailPart::KMailPart: InstanceName: "kontact" kontact(8762)/kmail KMailPart::KMailPart: InstanceName: "kontact"

[Bug 268947] Re: kontact crashed with SIGSEGV

2008-09-16 Thread Andreas Moog
Thanks. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. -- kontact crashed with SIGSEGV https://bugs.launchpad.net/bu

[Bug 268947] Re: kontact crashed with SIGSEGV

2008-09-16 Thread Xosé
It crashes at startup - always. -- kontact crashed with SIGSEGV https://bugs.launchpad.net/bugs/268947 You received this bug notification because you are a member of Almost Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu

[Bug 268947] Re: kontact crashed with SIGSEGV

2008-09-16 Thread Andreas Moog
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Attachment removed: "CoreDump.gz"