Bug 9457 - KAlarm sill not store a new (display) alarm
Summary: KAlarm sill not store a new (display) alarm
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-19 19:44 CET by Maurice Batey
Modified: 2013-08-28 17:42 CEST (History)
1 user (show)

See Also:
Source RPM: kdepim4-4.8.5-1.2.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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!
Note You need to log in before you can comment on or make changes to this bug.