OS/2, eCS & ArcaOS - Technical > Internet
Firefox - 45.9.0 for OS/2 GA1.1...anyone...anyone???
Joop:
--- Quote from: Dave Yeo on August 06, 2018, 12:49:27 am ---
--- Quote from: Joop on August 05, 2018, 09:31:38 pm ---
--- Quote from: Dave Yeo on August 05, 2018, 06:24:52 pm ---
--- Quote from: Joop on August 05, 2018, 01:41:26 pm ---Too bad that the focus is n longer on Firefox 45.9.0. It still not running on my system due to libc problems, and as far as I can read, I'm not alone with this problem.
--- End quote ---
What are the symptoms?
--- End quote ---
There is trouble with LIBC.
Exception C0000005 - Access Violation
Process: FIREFOX.EXE (05/21/2018 17:17:07 51,129)
PID: 48 (72)
TID: 01 (1)
Priority: 200
Filename: LIBC066.DLL (10/26/2014 20:16:29 1,361,666)
...
--- End quote ---
I have here,
libc066.dll │ 1361663│19/01/18│ 8:10a
which appears to be 4 years newer and 3 bytes smaller then yours. Is Firefox picking up a different version of libc somewhere or is exceptq screwing up in the libc it is finding?
Look at the bottom of your trp file, there should be a listing of "DLLs accessible from this process" and verify that the correct DLLs are found.
--- End quote ---
That's weird, I have the latest libc, only in zip package (libc-0.6.6-csd6.zip). At the bottom of the trp is a very long list of dll's. I will overview it again against the list from mozsupport-2018-05-05.zip.
Andy Willis:
--- Quote from: Joop on August 11, 2018, 06:23:19 pm ---That's weird, I have the latest libc, only in zip package (libc-0.6.6-csd6.zip). At the bottom of the trp is a very long list of dll's. I will overview it again against the list from mozsupport-2018-05-05.zip.
--- End quote ---
This would be the latest libc in zip:
http://rpm.netlabs.org/release/00/zip/libc-0_6_6-37_oc00.zip
André Heldoorn:
Is there a specific reason why SM can import (or auto-update) NoScript 5.1.8.7, but FF cannot? Its minimal required FF version is 45.0, and 5.1.8.6 works with FF.
Dave Yeo:
I've had problems auto updating some extensions with SM, haven't tried much with FF.
Hmm, looking right now, I'm still on NoScript-5.1.8.4 (both SM and FF) and the newest I see is 5.1.8.3 on AMO.
Hmm going to noscript.net, with Firefox (SM is using the AMO for SM extension) I do see 5.1.8.7 along with this tidbit,
--- Quote --- Notice: you may need to open about:config and set your xpinstall.signatures.required preference to false in order to install, since Mozilla doesn't support signatures for legacy add-ons anymore.
--- End quote ---
And doing that allowed me to update it in FF.
Note that soon Mozilla will be removing all classic extensions, which will be a bummer.
edit, note that SM doesn't require signed add-ons so isn't a problem. Both SM and FF are now updated. Probably going to have to do it manually from now on and eventually support will be dropped for our out of date browsers.
André Heldoorn:
--- Quote from: Dave Yeo on September 11, 2018, 08:44:12 am ---I do see 5.1.8.7 along with this tidbit,
--- Quote --- Notice: you may need to open about:config and set your xpinstall.signatures.required preference to false in order to install, since Mozilla doesn't support signatures for legacy add-ons anymore.
--- End quote ---
And doing that allowed me to update it in FF.
--- End quote ---
Thanks, the overlooked FF setting works here too. I'm used to manual updates, if anything to check what the latest old version is. This time SM updated itself, but 5.1.8.7 is the first version which required changing this FF setting. And perhaps the last versoin, albeit september 2018 is a changed end-of-service date for our FF/SM. IIRC this date was june or july.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version