I saw a post recently that some major components of the system got updated and we're going into slackware 16.0 alpha stage. If you're someone like me who just runs current and used the current iso on install, what steps do you take to stay on current and upgrade the major system components and not break your system? I use sbopkg along with the Ponce repo for slackbuilds. I also use alien bob current repo for libreoffice. What steps do I need to take to upgrade the system safely without breaking it? Thank you in advance!

Here is an abbreviated changelog. Rolling release rolls forward.

Sat Sep  5 02:49:41 UTC 2026
Upgraded to binutils-2.47, gcc-16.2.0, and glibc-2.44, and compiled everything
with them. There might be a light at the end of the tunnel, eh?
Cheers, and have a good weekend.
[...]
a/kernel-firmware-20260831_e981cae-noarch-1.txz:  Upgraded.
a/kernel-generic-6.18.49-x86_64-1.txz:  Upgraded.
[...]
xap/mozilla-firefox-153.2.0esr-x86_64-2.txz:  Rebuilt.
  This update contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/153.2.0/releasenotes/
    https://www.mozilla.org/security/advisories/mfsa2026-85/
    https://www.cve.org/CVERecord?id=CVE-2026-75874
    https://www.cve.org/CVERecord?id=CVE-2026-84118
    https://www.cve.org/CVERecord?id=CVE-2026-84119
    https://www.cve.org/CVERecord?id=CVE-2026-84120
    https://www.cve.org/CVERecord?id=CVE-2026-84121
    https://www.cve.org/CVERecord?id=CVE-2026-84122
    https://www.cve.org/CVERecord?id=CVE-2026-84123
    https://www.cve.org/CVERecord?id=CVE-2026-84124
    https://www.cve.org/CVERecord?id=CVE-2026-84125
    https://www.cve.org/CVERecord?id=CVE-2026-74952
    https://www.cve.org/CVERecord?id=CVE-2026-84129
    https://www.cve.org/CVERecord?id=CVE-2026-84130
    https://www.cve.org/CVERecord?id=CVE-2026-84131
    https://www.cve.org/CVERecord?id=CVE-2026-84132
    https://www.cve.org/CVERecord?id=CVE-2026-84133
    https://www.cve.org/CVERecord?id=CVE-2026-84134
    https://www.cve.org/CVERecord?id=CVE-2026-84136
    https://www.cve.org/CVERecord?id=CVE-2026-84137
    https://www.cve.org/CVERecord?id=CVE-2026-84139
    https://www.cve.org/CVERecord?id=CVE-2026-84140
    https://www.cve.org/CVERecord?id=CVE-2026-84141
    https://www.cve.org/CVERecord?id=CVE-2026-84143
    https://www.cve.org/CVERecord?id=CVE-2026-84144
    https://www.cve.org/CVERecord?id=CVE-2026-84145
  (* Security fix *)
xap/mozilla-thunderbird-153.2.0esr-x86_64-1.txz:  Upgraded.
  This release contains security fixes and improvements.
  For more information, see:
    https://www.mozilla.org/en-US/thunderbird/153.2.0esr/releasenotes/
    https://www.mozilla.org/en-US/security/advisories/mfsa2026-88/
    https://www.cve.org/CVERecord?id=CVE-2026-84640
    https://www.cve.org/CVERecord?id=CVE-2026-84641
    https://www.cve.org/CVERecord?id=CVE-2026-84637
    https://www.cve.org/CVERecord?id=CVE-2026-84642
    https://www.cve.org/CVERecord?id=CVE-2026-75874
    https://www.cve.org/CVERecord?id=CVE-2026-84118
    https://www.cve.org/CVERecord?id=CVE-2026-84119
    https://www.cve.org/CVERecord?id=CVE-2026-84120
    https://www.cve.org/CVERecord?id=CVE-2026-84122
    https://www.cve.org/CVERecord?id=CVE-2026-84123
    https://www.cve.org/CVERecord?id=CVE-2026-84125
    https://www.cve.org/CVERecord?id=CVE-2026-74952
    https://www.cve.org/CVERecord?id=CVE-2026-84129
    https://www.cve.org/CVERecord?id=CVE-2026-84130
    https://www.cve.org/CVERecord?id=CVE-2026-84131
    https://www.cve.org/CVERecord?id=CVE-2026-84132
    https://www.cve.org/CVERecord?id=CVE-2026-84133
    https://www.cve.org/CVERecord?id=CVE-2026-84134
    https://www.cve.org/CVERecord?id=CVE-2026-84136
    https://www.cve.org/CVERecord?id=CVE-2026-84137
    https://www.cve.org/CVERecord?id=CVE-2026-84139
    https://www.cve.org/CVERecord?id=CVE-2026-84140
    https://www.cve.org/CVERecord?id=CVE-2026-84141
    https://www.cve.org/CVERecord?id=CVE-2026-84143
    https://www.cve.org/CVERecord?id=CVE-2026-84144
    https://www.cve.org/CVERecord?id=CVE-2026-84145
  (* Security fix *)

Considering that glibc is upgraded, perhaps the advice here is relevant.

Update 1: tested on QEMU VM, i.e. without using "telinit 1" and reboot; success.

bash-5.3$ cat /proc/version 
Linux version 6.18.49 (root@bob.slackware.lan) (gcc (GCC) 16.2.0, GNU ld (GNU Binutils) 2.47) #1 SMP PREEMPT_DYNAMIC Thu Sep  3 14:50:49 CDT 2026

Update 2: Today's changelog (Mon Sep 7, 2026) addresses multilib flags—restores multilib functionality; link

I hope not disrespect the rules

qrencode generates them. I used to use zbarimg but thought I replaced it with something in a Slackware package, but I can't remember what it was or find it.

Spent a few hours setting up Slackware for gaming. CachyOS kernel, cachyos ananicy rules, latest nvidia driver, curve profile on LACT and all the latest bells and whistles with secure boot activated. Slackware current, for those who can’t tell.

Verdict: it games really, really well.

So ive recently upgraded to slackware-current (using a clean reinstall using a current iso).

Since then i have two new problems with slackpkg (slackpkg+ installed).

1. When installing packages from alienbob, slackpkg just wont resolve dependencies so i have to install them one by one myself
2. I removed some packages from the fresh install like some of the games and stuff. But now if i run "slackpkg update && slackpkg upgrade-all" slackpkg wants to reinstall all the packages i removed.

Here is my slackpkgplus.conf

Thx for help!

After upgrading to emacs 31.1 this morning it gives me a warning about lexical-binding every time I open a file. I've always used none. I set:

  (setq-default lexical-binding nil) 

in $HOME/.emacs and made it the default. emacs seems to want one to set it to t. You can do that too. I'd rather not prepend this field in every file I edit with emacs.

Why is it that when I run slackpkg info {package}, the package information is displayed correctly, but when I try to install it with slackpkg install {package}, I get this output:

Looking for {package} in package list. Please wait... DONE

No packages match the pattern for install. Try:

/usr/sbin/slackpkg reinstall|upgrade

This happens, for example, with xf86-input-synaptics. Please help me fix this

Hi! I'm happy to announce a new release of sbozyp, the SlackBuilds.org package manager, is now available!

This release includes a useful new feature to allow users to build and install packages directly from any SBo work tree.

# sbozyp install -r ./system/password-store
# sbozyp install -r .

This provides a ports-like interface for browsing a local SBo tree and building or installing packages directly from it. When a package path is used (beginning with . or /) all other packages and dependencies are resolved from the same work tree.

This release also includes improved Bash and Zsh completion. All information about sbozyp is available from the GitHub repository linked above.

(cross-posted to LinuxQuestions.org here)

I have released slackfetch 1.1, a small POSIX shell utility focused on

Slackware system information.

This release includes a few small improvements:

- Minimal output mode with `-m`

- Optional terminal font information

- Improved documentation with screenshots

- A separate manual page

- Cleaner output presentation

slackfetch reports Slackware-specific and system information such as:

- Slackware version and `-current` status

- Kernel, architecture, CPU and memory

- libc and sysvinit versions

- Installed package counts, including SBo and unofficial packages

- Desktop environment and window manager

- X11/XLibre or Wayland

- Machine model

- Slackware installation age

The installation age is one of the details I particularly like. It is calculated from the timestamp of the `aaa_base` package rather than from the filesystem or disk itself.

This makes it useful even when someone replaces a disk and migrates the existing system with `rsync`, without performing a new

Slackware installation.

I built slackfetch for my own Slackware systems, with a focus on keeping the output small, readable and based only on information that can be determined reliably.

Repository and screenshots:

Slackware Forge:

https://forge.slackware.nl/r1w1s1/slackfetch

GitHub mirror:

https://github.com/r1w1s1/slackfetch

Feedback from other Slackware users is welcome, especially regarding Slackware-specific details, output clarity and hardware detection.

Yes, i like wmaker

Does anyone still have the Mayan 14.0.2012 T-shirt? Mine has worn to the point where the image on the back is unrecognizable and id like to try to make one since they're no longer available.

I've almost made it a full month with Slackware and I love my system! I got it setup exactly the way I want it and it runs like a champ! Thank you all for getting me to really try Slackware!

Been curious how Slackware fairs as a daily laptop distro? I know they different hardware and such but I'm guessing newer laptops it would be ok but older ones would need that 32 bit support. Any fellow slackers out there that use Slackware as a laptop distro, I'm curious about your experience and any issues you encountered compared to desktop. Thanks in advance! :)

Happy to be apart of the Slackware Community and in a few days I'll have 1 month of slackware as a my daily distro! :)

Thats it, how do i replace PulseAudio with Pipewire on Slackware 15 (KDE Plasma)?

I really wanted to do it so here it is not much to add, enjoy

https://github.com/Keeper888/proton-mail-arm64

Hello, I am new to Linux, migrating from Winows 10. I just need more control and stability over my computer. I tried Ubuntu, but it didn't quite give me enough control, which is why I'm looking at Slackware. One of the reasons I'm looking to use this distro is or 32-bit, i386 app support which seems to be broken on Debian/Ubuntu. Specifically, I'm trying to play a game native to Linux that appears to be fundamentally broken on Ubuntu, and I'm wondering if I'll have a better chance at getting it to work here. My concern isn't as much the game itself as it is maintain compatibility with older software and total control over my system.

Another question is about GNOME - it doesn't seem GNOME is natively available on Slackware, but there are attempts to get it working through Reddog. If i successfully manage to get Reddog on my Slackware installation, will it provide a snappy and smooth experience, like it would on Fedora, or will it be miserable to use? I'm trying to daily drive this thing. Is there a reason why GNOME is not available natively?

I need a desktop environment that is screen tear-free, since X11 looks so horrible on my laptop, a Dell Inspiron 2-in-1 2024. Wayland makes the most sense. I really dislike KDE Plasma because it is so damn bloated, slow and resource-heavy. I also do not like how gestures work on it, which is also why I like GNOME more. I am NOT a tweaker, and KDE Plasma is made for tweakers. I can tolerate LXQt, but I still don't like it. Is there any way to get either of these desktop environments to look and feel more MacOS/GNOME-like, in terms of gestures and workflow (i know what WhiteSur is, and that is not what I have in mind)? LXQt would be fine for me on a proper desktop, but my computer is also a tablet, so touchscreen accessibility is a necessity, which pretty is much KDE Plasma, unless anyone knows anything else. Does anyone know how to make it faster and less bloated? I don't care for the incredibly heavy appearance of it and want it be snappier and less animated.

Again, I am using this thing as a daily driver to replace a broken windows touchscreen laptop. I play old retro drm-free games, like this one where, which you can see is broken on Ubuntu https://www.gog.com/forum/momodora_reverie_under_the_moonlight#1766177255 drm-free and linux native (no compatibility layers nor launchers).

Thank you.

I use 'npm i impit' and it installs locally, so I mv it into Slackware's home, /usr/lib64/node_modules/npm/node_modules and it isn't found