https://bugs.kde.org/show_bug.cgi?id=326672
Arne Babenhauserheide changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=326672
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #7 from Andrew
https://bugs.kde.org/show_bug.cgi?id=326672
Sandro Knauß m...@sandroknauss.de changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=326672
--- Comment #6 from Arne Babenhauserheide arne_...@web.de ---
Thank you!
I can test the fix once 4.11.4 made its way into Gentoo testing.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=326672
--- Comment #4 from Arne Babenhauserheide arne_...@web.de ---
Created attachment 83145
-- https://bugs.kde.org/attachment.cgi?id=83145action=edit
kmail-encrypt-all-crash-backtrace.txt
Backtrace from the KMail Crash (thank you for the info how to
https://bugs.kde.org/show_bug.cgi?id=326672
Laurent Montel mon...@kde.org changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=326672
--- Comment #2 from Arne Babenhauserheide arne_...@web.de ---
Dr. Konqui did not appear (I just reproduced it).
On the shell it prints this:
*** KMail got signal 11 (Exiting)
kmail2(7351) KMKernel::dumpDeadLetters: Danger, using an event loop, this
https://bugs.kde.org/show_bug.cgi?id=326672
--- Comment #3 from Jekyll Wu adap...@gmail.com ---
Try this :
$ gdb kmail
gdb set args --nofork
gdb run
gdb
For more inforamtion, see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
--
You are
