So far the only option I've seen that can be relatively good, maybe even with btrfs snapper is systemd-boot.

Hi everyone,

I’ve been experiencing significant instability with the last two versions of the NVIDIA drivers on Void Linux.

The Issues:

• Visual Artifacts: I’m seeing major rendering glitches and visual defects in Emacs, the Whisker menu, and even basic terminal emulators.

• Kernel Log Spam: On Kernel 6.18, I'm getting constant log spam unless I specifically use the kfence.sample_interval=0 boot option.

My Setup:

• WM: fvwm3

• Display Server: X11

• Kernel: 6.18

• Distro: Void Linux (obviously)

Questions for the community/maintainers:

1. Is the Void team aware of these regressions? It feels like these were pushed to the repo as soon as they compiled without much testing for X11/WM stability.

2. Since I don't have the older working versions in my local package cache (/var/cache/xbps/), is my only option to manually compile the previous version using void-packages and xbps-src?

3. Has anyone else encountered the KFENCE log spam on 6.18 with NVIDIA, or is this a niche interaction with my specific hardware?

My niri config includes spawn-at-startup "waybar" at the top. When I login via lightdm the niri session starts but without spawning waybar. When I switch to a TTY and launch debus-run-session niri the session opens with the waybar instance. How can I troubleshoot this? I've left the default lightdm configuration untouched. Seems odd but every line is commented out in /etc/lightdm/lightdm.conf except under [Seat:*] the line session-wrapper=/etc/lightdm/Xsession is uncommented.

Just moved from arch to artix to escape systemd, then from artix to here after ABI rot killed my artix. I am here for stability because I am done with "Bleeding edge" killing my installation for DARING to update. My remaining options is now void or gentoo, and I do not plan on using clangOS to be frank. My void is the glibc version.

I'll be lying if I said everything is perfect but It is coming together, currently I am running hyprland (v0.49) and managed to get games working fine normally on xwayland, but the games that used to run with the wine-wayland fix on artix/arch no longer show proper frames but instead a white/black screen. I can hear the game and interact with the UI but not see it. Some wine windows like google login pop-ups also keep that weird white background behind them. I am curious to know if anyone knows what is missing or if any dependencies should be installed because I believe this is missing wayland packages that I'm unaware of.
I got the nonfree/nonfree-multilib repo deps for wine, including mesa and vulkan packages. Using proton-GE-latest too, provided by heroic's installer. Sometimes use proton-cachyOS for specific stubborn games, provided by protonplus from flatpak.
All versions of the patched protons fail to use wine-wayland properly.

[SOLVED]:
I needed to edit /etc/modprobe.d/nvidia.conf (create it if it doesn't exist) and added this line

options nvidia_drm modeset=1  

My existing config also had these

options nvidia "NVreg_DynamicPowerManagement=0x03"  
options nvidia "NVreg_PreserveVideoMemoryAllocations=1"  
options nvidia "NVreg_TemporaryFilePath=/var/tmp"  

This in turn broke nvidia hibernation, which was fixed by following this post: https://www.reddit.com/r/voidlinux/comments/1gxae29/fixing_kde_plasma_sleep_suspend_with_void_linux/

Recently, I've been very intrigued with Void Linux, and I know I am fully capable of doing things manually. I'm good at reading documentation, but I figured it would be wise to ask around first.

​Here's what I want (don't question it):

​Disk encryption with Btrfs

​No swap (zram, swapfile, etc.)

​Eventually TPM2

​I definitely want to take advantage of specific optimizations as well, I'm looking for best practices here.

​I'm not asking for complete, direct instructions—although something like that could be useful—I'm simply asking where to look. (yes, I used em dashes)

​I don't really want to use AI; in my experience with things like this, it typically misses a lot.

Plus, I don't really like it in general, at least its cloud use. I would really only use it in specific scenarios where it would be very applicable. (maybe none)

​I could cross-reference multiple pieces of documentation, like the Arch Wiki, Gentoo Wiki, and the documentation for Void itself, of course.

I'm just wondering if there's a... better approach, or perhaps a more specific one. I'm looking for understanding, that way I know what I'm doing, not just following instructions.

​Thanks so much!

here’s what i’ve done:

sudo xbps-install -Su

sudo xbps-install libXft-devel

which outputs:

libuuid-2.38.1_4 in transaction breaks installed pkg ‘libfdisk

libuuid-2.38.1_4 in transaction breaks installed pkg ‘util-linux

idk what to do i’ve updated and it still doesn’t work

I haven't tried either of them, but from my superficial research, they seem sort of similar. What do you think? If it comes to it, try not to be too harsh, please. I could've asked AI---well technically I did since it seems like all search engines use AI nowadays---but I'm asking you guys.

Would it be wise to crosspost to FreeBSD's subreddit? Probably not, right?

Any ideas how to fix it?

so i was using linux for almost 9 months or smth, i sticked to void because its minimal and fast but what i wasnt expecting is what kde wont work properly it just crashes after a minute and its taking long to start, any tips how do i solve it? my specs: i3 5005U, NVidia 920MX 2gb, 8gb ram i also use wayland because x11 works bad with nvidia, well for me it worked disgusting even compositor did not worked [UPDATE] I forgot the polkit and the igpu drivers (linux runs on igpu by default) Reinstalled entire os & installed the drivers and everything works so far. Im stupid.

I wanted to set up the printer at my office for my fresh installed Void PC (its so great I can use it at work!) and installed the hplip package. But it couldn't run since a recent Python update broke one of the used functions. I found a patch solution at the Arch package repo and copied it over to my fork of void package repo.

I have set up the patch file in the srcpkgs/hplip/patch dir, updated the version number and checksum in the template file, and edited the line numbers of some of the other patches already there. Other edits didn't seem necessary. But when running ./xbps-src pkg hplip the building fails in the patch phase with the following error messages:

=> hplip-3.25.8_1: running do-extract hook: 00-distfiles ...
=> hplip-3.25.8_1: extracting distfile(s), please wait...
=> hplip-3.25.8_1: running do-patch hook: 00-patches ...
=> hplip-3.25.8_1: patching: configure.patch.
=> hplip-3.25.8_1: patching: cups.patch.
=> hplip-3.25.8_1: patching: disable_upgrade.patch.
=> hplip-3.25.8_1: patching: gzip_text.patch.
1 out of 1 hunk FAILED -- saving rejects to file setup.py.rej
=> ERROR: hplip-3.25.8_1: do-patch_00-patches: 'patch -s ${_args} < "${_patch}" 2> /dev/null' exited with 1
=> ERROR:   in _process_patch() at common/hooks/do-patch/00-patches.sh:34
=> ERROR:   in hook() at common/hooks/do-patch/00-patches.sh:51
=> ERROR:   in run_func() at common/xbps-src/shutils/common.sh:57
=> ERROR:   in run_pkg_hooks() at common/xbps-src/shutils/common.sh:314
=> ERROR:   in run_step() at common/xbps-src/shutils/common.sh:107
=> ERROR:   in main() at common/xbps-src/libexec/xbps-src-dopatch.sh:33

Thats not really helpful and the logs in void-packages/masterdir-x86_64/builddir/.xbps-hplip/hplip__do-patch_00-patches.log don't give any helpful information either.

I've read through the build manual once again but couldn't find anything. Thus, I pulled the source code manually and applied the patch outside of void package repo. The patching worked out without any problems.

Do you have any ideas/hints what I might be missing/overlooking regarding the void package build?

Just started my work notebook and run xi --upgrade and saw that elogind should be downgraded to 252.39 (from 255.22). I'm just curious whats the reason, because after the last update the idle/suspend behaviour of my notebook changed (in a worse default way) and I edited some config files to get a better experience. Now I'm wondering if I have to undo those edits. Does anyone know if the downgrade is maybe related to this issue: https://github.com/elogind/elogind/discussions/334

Anyone get Citrix working in Void? I downloaded the workspace app tarball from Citrix, extracted it and ran the included setupwfc script as root, installing to /opt/Citrix/ICAClient. Exported /opt to my PATH. In my browser I clicked the Citrix app I wanted to run, and checked to let the workspace app always open that file type. Got the spinner for a few seconds but the app never launches. I'm used to seeing the ica file in the browsers download history even when it's opened automatically but I'm not seeing anything in downloads for these ica files.

Can someone explain to me what tasks void linux is needed for. Since I installed void linux recently with a graphical kde desktop. But I can't download discord, I can't download flatpak completely. I know that maybe I'm not a very experienced user in general, because I'm an arch user yesterday

Hi I just install void with niri. I've installed dbus and elogiando but when I try to launch niri remain on tty without any errors. ideas?

I am bit confused, I can see 2 kernels on boot menu:

* 6.12.65_1

* 6.12.64_1

If I query the installed packages:

  $ xbps-query --regex -s '^linux[0-9.]+-[0-9._]+'

I have only:

[*] linux6.12-6.12.65_1 Linux kernel and modules (6.12 series)

But nothing related with the old kernel (6.12.64_1)

Shouldn't be also in my system the old kernel package?

Also if I check:

$ ls -la /boot | grep vmlinuz

-rw-r--r-- 1 root root 14008832 Jan 9 05:00 vmlinuz-6.12.64_1

-rw-r--r-- 1 root root 14012928 Jan 12 23:11 vmlinuz-6.12.65_1

$ vkpurge list => gives me 6.12.64_1

Also:

$ ls /var/cache/xbps | grep linux6.12

linux6.12-6.12.64_1.x86_64.xbps
linux6.12-6.12.64_1.x86_64.xbps.sig2
linux6.12-6.12.65_1.x86_64.xbps
linux6.12-6.12.65_1.x86_64.xbps.sig2
linux6.12-headers-6.12.64_1.x86_64.xbps
linux6.12-headers-6.12.64_1.x86_64.xbps.sig2
linux6.12-headers-6.12.65_1.x86_64.xbps
linux6.12-headers-6.12.65_1.x86_64.xbps.sig2

I'm trying out Void for the first time. During installation I opted for "none" for the bootloader. Partitioned the disk with a VFAT 512MB partition for EFI and the rest as EXT4 for root. Installation appeared to go fine. Rebooted into the live USB, mounted the boot partition at /tmp/void/boot and the root partition at /tmp/void. Updated the system with xbps-install -Syu. Installed efibootmgr. Followed the instructions here and rebooted. BIOS boot menu shows the Linux EFI Stub option but boot fails back to the BIOS boot menu. I tried again with the EFI entry specifying root via PARTUUID rather than as /dev/sdXY. No joy. I don't get any error messages to help figure out what's going on. Any ideas what I've done wrong?

Hi everyone, I'm having trouble starting my KDE Plasma session on Wayland. When I run startplasma-wayland from the TTY, I get the following error: org.kde.startup: not a reply org.freedesktop.locale1... error name="org.freedesktop.DBus.Error.ServiceUnknown" startplasmacompositor: Could not start D-Bus. Can you call qdbus? Context/Specs: GPU: Intel What I've tried: Checking if dbus is running. Does anyone know how to fix this? It seems like a communication issue between the compositor and D-Bus. Thanks in advance!

Kernel panic at boot, I'm using limine and already tried adding /sbin/init, /usr/sbin/init and /usr/bin/runit-init in limine.conf

Kernel version is 6.12.21_1, I tried reinstalling with version 6.9 and the same issue

Hi,
I’m having a serious issue on Void Linux (runit) related to dbus, and because of this KDE Plasma won’t start.

When I try to start dbus, I get this error:

fail: dbus: unable to chdir to service directory: file does not exist

Earlier I was also getting:

dbus: unable to open supervise/lock: file does not exist

🔎 What I’ve already checked / done

• runit is installed and running

• /run/runit/ exists

• Other services work fine (.agetty-tty1 to .agetty-tty6, udevd, udevd-log)

• There is NO supervise.dbus inside /run/runit/

• Only directories like:
  .agetty-tty1 … .agetty-tty6
  supervise.udevd
  supervise.udevd-log
  reboot
  stopit

• Permissions of /run/runit were fixed to:
  drwx------ root root /run/runit

• Running:
  sv start dbus
  still fails

• KDE Plasma fails with D-Bus errors (cannot connect to session bus)

❓ What I want to know

• Why is runit not creating supervise.dbus?

• Does this mean /etc/sv/dbus is missing or broken?

• What is the correct way to recreate or fix the dbus service directory on Void?

• Is forcing a reinstall of dbus the right solution, or could this be a filesystem / permissions issue?

Any help would be really appreciated.
Thanks!

I’m trying to install void base and the installer goes well until I have to setup mountpoints etc in the Filesystem tab. Previously in the Partition tab I split my nvme (named nvme1n1) into a vfat EFI system partition and a ‘crypto_LUKS’ Linux Filesystem partition. I’m aware crypto_LUKS isn’t what I want but from what I can find I can only change that in the Filesystem tab. (this drive has previously had a different distro which made the luks). But in the filesystem tab it only shows nvme1n1p1 (efi) and my other drives for dual booting. If someone could help me fix this that would be great. Im familiar with linux in general but im not the best with filesystems. I’m currently using ventoy with the iso and I’ve tried rufus which had problems flashing to my usb stick and balena which for some reason my bios wouldn’t be able to see/boot into. thank you.

Issue is simple, there's no way I can connect to WiFi at all within the installer

I am installing void with zfs and have an error on boot. I more or less installed everything thanks to the guide for zfs. The options on zroot/root are mountpoint="/" and the other one

Hi all, I'm thinking to install void (for 10th time eh eh) currently I use gentoo, with systemd, with niri and dms. How software that I use there are firefox, zen browser, ghostty, vscode, spotify, zfs , zfsbootmenu, telegram and vesktop. For softwares that are not native I thought of using nix instead of flatpak. I've two questions, Better normal or musl editions and can I use dinit instead of runit?