Bug 9457

Summary:	KAlarm sill not store a new (display) alarm
Product:	Mageia	Reporter:	Maurice Batey <maurice77>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stormi-mageia
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kdepim4-4.8.5-1.2.mga2.src.rpm	CVE:
Status comment:

Description Maurice Batey 2013-03-19 19:44:51 CET

Description of problem:

When a new (display) alarm is defgined, KAlarm will not store it, saying:

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

Version-Release number of selected component (if applicable):

Version 2.8.6-ak

How reproducible:


Steps to Reproduce:
1. Define new (display) alarm
2.  Hit OK
3.  Kalarm states 
   "You must select a calendar to save the alarm in"

(even if /config/storage is set to 'Store in default calendar')


Reproducible: 

Steps to Reproduce:

Comment 1 Maurice Batey 2013-03-20 20:10:32 CET

This has been resolved, after finding:

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

KAlarm had somehow got disconnected from calendar.ics.

I was able to reconnect it via the 'Add' function on the Asctive alarm calendar.

New alarms are now stored.

Comment 2 Samuel Verschelde 2013-08-28 17:28:24 CEST

Thanks for giving us that link. I can see that it's not a bug, but since it's confusing the author improved it in recent versions of KAlarm. This will be better in future versions of Mageia then.

Status: NEW => RESOLVED
CC: (none) => stormi
Resolution: (none) => INVALID

Comment 3 Maurice Batey 2013-08-28 17:42:01 CEST

Good to hear it's now sorted out. Thank you, Samuel!