https://bugs.kde.org/show_bug.cgi?id=407797
Martin van Es changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=407797
--- Comment #6 from Kamil Dudka ---
(In reply to Kamil Dudka from comment #5)
The same scenario worked fine for me now with kmail 5.11.3 but I am not sure
whether it was upgrade of kmail or something else that fixed it for me...
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=407797
Christoph changed:
What|Removed |Added
CC|ilove...@mojo.cc|
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=407797
Kamil Dudka changed:
What|Removed |Added
CC||kdu...@redhat.com
--- Comment #5 from Kamil Dudka
https://bugs.kde.org/show_bug.cgi?id=407797
Christoph Feck changed:
What|Removed |Added
CC||ilove...@mojo.cc
--- Comment #4 from Christoph
https://bugs.kde.org/show_bug.cgi?id=407797
--- Comment #3 from Martin van Es ---
Do you have a hint on what dbg packages to install for a useable backtrace
then?
Until then, this is the (unusable) trace of the segfaulting thread:
hread 1 (Thread 0x7ff7aa718f00 (LWP 12242)):
[KCrash Handler]
#6
https://bugs.kde.org/show_bug.cgi?id=407797
Laurent Montel changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #2 from Laurent Mon
https://bugs.kde.org/show_bug.cgi?id=407797
--- Comment #1 from Martin van Es ---
Hmm... even pressing "Ok" on the folder properties dialog without making
changes crashes kmail?
--
You are receiving this mail because:
You are watching all bug changes.
