Red Hat Bugzilla – Bug 808066
Kalarm not allowing editing or deleting of alarms
Last modified: 2012-04-06 17:32:41 EDT
Description of problem:
Kalarm not allowing editing or deleting of alarms. See upstream bug:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create new alarm, if needed
2. edit any alarm
"error saving alarm"
works ok on my f16 (and f17 testing) boxes, so I can't reproduce this problem.
wait! spoke too soon, my test audio alarm went off (and is repeatedly playing... another bug?), and *now* it won't let me edit or delete it.
OK, according to the upstream bug, this has been fixed in kde-4.8.2 (coming soon, early april).
updated these rpms from updates-testing:
then quit kalarms and restarted it.. and it doesn't show any of my alarms! The alarm list is completely empty. :-(
Any chance of getting a fix before then? I depend on several daily alarms... Or is there a revert procedure to got back to the old versions of kdepim (or kde*, if necessary)?
I guess they did have a reference to the fix,
git commit ae66e32fb194e01e06521c78e9c72d772d291261
I'll see if I can track that down.
OK, test build underway,
kdepim-4.8.1-4.fc16 has been submitted as an update for Fedora 16.
kdepim-4.8.1-4.fc17 has been submitted as an update for Fedora 17.
works for me.. though my main user was still coming up with a blank alarm list and all menu item's greyed out.. a new user worked fine.. anyone with the empty list/greyed out menus should see comment 11 of http://old.nabble.com/-Bug-290050--New%3A-cannot-add-alarms-after-upgrading-to-4.8-beta-td33047691.html
Thanks for the quick fix, Rex!
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kdepim-4.8.1-4.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
kdepim-4.8.1-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.