| Summary: | Crash while editing alarm item and updating packages on Debian Buster | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | Andreas v. Heydwolff <listmail> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | Keywords: | drkonqi |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | 815c32b1c5de414b2e93dd03aa9b1e60818f499d | Version Fixed In: | 20.04.2 |
| Sentry Crash Report: | |||
|
Description
Andreas v. Heydwolff
2019-09-22 08:06:01 UTC
At what exact point did the crash occur? Did you already have the alarm edit dialog open when the crash occurred? If not, how did you try to open the alarm edit dialog - via the main window, or by clicking on a message window button? On 23.09.19 12:40, David Jarvie wrote:
> https://bugs.kde.org/show_bug.cgi?id=412181
>
> --- Comment #1 from David Jarvie <djarvie@kde.org> ---
> At what exact point did the crash occur? Did you already have the alarm edit
> dialog open when the crash occurred? If not, how did you try to open the alarm
> edit dialog - via the main window, or by clicking on a message window button?
>
Hi David,
I used the message window button, and I seem to remember that the edit
window was already open.
Regards
I think I finally worked out what was triggering this crash, although I don't understand what seems to be a rare sequence of events leading up to it. It should now be fixed, for KDE release 20.04.2, KAlarm version 2.14.2, by commit 815c32b1c5de414b2e93dd03aa9b1e60818f499d. David: FTR, the 'BUG: XXX' keyword must be on a new line in the commit body to close issues automatically. it has no effect when used on the commit title |