704781 - Reacting on event reminder leads to MODIFICATION_FAILED

Status: RESOLVED DUPLICATE of bug 701659

(Calendar :: General, defect)

Description

[r0bb3n]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0a2) Gecko/20111122 Firefox/10.0a2
Build ID: 20111122042008

Steps to reproduce:

When getting an event reminder (e.g. Birthday of somebody), I try different action (remind later, push X-Button, close all) to react on this remind (for instance select "remind me in 2 hours again"). The event is part of a local calendar with full permissions of read and write.


Actual results:

Error-Dialog pops up with: MODIFICATION_FAILED. No additional description is available in this dialog.

Andvanced messages from error console:
Warnung: getAttributeNode() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen getAttribute().
Quelldatei: chrome://calendar/content/calendar-error-prompt.xul
Zeile: 0

Fehler: Beim Schreiben in den Kalender Privat ist ein Fehler aufgetreten! Fehlercode: MODIFICATION_FAILED. Beschreibung: 
Quelldatei: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/r0bb3n/AppData/Roaming/Thunderbird/Profiles/p4xx1bxf.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js
Zeile: 1101

Warnung: Fehler beim Lesen von Daten für Kalender: Privat. Allerdings ist dieser Fehler wahrscheinlich vernachlässigbar, daher versucht das Programm fortzufahren. Fehlercode: 0x80004005. Beschreibung: generation too old for for modifyItem

*************************
My system:
OS: Windows 7 32bit
Thunderbird:
    Version: 8.0
    User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
  Erweiterungen
    AddressBookTab, 1.4.2, true, [e-mail]
    Allow HTML Temp, 3.2.3, true, {532269cf-a10e-4396-8613-b5d9a9a516d4}
    Automatic Export, 0.5.1, true, {A79E82DD-9CE6-87C7-0006-87D0FD2FCD42}
    British English Dictionary, 1.19.1, true, [e-mail]
    Deutsches Wörterbuch, 2.0.2, true, [e-mail]
    Enigmail, 1.3.3, true, {847b3a00-7ab1-11d4-8f02-006008948af5}
    Lightning, 1.0, true, {e2fda1a4-762b-4020-b5ad-a41df1933103} (BuildID=2011110405001)
    MinimizeToTray revived (MinTrayR), 1.0, true, [e-mail]
    MyPhoneExplorer, 2.0.9, true, [e-mail]
    Provider für Google Kalender, 0.9, true, {a62ef8ec-5fdc-40c2-873c-223b8a6925cc}
    Quicktext, 0.9.11.1, true, {8845E3B3-E8FB-40E2-95E9-EC40294818C4}
    XNote++, 2.2.7, true, [e-mail]
    ESET Smart Security Extension, 4.2.71.2, false, [e-mail]
    ThunderBrowse, 3.8, false, [e-mail]


Expected results:

The reminder Dialog should disappear without any notification and in 2 hours (e.g.)  the reminder should reappear for this event.

Comment 1

[Matthew Mecca [:mmecca]]

Was this a repeating event, with an alarm set more than 6 hours before? If so this is likely Bug 701659

Comment 2

[Rolf Sponsel]

Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5

Just want to contribute the error messages, in english, from the Error Console of SeaMonkey 2.5 + Lightning 1.0, since I experience this same behavior in SeaMonkey 2.5 (although the Portable version, see portableapps.com) after upgrading from SM 2.4.1 (w/ some beta version of Lightning 1.0 - don't remember which one, sorry, but I think it was b7):


Warning: There has been an error reading data for calendar: Birthdays.  However, this error is believed to be minor, so the program will attempt to continue. Error code: 0x80004005. Description: generation too old for for modifyItem

Error: An error occurred when writing to the calendar Birthdays! Error code: MODIFICATION_FAILED. Description: 
Source File: resource://calendar/modules/calUtils.jsm -> file:///X:/PortableApps/SeaMonkeyPortable/Data/profile/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js
Line: 1101

Warning: Use of getAttributeNode() is deprecated. Use getAttribute() instead.
Source File: chrome://calendar/content/calendar-error-prompt.xul
Line: 0


If it is a duplicate of bug 701659 then there is no need for any further action. I just wanted to mention that I see the same using Lightning 1.0 in SeaMonkey 2.5 too, and contribute the error message in english - since I have it handy.