SeaMonkey Internet Suite

Unofficial News in English language

Leave a comment

Add-On “PrefBar” crashes SeaMonkey 2.52 ⚠️️

One of my favorite add-ons crashes latest SeaMonkey Trunk-Builds like

UNofficial (by FRG) en-US SeaMonkey 2.52a1 (NT 6.1; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 Build 20170513191754 (Default Classic Theme) on German WIN7 64bit

When I launch SeaMonkey it crashes immediately if PrefBar add-on is active.

The problem is not Win64; x64 related.


Can someone confirm the problem❔

Any theory concerning the roots of the problem❔



SeaMonkey Project – calling for volunteers

Blogpost in englischer SpracheThe SeaMonkey project is entirely driven by volunteers, and we will need some  more of them, as FRG (Frank-Rainer Grahl)  told on mozillazine.

With some HTML and XHTML knowledge (and some endurance, of course)  for example you can do substantial contribution to SeaMonkey Help. Also required: Translation to other languages than English for Help-chapters, Add-Ons, Wiki-pages

Don’t be shy, leave a comment how we can reach you and where you see your skills for contribution.

Leave a comment

Bug 1329724 – Empty lines in email body disappear

Zur Mozilla-Bugzilla HomepageBased on postings in (“[SM 2.46] Leerzeilen verschwinden beim Antworten”) I reported Bug 1329724 – Empty lines in email body disappear, but until now it seems nobody was able to reproduce the problem with the steps from bug report.

I did tests on mozilla.test with Server-Installations of unofficial (by FRG) en-US SeaMonkey 2.50a1 (NT 6.1; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 Build 20170108183322 (Default Classic Theme) on German WIN7 64bit (Re: Empty lines disappear, Rainer Bielefeld 06:08 +0100, Message-ID: <>, and the issue was still reproducible.

It would be great if someone else could reproduce the problem with the Steps To Reproduce from my report.

And, of course, it also would be great if you find other reliable ways how to provoke disappearing empty lines in replies; please submit additional separate Bugs if you are not sure that the problem you observe is exactly the same.

1 Comment

New unofficial 2.49 localized nightly SeaMonkey builds available for download

This blog post in German languageAdrian Kalla again contributed lots of unofficial English and localized installers and language packs in various languages for WINDOWS and Linux:

Dates for the folders are wrong. In fact folder contents is 2016-10-26, 2016-10-27

latest-comm-central-linux32/ 2016-09-23
latest-comm-central-linux64/ 2016-09-23
latest-comm-central-windows32/ 2016-09-24
latest-comm-central-windows64/ 2016-09-24

Additional builds with date 2016-10-16 / 2016-10-17 available:



Continue reading

Leave a comment

Mac is back (new official Trunk builds)

This blog post in German languageAfter a while of waiting we now have new SeaMonkey Trunk  builds for MAC

Be careful! These builds are for testing purposes only. Keep backups of your data, some of the code you’re testing might not have been tested at all before and might cause unexpected problems. If you encounter any such problems, please report bugs for them.

Continue reading

Leave a comment


Zur Mozilla-Bugzilla Homepage I still report new bugs I find with status UNCONFIRMED, even if (after careful investigation) I am pretty sure that the report is concerning a real bug and complete enough so that a developer can take on. Reason is that I believe in the two-man rule. Often a review by an other user adds information, may be concerning additionally affected Operating System or an aspect of the problem not yet mentioned or something else. But in the SeaMonkey project, due to very limit “human QA resources” and the lack of interest of most SeaMonkey users to contribute to the project, the bug review process  is horrible slow, even Bug reports what can be reproduced easily do not find a user who is willing to do a test whether he can reproduce the problem.

SeaMonkey needs you

So in future I myself will change bug status to NEW after 2 weeks (or so) of waiting if I think that all requirements for starting bug fixing process are fulfilled and nobody confirmed the bug. But, of course, it would be great if YOUR help would make superfluous this proceeding with my own “confirmation”. Be courageous and grasp the nettle of confirming some [easyconfirm] bugs.