https://bugs.kde.org/show_bug.cgi?id=499859
David Jarvie <djar...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Akonadi |general
Latest Commit| |https://invent.kde.org/pim/
| |kalarm/-/commit/041337fa91a
| |e94cdeabcd48af933a9e7adf82d
| |37
Status|REPORTED |RESOLVED
Version Fixed In| |24.12.3
Resolution|--- |FIXED
--- Comment #8 from David Jarvie <djar...@kde.org> ---
A fix has been applied to ensure that KAlarm doesn't exit without good reason
in KAlarmApp::activateInstance() if session restoration is required. The fix
will be in KAlarm version 3.10.3, which will be released in KDE Gear 24.12.3.
Commit 041337fa91ae94cdeabcd48af933a9e7adf82d37.
The crash only occurs when KAlarm exits prematurely, and could still occur if
KAlarm exited due to an error at the same stage. As far as I can see, the
crash, which is in the Akonadi RemoteLogger destructor, is outside KAlarm's
control.
--
You are receiving this mail because:
You are watching all bug changes.
