Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20101112 Firefox/4.0b8pre SeaMonkey/2.1b2pre - Build ID: 20101112022323 Lightning 1.1a1pre mozilla-central linux nightly dated 2010-11-11 bp-82556800-2796-4243-9f10-9adf82101112 Reproducible: Always Steps to Reproduce: 1. Make sure Lightning is installed and enabled 2. Start or restart SeaMonkey (or, presumably, Thunderbird). Additional info: Symptoms similar to those of bug 599637, except that: - the bug now happens at every startup if Lightning is enabled - it happens in Calendar code, not in javascript interpreter code which makes me believe it's a different bug (and a Calendar bug rather than a Core bug, but I'm not sure about the proper bugzilla Component). Here is the crash data (summary and crashing thread) as reported by Breakpad and Socorro: Signature libcalbasecomps.so@0xedad4 UUID 82556800-2796-4243-9f10-9adf82101112 Time 2010-11-12 07:04:43.424536 Uptime 42 Last Crash 1135490 seconds (1.9 weeks) before submission Install Age 42 seconds since version was first installed. Product SeaMonkey Version 2.1b2pre Build ID 20101112022323 Branch 2.0 OS Linux OS Version 0.0.0 Linux 2.6.34.7-0.5-desktop #1 SMP PREEMPT 2010-10-25 08:40:12 +0200 i686 CPU x86 CPU Info AuthenticAMD family 6 model 7 stepping 1 Crash Reason SIGSEGV Crash Address 0x54746566 User Comments at startup with Lightning enabled Processor Notes EMCheckCompatibility False Crashing Thread Frame Module Signature [Expand] Source 0 libcalbasecomps.so libcalbasecomps.so@0xedad4 1 libcalbasecomps.so libcalbasecomps.so@0xecf3c 2 libcalbasecomps.so libcalbasecomps.so@0x29e6b6 3 libcalbasecomps.so libcalbasecomps.so@0xf163c 4 libcalbasecomps.so libcalbasecomps.so@0x29e6b6 5 libxul.so js_ReportUncaughtException js/src/jsexn.cpp:1304

Same as Bug 609553?

(In reply to comment #1) > Same as Bug 609553? bug 609553 crashes with SIGABRT, I get SIGSEGV, and at a somewhat different address but still in libcalbasecomps.so. I'll leave you the judge of whether they can be dupes anyway.

Symptoms have changed: No crash now (maybe the fix for bug 609553 cured it) but the calendar tab looks as if I had no calendars defined (no calendar list, empty Day, Week, Multiweek or Month view, empty events list above that); and yet about:config has the calendar.registry.* entries for all my calendars, and with (among others) *.disabled == false. That is of course a different bug but I can't find it.