Bug 374424 - Calendar files are wrongly created read-only or disabled
Summary: Calendar files are wrongly created read-only or disabled
Status: CLOSED WORKSFORME
Alias: None
Product: kalarm
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.11.9
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-01 16:52 UTC by David Jarvie
Modified: 2021-01-09 17:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Jarvie 2017-01-01 16:52:03 UTC
Bugs reported in the KDE Forums https://forum.kde.org/viewtopic.php?f=229&t=138128&p=369598#p369598:

When KAlarm is run the first time, the calendar files are created read-only.

Creating new calendar files via the GUI results works, but they are initially disabled.
Comment 1 David Jarvie 2017-01-02 18:10:11 UTC
Calendar files being created read-only was probably fixed in version 2.11.10, which fixed default calendar files not being created on first run.
Comment 2 David Jarvie 2017-01-05 22:10:14 UTC
See Bug 362962 for the read-only creation bug report.
Comment 3 David Jarvie 2018-08-02 22:28:36 UTC
I can't reproduce calendar files being created disabled, so closing.