Assuming it hasn't crashed anymore due to lack of comments. (A month and a half
is long enough to wait I think.)
Feel free to reopen it if you can get it to crash again.
** Changed in: kdepim (Ubuntu)
Status: Incomplete = Invalid
--
kontact crashed with SIGSEGV
This is what apport gives me with kdepim-dbg installed. I notice that retracing
failed even with debug libraries installed. I'm not exactly sure how this crash
is triggered, but it's the second crash in kontact for me this morning (i.e.
the last four hours).
I can try to see if I can trigger
Great, seems that reopening the bug and subscribing broke the adding
additional attachments part of apport. Anyway, as the retrace failed
with the debug libs as well, there's probably not too much that's lost
this way. Of course now run from gdb, kontact is rock solid.
--
kontact crashed with
Hehe maybe we should run kontact in gdb by default? ;-). Restoring
Incomplete status.
Usually you wouldn't have to run in gdb, apport or KCrash would attach
to the threads upon crash and create the traces automagically, which
works with 97% of all crashes.
** Changed in: kdepim (Ubuntu)
Yeah, seems to be not working on all the kontact crashes I've seen so
far, though. Oh well, I'll continue to run it, let's see if it crashes
again.
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/267093
You received this bug notification because you are a member of Ubuntu
Bugs,
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
Man, what's with apport lately? Retracing seems to fail a lot.
Any chance this is reproducible, and that you can acquire a better backtrace by
installing kdepim-dbg?
Thanks for taking the time to report it though. :-)
** Changed in: kdepim (Ubuntu)
Status: New = Incomplete
** Visibility
