SeaMonkey 2.49.2 is on the way
25 posts
• Page 1 of 2 • 1, 2
Real life did cause a delay but building has finally started:
https://blog.seamonkey-project.org/2018 ... -49-2-and/ Progress seems to be good and the candidates seem to work fine. https://archive.mozilla.org/pub/seamonk ... andidates/ ewong hope to get updates working but due to the nature of the beast we will see if this is the case when the release is done. If you want to try a candidate please backup your profile before installing. FRG
![]() ![]() How to Ask Questions The Smart Way - How to Report Bugs Effectively
![]() Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20180711 SeaMonkey/2.49.4 Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20170619 SeaMonkey/2.51
![]() Cheers! ![]() How to Ask Questions The Smart Way - How to Report Bugs Effectively
![]() Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20180711 SeaMonkey/2.49.4 Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20170619 SeaMonkey/2.51 Thanks so much!
Are the Composer insertion, copy/paste, etc. capabilities that were a problem with 2.49.1 fixed in 2.49.2? I was advised to wait until 2.49.2 when the fix should be operable. . . . . . . . . . . Pete
How to Ask Questions The Smart Way - How to Report Bugs Effectively
![]() Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20180711 SeaMonkey/2.49.4 Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20170619 SeaMonkey/2.51 Working for me as well so far, lightning calendar too, no update required
I was getting lots of script errors using 2.49.1 when viewing pages from reuters and these seem to be cured on 2.49.2 https://www.reuters.com/ FYI, I tried build 1, everything worked perfectly except for one niggling problem. Had to minimize browser to see messaging windows. Not a clue why. Did not install into program folder, instead extracted entire SeaMonkey subfolders into app/Seamonkey folder (I use Portable SeaMonkey). About confirmed that I had 2.49.2 installed at that point.
Have reverted to 2.49.1 for now... will try again when official or next build comes out. -N-
Early Blue Theme, Dell D420, XP PRO SP3, Registry Hack, AvastFree, MalwareBytesPro and Scotty is on Patrol Dulce bellum inexpertis This is probably the release version. ewong is in the verification stage now and I doubt a build 2 is needed. And even then nothing would change in the source.
Might be an extension problem. Also there is some tightend security. Try setting layout.css.moz-document.content.enabled to true if you use stylish or user css which uses moz-document See Bug 1035091. ![]()
I do hope not, it's crashing every few hours here. Including, ironically, just now as I hit the Help> Trouble Shoot menu entry to get the Build ID for this post! - 20180205032537 Obviously, as always, this may turn out to be something at my end so people shouldn't take this as a universal given with this build. Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.) > I do hope not, it's crashing every few hours here.
Do you have a crash id? Symbols are probably not yet up but maybe I find something. So far this is rock solid for me but I am not using mail in this release. For this I use a 2.53 in a vm. ![]()
Random selection. Sometimes crashes are not sending reports as well. *Edited out crash reports* There's no obvious pattern and the bug reports seem to nearly (always?) have a different reason each time. For the time being I've gone back to 2.49.1, but when stuff is less important to get done, I'll put 2.49.2 back on and continue to wade through/disable my few extensions to try to see if the perp is at my end. Last edited by Frank Lion on February 10th, 2018, 5:29 am, edited 1 time in total.
Metal Lion latest SeaMonkey & Thunderbird Themes - Sea Monkey and Silver Sea Monkey
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.) SM 2.29.2 installed and working fine on Mac w/El Capitan 10.11.6.
Frank, I looked at the crashes and they are all over the place. A guess would be old Nvidia driver or some problem in Spidermonkey or core. There were some changes in the source but nothing points out.
Same here: https://crash-stats.mozilla.com/topcras ... ion=2.49.2 So far looks like a "normal" release. Ewong is still in the "post-processing" validation phase:
https://bugzilla.mozilla.org/show_bug.cgi?id=1402214
25 posts
Page 1 of 2 • 1, 2
Who is onlineUsers browsing this forum: No registered users and 6 guests |
![]() |