https://bugs.kde.org/show_bug.cgi?id=426436
Andre Heinecke changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=426432
Laurent Montel changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #1 from Laurent
https://bugs.kde.org/show_bug.cgi?id=426432
--- Comment #2 from Axel Braun ---
(In reply to Laurent Montel from comment #1)
> bactrace ?
konqi did not deliver one - how can I force this?
>From journalctl:
Sep 12 11:08:48 X1E kontact[2623]: org.kde.pim.kmail: Danger, using an event
loop, this
https://bugs.kde.org/show_bug.cgi?id=426432
Bug ID: 426432
Summary: kmail 5.15.1: Crash when sending encrypted mail
Product: kontact
Version: 5.15.0
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=426436
Bug ID: 426436
Summary: Kleopatra: Error message while refreshing OpenGPG keys
Product: kleopatra
Version: 3.1.11
Platform: FreeBSD Ports
OS: FreeBSD
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=426436
Andre Heinecke changed:
What|Removed |Added
Attachment #131572|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=425931
--- Comment #4 from john4deidre2...@xtra.co.nz ---
Created attachment 131584
--> https://bugs.kde.org/attachment.cgi?id=131584=edit
New crash information added by DrKonqi
kontact (5.15.1 (20.08.1)) using Qt 5.15.0
- What I was doing when the
https://bugs.kde.org/show_bug.cgi?id=426432
--- Comment #3 from Axel Braun ---
After installing some 10.000 debugsource-packages:
docb@X1E:~> gdb kontact
GNU gdb (GDB; openSUSE Tumbleweed) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
https://bugs.kde.org/show_bug.cgi?id=426436
--- Comment #3 from Gerard Seibert ---
(In reply to Andre Heinecke from comment #2)
You are probably right. I did remove any mention of "debug" in the gpg.conf
file, but the same error message is displayed.
This is my gpg.conf file:
###+++---
https://bugs.kde.org/show_bug.cgi?id=426432
--- Comment #4 from Christoph Feck ---
You need to use the 'bt' command in gdb after the crash to get the actual
backtrace. For more information, please see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
10 matches
Mail list logo