Summary: | If Kalarm started twice it crashes | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | RJ <ogldelphi> |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | CLOSED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | 6bd68f98d675e30fab24713e63dfe72cdfd6f4f5 | Version Fixed In: | 16.08.3 |
Description
RJ
2016-10-24 20:40:14 UTC
I can confirm that KAlarm crashes when a second instance is started. As you say, this shouldn't happen. The message about "No writable active calendar" indicates that you won't be able to save alarms to disk. This should have been fixed in KAlarm version 2.11.10-5, which will be in KDE Applications 16.08.3. See bug 362962 for details on how to get round that issue with earlier KAlarm versions. The crash has now been fixed in KAlarm version 2.11.10-5 (which will be in KDE Applications 16.08.3), by commit 6bd68f98d675e30fab24713e63dfe72cdfd6f4f5 in branch Applications/16.08. Starting a second instance now pops up the first one if it is running in the system tray, as expected. |