SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Grabbed the SRC from kernel.org and it is now compiling using /boot/config-huge-6.1.55.x64
WOW... I did not keep count but there are a TON of new options all of which I simply chose the default.
Thats the reason i prefer wait for a "official config" , some time back i do exactly the same ... and select default options on new config things ... but now i prefer wait for official configs.
ap/sc was supposed to be removed and replaced by ap/sc-im in Slackware.15.0 according to CHANGES_AND_HINTS. However, sc is still included in 15.0 and current.
PS. Small nitpick: in CHANGES_AND_HINTS for 15.0 I read that n/openssl10 has been removed. Actually there was no such package and openssl has been upgraded from 14.2 to 15.0
Last edited by Didier Spaier; 10-09-2023 at 04:33 PM.
Reason: PS added.
This release contains a critical stability/minor security update which affects
Electron applications that utilize Portal notifications (eg, through Flatpak).
It is highly recommended that all users of libnotify 0.8.x update to this
release.
Please note that this fix has increased the minimum required version of glib to
2.62.0.
* notification: Use g_signal_connect_object (#34) [Maximiliano]
* notification: Move disconnect to dispose [Maximiliano]
ap/sc was supposed to be removed and replaced by ap/sc-im in Slackware.15.0 according to CHANGES_AND_HINTS. However, sc is still included in 15.0 and current.
Actually, it was removed and then brought back. The mistake was declaring its removal in CHANGES_AND_HINTS and then not correcting it after the package was brought back.
Quote:
PS. Small nitpick: in CHANGES_AND_HINTS for 15.0 I read that n/openssl10 has been removed. Actually there was no such package and openssl has been upgraded from 14.2 to 15.0
The package existed during the -current development cycle after 14.2. My opinion is that it's better to mention such things rather than pretend they never happened.
Mon Oct 9 18:10:01 UTC 2023
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
# #
# Effective January 1, 2024, security patches will no longer be #
# provided for the following versions of Slackware (which will all #
# be more than 7 years old at that time): #
# Slackware 14.0, Slackware 14.1, Slackware 14.2. #
# If you are still running these versions you should consider #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own #
# security patches. #
####################################################################
That's a hell of a long life cycle.
14.0 2012-09-28
14.1 2013-11-04
14.2 2016-06-30
https://bugs.archlinux.org/task/79292 Looks like glibc 2.38 breaks EAC again. (I don't have any games using it, so can't verify, nor am I on glibc 2.38.) I seem to recall the same issue causing problems with electron apps, as well.
I haven't noticed any issues with electron apps (Discord, VSCodium, poddr) that I didn't have before. I can't speak to EAC, since I don't play games with them, but so far no issues with glibc 2.38.
I think these might be nice options to have for mesa if they allow it to compile (haven't tried compiling it myself):
Code:
-Ddri3=enabled
-Dexpat=enabled
-Dgbm=enabled
I believe that all these options are properly auto-detected.
The DRI3 and GBM are what the modern graphic drivers uses, and without them, the Wayland/Plasma5 will not work at all on a barely modern graphics card. So, they are here, in my humble opinion.
Regarding EXPAT, it is used for interpreting the XML files. Like is the famous /etc/drirc and its ~/.drirc counterparts. Honestly, I have never heard the Mesa having issues with these config files, so I bet that EXPAT is properly integrated.
Last edited by LuckyCyborg; 10-12-2023 at 04:41 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.