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.
I believe that's the time to jump ASAP to kernel 5.19.16 on -current and 5.15.74 on stable v15.0 because they fixes 5 (five) really nasty CVEs on WiFi management.
As an aside 5.19.16 will work as well on 15.0. Dunno if using a non-LTS kernel is acceptable in Slackware stable though.
Last edited by Didier Spaier; 10-15-2022 at 07:28 AM.
I believe that's the time to jump ASAP to kernel 5.19.16 on -current and 5.15.74 on stable v15.0 because they fixes 5 (five) really nasty CVEs on WiFi management.
Thanks you!
time to jump ... when kernels are released only some hours back...
The real jump is go to 6.0 on -current , thats a jump , -current offers ever all kernels in same branch , no need to request that.
BUT there is no thread for requests for -stable and I for one I will NOT open one like this, because half of this forum will jump in to argue with me how perfect is Slackware 15.0 and how absurd is from a philosophical, ethical and practical POV to have requests for -stable.
Last edited by LuckyCyborg; 10-15-2022 at 03:13 PM.
BUT there is no thread for requests for -stable and I for one I will NOT open one like this, because half of this forum will jump in to argue with me how perfect is Slackware 15.0 and how absurd is from a philosophical, ethical and practical POV to have requests for -stable.
While it’s still missing the long-anticipated two-finger swipe horizontal gesture for navigating
back and forward on a website without having to hold down the Alt key, the Mozilla Firefox 106
release is here to introduce annotation capabilities in the built-in PDF viewer that let you write
text, draw, or add signatures to PDF files.
This release adds a week's worth of new translations and fixes from KDE's contributors.
The bugfixes are typically small but important and include:
- Fuzzy-clock: Fix colors in full representation (calendar view). Commit.
- Colorpicker: Make left-clicking a color copy in the default format. Commit. Fixes bug #457311
- Plasma Audio Volume Control: Don’t crash when the server doesn’t respond. Commit. Fixes bug #454647. Fixes bug #437272
For the xap/libnma package can we add the following meson build option?
Code:
-Dlibnma_gtk4=true
GTK4 is already included so this can be enabled to build the libnma-gtk4 library without any other requirements. It increases the libnma package size from 284K to 326K.
Here's the detail from the meson_options.txt
Code:
option('libnma_gtk4', type: 'boolean', value: false, description: 'build library libnma-gtk4 for use with GTK4')
I'm asking because its a dependency to build newer versions gnome-control-center, which is an SBo package I maintain and would like to be able to update in future releases of Slackware.
Looking at the commits, it seems to be the upstreaming of the patches debian have been using, along with a few build/tools related changes, so not much in the way of actual development of the window manager itself. As you say, that's going on in fvwm3 (which, to my shame, I haven't gotten around to trying yet).
Also note that while release/2.7.0 branch has been created and tagged 2.7.0, they haven't as yet created a "Release" on github — the latest is still 2.6.9 in the Github Web UI — so one needs to go looking for the branch or tag directly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.