Closed
Bug 703226
Opened 13 years ago
Closed 13 years ago
Cannot dismiss or snooze recurring alarms without errors
Categories
(Calendar :: Lightning Only, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 701659
People
(Reporter: neil, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 Build ID: 20111104165243 Steps to reproduce: Linux (Fedora 14 *and* CentOS 5) Thunderbid 8.0 w/ Lightning 1.0, using Google calendar. This is brand new since updating (first at home on Fedora, then a week or so later at work on Cent OS, both times the problem started after the update). Tried to snooze a yearly reminder. Then tried to dismiss it. Finally closed it with window's 'X' button. Actual results: Dialogue stayed up when using its own buttons. After closing via 'X', I get a prompt saying that the event has changed on the server in the meantime, do I want to reload or overwrite (as if the inital snooze/dismiss has worked its way to the server, but the window itself hasn't been closed)? It seems to not matter which answer I give; if I snooze, I (so far) do get the repeat reminder. Expected results: Dialogue closed after selection appropriate option. I cannot repeat this with *new* events (I just created a daily repeated alarm [via Google], and it's behaving properly). I shall edit & resave the ones that are currently causing problems (via Google) and see if the issue goes away.
OK, managed to re-create it with a new yearly repeated all-day event. The dialogue doesn't go away when expected, and then when force-closed gives: This item has recently been changed on the server. Submitting your changes will overwrite the changes made on the server. Note that I *didn't( make changes on the server, I still think that those changes were Lightning's previous attempt to save.
Comment 2•13 years ago
|
||
Was the reminder set more than 6 hours before? If so this is likely Bug 701659
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•