Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I tried installing it like the 32bit version. Working on getting wifi to work so I'll be able to remotely work on it. Need to work out all the kinks. Wicd-curses didn't work properly.
Thanks for Slarm64, I really enjoy this distro, I use it as my daily driver on a Pinebook. Anyway...
Is anyone else having issues with Seamonkey lately? When I try to run it, I get this:
Code:
bash-5.0$ seamonkey
XPCOMGlueLoad error for file /usr/lib64/seamonkey-2.49.5/libxul.so:
libicui18n.so.64: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
I get no such error on my x86_64 -current machine, just FYI. I have tried reinstalling to no avail. Thanks in advance.
thanks for the information.
yes there is one, seamonkey is linked to system libraries, set to rebuild, in the morning there will be an updated package.
Great to hear, I will be looking forward to the update. I have been wanting to use Seamonkey more often, so this is good news to my eyes.
FWIW, I host a public mirror for Slarm64, and plan to for the foreseeable future. People can use this as a US-based alternative if they like. I believe the physical server lives in Phoenix, AZ. This syncs three times per day from http://mirrors.slackware.bg/slarm64/...rrent/slarm64/ (because sometimes the sync is incomplete), so it is relatively current.
Interesting, I will try to figure out why that file is not visible. Inspecting via FTP shows that the file is present, but maybe something in .htaccess is preventing it from being seen. I will look into this, thanks for bringing it to my attention.
After a support ticket was filed with the hosting provider to determine why that file is not visible on the server, they confessed that it is a security setting on their side that cannot be changed that makes all README* files invisible from a browser, even when the file is present on the server and can be accessed directly, as above.
A bit of cron job trial and error lead to a command that creates a copy with underscores appended to each end of the filename, which makes it visible from the browser.
So now there are two versions of each README* file on the server, the unmodified original, and the same file with a slight name change that allows one to see it in the browser.
Thanks for pointing that out, I hadn't noticed yet.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
