Version: 2.4.5 (using 4.4.3 (KDE 4.4.3), Debian packages) Compiler: cc OS: Linux (x86_64) release 2.6.32-5-amd64 Since KDE SC 4.4.3 (I guess) new alarms cannot be deferred anymore. I get the following message : "Cannot defer alarm : Alarm not found". Some old alarms can still be deferred.
I can't reproduce the bug - I tried with both recurring and non-recurring new alarms. Can you please attach your active alarm calendar file containing a non-deferrable alarm(probably ~/.kde/share/apps/kalarm/calendar.ics), and identify at least one example of an alarm you can't defer. You can edit the display texts in the calendar if you like, for privacy.
Created attachment 43529 [details] My alarms calendar At least the first alarm "moutouelle" contains the bug
Unfortunately I still can't reproduce the problem. 1) Does the bug happen with recurring alarms, or only non-recurring ones? 2) Can you please attach your KAlarm config file (probably ~/.kde/share/config/kalarmrc). 3) Can you also try displaying the Defer dialogue for an alarm you know will show the bug, and before clicking OK in the Defer dialogue, make a copy of the following files in the ~/.kde/share/apps/kalarm/ directory (or wherever your calendar files are: - calendar.ics - displaying.ics - expired.ics Once you have confirmed that the bug happens when you click OK, please attach these three files, and identify which alarm you were testing the bug with. Hopefully that will give me enough information to find out what's going wrong.
Le vendredi 21 mai 2010, David Jarvie a écrit : > 1) Does the bug happen with recurring alarms, or only non-recurring ones? Seems to only happen with non recurring ones. > 2) Can you please attach your KAlarm config file (probably > ~/.kde/share/config/kalarmrc). Done. > 3) Can you also try displaying the Defer dialogue for an alarm you know > will show the bug, and before clicking OK in the Defer dialogue, make a > copy of the following files in the ~/.kde/share/apps/kalarm/ directory (or > wherever your calendar files are: > > - calendar.ics > - displaying.ics > - expired.ics Done > Once you have confirmed that the bug happens when you click OK, please > attach these three files, and identify which alarm you were testing the > bug with. The alarm name is "test" > Hopefully that will give me enough information to find out what's going > wrong.
You haven't attached the files.
Created attachment 43898 [details] Test as asked in comment #3 1/4
Created attachment 43899 [details] Test as asked in comment #3 2/4
Created attachment 43900 [details] Test as asked in comment #3 3/4
Created attachment 43901 [details] Test as asked in comment #3 4/4
Thanks. It turns out that the alarm isn't being written to displaying.ics when it is shown. There should be a fix soon.
Now fixed in KDE 4.4 branch (SVN commit 1132307). Note that this bug does not apply to KDE trunk. The fix has missed the deadline for KDE 4.4.4 - it should be in the next release, either KDE 4.4.5 or KDE 4.5.0.