#23 ThunderSnarl breaks alert dialogs in Lightening 1.0b1

Crash (8)

I am using Thunderbird 3.0 and Lightening 1.0b1 w/ the associated GMail provider. I have numerous calendars all using the GMail provider and none using local calendars. When an alarm goes off, the alarm dialog box comes up with the string "Failed to read 'alarmWindowTitle' from chrome://calendar/local/calendar.properties." and the Dismiss and Snooze buttons are completely non-functional. A quick look in the Error Console shows the following error.

Error: Failed to read 'alarmWindowTitle' from chrome://calendar/locale/calendar.properties. Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.formatStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://calendar/content/calUtils.js :: calGetString :: line 639" data: no]
Source File: chrome://calendar/content/calUtils.js
Line: 645

Clicking the Dismiss button ha no effect, but clicking the Snooze button causes an error to be put in the error log (something about the number of arguments for a call being incorrect). Sorry, but I don't have a copy of this error since I can't get another alert window to pop up.

Everything with Lightening works just fine when I have ThunderSnarl disabled.


  • Sven Walther

    Sven Walther - 2010-01-16
    • priority: 5 --> 7
    • assigned_to: nobody --> svenwal
    • status: open --> open-accepted
  • Sven Walther

    Sven Walther - 2010-01-16

    Confirmed - this is how ThunderSnarl Works with Lightning 0.9 (and 0.8). Hope to get a new release out within a week - already started work on it with a much "cleaner" way of capturing the alerts. Maybe I will put out out an intermediate release without Lightning at all first

  • Sven Walther

    Sven Walther - 2010-01-17

    ThunderSnarl 2.0.1 released which (for now) disables Lightning. Will add Lightning 1.0 back with ThunderSnarl 2.1 in the near future


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks