![]() ![]() So that was a bit more of a clue which led me to this discussion. Libgtk-3.so.0: cannot open shared object file: No such file or directory XPCOMGlueLoad error for file /usr/lib/seamonkey/libmozgtk.so: On a different PC, also running 64-bit LinuxMint 18.3, I was able to start up 2.46 SM as usual under the root Id, and perform the update, but then got a bit more informative error: That was giving vague messages like "./seamonkey file not found", which left me wondering why the command could not find the file the command named (seamonkey) even though it was in my pwd, and worked on the old disk drive with the same software and ini files. I have been going round and round with this issue the last 2 days on 2 different PC's with 64-bit Linuxmint 18.3, one a new build that would not run the Seamonkey 2.48 I copied over from an older disk (whole home dir for main personal Id) that was running same 64-bit LinuxMint 18.3. what's the prerequisites of making the Linu圆4 builds 'official' aside for the issue of getting the tests done for Linu圆4 but our testing infrastructure is busted.Maybe change the online documentation? (perhaps as part of bug 1208822 "System Requirements page needs update"?).How are we going to get out of the following vicious circle? 64-bit builds are not "official" because too few users, and users don't install them (some even prefer compiling their own) because they aren't "official".I pointed them to the x86_64 release at the bottom of the "Other languages" release page for 2.38 and to the x86_64 2.40a2 aurora & 2.41a1 trunk builds at the bottom of the ftp.m.o nightly/latest-comm-* pages but they said these were not "official". On October 7 two people asked in #seamonkey at a few minutes' interval when there would be "official" 64-bit SM builds for Linux.What about declaring linux-x86_64 builds found at and at ftp.m.o as "official" ? - Tonymec (talk) 13:56, 7 October 2015 (PDT) SM 2.35 was delayed, no 2.36 and 2.37, there is 2.38, 2.39 and 2.40 but no releases since as it has basically missed three major Releases. The SeaMonkey community is struggling to get new Releases out as is due to building, machines and infrastructure issues. Besides many Linux distros provide 64-bit SeaMonkey packages for SM 2.40. The 64-bit Linux version is only as en-US and no other languages and is not really official even though it is built on same machines as I said. The 64-bit build is on the page I mentioned yes. So I repeat my original question, why don't they have a 64-bit version readily and easily and obviously available? Why wouldn't they have included the 64-bit as well as the 32-bit version?įollow-up: I looked more carefully, and if you dig around you can find the 64-bit version, but it's under the heading "Contributed builds (other platforms)", and to a relative newcomer such as myself, I would never have thought to look here, having trusted that the Linux download link provided by the website at the top of the page was correct. deb archive files at sourceforge.Gracious1 wrote:I downloaded the tarball available at the SeaMonkey Project site. sudo apt-get install seamonkey-mozilla-build sudo apt-key adv -recv-keys -keyserver 2667CA5C Sources List sudo nano /etc/apt/sources.list The latest stable release is SeaMonkey 2.46 at the time of this writing."įollowing the instructions here, I ended up with a working version of SeaMonkey 2.53.1 that gets installed with apt and is launched properly from the main menu system. SeaMonkey, formerly known as Mozilla Suite, is an open-source, community-driven Internet application suite. ![]() "This tutorial will be showing you how to install SeaMonkey on Ubuntu 16.04. ![]() The version of The Mozilla browser that I have just installed on my Debian based Zorin computer is called seamonkey-mozilla-build
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |