Bug 317042 - KAlarm (Version 2.8.6-ak) will not save new alarm
Summary: KAlarm (Version 2.8.6-ak) will not save new alarm
Status: CLOSED WORKSFORME
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: KDE 4
Platform: Mageia RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 18:36 UTC by Maurice Batey
Modified: 2020-08-18 10:31 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maurice Batey 2013-03-19 18:36:51 UTC 
On 64-bit Mageia-2, when defining a new (display) alarm, KAlarm - 
instead of storing the new alarm - puts out the failure '2':

  "You must select a calendar to save the alarm in"

N.B. In 'configure/storage, I tried selecting 'Store in default calendar',
but the problem persists.



Reproducible: Always

Steps to Reproduce:
1. In KAlarm, select 'New/Display'
2. Define new alarm
3. Hit 'OK'  -->  

Actual Results:  
KAlarm puts out:   "You must select a calendar to save the alarm in"
- so cannot define a new alarm....

Expected Results:  
New alarm stored and shown in KAlarm list

rpm -qif /usr/bin/kalarm
Name        : kalarm
Epoch       : 2
Version     : 4.8.5
Release     : 1.2.mga2
Architecture: x86_64
Install Date: Fri 07 Sep 2012 17:16:44 BST
Group       : Graphical desktop/KDE
Size        : 2202165
License     : GPLv2 and LGPLv2 and GFDL
Signature   : RSA/SHA1, Tue 14 Aug 2012 11:07:22 BST, Key ID b742fa8b80420f66
Source RPM  : kdepim4-4.8.5-1.2.mga2.src.rpm
Build Date  : Tue 14 Aug 2012 11:00:35 BST
Build Host  : ecosse.mageia.org
Relocations : (not relocatable)
Packager    : mikala <mikala>
Vendor      : Mageia.Org
Comment 1 David Jarvie 2013-03-20 09:23:38 UTC 
Can you please check whether you have any enabled, writable active alarm calendar. Use the menu option View -> Show Calendars and with Active Alarms selected, check the status of the calendars displayed. The error you see will occur if there are none shown, or if none of them are ticked, or if when you hover the mouse over them they are shown as read-only. In that case, you need to either add a new calendar, enable a calendar by ticking it, or investigate why it is read-only (probably due to file permissions).
Comment 2 Maurice Batey 2013-03-20 18:16:10 UTC 
The 'Active Alarms' entry was greyed out.

Fortunately a fellow Mageia user was able to point me at:

    http://forum.kde.org/viewtopic.php?f=229&t=110230

and by using 'Add' for Active Alarms I was able to reconnect KAlarm with calendar.ics.
  (How/why had it become disconnected?)

So I'm happy to report that new alarms *are* being stored, so the issue is RESOLVED.

Thank you for your prompt response - much appreciated!
Comment 3 David Jarvie 2013-04-14 21:55:13 UTC 
In KDE 4.11, the user will be warned if KAlarm starts up without any enabled, writable calendars. This may help users to sort out the type of problem you describe. See bug 316338.
Comment 4 Maurice Batey 2020-08-18 10:31:58 UTC 
Agreed! Apologies for leaving this open...