Closed Bug 1144285 Opened 9 years ago Closed 4 years ago

(Portable) SeaMonkey 2.33 and Lightning 3.8b1/3.8b2 shows no events or tasks

Categories

(SeaMonkey :: Calendar, defect)

Product:
SeaMonkey
Component:
Calendar
Version:
SeaMonkey 2.33 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: Carsten.Huetter, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33
Build ID: 20150308222025

Steps to reproduce:

I updated PortableApps SeaMonkey 2.32.1 to SeaMonkey 2.33 and updated the corresponding Lightning 3.7b1 to 3.8b1. 


Actual results:

After updating, the calendar views does not show any events or tasks. The calendar window flickers somewhat, repeatedly repainting the event list's heading. The calendar view tabs are missing as well.

The error console shows:

Zeitstempel: 17.03.2015 19:33:56
Fehler: TypeError: Components.classes[cid] is undefined
Quelldatei: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/*****/Programme/PortableApps/PortableApps/SeaMonkeyPortable/Data/profile/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js
Zeile: 17



Expected results:

The calendar window should show all the calendar's events and all the view tabs.
I reported this issue to the PortableApps support. John T. Haller replied:

"If an extension works in local SeaMonkey, it should work in portable SeaMonkey since SeaMonkey Portable includes a completely unmodified copy of SeaMonkey launched with the -profile switch pointing to a portable profile. Any extensions that fail likely fail due to an incompatibility with that particular command line switch. This issue should usually be reported to the extension developer."

There were no issues with portable SeaMonkey and Lightning up to 2.32.1/3.7b1.
I did a quick test and I see no problems. Tested the official Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33 with Lightning 3.8b2, both in German.
I have the identical problem with normal SeaMonkey and Lightning 3.8b1/3.8b2. In case it's relevant, I'm using EN-GB, and I notice that it's one of the language variants that has very different file sizes.
(In reply to Stefan Sitter from comment #2)
> I did a quick test and I see no problems. Tested the official Mozilla/5.0
> (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33
> with Lightning 3.8b2, both in German.

I already performed the update to SeaMonkey 2.33/Lightning 3.8 on two windows systems (XP 32bit, Win7 64bit) and one linux system (Ubuntu 14.04 LTS 64bit) without any gliches, just as you did. So far, I experienced this particular issue with the portable SeaMonkey (PortableApps edition) only.
Have you tried Lightning 3.8b2? The first beta had flaws like this.

Beside of this, it may be a binary issue. On what OS are you on?
(In reply to MakeMyDay from comment #5)
> Have you tried Lightning 3.8b2? 

Yes. Same negative result.

> Beside of this, it may be a binary issue. On what OS are you on?

It's Win7 aka Win NT 6.1 32bit.
I am having the same issue with regular SeaMonkey on Win XP. I have tried installing an older version of Lightning which has been reported to work but that did not work for me either.

I have seen reports of the same problem on Win 7 and Win 8 but others report success.
Further information:
- WinXP SP3 (Workstation) has this problem with 2.33 and 2.33.1 with Lightning 3.8b2.
- Win7 32-bit (Laptop) doesn't have the problem.

Problem symptoms:
- Calendar views do not show events etc.
- SeaMonkey uses about 5% CPU all of the time (even if there's no browser window open). As soon as the calendar is closed, the CPU usage becomes normal (i.e. it's only used when required).
- The Calendar display tab is damaged - the "close tab" button is missing; the calendar toolbar is displayed twice; the "Events" display section disappears off the right hand side of the window and can't be changed; the "Show" radio buttons are greyed out.

The problem occurs even when almost all other extensions are disabled.

This MozillaZine topic describes the same problem - http://forums.mozillazine.org/viewtopic.php?f=5&t=2920337 - and it appears from Bug 1136890 Comment 8 posted by MakeMyDay that the problem will only be fixed in Lightning 3.9. (Note that setting calendar.icaljs to false does NOT fix the problem.)
Bug 1136890 suffered from different issues and only one of them was the icaljs thing. On top of this, there exist localization issues and eventually a backend problem of the Windows builds in combination with SM. I read somewhere that TB 36b works fine.

So, if you are not using a localized version and have icaljs disabled but you ate expiriencing this issue, can you please test whether this is still an issue in Lightning 3.9b with SM 2.34b?
Where can one download SeaMonkey 2.34b?
Not sure why "Duplicate of this bug: 114692" as this bug (1144285) is for the 'Portable Apps build of SeaMonkey' which may, or may not be compatible with the builds provided on "http://www.seamonkey-project.org/"... In any event, I can confirm the symptoms "After updating, the calendar views does not show any events or tasks. The calendar window flickers somewhat, repeatedly repainting the event list's heading. The calendar view tabs are missing as well." in:

User agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1
Build identifier: 20150321194901
Windows 8.1
Lightning	3.8b2	true	{e2fda1a4-762b-4020-b5ad-a41df1933103}

Note: seems to work fine on Windows 7 and another Windows 8.1 that I fixed - no issues on linux.

Can we please expect a fix to this soon?
As 2.34b is not yet availabe, can somebody give the aurora build of SM 2.35 with Lightning 4.0 a try to check whether this is still an issue there?
Why is this bug still marked unconfirmed? There seem to be several reports of the same bug, and other similar bugs marked as dups. 

I concur with the previous comment that there may be confusion about whether this bug applies only to Portable Seamonkey. That is the reason I filed another bug against Seamonkey, which was marked as a duplicate of this one. I suspect they are the same and that makes it potentially more significant.

As for testing SM 35 and Lightning 4.0 I'm not sure that will confirm the bug is not present in those builds. It appears this bug does not affect every installation, some people are reporting success with the existing builds.
You're right, this is a confirmed bug, so I changed the status (but this means not that we're any closer to a resolution yet). Based on the error messages this is the same issue whether for portable or installable edition. To make this obvious, I slightly changed the title of the this bug.

Apart from testing with SM 2.35/Ltn4.0, everybody who has an affected installation, can you please check whether you also expirience the issue with a new and clean profile?

So far is seems clear that this issue is only on Windows, while it spreed over various combinations of versions and architectures and the same combinations work for some and fail for others - irrespective whether it's the portable or installed edition. Problems seem to start with Ltn 3.8 rsp. SM 2.33.

Since 3.3 we've had only few build config changes up to 3.8 and no Windows specific targeting for 3.8. Also, Thunderbird doesn't seem to be affected - at least there're no reports. Maybe the problem is in Seamonkey and in Lightning. Philipp, Neil, do you have any idea?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(philipp)
Flags: needinfo?(neil)
Summary: Portable SeaMonkey and Lightning 3.8b1/3.8b2 shows no events or tasks → (Portable) SeaMonkey and Lightning 3.8b1/3.8b2 shows no events or tasks
I downloaded SeaMonkey Portable 2.33.1 and then installed Lightning 3.8b2, I then opened the Mail & Newsgroups window and opened Events and Tasks - Calendar, but nothing looked wrong to my untrained eye. (I did notice that the Today pane kept on defaulting to 30 Jan 5555 though.) Is there anything else I should be doing to try to reproduce this bug?
The 5555 bug is unrelated and meanwhile fixed. Most probably you need events, because event handling is what our backend does.
Thanks for updating this bug.

I have tested my broken installation with a clean profile and it did not fix the issue.

The machine with the issue is at a different site so I can't test the other versions on it until late next week when I will be there. In the meantime I don't want to break any more machines. If you need any tests or information I will be happy to do it when I'm there. 

In any event I think if the newer versions correct the problem that may indicate it is not present in those version. On the other hand it may be something in the install that breaks the existing installation that may not be corrected by a more recent version. 

On Bug 1146927 (now marked as a dup) I uploaded a screen shot of my issue, if that helps.
Also tried with a clean profile - same results. I then tried backing down to SeaMonkey 2.33 - no change, so perhaps in that case it is something in the profile. I'll try again with a clean 2.33 later. Regarding working 2.33.1 Win 8.1 - the machine is remote so I'll need to have access again before I can test. I'll try in a Win 8.1, Win 7 and Win 10 in Virtual Machiness to see if I can reproduce in those. It it works in those, then perhaps it could be related to graphics hardware?
last know working version is SM 2.32.1 with LN 3.7b on Win7/32
(I am german but I have to take the english version, as there are no LN-localisations)
actually I downgraded to that SM due to lack of a working LN.

martin
That's what I did. 

Sadly, I'm lacking the technical knowledge and the coding skills to find the reason of SeaMonkey 2.33.1 and Lightning 3.8b1/2 working on some systems but not on others.
NoOp,

For me the bug first appeared in 2.33 3.8b1. I would not expect backing down from 2.33.1 to 2.33 to affect the results. 

I don't recall the version I had before upgrading it might have been older than 2.32
Sorry Rob, I backed down to SM 2.*32*.1/LTG 3.7b1, just as mhonline. This combo is still playing the jazz, so to speak.

Many thanks for all your commitments to the Mozilla community!
Sorry, but I still don't seem to have any problems with events or tasks, so I don't know what could be going wrong here.
Flags: needinfo?(neil)
(In reply to neil@parkwaycc.co.uk from comment #26)
> Sorry, but I still don't seem to have any problems with events or tasks, so
> I don't know what could be going wrong here.

Neil: What version of Windows are you using? How did you install the Portable Apps version - standalone or via the PA platform? What is the build configuration?

I just installed 

User agent: Mozilla/5.0 (Windows NT 6.3; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1
Build identifier: 20150321194901 (same build as that reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1146927)
Build Machine

sea-vm-win32-1
Source

Built from http://hg.mozilla.org/releases/mozilla-release/rev/df45b1c67169
Build platform
target
i686-pc-mingw32
Build tools
Compiler 	Version 	Compiler flags
cl 	1600 	-TC -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4244 -wd4267 -wd4819 -we4553
cl 	1600 	-TP -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4251 -wd4244 -wd4267 -wd4345 -wd4351 -wd4482 -wd4800 -wd4819 -we4553 -GR- -DNDEBUG -DTRIMMED -Zi -UDEBUG -DNDEBUG -O1 -Oi -Oy
Configure arguments

--enable-crashreporter --enable-release --enable-application=suite --enable-update-channel=release --enable-update-packaging --enable-jemalloc --enable-tests --disable-gamepad --with-external-source-dir=e:/builds/slave/rel-c-rel-w32-bld/build

On both Windows 8.1 and Windows 10 build 9926 - no previous SeaMonkey installs on either virtual machine. I did not add any add-ons, or email accounts, just install Lightning 38b2 from 
https://addons.mozilla.org/en-us/seamonkey/addon/lightning/versions/
Version 3.8b2 Released March 12, 2015 4.3 MB Works with SeaMonkey 2.33 - 2.33.*, Thunderbird 36.0 - 36.* 

Restarted, opened up Calendar, created a 'test' calendar (on local machine)- entered no data, restarted SeaMonkey, selected Calendar, clicked on the calendar icon - that opens the calendar tabe in the mailnews window. Result same as the description of this bug and that of https://bugzilla.mozilla.org/show_bug.cgi?id=1146927 and comment 1 of this bug report "Actual results:

After updating, the calendar views does not show any events or tasks. The calendar window flickers somewhat, repeatedly repainting the event list's heading. The calendar view tabs are missing as well."

Note: this exactly the reason why I believe 1146927 should have been left open and not marked as a duplicate of this bug report - we now have multiple builds that people are attempting to troubleshoot/work with. I'm not concerned about a Portable Apps build of SeaMonkey, they have a support page: http://portableapps.com/support for their builds. Can we please reopen and use 114692 for the Mozilla provided builds of SeaMonkey 2.33.x and Lightning?
Just tested with a newly installed Windows 7 VM - same results.

User agent: Mozilla/5.0 (Windows NT 6.1; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1
Build identifier: 20150321194901

Build Machine

sea-vm-win32-1
Source

Built from http://hg.mozilla.org/releases/mozilla-release/rev/df45b1c67169
Build platform
target
i686-pc-mingw32
Build tools
Compiler 	Version 	Compiler flags
cl 	1600 	-TC -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4244 -wd4267 -wd4819 -we4553
cl 	1600 	-TP -nologo -D_HAS_EXCEPTIONS=0 -W3 -Gy -wd4251 -wd4244 -wd4267 -wd4345 -wd4351 -wd4482 -wd4800 -wd4819 -we4553 -GR- -DNDEBUG -DTRIMMED -Zi -UDEBUG -DNDEBUG -O1 -Oi -Oy
Configure arguments

--enable-crashreporter --enable-release --enable-application=suite --enable-update-channel=release --enable-update-packaging --enable-jemalloc --enable-tests --disable-gamepad --with-external-source-dir=e:/builds/slave/rel-c-rel-w32-bld/build

Extensions
Name 	Version 	Enabled 	ID
ChatZilla	0.9.91	true	{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}
DOM Inspector	2.0.15pre	true	inspector@mozilla.org
Lightning	3.8b2	true	{e2fda1a4-762b-4020-b5ad-a41df1933103}
So what aditional information is required to resolve this issue? SeaMonkey 2.33.1 was released on 3/23 and we are still without a working Windows SeaMoneky and Lightning.
Sorry for that, but based on the current information, this is probably not a Lightning issue. It only affects SM on windows, so it would probably require somebody from the SM team familiar with recent built changes compared to TB to bring some light into this. Can you ask on IRC to catalyse this?
OK I tried some more stuff. 

On my broken machine I logged in as another user . That user had Lightning 3.3.3 installed and while it didn't look as bad and later builds it didn't work. I disabled compatibility checking and installed 3.8b2, same results as before. I also tried to install 3.8 and 4.0 neither would install even with compatibility checking disabled.

I'd try to install a later build of SeaMonkey but couldn't find a windows build. Can someone give me a link?
Rob, thank you for your test but unfortunately it was a waste of your time. We know that incompatible versions of SeaMonkey and Lightning do not work together. This is the reason why the compatibility check and the restriction to not install an incompatible Lightning release exists in the first place.

I just retested as described in Comment 27 above and it still works fine for me. Test system was Windows 7 64-bit with SeaMoneky 2.33.1 (en-US, BuildID 20150321194901) and Lightning 3.8b2 (BuildID 20150213145316). It looks like there is no SeaMoneky 2.34 or 2.35 build available for testing that would be compatible with Lightning 3.9 or 4.0.

Question is: What makes your OS installation or SeaMonkey setup different from other ones? We have in this bug reports that the same builds work for some users but fail for others. Maybe there is something special on how you install SeaMoneky? On how and where you create the SeaMoneky profile? Maybe there is some application e.g. virus scanner that prevents Lightning from accessing its files?
Hello, 

Problem isn't only on Windows, as I made a bug report here: https://bugzilla.mozilla.org/show_bug.cgi?id=1131949 , I have it on Linux too.

What I find out was that when I run Seamonkey as New system user/ Profile, everything was fine. I suppose some settings are staying in the Seamonkey Profile even I remove lightning - which I did it several times -.

Can anybody tell me in which files does Lightning keeps its settings, so I can try to clean from Lightning settings/ delete them?

Any other way to have some debug output so I can investigate / provide it here?
Stephan, 

I cannot tell you what makes my installation different for others. I do not have any special or unusual software installed. No significant changes have been made to my computer recently. I use AVG antivirus. If it would help I can try to provide any information I can.  

I have had SeaMonkey on this computer for a long time and have upgraded it from time to time. Each time I upgrade SeaMonkey I install the version of Lightning for that version SeaMonkey, it has always worked before. I do not upgrade with every release.

There have also been reports that older versions of Lightning does work with SeaMonkey 2.33. There have been reports of Windows 7/7.1 Systems do not work with this combination. I have not seen a report of a Windows 8 system no working.
(In reply to Stefan Sitter from comment #32)
...
> Question is: What makes your OS installation or SeaMonkey setup different
> from other ones? We have in this bug reports that the same builds work for
> some users but fail for others. Maybe there is something special on how you
> install SeaMoneky? On how and where you create the SeaMoneky profile? Maybe
> there is some application e.g. virus scanner that prevents Lightning from
> accessing its files?

Well... for some reason Lightning is now working on this Win 8.1 SeaMonkey 2.33.1. Now I have to figure out what could possibly change to have it start working. 
  I made several changes just prior that I can recall: 1) I was having SSL mail cert issues & finally resolved it by turning off SSL Scanning in Avast 2015.10.2.215, 2) I also turned off Avast Browser Cleanup and Grimefighter. (Don't ask me about Avast as I typically run linux on all of my systems).
I'll experiment this evening by reversing those and see if there is any change. 
  On the Windows 8.1 virtual machine that I tested with a new install, it also has Avast - I'll blow that out and test. I don't recall what I have running on the Window 10 and Windows 7 virtual machines - I do not have those up at this time & will check later. But you may be on to something regarding virus scanners - I can sandbox the VM's, remove all AV and test that way.
Scratch the AV theory - on the VM I uninstalled all AV with same issues; Clean Win 8.1, new SeaMonkey 2.33.1, new calendar - no change. 

@Stephan: you said: "I just retested as described in Comment 27 above and it still works fine for me. Test system was Windows 7 64-bit with SeaMoneky 2.33.1 (en-US, BuildID 20150321194901) and Lightning 3.8b2 (BuildID 20150213145316). It looks like there is no SeaMoneky 2.34 or 2.35 build available for testing that would be compatible with Lightning 3.9 or 4.0."

So I also checked to see if I am using the same build ID - I am:
<em:id>{e2fda1a4-762b-4020-b5ad-a41df1933103}</em:id>
    <em:name>Lightning</em:name>
    <em:version>3.8b2</em:version> <!-- BuildID=20150213145316 -->
Seamonkey Build identifier: 20150321194901

So without some other way to trace/troubleshoot I'm stumped. My only other guess is that perhaps
I have no idea off hand, sorry. I believe all I would suggest has already been, trying a new profile, new download of both Seamonkey and Lightning, etc.
Flags: needinfo?(philipp)
(In reply to Philipp Kewisch [:Fallen] from comment #37)
> I have no idea off hand, sorry. I believe all I would suggest has already
> been, trying a new profile, new download of both Seamonkey and Lightning,
> etc.

Ummm... perhaps you missed that I've installed new Windows systesm (7, 8.1, and 10) and installed NEW SeaMonkey 2.33.1 and Lightning in each - all failed. Just tested on another NEW Windows 7 - 32 bit this time & it failed as well. I don't mind helping to troubleshoot from a user perspective, but without some other debug/troubleshooting methods/advise there isn't much else I can contribute here.
Just two ideas:

1. Did you always test on the same hardware. Does it support hardware accellaration? Do you have support for that enabled in SM (search for direct2d in about:config) and if so, does disabling the same change anything (not neccessarily resolving completely, because this issue may be a coincidence of multiple problems)?

2. SM currently seems to have build problems for Windows - the last nightly builds at [1] are for 2.34a1 from early December. Eventually problems already started in 2.33 life cycle - without preventing SM from building but leading to a binary incompatible version compared to Lightning. This would need some of the SM build folks to confirm or investigate.

[1] http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/
There is a lot to read here, I'm sorry that I didn't read every comment in detail. I was aware that what I mention has likely been suggested, but I was flagged for needinfo and wanted to reply. The only thing I have left to offer is a teamviewer session if you ping me on IRC. Maybe you can give me a short summary of what version combinations are working and which are failing on what OS versions and which antivirus software is involved respectively.
Philipp how can I reach you on IRC ? server / channel / nick ? I am not sure if TeamViewer will work, since in my case at the moment the flickering happens, CPU goes to max and all X windows don't respond very well. I could send you a video taken from my mobile phone of my screen if that helps.
I have several pc running windows 7 32 bit, language german.
After several days installing and de-installing Seamankey and lightning I was successful to get one system working with SM 2.33.1 and lightning 3.8b2
The other system has the same the same structure of directories, eg. SM resides in "Program Files" und the profile resides in "mozdata". Even I copied the content from the working system completely to the other system (into empty directories), i was not successful. 
But the error console of the system without correct function showed:

Failed to load native module at path
'c:\mozdata\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103}\components\calbasecomps.dll':
(80070057) error 126

The file exists at the same place and location within both systems. Is there any hint for this?
A video wouldn't really help, all I could do is some exploratory debugging and I would need teamviewer for that. What kind of flickering? This sounds like a totally different issue? What I am trying to debug here is binary incompatibilities. The error 126 shows that there is definitely some binary incompatibility between Lightning and Seamonkey, I just don't understand why it sometimes works.

As a workaround you could try setting calendar.icaljs to true until the next Seamonkey is released and they have their windows build issues resolved. I know it has been mentioned this doesn't work, but given there are multiple people with different configurations its worth a try.

irc.mozilla.org channel #calendar nickname Fallen
Icaljs cannot not work for 3.8 - for what reason ever the fixes for the broken icaljs have not been backported.
Thanks to NoOp I've been able to debug this in a TeamViewer session. I'm fairly certain this is an issue with the Seamonkey build infra not linking with the right flags, but I do have a workaround:

Please install the following redistributable packages. I installed them in the order 2013 2010 2012 and it worked afterwards, it may be sufficient to just install 2012:

Visual C++ 2010 Redistributable Package (x86):
http://www.microsoft.com/en-us/download/details.aspx?id=5555

Visual C++ Redistributable for Visual Studio 2012 Update 4:
http://www.microsoft.com/en-us/download/details.aspx?id=30679

Visual C++ Redistributable Packages for Visual Studio 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40784

If this doesn't fix the issue please comment. If it does, I'd suggest to wait until 2.34 and hope this fixes it even without the redistributables. Otherwise we should check with the Seamonkey folks.
I've just found a possible solution to the  problem - you must install the appropriate Visual Studio 2013 package from the page https://www.microsoft.com/en-gb/download/details.aspx?id=40784 .

This is as a result the Mozilla changes delivered with Thunderbird 36 - see bugs 1132271 and 1001332.

After installing the appropriate version of the download (Windows XP 32-bit in my case) and re-starting the computer (just to be safe), I upgraded SeaMonkey. Lightning now behaves correctly.

Note that the Visual Studio packages do not come with vanilla Windows installations (you only get the one available at the time of release), but other software might well bring in the required files (msvcp120.dll and msvcr120.dll, I think).

SeaMonkey should probably bundle the software with the Windows builds or at least put the requirement in the release notes.
(In reply to Philipp Kewisch [:Fallen] from comment #45)
...
> Please install the following redistributable packages. I installed them in
> the order 2013 2010 2012 and it worked afterwards, it may be sufficient to
> just install 2012:
> 
> Visual C++ 2010 Redistributable Package (x86):
> http://www.microsoft.com/en-us/download/details.aspx?id=5555
> 
> Visual C++ Redistributable for Visual Studio 2012 Update 4:
> http://www.microsoft.com/en-us/download/details.aspx?id=30679
> 
> Visual C++ Redistributable Packages for Visual Studio 2013:
> http://www.microsoft.com/en-us/download/details.aspx?id=40784
> 
> If this doesn't fix the issue please comment. If it does, I'd suggest to
> wait until 2.34 and hope this fixes it even without the redistributables.
> Otherwise we should check with the Seamonkey folks.

Just tested on the Windows 7 VM and this works for me. You tested on my Win 8.1 & Charles tested on WinXP - I'll bring up the Windows 10 VM and test there.
OK, if I understand correctly the problem is that both Thunderbird and Lightning are build with Visual C++ 2013 but SeaMonkey is still build with Visual C++ 2010. Therefore the SeaMonkey installer contains only the VS2010 (msvcp100.dll/msvcr100.dll) files but not the VS2013 (msvcp120.dll/msvcr120.dll) files. The SeaMonkey switch to VS2013 is tracked in Bug 1092468.
Works on Windows 10 Professional & Enterprise w/Visual C++ libraries installed. Thanks Philipp!
Thanks guys - and that explains why Lightning started working on this Win 8.1 machine - I checked the program installs & apparently another program that I installed installed the Visual C++ libraries for me. Mystery solved!
Many thanks to all of you, and special thanks to Philipp! 

In my case it was enough to just install the Visual C++ Redistributable Packages for Visual Studio 2013; SeaMonkey 2.33.1 and Lightning 3.8b2 are working again just as they did all the years before.

Time for another donation - said and done.
Thanks for confirming. I'm duping this against bug 1092468 then.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE

(In reply to Philipp Kewisch [:Fallen] from comment #45)
> Thanks to NoOp I've been able to debug this in a TeamViewer session. I'm
> fairly certain this is an issue with the Seamonkey build infra not linking
> with the right flags, but I do have a workaround:
> 
> Please install the following redistributable packages. I installed them in
> the order 2013 2010 2012 and it worked afterwards, it may be sufficient to
> just install 2012:
> 

Thanks Guys! this worked. I installed al three files, although I did get an error message that I already had an earlier version of the 2010 file already installed. It would be nice if someone could identify the latest version of that file.
> Visual C++ 2010 Redistributable Package (x86):
> http://www.microsoft.com/en-us/download/details.aspx?id=5555
> 
> Visual C++ Redistributable for Visual Studio 2012 Update 4:
> http://www.microsoft.com/en-us/download/details.aspx?id=30679
> 
> Visual C++ Redistributable Packages for Visual Studio 2013:
> http://www.microsoft.com/en-us/download/details.aspx?id=40784
> 
> If this doesn't fix the issue please comment. If it does, I'd suggest to
> wait until 2.34 and hope this fixes it even without the redistributables.
> Otherwise we should check with the Seamonkey folks.
@Philipp Kewisch:

My bug report was that: https://bugzilla.mozilla.org/show_bug.cgi?id=1131949  and MakeMyDay marked as duplicated of this one. For sure installing Visual Studio Packages won't help a lot in my Linux installation ;)
Sorry, this was errornously. I've reopened the other bug again.
Status: RESOLVED → REOPENED
Component: General → Lightning: SeaMonkey Integration
Depends on: 1092468
Resolution: DUPLICATE → ---
Summary: (Portable) SeaMonkey and Lightning 3.8b1/3.8b2 shows no events or tasks → (Portable) SeaMonkey 2.33 and Lightning 3.8b1/3.8b2 shows no events or tasks
John T. Haller from PortableApss.com found a way to add the necessary DLL files into a portable SeaMonkey installation. For future PortableApps SeaMonkey releases the VC++ 2013 DLL files will be included. Continue reading here: http://portableapps.com/node/43603
@Philip Chee: I'm pretty new to using bugzilla, so I have to apologize for not being able to follow the logic behind reopening this bug. The issue "SeaMonkey development switch to VS2013 environment" (bug 1092468) is not solved. OK. But the resulting problem (this bug) can be solved by integrating VC++ 2013 dll files. So this particular bug is solved, isn't it? So why reopening it?
@Carsten:
the comment 33 and 55 belongs to a system working on Linux, the last solution is a workaround for windows systems.
Comment 55 refers to a completely different problem, unrelated to this bug. In comment 56 you can read that bug 1131949 has been erroneously duplicated to this one.

Comment 33 refers to the same bug 1131949, which was finally solved by Philipp: "We discussed this via IRC, it was the noexec flag on the partition." Completely unrelated to this bug. Local system problem. And resolved.

So I still find it hard to understand why this particular bug should stay reopened.
Since this refers specifically to the Portable Apps version I agree this bug may be closed. However the Portable Apps people should not have to take this extra step themselves. Once we switch to VS2013 the correct DLLs will be packaged so PA will not need to do that.

Therefore I'm leaving this bug open until Bug 1092468 is fixed so that it doesn't disappear from my bug radar.
@Philip Chee: OK, these are thoughts I'm able to follow. Thanks for the clarification. From my point of view, this bug has a "worksforme" status. But his does not include the Mozilla's developer's perspective of "still some work to do to eliminate the possibility of bugs like this one" - i. e. completing the migration to VC++ 2013.
Some further information if someone uses Windows 7 64-bit (see post 9 by "smsmith" in the MozillaZine topic http://forums.mozillazine.org/viewtopic.php?f=40&t=2927825&sid=e627adfa61aa1fd6b0fb10a599b2e101 ):

It's necessary to install both the x86 and x64 versions of VS 2013 if there's any 32-bit software installed.

To help diagnosis, you get an "Information Message" in the Error Console when you open the tab for Lightning which contains the text "Failed to load native module at path xxx\extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103}\components\calbasecomps.dll : (80070057) error 126". The errors which occur later are caused by this.
log console show this message:
Horodatage : 27/04/2015 15:31:00
Erreur : TypeError: Components.classes[cid] is undefined
Fichier Source : resource://calendar/modules/calUtils.jsm -> file:///C:/Users/S227772/AppData/Roaming/Mozilla/SeaMonkey/Profiles/9qmuhwhp.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js
Ligne : 17

The pointed code place is this one (third line):
function _calIcalCreator(cid, iid) {
    return function(icalString) {
        let thing = Components.classes[cid].createInstance(iid);
        if (icalString) {
            thing.icalString = icalString;
        }
        return thing;
    };
}
Status: REOPENED → NEW
Component: Lightning: SeaMonkey Integration → Calendar
Product: Calendar → SeaMonkey
Version: Lightning 3.8 → SeaMonkey 2.33 Branch

Lets put this one to rest. Lightning is now bundled with SeaMonkey. The binary components are integrated. Default is to build with calendar enabled. If someone chooses to disable this bad things will happen and Lightning will never work with this version.

Status: NEW → RESOLVED
Closed: 9 years ago → 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.