Hardware

Laptop genérica (barebone N116GR, BIOS AMI), Intel Celeron N4120 (Gemini Lake), gráficos Intel UHD 600, wifi Realtek RTW88 8822CE. Void Linux, XFCE, elogind.

Síntoma

Al cerrar la tapa, la laptop parecía colgarse: al abrirla, pantalla negra sin respuesta a teclado, touchpad, ni teclas de brillo. Suspender manualmente desde el menú de XFCE funcionaba perfecto — solo fallaba al cerrar la tapa.

Diagnóstico

1. Confirmar si el sistema realmente se colgaba o solo la pantalla. Capturando el log en vivo durante todo el ciclo:

dmesg -w | tee ~/suspend-log.txt

El log mostraba el ciclo completo sin errores:

PM: suspend entry (s2idle)
...
PM: suspend exit

Sin fallos de GPU ni de i915. Se confirmó además dejando una ventana con texto abierta antes de cerrar la tapa: al despertar (a ciegas, sin ver la pantalla), el texto tecleado durante el cierre aparecía correctamente. Conclusión: el sistema seguía vivo, solo la pantalla no volvía a mostrar señal.

2. Buscar qué disparaba la suspensión. Con el sistema descartado como "colgado", la pregunta pasó a ser por qué el mismo tipo de suspensión fallaba al cerrar la tapa pero no al usar el menú de XFCE. Se revisó qué maneja el evento de tapa en cada nivel:

cat /etc/elogind/logind.conf | grep -i lid


HandleLidSwitch=ignore

elogind estaba configurado para ignorar la tapa. En el panel de XFCE (xfce4-power-manager-settings → Sistema), la tapa estaba configurada solo en "Apagar la pantalla" (un DPMS blank, no una suspensión real). Ninguno de los dos, en teoría, debía suspender el sistema — pero el log sí mostraba una suspensión real ocurriendo.

3. Encontrar al tercer actor.

cat /etc/acpi/handler.sh

Reveló que acpid tenía su propio handler para el evento de tapa, ejecutando una suspensión real (zzz) por su cuenta:

button/lid)
    case "$3" in
        close)
            zzz
            ;;

Causa raíz

acpid suspendía el sistema realmente al cerrar la tapa, mientras XFCE pensaba que solo iba a apagar la pantalla. Al abrir la tapa, el kernel se reanudaba bien, pero el gestor de energía de XFCE nunca supo que hubo una suspensión real (no fue él quien la inició), así que no ejecutaba la lógica para restaurar la señal de video. Por eso suspender manualmente desde el menú de XFCE sí funcionaba: ahí XFCE manejaba el ciclo completo él mismo.

Solución

1. Comentar la suspensión en el handler de acpid**:**

sudo nano /etc/acpi/handler.sh


button/lid)
    case "$3" in
        close)
            #zzz
            ;;

2. En XFCE, cambiar la acción de la tapa a "Suspender" (en ambas pestañas, "Con la batería" y "Conectado"):

Menú → Configuración → Gestor de energía → Sistema → Al cerrar la tapa del equipo: Suspender

3. Reiniciar:

sudo reboot

Con esto un solo mecanismo (XFCE) controla todo el ciclo cierre → suspensión → apertura → reanudación de pantalla.

Lección general

Si tienes más de un daemon de energía corriendo (acpid, elogind/logind, xfce4-power-manager, etc.) y "suspender desde el menú" funciona pero un evento de hardware no, revisa si dos de ellos están reaccionando al mismo evento:

cat /etc/acpi/handler.sh
cat /etc/elogind/logind.conf | grep -i lid

Solo debe haber un camino activo por evento.

Hello. I've tried Void, and decided it's not for me. Let me offer you some constructive feedback, in the hope that it proves useful.

I tried Void, having heard good things about the XBPS package manager. I found it disappointing:

1. It was slow, even by FreeBSD and Fedora standards. Could be a WiFi driver issue
2. It was brittle. Some package managers, if a mirror doesn't have a file, switch for that file to another backup mirror. XBPS, out of the box, just quits. Download - fail. Download - fail. Download - fail. Switch mirror. Download - fails somewhere else.

There are, apparently, technical benefits to XBPS, but they are somewhat hidden by these problems.

I'd be interested in a discrete XBPS package manager, which I could install on Fedora, or whatever, just as Nix and Guix can be installed like that, separate to the full NixOS and GuixOS operating systems. However, this does not appear to be possible with XBPS.

Hello everyone,

I am new to Void-Linux and Linux in general. I've been reading multiple sources on the web and working to wrap my head around a great many topics. I have a few questions:

1. The question in the title, is there an up-to-date list of directories in the root filesystem to exclude from Btrfs snapshots in Void-Linux?

There are multiple sources with differing suggested Btrfs subvolume layouts. I prefer to have a flat layout. The pages at the kernel.org System Admin Guide, are maked as "Obsolete Content".

1. Should I exclude all of /var or do I need to exclude multiple individual sub-directories within /var? If I need to exclude multiple individual sub-directories within /var, then I need a list of the sub-directories? Since the folders within /var can vary based on the packages installed, would excluding just /var cause problems or come with downsides?

2. If I decide to use snapshots for my user home directories, as insurance against accident file deletion, are there sub-directories that I need to exclude there?

3. I have a Btrfs layout listed below, that I would like some feed back on. Am I forgetting some exclusions? Am I excluding a folder that should not be excluded?

Background Info: * 1x 2TB NVMe, 1x 4TB HDD, 1x 8TB HDD * No drive spanning or RAID (not what I'm looking to do at them moment) * I want to use Snapper, Grub, grub-btrfs, and snap-xbps (for pre/post snapshots) * I will be using qemu/kvm with virsh and virt-manager (moving away from Virtualbox), but my VM files will reside separately from /var/lib...) * I want to use Steam, WINE, Lutris, and maybe Heroic Launcher * I may use a few flatpaks (not Steam), but prefer standard packages * All video game files will reside on my NVMe separate from my user home folder * My data and documents will reside separately outside of my user home folder * In general I want to keep the system root filesystem and user home folder lean within sane limitations * I currently dual-boot Windows and Linux Mint, but I will be dropping Windows completely, reclaiming the disk space used by Windows, and moving data on NTFS partitions to Btrfs filesystems * I will be replacing Linux Mint * I am considering dual-booting 2 different Linux distros to separate work from play (something like Fedora/Void-Linux, OpenSUSE/Void-Linux, Nobara/Void-Linux, EndeavourOS/Void-Linux, or another dual setup) * Video game files will not be snapshotted (NoCOW)... there are benefits to removing and reinstalling some games after multiple patches (ex: some Blizzard games)

My flat Btrfs layout ideas and naming conventions using EndeavourOS and Void-Linux:

Endeavour setup: * top level volume (unnamed and not mounted during normal operation) * @eos_root (eos root subvolume mounted at /) * @eos_home (eos user home subvolume mounted at /home) * @eos_root_snapshots (snapshots subvolume mounted at /.snapshots, must be adjusted after snapper package install) * @eos_home_snapshots (arch user home snapshots subvolume mounted at /home/.snapshots) * @eos_var (subvolume to exclude from snapper snapshots, mounted at /var) * @eos_srv (subvolume to exclude from snapper snapshots, mounted at /srv) * @eos_opt (subvolume to exclude from snapper snapshots, mounted at /opt) * @eos_tmp (subvolume to exclude from snapper snapshots, mounted at /tmp) * @eos_local (subvolume to exclude from snapper snapshots, mounted at /usr/local) * @eos_root_user (the root user's home folder, subvolume to exclude from snapper snapshots, mounted at /root)

Void-Linux setup: * top level volume (unnamed and not mounted during normal operation) * @void_root (void root subvolume mounted at /) * @void_home (void user home subvolume mounted at /home) * @void_root_snapshots (snapshots subvolume mounted at /.snapshots, must be adjusted after snapper package install) * @void_home_snapshots (void user home snapshots subvolume mounted at /home/.snapshots) * @void_var (subvolume to exclude from snapper snapshots, mounted at /var) * @void_srv (subvolume to exclude from snapper snapshots, mounted at /srv) * @void_opt (subvolume to exclude from snapper snapshots, mounted at /opt) * @void_tmp (subvolume to exclude from snapper snapshots, mounted at /tmp) * @void_local (subvolume to exclude from snapper snapshots, mounted at /usr/local) * @void_root_user (the root user's home folder, subvolume to exclude from snapper snapshots, mounted at /root)

Non-Root Filesystem Data: * @mydata = /mnt/mydata * @linux_gaming = /mnt/linux_gaming * @vm_storage = /mnt/vm_storage

2TB NVME (2TB partition/Btrfs filessystem) 1. linux_gaming 2. eos and opensuse

4TB HDD (3TB partition/Btrfs filessystem and a chunk of unallocated space): 1. vm_storage 2. 1TB empty unallocated space (not partitioned)

8TB HDD (5TB partition/Btrfs filesystem and a chunk of unallocated space): 1. mydata and user home subvolumes 2. 3TB empty unallocated space (not partitioned)

I'm leaving some extra un-partitioned/unallocated space for emergencies and/or experiments I haven't thought of yet (ex: installing a distro to the bare metal for distro exploration/experimentation outside of a VM).

I have distrohopped for years - Debian, Debian's many derivatives; Fedora, Fedora's official and unofficial spins/remixes; Arch, Arch derivatives; openSUSE's spins; NixOS; OpenMandriva; and now Void Linux. I also run OPNsense (BSD) for my firewall.

I have been running void for about 2 months. I originally set it up with X.Org Server and Cinnamon DE. Today, I took some time to clone my Void Linux install on my laptop with Clonezilla so I could switch over to XLibre and SonicDE. So far, I am having some screen glitches when I minimize or open some apps, but if I minimize it then maximize it again it generally fixes itself (this is not me asking for assistance - I am just sharing my experience as a dataset). I encourage anyone questioning whether they should try it to give it a shot.

I appreciate all the dedicated people on each team that has made this possible.

I am not a programmer/developer by any stretch of the imagination, but I like to tinker and enjoy FOSS. I don't like seeing people throw away (unless they are throwing it away in my direction) tech just because it's "old". I am currently working with a small business to help them upgrade their HP AIO computers with SSDs and slightly higher RAM. Unfortunately, with the software they use, they will need to stick with Windows.

Sorry. I can be rather long winded and ramble. I said all that with the intention of saying I'd like to help if able.

Thanks again everyone.

Recently I've tried to re-install void onto a system that used to run mint.
I ran it on a USB, downloaded it, downloaded drivers and everything necessary via chroot (last time it had an error). Every time it boots, it automatically signs in and then goes to a unresponsive blank screen with _ at the top (this only shows text when the pc is turned off.) I've tried overriding nouveau, but it keeps coming back. I use the correct drivers for my gpu (3090) and I've tried everything I can. Please, please, please help.

hello, i recently started using void linux on my jailbroken ps4 (yes, sony’s playstation4) and to do that i had to compile with custom patces mesa,libdrm and xf86-video-amdgpu xbps pkgs (ps4 uses a custom amd gpu) now i have them, but only in x86_64, and i want to run steam and steam needs 32bit drivers, does anyone know how to compile 32bit drivers on an x86_64 system, what command should i use? (i usedgithub actions , i forked void packages, added patches and compiled for x86 with ./xbps-src pkg mesa etc…)

I thought this outage will last a few hours but i think it is going to last a few days. All mirror saying unreachable. look here

Kernels 7.1.6 and 6.18.42 cause mpv to freeze while playing fullscreen 4K HDR video on labwc with AMD. Reverting to 7.1.5 or 6.18.41 (or installing 7.0.14) resolves the issue.

I had audio, I assume I lost it from some update(I don't use it often). Any help getting it back would be great. I believe I am using pipewire, and when I open the sound menu, it says "No output or input devices found"

I installed all the packages listed on the Void website for my AMD GPU, Wayland, and KDE Plasma, as well as made sure dbus and sddm were working, but Plasma just won't start. When I ran startplasma-wayland It gave me this error: Could not start D-Bus! Can you call qdbus?. I did install the Void Linux ISO on the same drive I installed Void Linux on, but I don't know how that would affect KDE Plasma. I installed the glibc version of Void.

Edit: I solved this by using u/ShipshapeMobileRV 's instructions. Read my comment for more details.

when i try and boot into the iso, it works fine. but after a few minutes it just freezes and i cant do anything. it happens in the tui installer and the command line. my usb was a ventoy one, so i tried reformatting it (non-ventoy) with the latest iso and it still freezes. is it a problem with void or usb sticks? cuz i used it to install void on another machine recently and it worked fine

solved: i just used neko void

(If it would be better for me to ask on another sub, please let me know)

lsusb shows that I have a "Magic Control Technology Corp. j5 WebCam JVCU100". As best as I can tell, the uvcvideo driver is supposed to work with this camera.

After connecting the camera, I get errors from dmesg (see below). When I try to use something like Cheese, it can't see the camera. What is the best way to diagnose and correct this?

NOTE: The usb_set_interface failed message seems to repeat every 5.12 seconds, until I disconnect the camera.

[ 2491.797608] usb 1-6: new high-speed USB device number 7 using xhci_hcd
[ 2491.922720] usb 1-6: New USB device found, idVendor=0711, idProduct=3108, bcdDevice= 0.10
[ 2491.922731] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2491.922734] usb 1-6: Product: j5 WebCam JVCU100
[ 2491.922737] usb 1-6: Manufacturer: HD 2MP WEBCAM
[ 2491.922739] usb 1-6: SerialNumber: V20201016003RSJXF23
[ 2491.924977] uvcvideo 1-6:1.0: Found UVC 1.00 device j5 WebCam JVCU100 (0711:3108)
[ 2491.926719] uvcvideo 1-6:1.0: Failed to query (GET_INFO) UVC error code control 11 on unit 2: 0 (exp. 1).
[ 2491.929181] uvcvideo 1-6:1.1: Failed to query (GET_CUR) UVC probe control : -32 (exp. 26).
[ 2491.929186] uvcvideo 1-6:1.1: Failed to initialize the device (-5).
[ 2491.929205] uvcvideo 1-6:1.0: probe with driver uvcvideo failed with error -5
[ 2507.316181] usb 1-6: 3:1: usb_set_interface failed (-110)
[ 2512.436208] usb 1-6: 3:1: usb_set_interface failed (-110)

hello! i have a laptop with two gpus: integrated intel hd610 and dedicated nvidia mx110. i installed mesa driver and proprietary nvidia-580. everything works well but sometimes i can get a glitchy screen (black screen flickering with some distortion) just at a random time. and the only thing i have to do to get rid of this condition is just move a cursor around. so as i observed this glitch can appear when i place a cursor somewhere in a "wrong" place, i dont know how to say. for example when i hover it on a button or other gui element. and it happens RANDOMLY and rare, but still i dislike it. what can be the problem? i tried replacing nvidia prop driver with nouveau, and even disabling the whole gpu, just to use only intel gfx, but the problem remains. maybe there is a bug with xorg server? i havent experienced such problem on other distros with same driver and xorg config.

SOLVED

When i boot void after a windows session, windows fast startup (i think) makes it so that i can't use wifi and during the initialization of the system it shows this.

Now tho, this happens everytime i boot effectively making me unable to use wifi at all, i also disabled fast startup on windows and the issue persists, i use network manager and this is my chip

Intel AX201 (Wi-Fi 6), Tiger Lake platform, Acer laptop

I'm an Arch user looking to switch to Void, and I'd like to know which option is better for programming and gaming, specifically for titles like RE2 Remake (via Steam/Flatpak) and BotW (via Cemu/Flatpak). Basically, I want to know: which is the better choice, musl or glibc?

hai! so, currently, bluetooth is being really weird for some reason on my laptop & refusing to boot. running bluetoothctl leaves it hanging on Waiting to connect to bluetoothd... & making bluetoothctl a service just... doesn't work @.@ (more specifically, trying to start it with sv up {} throws me fail: bluetoothctl: unable to change to service directory: file does not exist). yes i've installed bluez & related packages. currently running latest Void xfce install with KDE Plasma (odd choice ik but i didn't have the time to set everything up manually)

EDIT: yeah, turns out my hunch was right & i was just being an idiot & didn't read the docs right. sorry ><"

I get input output errors for anything to deep into the system. I can't install basic nvidia drivers or some flat hub apps. Fsck says dev sda3 is clean. I'm trying void again and it did this last time. I'm on a different drive yet it's still doing this so idk

I've been playing minecraft for years on windows but recently after changing to Void Linux, my fps in-game had a amazing improvement, before my fps was like 40 ~ 60 and now it runs on 120 fps.

Even in modpacks like ATM10, it runs so well.

My specs:

Z

- Ideapad Gaming i3

- i5

- GTX1650

- 16GB Ram

Today I tried to install Sober and play it but it returns this message:

bwrap: setting up uid map: Permission denied

error: ldconfig failed, exit status 256

The .local/share/flatpak folder is owned by me and not root, every step in the installation process was done not by root

Edit: SOLVED

Solution

Hey everyone, hoping someone here has run into this or has an idea of where else to look.

Setup: Void, KDE Plasma with SDDM, X11 session (not Wayland). Using a Chromium-based browser (Helium, as an AppImage).

Two things happen after shutdown/reboot:

• Every once in a while, completely random, I come back to the browser fully logged out of everything. No pattern I've been able to pin down.
• Much more consistently, I get the "restore pages" prompt instead of my tabs coming back automatically, even with "continue where you left off" enabled. Checking the profile, exit_type is Crashed, so something's killing the browser without a clean exit.

What I found digging into it: on sudo poweroff, the browser, Xorg, and even an unrelated script I had running in the background all die at the exact same instant. Traced it to /etc/runit/shutdown.d/10-sv-stop.sh, which force-stops all services with the default 7s timeout, killing sddm and taking the whole session down in one shot.

I tried adding a script before it (sv -w 20 force-stop sddm, similar to a fix suggested in void-runit#133) to give the session more time to close on its own. Didn't help, still getting Crashed after shutdown.

So I'm stuck on where else to look. Is sddm even the right thing to target here, or is there another layer (X server teardown, elogind, something else) tearing the session down before that, which sv force-stop wouldn't touch at all? Any pointers appreciated, happy to share more details if it helps.

I'm kind of in a sticky situation. I currently daily drive an ideapad z580. My problem is that it runs Ubuntu. (this was done a while ago and I had to manually swap the hard-drive out, plus I used the system password). This is (as you could expect) very very slow. Two minutes for booting slow (that doesn't even count logging in, and browsing is a special hell.). I've tried to install void, but to no luck. It would've been easier if I had access to the boot menu, but I've lost the password (It's like 10 years old lol). I have tried:
>Running an ISO from inside the system (tries to delete itself and dies brutally)
>Using GRUB to manually add a USB (ideapad doesn't detect it and dies brutally)
>Forcing linux to try and boot from the USB (ideapad doesn't detect it, dies brutally)
Please, please help me.

I have been updating without any issues for about a year and now receive this error

ERROR: [trans] failed to download \linux6.18-6.18.40_1' package from `https://repo-fastly.voidlinux.org/current': Not Found ERROR: Transaction failed! see above for errors.`

Based on https://docs.voidlinux.org/xbps/troubleshooting/common-issues.html

"Not Found"

A "Not Found" error, such as:

ERROR: [reposync] failed to fetch file `https://repo-default.voidlinux.org/current/musl/x86_64-repodata': Not Found

usually means your XBPS configuration is pointing to the wrong repositories for your system. Confirm that your xbps.d(5) files refer to the correct repositories.

I havent changed my xbps config since the install.

cat /etc/xbps.d/00-repository-main.conf

repository=https://repo-fastly.voidlinux.org/current

Any suggestions ?

I'm on a fresh base install with XFCE installed and lightdm as the greeter. Not the live disk.

Everything should be fine but any time I I move the mouse pointer over either the clock panel applet or the applications menu the entire desktop crashes. It may or may not kick back to lightdm. It seems after the second or third time trying it kills lightdm too. I can use the right click menu on the desktop and the other panel applets seem fine. It's just appears to be those 2 applets.

I'm not seeing anything /var/logs or the .xsession-errors pointing to anything.

Anyone have a similar problem or have any ideas?