Can you, would you, clarify please? What sort of software "not specifically compiled for Slackware" did you try?

More updates arrive today ..read changelog

http://www.slackware.com/changelog/current.php?cpu=i386

I ran into dependency hell trying to get to get KiCad running. There was a slackbuild script but it needed some library that I could never track down a package for. Trying to compile that library needed more libraries and things went poorly from there. KiCad has a flatpack container but again dependency hell in trying to find someone who has flatpack binaries for slackware. In the end I did finally get flatpack up and running with sbo scripts but come on the effort required isn’t worth my time.

I did get VMware up and running although its unsupported on Slackware. The VM consumed lots of idle cpu and would get laggy.

1 members found this post helpful.

No it was current and then I made the mistake of updating everything and then it stopped playing. Someone else here confirmed they had the same problem. As of two weeks ago current was still broken in that regard.

Thank you, epitaxial, for explaining your problems with KICad. I strongly suspect that will be solved when Slackware 15 is released and Slackbuilds puts 14.2 in the back seat. There may be others here that have some familiarity with KICad that can help sooner but I get your point. In the past I've had a bit of extra work trying to get a good Electronic Schematics drag 'n drop template working just right, but for me it was just finding which one of many worked the best and was the easiest to support. It's still worth it to me that my base system, Slackware, is sacrosanct, and stays stable and solid.

NOTE: In my case the difficulty was increased by my requiring good vacuum tube support.

1 members found this post helpful.

Using KDE Plasma DE, zoom-linux freezes and crashes. zoom error log states:

zoom-linux was working fine until 3/10 slackpkg upgrade-all

I tried to use system-settings to not change opacity when moving windows, but no effect (I don't know if I did it right).

I'm going to try xfce

1 members found this post helpful.

I used zoom-client this morning on my laptop for a meeting. No issues. The laptop is at Sun Mar 7 20:32:09 UTC 2021 ChangeLog.txt with zoom-client-5.5.7011.0206.

I am upgraded that laptop now to the Sat Mar 13 05:37:56 UTC 2021 ChangeLog.txt to test.

I tested with this desktop which is at Fri Mar 12 01:46:50 UTC 2021 ChangeLog.txt, everything works okay.

This is with KDE Plasma

1 members found this post helpful.

How do you get the link to the specific message?
With KDE Plasma as of March 11 or 12, when I made changes using the system settings the desktop turned black and I could see trails of the mouse pointer. I was somehow able to exit (don't remember steps) and restart. I did not get back to the console because I had switched to graphical login in /etc/inittab to avoid the the kwallet popup. There is probably some key combination to do that, but I don't know it.

I changed to xfce with xwmconfig and then started zoom-linux. It immediately showed a crash report popup, but then started and worked fine. I was running kernel 5.10.15, but yesterday switched to 5.11.6. I started xfce and zoom-linux this morning and it worked.

I have zoom-linux-5.5.7938.0228-x86_64-1_SBo because I downloaded the client from zoom.us and used that tarball in the Sbo slackbuild.

Nvidia driver for my GT-710: nvidia-driver-460.39-x86_64-1_SBo

I used to use fluxbox, but zoom-client said it needed a compositor, so I switched to xfce and then to KDE. Now back to xfce. I was generally pleased with KDE Plasma, but it has issues.

What message are you referring to.

My laptop is up to date now Sat Mar 13 05:37:56 UTC 2021 ChangeLOg.txt, zoom is working fine. I am also on the 5.11.6 kernel on both computers.

I created my own SlackBuild for the zoom-client. Just upgraded to 5.5.7938.0228. I normally update before a scheduled meeting, the one this morning was short notice.

"Originally Posted by <name> View Post"

Perhaps your slackbuild is better than mine. As I said, all I did was use the recent zoom download tarball in the SBo zoom-linux.tar.gz package.

Also, I have had this computer for years and might have some things in .kde and .config that cause problems. Furthermore, I do not know all the subtleties of keeping up to date with slackpkg. I do not want to run "slackpkg clean-system" because I have a lot of "ponce" packages. slackpkg install-new says: "No packages match ..."

I am still on xfce. I'll try KDE again later.

Thanks

I compared my SlackBuild to the one on SBo, the only real differences is I place zoom in /usr/lib64/ not in /opt/.

This is a possibility, but I doubt it would affect zoom. The Slackware install on this computer is probably 15 years or so old from the first time it was installed. It has been on two previous computers before this one and many, many updates over the years.

Running "slackpkg clean-system" is an important part of keeping up to date with slackpkg, it removes old, obsolete packages that are no longer part of Slackware and yes, good third party packages too since they are not part of Slackware. This is what /etc/slackpkg/blacklist is for. You should put third party packages like those from "ponce" in /etc/slackpkg/blacklist. Then running "slackpkg clean-system" will only remove all other packages that are not or no longer part of Slackware. "slackpkg clean-system" gives you a chance to back out if there are packages listed that you don't want to remove.

To add ponce's packages to blacklist add "[0-9]+ponce" without the quotes to blacklist.

"slackpkg install-new" only searches for "Added" packages in ChangeLog.txt. Once those packages have been added to the system, they no long show up, unless you remove them for some reason.

slackpkg only handles Slackware packages. If you have a lot of third party packages, your should look in to adding slackpkg+ to the mix. The combination of slackgpkg with slackpkg+ make management of slackware with third party packages installed a breeze.

I've been guessing that you are using -current.

I prefer to not use the blacklist to retain third party packages. A lot of third party packages from SlackBuild.org/Ponce depend on underlying libraries supplied by Slackware which aren't included in the Requires section of the .info section. In Current with it's high churn rate I find it necessary to recompile all my SlackBuild.org/Ponce packages to keep them in sync with latest Current libraries, "slackpkg clean-system" without a blacklist removes them all so I can start with a clean system on which to recompile my enables me recompile all my SlackBuild.org/Ponce packages.

I'm sure readers will have other strategies that work for them

I cannot imagine doing that with the 358 third party packages I have installed. Not all of these need to be recompiled. I have been using -current for years. I don't blacklist them anyway as I use slackpkg with slackpkg+ to manage this.

1 members found this post helpful.