| Summary: | Kalarm not allowing editing or deleting of alarms | ||
|---|---|---|---|
| Product: | [Applications] kalarm | Reporter: | bill p. (aka google01103) <dweeble01103> |
| Component: | general | Assignee: | David Jarvie <djarvie> |
| Status: | CLOSED FIXED | ||
| Severity: | major | CC: | alex, andy75043, arthur, darose |
| Priority: | NOR | ||
| Version: | KDE 4 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.8.2 | |
| Sentry Crash Report: | |||
| Attachments: | xsession-errors with all Kalarm processes checked in Kdebugdialog | ||
I assume that you are using KAlarm version 2.8.1. If so, this has been fixed for KDE 4.8.2 (git commit ae66e32fb194e01e06521c78e9c72d772d291261). using 4.8.1 so I can't edit nor delete but I can add alarms? 4.9 beta one is not till 5/25 what can I do till then? I'd rather not compile all of KDE from git (not sure I could). Can I just compile the kalarm package? as it's not available on the Kalarm download page the git command to dl is _____? is the bug in 4.8.0? can fix be back ported to 4.8.1 The bug wasn't in 4.8.0, so you could try this if it's available. However there were other problems, including crashes in 4.8.0, so it may not work for you either. 4.8.2 should be released in early April, and in the meantime I'm working on releasing the latest version on the KAlarm website, hopefully in the next week or two. The bugs are due to the major changes in the storage access method in KDE 4.8, and unfortunately some significant bugs only came to light after it was released (and the bug in this report arose as a by-product of fixing these). I'm fairly confident that 4.8.2 should be much more usable. I compiled and installed Kalarm 2.7.4 (source from the Kalarm website) after removing the 4.8.1 package. But not all the alarms showed unfortunately. could you post here when the latest version is available for testing and I'd be happy to help test thanks, FYI - we're seeing this bug on Arch Linux as well: https://bugs.archlinux.org/task/28891 The bug would apply to all 4.8.1 packages, regardless of distro. I don't understand why alarms would be missing when reverting to KAlarm 2.7.4, since the calendar format hasn't changed since then. I'll post here when an update is issued. David - re-dl'ed and re-compiled 2.74 and again not all alarms showed, re-installed 4.8.1 and again all show *** Bug 296703 has been marked as a duplicate of this bug. *** I have this problem as well, but only on one user account; the other works fine. Is there something I can do (set a flag, delete or modify a file, etc.) to work around this on the affected account? It's a nuisance, but not worth jumping through the hoops to bypass the Fedora update process. Comment 3 in the bug report explains your options. If 4.8.0 doesn't work, unfortunately you'll have to wait for KDE 4.8.2. If you're the brave sort, you can try rebuilding the package with the patch that fixes this. (See: http://projects.archlinux.org/svntogit/packages.git/plain/trunk/fix-kalarm-issue-with-alarms.patch?h=packages/kdepim&id=0789134b1d62bb61214c0fab382132d9b28e0374) Or you could try to see if your distro's KDE maintainer would be willing to rebuild the package to address this. (It really is a rather functionality-crippling bug.) The maintainer on ArchLinux was kind enough to do that for me. I agree, it would be crippling to anyone who uses lots of short-term
alarms, especially since it affects deletions as well as changes. But
as it happens, I only have a handful of alarms I rely on regularly, and
I tend to use a kitchen timer or my watch for one-time events, so it
isn't that big a deal to me -- certainly not worth the download and
rebuild effort.
If you want to mention it to the Fedora distro team, by all means add my
name to those interested; it can't hurt, and might help. But frankly, I
doubt it would make much difference either way; Fedora has a big user
list, and I'm very small fry to them.
-- Andy
Garland, TX
On 03/30/2012 04:12 PM, David Rosenstrauch wrote:
> https://bugs.kde.org/show_bug.cgi?id=295926
>
> --- Comment #11 from David Rosenstrauch<darose@darose.net> ---
> If you're the brave sort, you can try rebuilding the package with the patch
> that fixes this. (See:
> http://projects.archlinux.org/svntogit/packages.git/plain/trunk/fix-kalarm-issue-with-alarms.patch?h=packages/kdepim&id=0789134b1d62bb61214c0fab382132d9b28e0374)
> Or you could try to see if your distro's KDE maintainer would be willing to
> rebuild the package to address this. (It really is a rather
> functionality-crippling bug.) The maintainer on ArchLinux was kind enough to
> do that for me.
>
Can anyone tell me when KDE 4.8.2 will be released? That bug is driving me crazy but I don't want to rebuild it from sources... Tuesday, April 3, 2012: KDE SC 4.8.2 is scheduled to be released |
Created attachment 69576 [details] xsession-errors with all Kalarm processes checked in Kdebugdialog Kalarm started not functioning correctly this morning, may or not be because of a recent update but since I had not added/deleted/edited any alarms recently unable to know. Issues: -> deleting alarm - message "error deleting alarm" -> saving an edited existing alarm - message "error saving alarm" but can create new alarm as it works fine things I tried that did not work: - restarting KDE - restarting computer - restoring Kalarm rc files and folder from past Satuday's backup Ran Kdebugdialog and selected all Kalarm processes (activities?) and did not see anything obvious in ~/.xsession-errors (file attached, unfortunately there's a bunch of extraneous soprano stuff)