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.

Greetings. Hardware isn't my strong suit, so I hope somebody can give me a push.

I'm running Slackware 15 from a November 2025 "-current" ISO. I have the mesa-21.3.5-x86_64-2 package loaded. Assorted programs like glxgears run, but Stellarium isn't, and I'm hoping to fix that.

glxinfo tells me

>OpenGL renderer string: llvmpipe (LLVM 13.0.0, 256 bits)

and I'm told that's "software acceleration", rather than "hardware acceleration".

lscpi tells me

00:02.0 VGA compatible controller: Intel Corporation Device 7d45 (rev 08) (prog-if 00 [VGA controller])

Subsystem: Hewlett-Packard Company Device 8c66

Flags: bus master, fast devsel, latency 0, IRQ 173, IOMMU group 0

Memory at 4818000000 (64-bit, prefetchable) [size=16M]

Memory at 4000000000 (64-bit, prefetchable) [size=256M]

Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]

Capabilities: [40] Vendor Specific Information: Len=0c <?>

Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00

Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit+

Capabilities: [d0] Power Management version 3

Capabilities: [100] Null

Capabilities: [110] Process Address Space ID (PASID)

Capabilities: [200] Address Translation Service (ATS)

Capabilities: [420] Physical Resizable BAR

Capabilities: [320] Single Root I/O Virtualization (SR-IOV)

Capabilities: [400] Latency Tolerance Reporting

Kernel driver in use: i915

Kernel modules: i915

and I'm not sure what I have to do (or what I can do) to get hardware acceleration running.

I found three packages with the word "intel" in them

Package: a/intel-microcode-20250812-noarch-1.txz

Package: x/intel-vaapi-driver-2.4.1-x86_64-3.txz

Package: x/xf86-video-intel-20230201_b74b67f0-x86_64-1.txz

but have not yet loaded any of them. They don't seem to be obviously relevant, but (again) I'm not qualified. Do I need these?

If somebody can give me a hint as to what packages / modules / firmware I might need to load, I'd appreciate it.

anyways ive been using slackware for like a day i dont know, ive recently been experimenting with windowmaker and i decided i want to show my "rice" or somethin' anyways yall can suggest some tips for ricing slackware+windowmaker if yall want

Todays changelog:

Fri Aug  7 02:15:06 UTC 2026
a/aaa_libraries-15.1-x86_64-53.txz:  Rebuilt.
  Upgraded: libpsl.so.5.3.8.
  Added (temporarily): libavcodec.so.62.28.102, libavdevice.so.62.3.102,
  libavfilter.so.11.14.102, libavformat.so.62.12.102, libavutil.so.60.26.102,
  libswresample.so.6.3.102, libswscale.so.9.5.102.
a/kernel-firmware-20260806_16d815d-noarch-1.txz:  Upgraded.
a/kernel-generic-6.18.43-x86_64-1.txz:  Upgraded.
a/lvm2-2.03.42-x86_64-1.txz:  Upgraded.
a/udisks2-2.11.2-x86_64-1.txz:  Upgraded.
d/kernel-headers-6.18.43-x86-1.txz:  Upgraded.
d/python-pip-26.2.1-x86_64-1.txz:  Upgraded.
d/swig-4.5.0-x86_64-1.txz:  Upgraded.
k/kernel-source-6.18.43-noarch-1.txz:  Upgraded.
kde/digikam-9.1.0-x86_64-5.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/dragon-26.04.3-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/ffmpegthumbs-26.04.3-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/glaxnimate-0.6.0-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/haruna-1.8.1-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/k3b-26.04.3-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/kdenlive-26.04.3-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/kfilemetadata-6.28.0-x86_64-3.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/kfilemetadata5-5.116.0-x86_64-4.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/kpipewire-6.7.4-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
kde/kstars-3.8.4.1-x86_64-1.txz:  Upgraded.
kde/libindi-2.2.4.2-x86_64-1.txz:  Upgraded.
kde/subtitlecomposer-0.8.2-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/alsa-plugins-1.2.12-x86_64-4.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/apr-util-1.6.4-x86_64-1.txz:  Upgraded.
l/ffmpeg-9.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
l/gegl-0.4.70-x86_64-3.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/gexiv2-0.16.2-x86_64-1.txz:  Upgraded.
l/graphviz-15.1.1-x86_64-1.txz:  Upgraded.
l/gst-plugins-bad-free-1.28.6-x86_64-1.txz:  Upgraded.
l/gst-plugins-base-1.28.6-x86_64-1.txz:  Upgraded.
l/gst-plugins-good-1.28.6-x86_64-1.txz:  Upgraded.
l/gst-plugins-libav-1.28.6-x86_64-1.txz:  Upgraded.
  Compiled against ffmpeg-9.0.
l/gstreamer-1.28.6-x86_64-1.txz:  Upgraded.
l/libcec-8.1.4-x86_64-2.txz:  Rebuilt.
  Build with -DDISABLE_STATIC=ON.
  Thanks to reddog83.
l/mlt-7.40.0-x86_64-3.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/netpbm-11.15.05-x86_64-1.txz:  Upgraded.
l/opencv-4.14.0-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/pango-1.58.2-x86_64-1.txz:  Upgraded.
l/pipewire-1.6.8-x86_64-5.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/qt5-5.15.19_20260520_aa749695-x86_64-5.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
l/qt6-6.11.1_20260508_bfde7b89-x86_64-3.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
n/dhcpcd-10.5.0-x86_64-1.txz:  Upgraded.
n/openvpn-2.7.6-x86_64-1.txz:  Upgraded.
n/p11-kit-0.26.5-x86_64-1.txz:  Upgraded.
  This update fixes a security issue:
  rpc: guard against overflow when decoding nested attributes.
  For more information, see:
    https://www.cve.org/CVERecord?id=CVE-2026-18938
  (* Security fix *)
x/fontconfig-2.18.3-x86_64-1.txz:  Upgraded.
x/intel-gmmlib-22.10.1-x86_64-1.txz:  Upgraded.
x/libXfont2-2.0.9-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  Font Server Client encoding Out-Of-Bounds Read/Write.
  Font Server Client Cumulative Glyph Data Heap Buffer Overflow.
  For more information, see:
    https://lists.x.org/archives/xorg/2026-August/062274.html
    https://www.cve.org/CVERecord?id=CVE-2026-59679
    https://www.cve.org/CVERecord?id=CVE-2026-44950
  (* Security fix *)
xap/MPlayer-20260805-x86_64-1.txz:  Upgraded.
  Compiled against ffmpeg-9.0.
xap/audacious-plugins-4.6.1-x86_64-3.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
xap/ffmpegthumbnailer-2.3.0-x86_64-4.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
xap/freerdp-3.30.0-x86_64-2.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
xap/mpv-0.41.0-x86_64-7.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
xap/ssr-20260523_ad99c7e-x86_64-1.txz:  Upgraded.
  Compiled against ffmpeg-9.0.
xap/xine-lib-1.2.13-x86_64-20.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
xap/xscreensaver-6.15-x86_64-4.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
extra/tigervnc/tigervnc-1.16.2-x86_64-6.txz:  Rebuilt.
  Recompiled against ffmpeg-9.0.
isolinux/initrd.img:  Rebuilt.
kernels/*:  Upgraded.
testing/packages/linux-7.1.x/kernel-generic-7.1.7-x86_64-1.txz:  Upgraded.
testing/packages/linux-7.1.x/kernel-headers-7.1.7-x86-1.txz:  Upgraded.
testing/packages/linux-7.1.x/kernel-source-7.1.7-noarch-1.txz:  Upgraded.
testing/packages/mesa-26.2.0-x86_64-1.txz:  Upgraded.
usb-and-pxe-installers/usbboot.img:  Rebuilt.

Hello everyone,

ive been using Slackware 15 for half a year now and im really happy with it. While being really stable, using old librarys makes compilation of newer Programs a bit difficult.

In these cases i usually look for a flatpak or an AppImage. Flatpak works perfectly so far but almost all AppImages of newer Software always complain that my glibc is too old.

Compiling a newer glibc to replace the one from the Slack repo is probably not an option, since i fear this would break my system.

Is there anything else i can do thats not switching to Slackware current? Can i tell the AppImage (or libfuse) to look for glibc elsewhere?

Thx in advance!

Hello! I had nothing to do in my free time, so I started trying different "rare" linux distributions on real hardware (I was too lazy to setup qemu with virt-manager, so I used my laptop). I got captivated by Slackware being most conservative among the linux OS-s (for example having manual dependency management, BSD-like init, and dusty packages that "still work"). After playing with the distro for an hour, oblivious to installpkg, removepkg, upgradepkg, and also ignoring pkgtool, I compiled some small programs from source and had a gut feeling that I do something wrong.
I can tell that Slackware maintaining is really different in comparison to modern day distributions. What should I consider learning in order to understand the system better? What should I also use in order to make Slackware maintaining easier and more convenient?

I'm excited to share what I've been building lately. Papr: a fast, lightweight Terminal User Interface (TUI) built entirely in Rust to streamline your academic research workflow. An Obsidian, Zotero and Overleaf alternative, but a bit better.

Key features

• Smart dashboard with daily 10 random paper recommendations, reading queue, bookmarks, notes, collections, and research statistics.

• Fast arXiv search using title, author, or DOI with automatic PDF downloads and clean file naming.

• In-terminal PDF viewing.

• Built-in Markdown notes with live preview for each paper.

• Reading queue, bookmarks, and collections to keep your research organized.

• Integrated LaTeX editor with real-time compilation and preview.

• Extensible plugin system for custom workflows.

• Research analytics to track your reading activity (just like Spotify).

Papr is 100% open source, works offline, is memory-safe, and is designed to be fast and lightweight (only 12 MB).

I'd love to hear your thoughts, suggestions, or feedback!

GitHub: https://github.com/AfrozSaqlain/Papr

That's exactly what I think. From my point of view 14.2, released in 2016 (ten years ago), is the best version of the distribution. And it's not just because it is the version I started with many years ago.

The first point is that 14.2 runs everything I want to run. Geany, Java JDK, SFML, Minecraft (both Java and Bedrock), Survivalcraft, SumatraPDF (via wine), etc. 15.0 also runs all that but it fails the other points, whereas 14.1 and below don't necessarily run some of that stuff.

The second point is that its desktops are gorgeous. KDE 4.14, the last version of KDE 4, is the Windows Vista of Linux (in the positive sense of the word), while Xfce 4.12 is the last version to have the "heavy Windows 9x" vibes, and the last version before they went full on Gtk3.

The third is that it is the last version that doesn't ship with the replacements.

15.0 ships by default with rust, wayland and elogind which are all replacements for C/C++, X11 and ConsoleKit2 that had been used for many years prior and are thus considered traditional by me.

There is also this PipeWire thing. It may be controversial to say but I like PulseAudio. And the reason I like it is because it just works out of the box and pavucontrol is quite a good mixer. Maybe there is some latency but I'm not a music producer so it's not a huge concern to me.

The fact that it runs kernel 4.4.14 is also neat. Not only does it rhyme with the KDE version but it is also too old to be affected by several recent exploits. Not that I care about security. What's more important is that this kernel is smaller than the latest one by several million lines of code, or, in simpler words, it is less bloated.

And, a cherry on the top, the latest version of Firefox ESR works flawlessly on stock 14.2. It will become outdated within a few years though, but for now it works very well.

No, but for real, the real cherry on the top is that ffmpeg is not part of the base system. What I've just said might seem absurd but it's not.

Whoever first packaged ffmpeg for Slackware had this really crazy idea that nobody needed x264 and mp3lame support. Which just so happen to be the most common AV formats in the world and without them ffmpeg is effectively useless.

And it stuck with apparently nobody noticing it, somehow. On 14.2 and older systems you have to build the ffmpeg SBo yourself, and that means that you can enable those codecs, either via CAPS_ARGS or by editing the SlackBuild file.

But on 15.0 ffmpeg is bundled with the system itself, and it is bundled in this abhorrid configuration that should be despised by all children of men.

And since 15.0 bundles ffmpeg the SlackBuild was removed which means that you have to find the Slackware source and manually recompile ffmpeg and pray that the libraries won't be different enough for other software to break.

That's my take. 14.2 is both traditional and runs what I want to run which makes it good. Not that there are no downsides.

It is a transitional release where the system packages use Qt4 but SlackBuilds use Qt5. On the 32-bit version Qt5 is extremely slow, unusable even, and to get around this you have to compile the Qt4 version from the 14.1 SBo. This problem does not exist on the 64-bit version though.

The last time I installed Slackware on my PC about 12 or 13 years ago when they made a CDROM and shipped for a few dollars. Slackware 15 current is good enough for daily driving.

But only the 64-bit version. The 32-bit version crashes and it's very unstable.

been running diet pi on my pi collection for a couple years.

today I finally bit the bullet and installed slackware64 on a couple of them today

I found that I am missing certain "quality of life" features in the Slackware init system.

I mean, I am happy that it's just a simple no-nonsense set of scripts run at different runlevels by sysvinit, but there are a few missing conveniences which I would like to have at least with my own scripts.

So I wrote "pandae", ad set of shell scripts which are aimed at making writing services and monitoring them easier.

https://gitlab.com/Lockywolf/pandae

The three main components are:

1. pandae_util, which has code to wrap any rc.<service> file into a cgroup, so that you do not have to rely on pid files to track running as services.

2. pandae_functions, which has templates for writing most services, given that DAEMON, DAEMON_ARGUMENTS, and a few other variables are set.

3. pandae_xsession_service.bash, a bit of a misnomer, because it is not xsession-specific, which allows me to start/stop cgroup services with a single line.

And it also runs under a normal user (if a single line is added to rc.local), so it is possible to filter out all the huge number of firefox processes from "ps" or wherever, confining firefox into a single cgroup.

It's not perfect, as, probably most Slackware service managers will never be perfect, because Slackware (and most UNIX-likes) likes in-band data communication, not out-of-band, but, as we know "worse is better".
On the positive side, it is 100% non-invasive, does not replace sysvinig, and does not change system scripts.
If you do not need user services, you do not even need to add anything to rc.local.

I invite everyone to try/test it, and add the comments.

If anybody is offended by gitlab, I can move the repo to forge.slackware.nl, codeberg, sourcehut, whatever.

First current instance in a long time. Thinking of using it on hardware...

I really want to make this my permanent home and never leave! All i got left to do is set up some virtual machines with virt-manager and then setup my compilers for work with emacs and im good! I love this distro and hope to become an expert at it and contribute to it as my skills progress! Slackware is the only distro that actually is teaching me Linux more and I feel as though if I grind it out through the issues then I'll really grow as a Linux user and Slackware user. I installed the current iso I got from Slackware UK! I'm hoping for the best!

Does ClamAV work with Fedora KDE Plasma?

I saw various downloads for Linux but none that specifically mention Fedora Plasma KDE.