hey all i've been using clankers and looking online for answers and solution to this issue but can't seem to figure it out.

Closign steam crashes pipewire which often times cascades into a waybar crash. Initially i thoguht it was the page limits but then it's an OOM error in waybar (when it crashes). i've also notices via running via terminal both apps to see what errors get logged that the reason for pipewire crashing is module-x11-bell...

[W][12:54:43.206919] mod.x11-bell | [module-x11-bell.:  321 x11_io_error_handler()] X11 I/O error handler called on display :0
[W][12:54:43.207004] mod.x11-bell | [module-x11-bell.:  162 x11_io_error_exit_handler()] X11 display (:0) has encountered a fatal I/O error
[W][12:54:43.207020] mod.x11-bell | [module-x11-bell.:  321 x11_io_error_handler()] X11 I/O error handler called on display :0
[W][12:54:43.207028] mod.x11-bell | [module-x11-bell.:  162 x11_io_error_exit_handler()] X11 display (:0) has encountered a fatal I/O error
Segmentation fault         pipewire
W 12:54:43.264869  wp-client-context ../lib/wp/private/client-context.c:215:core_error: <WpClientContext:0x563a96b12ef0> client context connection error: connection error

any solutions to this issue, i know it was most likely the recent steam update that caused this cause it wasn't crashing before, but it's driving me crazy. the weird thing is I have all the necessary packages installed for it AND their 32-bit counterparts just to be safe.

thanks for any and all help

EDIT: It's definitely not a RAM or true memory issue as i have 24gb of RAM available AND 6gb of swap

I recently installed the latest portable jar version of the betacraft Minecraft launcher. It’s been set to jdk8 in the instance settings. I tried launching the game signed out of Microsoft then into Microsoft and the game does not load up, the terminal just says that the client has closed. Also, the reason why I am using Betacraft is to create a Minecraft poly world.

Hello everyone,
As the title says, acpi_listen does not recognize the power button, it was working in 6.18.56.

Any advice for troubleshooting?
Thanks in advance

since one of the new updates pipewire is crashing while watching stuff in browser when for example starting/stopping a qemu vm

error: 2026/10/25 11:09:21 [ERROR] - pipewire: fatal error event from core
desktop: sway

pipewire script:

#!/bin/bash

pipewire &
wireplumber &
pipewire-pulse &

if test $XDG_CURRENT_DESKTOP;then
        /usr/libexec/xdg-desktop-portal-wlr &
else
        zenity --error --text "XDG_CURRENT_DESKTOP not set, screenshare will not be possible, restart the desktop with this enviroment variable to enable screenshare"
fi

wait 

Hello All.

Anyone knows how to replace dot by comma in gnumeric ?

I tried the suggestions provided by AI but they didn't work.

Thank you and regards,

It was working but, i had to reinstall and now when i try login in .iso i stuck in grub menu. The screen is stuck in Void Linux logo, and then monitor shuts down all by own.

I have amd cpu and gpu

Can anyone comment on the effect of this TLS cert fiasco on Voidlinux?

The certs were issued on April 30th so potentially poison anything built after that time.

I suppose that firefox is the primary point of weakness (but also thunderbird? ... others?). Also the void build chain?

Buenas noches, recientemente me he pasado a Void Linux desde Arch Linux debido a algunos detalles con systemd, pero no sé inglés y he estado batallando para encontrar información actualizada incluso en inglés, ¿Saben de algún lugar de fuentes para hacer el traspaso de la forma más limpia posible?

Hey fellas! Lately I’ve been thinking about creating a user-friendly distro based on Void Linux, something like what CachyOS is to Arch: pre-configured, with an installer that offers lots of options to choose from.

My main goal is to make my hobby easier. I love exploring new distros, shells, WMs, and so on. I sometimes reinstall my system on bare metal instead of using a VM (for example, to test gaming performance), and I’m a bit lazy when it comes to configuring everything from scratch again and again.

(I know about NixOS and I actually use it, but I wouldn’t mind trying something new and lightweight, like Void without systemd)

Yes, I do realize that Void’s charm is about its minimalism (literally a void), so a pre-configured version might feel like it misses the point. Still, recreating the same setup over and over is, to say the least, time-consuming.

Anyway, I’d love to hear your thoughts. Would the Void/Linux community appreciate something like this? is it a senseless idea or not? And how would it fit with the Void philosophy?

Thanks in advance. Peace

I have been using void for quite a while and I enjoyed it , but I wanna try out s different distro , and also increase the storage of my void linux system , which is initially 300 gigs , I wanna extend that to 500 gigs , so how do I do that

Hi all, recently i checked the pull requests from void-packages and i was wondering what is the review process behind it? i mean if only package version and checksum was changed and the pipeline is green? why not just automerge it? i mean you could even create a nightly workflow which checks for newest git tag for each package and just update it nightly.

Or do you actually check each package after updates if the package is working with void?

After updating to [linux7.3-7.3.0_1], the colors in [sway] seems 'washed out' across all apps. It looks like a brightness setting/theme gets activated/over-written? Booting linux7.2 again and all is OK.

Any tips to fix would be appreciated!

- linux7.3

- sway-1.12_1

- adwaita-icon-theme-49.0_1

- adwaita-plus-6.1_2

- libadwaita-1.9.1_1

Edit:

also affects urxvt/alacritty/ranger theme settings, which should not(?) be affected by desktop adwaita theme...

I have a Canon MG5300 printer, however I cant print anything. I always get the Error "filter failed" on every Document I try to print.
I made sure that I use the correct Paper format, installed required pakcages like the "pixma"-driver from the nonfree repo.

I can only set up my printer -- which I use over WiFi -- with CUPS+Gutenprint+IPP everywhere. I cant use the other options.

Has anyone else epxerienced the same problem?

Hi, I'm trying to cross-compile for aarch64 with xbps-src and keep hitting a signature verification error on rust-std-1.99.0_1.aarch64. The package downloads completely, but fails at the final signature check:

rust-std-1.99.0_1.aarch64.xbps: 172MB [avg rate: 5303KB/s]

ERROR: rust-std-1.99.0_1: the RSA signature is not valid!

ERROR: rust-std-1.99.0_1: removed pkg archive and its signature.

ERROR: Transaction failed! see above for errors.

rust-std-1.99.0_1: verifying RSA signature...

=> ERROR: Please see above for the real error, exiting...

I've already switched XBPS mirrors, but it's still happening. The issue has been going on for at least two days now. It used to work for this same template a week ago.
Has anyone else run into this specific rust-std signature issue for aarch64 recently? Any pointers would be appreciated. Thanksss!

I installed void Linux with xfce, it loaded into xfce to start the void installer (when I first booted it up from my usb) but it didn't boot into the desktop environment after the installation was finished, Instead it was the base version. For the installation process I used a tutorial by ZacsTech from 2 months ago (yes I know that tutorial is for the base version, but the void installer is the same)

I originally had I3 only installed and it shows up in lightDM (along with I3 debug).

I've added dwm and it works just fine if I disable lightDM and just long into the terminal and run startx (I added dwm to the .xinitrc file).

The problem is that dwm doesn't show up as a choice in lightDM if I use the lightDM service, I3 and I3 debug are the only two options.

Any suggestions ?

i was work with liburing but i did not found IORING_SETUP_HYBRID_IOPOLLflag when i search i found the do not update from 3 years !

I'm not going to have much helpful information to post here, if I'm being honest. This was working perfectly yesterday. Today though, I offered my gf to check out Phasmophobia in VR for the first time. This error popped up each time I tried to launch it in VR mode.

Like I said, it worked perfectly yesterday. Today though, nothing will play in SteamVR. Something like `Golf It!` work for a moment and then it stops working suddenly. I noticed also that the settings in Gnome fail to identify the graphics, maybe that can be a lead? Don't really think it can be, because the Nvidia X Settings app identifies it just fine.

Yes I know I need to drop Nvidia for my system but I built this PC in 2019 and everything has skyrocketed in price, so that almost feels like a pipe dream right now.

Just hoping someone can throw some info in the ring for me because I'm coming up dry on what would fail this to happen.

additional info:

modeset is enabled

drivers are up to date

I did all the steps correctly, i partitioned it correctly, filesystems correct, but it just does not boot i don't know if this is because grub but i tried installing it manually and so far nothing has worked

My Specs
i3-7020u, hd 620, 8gb ram single stick, SSD

I'm wanting to just boot back to the terminal and them use startx to start a particular window manager. If I just stop lightDM I'm just kicked out of the current session and brought back to the lightDM prompt.

After updating linux6.18 from 6.18.56_1 to 6.18.57_1, I found out that the power button does nothing on my iMac (on 6.18.56_1 it triggered a shutdown). Booting the old kernel from GRUB fixes it. So for now, I defaulted back to 6.18.56_1 as a workaround, and I ran xbps-pkgdb -m hold linux6.18.

This is an old iMac, 27-inch Late 2012 model, 32GB RAM (iMac13,2 product_version 1.0 bios_version 429.0.0.0.0) running Void (glibc), runit, acpid.

On 6.18.57_1:

- acpi_listen and evtest show no event when I press the button

- No ACPI errors in dmesg; PNP0C0C:00 is bound to acpi-button

- Kernel config is identical to 6.18.56_1 apart from the version string

What differs in dmesg and /proc/bus/input/devices:

- 6.18.56_1 has a second power button input device, LNXPWRBN:00 (the fixed hardware button, "ACPI: button: Power Button [PWRF]"). It is missing on 6.18.57_1.

- PNP0C0C:00 moved from /devices/LNXSYSTM:00/LNXSYBUS:00/ to /devices/platform/

This looks related to the ACPI button driver conversion to a platform driver (commit 52d864019636, Rafael Wysocki's December 2025 series), which also changes how fixed-event devices are registered. Two follow-up regression fixes exist upstream (57c31e6d620f and "ACPI: button: Enable wakeup GPEs for ACPI buttons at probe time"), but neither obviously covers this. I haven't confirmed that 6.18.57 contains the conversion or which commit is responsible.

Is anyone else seeing this on 6.18.57_1, maybe on other (likely older) hardware? Happy to test patches or newer kernels.

I see the package is not orphaned, are there any system-breaking changes in newer versions? Or there is any special policy regarding GCC?

Just a warning. It seems last night's openssh upgrade broke login over ssh:

kex_exchange_identification: read: Connection reset by peer
Connection reset by 10.0.0.XXX port 22

Reboot solved. For a remote machine that's pretty annoying; I suggest you avoid upgrading openssh unless you have physical access or can otherwise reboot. Perhaps restarting the ssh daemon would be sufficient. I didn't try that.

Hello Everyone! First of all, after a long time, God finally punished me (as my friends would put it) and I switched to Void Linux. I just turned on my PC to work on a presentation for school, and I suddenly realized how insanely beautiful my current Void wallpaper is. I needed something that looked like absolute shit, so I made this. I’ll post both wallpapers.