Documenting my system as I go on: https://joespano.xyz

The source is xbps-query -m, which shows packages I explicitly installed rather than every dependency on the system. The point is not to document every library. The point is to remember why the main pieces are here.

Base system

• base-system — Void base system
• base-devel — compiler, make, headers, and normal build tools
• void-docs — local Void documentation
• xtools — Void package/repository helper tools
• opendoas — simple privilege escalation

This is the core of the machine. Void stays small enough that the manually installed package list is still understandable.

Desktop

• xorg-minimal — minimal X11 system
• xinit — start X from the console
• spectrwm — window manager
• st — terminal
• dmenu — launcher
• slock — screen locker
• xwallpaper — wallpaper
• xrandr — display layout
• xsetroot — root window/status text utility
• font-iosevka — main terminal/programming font

The desktop is intentionally plain: X11, spectrwm, st, and dmenu. No desktop environment.

Terminal workflow

• bash — current shell
• abduco — session attachment
• dvtm — terminal tiling
• nnn — file manager
• fzf — fuzzy selection
• fd — file search
• ripgrep — text search
• tree — quick directory views
• xclip — clipboard bridge

This is the part of the system that should get faster over time. The goal is to move around files, search text, edit notes, and work in the terminal without building a large custom framework.

Editing and development

• vis — primary editor
• git — version control
• hugo — static site generator
• curl — HTTP testing and downloads
• wget — downloads
• jq — JSON processing
• groff — formatting and manpage-related work
• man-pages-devel — development manpages

This site is written in Markdown, edited locally, committed with Git, built with Hugo, and deployed to Codeberg Pages.

Browsing

• firefox — general web browser
• qutebrowser — keyboard-driven browser

Firefox is still useful for compatibility. Qutebrowser fits the keyboard-driven direction better and should become more important as the configuration settles.

Reading, RSS, and communication

• newsboat — RSS reader
• weechat — IRC
• zathura — document reader
• zathura-pdf-mupdf — PDF backend
• calibre — ebook management

RSS is part of the publishing loop for this site. Posts and project pages are available through feeds and can be read from Newsboat.

Media and images

• mpv — media player
• ffmpeg — audio/video conversion
• nsxiv — image viewer
• ImageMagick — image manipulation
• maim — screenshots
• slop — region selection for screenshots

This covers basic media handling without pulling in a heavy desktop stack.

Passwords and keys

• pass — password store
• gnupg2 — GPG backend for pass
• openssh — SSH keys and remote Git access

The website repo uses SSH to push to Codeberg.

Hardware and graphics

• intel-video-accel — Intel video acceleration support
• mesa-dri — Mesa DRI drivers
• mesa-vulkan-intel — Intel Vulkan support
• libva-utils — VA-API testing tools
• smartmontools — disk health

These packages support the T480 hardware and give me tools to inspect whether graphics/video acceleration and storage health are working.

Printing and documents

• cups
• cups-browsed
• cups-filters
• avahi
• nss-mdns
• libreoffice

This is the practical document/printing stack. It exists because a daily-driver laptop still needs to print, open forms, and deal with ordinary documents.

CAC and smart card tools

• opensc
• opensc-pkcs11
• pcsc-ccid
• pcsc-tools
• pcsclite

These are for smart card/CAC-related workflows.

System utilities

• btop — system monitor
• cronie — cron daemon
• rsync — file sync and backup tool
• unzip — archive extraction
• setxkbmap — keyboard layout
• dbus — desktop/system messaging needed by some programs

These are small pieces that make the system practical.

Things to review later

• Should I switch to tmux or stick with what I'm working with now

Rebuild note

A future version of this note should turn into a small package manifest and rebuild script.

For now, this page is just a record of what is installed and why.

I have this problem that elogind doesn't wanna start.
I can manually start it by using sudo /usr/libexec/elogind/elogind.wrapper but setting up the service always shows me that it's down (down: elogind: 178s, normally up; run: log: (pid 28672) 187s).

I also removed it and tried to test the service first. It works as expected. Removing the down file tho it still shows that it's down (but is normally up (?)).

In the handbook it says

>If you're having any issues with elogind, enable its service, as waiting for a D-Bus activation can lead to issues.

Should I just put like 2 seconds to the elogind run file? So it completely waits for the dbus service to be up?I have this problem that elogind doesn't wanna start.
I can manually start it by using sudo /usr/libexec/elogind/elogind.wrapper but setting up the service always shows me that it's down.I also removed it and tried to test the service first. It works as expected. Removing the down file tho it still shows that it's down (but is normally up (?)).In the handbook it saysIf you're having any issues with elogind, enable its service, as waiting for a D-Bus activation can lead to issues.Should I just put like 2 seconds to the elogind run file? So it completely waits for the dbus service to be up?

Edit: Quick update, i just got rid of the elogind service although it's still installed on my system and my system has faster boot time now. Why 😅?

I have an Acer laptop and started using Void Linux today; I'm really loving the system. However, I'm having a serious issue with PipeWire. I've tried setting it up several times but never quite get it right—or it only works halfway. For instance, I followed the steps correctly, but it only picks up audio from my monitor, or sometimes it recognizes my laptop's sound card but my headset microphone simply doesn't work (only the laptop's built-in mic does). I was wondering if anyone knows how to fix this; I'd be very grateful.I have an Acer laptop and started using Void Linux today; I'm really loving the system. However, I'm having a serious issue with PipeWire. I've tried setting it up several times but never quite get it right—or it only works halfway. For instance, I followed the steps correctly, but it only picks up audio from my monitor, or sometimes it recognizes my laptop's sound card but my headset microphone simply doesn't work (only the laptop's built-in mic does). I was wondering if anyone knows how to fix this; I'd be very grateful.

TL;DR, Does anyone have any examples/experience using zzz hooks to trigger a screen locker?

Hi everyone,

I've been using void on my M2 macbook for just under 6 months and have been careful to design a system which is reliable and easy to work on.

I will be traveling more with my laptop and finally decided to stop procrastinating and set up my screen locker correctly as currently I just have to remember to trigger it before closing my lid/suspending which doesn't always happen. To clarify, I use acpid to detect the lid close event and run zzz (I believe this might even be the default config).

After sifting through the man pages i found zzz has suspend/resume hooks which seems great for my usecase. For my system I've steered clear of systemd/logind due to my desire to keep my system simple and easy to work on so 'just use logind' is not an ideal solution in my case, otherwise i would just use swayidle's before-sleep directive and be done with it.

The issue is, swaylock requires both XDG_RUNTIME_DIR and WAYLAND_DISPLAY environment variables which are not present in the env that zzz runs its hooks. Duplicating my logic for these variables from my bash_profile just seems wrong (although I don't see another alternative at this time). My .bash_profile can be found at github.com/unworried/dotfiles.

All feedback and advice is welcome! Thanks to everyone in advance :)

Edit 1: Corrected dotfiles reference, should be .bash_profile not .bashrc.

Hello,

I am running Void on Lenovo x270 laptop without any nvidia, amd or broadcom components. But during the update I can see these packages. So I tought I can just remove them but seems I can not beacause of some dependencies.

Any way to remove them ? I mean, I would probably not die if I just keep them on the system...

Thank you for your help.

[medo@localhost ~]$ sudo xbps-install -Su
[*] Updating repository \https://repo-default.voidlinux.org/current/x86_64-repodata' ...`

Name                    Action    Version           New version            Download size
cairomm                 update    1.14.5_1          1.14.6_1               47KB  
chromium                update    149.0.7827.53_1   150.0.7871.46_1        132MB  
fastfetch               update    2.64.2_1          2.65.2_1               694KB  
firefox                 update    152.0.2_1         152.0.4_1              87MB  
iceauth                 update    1.0.9_1           1.0.11_1               17KB  
libarchive              update    3.8.7_1           3.8.8_1                369KB  
libass                  update    0.17.4_1          0.17.5_1               118KB  
libevent                update    2.1.12_3          2.1.13_1               210KB  
libfontenc              update    1.1.8_1           1.1.9_1                14KB  
libgsm                  update    1.0.22_2          1.0.24_1               37KB  
libnvme                 update    1.16.1_1          1.16.2_1               94KB  
linux-firmware-amd      update    20260410_1        20260622_1             30MB  
linux-firmware-broadcom update    20260410_1        20260622_1             12MB  
linux-firmware-intel    update    20260410_1        20260622_1             13MB  
linux-firmware-network  update    20260410_1        20260622_1             433MB  
linux-firmware-nvidia   update    20260410_1        20260622_1             105MB  
noto-fonts-ttf          update    2026.06.01_1      2026.07.01_1           17MB  
ocl-icd                 update    2.3.2_2           2.3.5_1                105KB  
rtkit                   update    0.13_3            0.14_1                 34KB  
tesseract-ocr           update    5.5.0_3           5.5.2_1                6592KB  

Size to download:              838MB
Size required on disk:        1331MB
Space available on disk:        28GB

Do you want to continue? [Y/n] n
Aborting!
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake-U GT2 [HD Graphics 520] (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
03:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$  
[medo@localhost ~]$ sudo xbps-remove linux-firmware-nvidia linux-firmware-amd linux-firmware-broadcom
linux-firmware-nvidia-20260410_1 in transaction breaks installed pkg \linux-base-2026.03.23_1'linux-firmware-amd-20260410_1 in transaction breaks installed pkg \linux-base-2026.03.23_1'linux-firmware-broadcom-20260410_1 in transaction breaks installed pkg `linux-firmware-network-20260410_1'ERROR: Transaction aborted due to unresolved dependencies.[medo@localhost ~]$``

Did anybody already have the idea that I can just copy and paste to my DE?

Dear community,

I've been having an issue where sometimes when lightdm starts, it will lands on manual login mode (the mode that requires the user to enter both username and password, which appears as "Other"). This happens randomly and I don't know how to reproduce it, but I have captured a log file (/var/log/lightdm.log)

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=6305
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 6315: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.00s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.00s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.47s] DEBUG: Got signal 10 from process 6315
[+0.47s] DEBUG: XServer 0: Got signal from X server :0
[+0.47s] DEBUG: XServer 0: Connecting to XServer :0
[+0.51s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.51s] DEBUG: Session pid=6329: Started with service 'lightdm-greeter', username 'lightdm'
[+0.60s] DEBUG: Session pid=6329: Authentication complete with return value 0: Success
[+0.60s] DEBUG: Seat seat0: Session authenticated, running command
[+0.60s] DEBUG: Session pid=6329: Running command /usr/bin/lightdm-gtk-greeter
[+0.60s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.60s] DEBUG: Session pid=6329: Logging to /var/log/lightdm/seat0-greeter.log
[+0.62s] DEBUG: Activating VT 7
[+0.62s] DEBUG: Activating login1 session c15
[+0.62s] DEBUG: Seat seat0 changes active session to c15
[+0.62s] DEBUG: Session c15 is already active
[+0.70s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+0.76s] DEBUG: Greeter start authentication
[+0.77s] DEBUG: Session pid=6367: Started with service 'lightdm', username '(null)'
[+0.77s] DEBUG: Session pid=6367: Got 1 message(s) from PAM
[+0.77s] DEBUG: Prompt greeter with 1 message(s)
[+7.39s] DEBUG: Greeter start authentication for tb
[+7.39s] DEBUG: Session pid=6367: Sending SIGTERM
[+7.39s] DEBUG: Session pid=6376: Started with service 'lightdm', username 'tb'
[+7.39s] DEBUG: Session pid=6367: Terminated with signal 15
[+7.39s] DEBUG: Session: Failed during authentication
[+7.39s] DEBUG: Seat seat0: Session stopped
[+7.39s] DEBUG: Launching process 6377: /usr/bin/pkill -9 -u tb
[+7.40s] DEBUG: Process 6377 exited with return value 1
[+7.40s] DEBUG: Seat seat0: Exit status of /usr/bin/pkill -9 -u tb: 1
[+7.40s] DEBUG: Session pid=6376: Got 1 message(s) from PAM
[+7.40s] DEBUG: Prompt greeter with 1 message(s)
[+9.11s] DEBUG: Continue authentication
[+9.13s] DEBUG: Session pid=6376: Authentication complete with return value 0: Success
[+9.13s] DEBUG: Authenticate result for user tb: Success
[+9.13s] DEBUG: User tb authorized
[+9.13s] DEBUG: Greeter requests session xfce
[+9.13s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+9.13s] DEBUG: Terminating login1 session c15
[+9.13s] DEBUG: Session pid=6329: Sending SIGTERM
[+9.14s] DEBUG: Seat seat0 changes active session to 
[+9.14s] DEBUG: Greeter closed communication channel
[+9.14s] DEBUG: Session pid=6329: Exited with return value 1
[+9.14s] DEBUG: Seat seat0: Session stopped
[+9.14s] DEBUG: Seat seat0: Greeter stopped, running session
[+9.14s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+9.14s] DEBUG: Session pid=6376: Running command /etc/lightdm/Xsession startxfce4
[+9.14s] DEBUG: Creating shared data directory /var/lib/lightdm-data/tb
[+9.14s] DEBUG: Session pid=6376: Logging to .xsession-errors
[+9.15s] DEBUG: Activating VT 7
[+9.15s] DEBUG: Activating login1 session c16
[+9.15s] DEBUG: Seat seat0 changes active session to c16
[+9.15s] DEBUG: Session c16 is already active

and also the old log file when it happen (for reference)

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=6212
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 6222: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.00s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.06s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.06s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.46s] DEBUG: Got signal 10 from process 6222
[+0.46s] DEBUG: XServer 0: Got signal from X server :0
[+0.46s] DEBUG: XServer 0: Connecting to XServer :0
[+0.51s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.51s] DEBUG: Session pid=6235: Started with service 'lightdm-greeter', username 'lightdm'
[+0.59s] DEBUG: Session pid=6235: Authentication complete with return value 0: Success
[+0.59s] DEBUG: Seat seat0: Session authenticated, running command
[+0.59s] DEBUG: Session pid=6235: Running command /usr/bin/lightdm-gtk-greeter
[+0.59s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.59s] DEBUG: Session pid=6235: Logging to /var/log/lightdm/seat0-greeter.log
[+0.60s] DEBUG: Activating VT 7
[+0.60s] DEBUG: Activating login1 session c14
[+0.60s] DEBUG: Seat seat0 changes active session to c14
[+0.60s] DEBUG: Session c14 is already active
[+0.69s] DEBUG: Greeter connected version=1.32.0 api=1 resettable=false
[+0.74s] DEBUG: Greeter start authentication
[+0.74s] DEBUG: Session pid=6271: Started with service 'lightdm', username '(null)'
[+0.74s] DEBUG: Session pid=6271: Got 1 message(s) from PAM
[+0.74s] DEBUG: Prompt greeter with 1 message(s)
[+3.33s] DEBUG: Seat seat0 changes active session to 
[+5.50s] DEBUG: Seat seat0 changes active session to 6
[+46.64s] DEBUG: Got signal 15 from process 1555
[+46.64s] DEBUG: Caught Terminated signal, shutting down
[+46.64s] DEBUG: Stopping display manager
[+46.64s] DEBUG: Seat seat0: Stopping
[+46.64s] DEBUG: Seat seat0: Stopping display server
[+46.64s] DEBUG: Sending signal 15 to process 6222
[+46.64s] DEBUG: Seat seat0: Stopping session
[+46.64s] DEBUG: Terminating login1 session c14
[+46.64s] DEBUG: Session pid=6235: Sending SIGTERM
[+46.64s] DEBUG: Seat seat0: Stopping session
[+46.64s] DEBUG: Session pid=6271: Sending SIGTERM
[+46.64s] DEBUG: Session pid=6271: Terminated with signal 15
[+46.64s] DEBUG: Session: Failed during authentication
[+46.64s] DEBUG: Seat seat0: Session stopped
[+46.64s] DEBUG: Launching process 6302: /usr/bin/pkill -9 -u tb
[+46.65s] DEBUG: Process 6302 exited with return value 0
[+46.65s] DEBUG: Seat seat0: Exit status of /usr/bin/pkill -9 -u tb: 0
[+46.65s] DEBUG: Greeter closed communication channel
[+46.65s] DEBUG: Session pid=6235: Exited with return value 1
[+46.65s] DEBUG: Seat seat0: Session stopped
[+46.65s] DEBUG: Seat seat0 changes active session to 
[+46.66s] DEBUG: Process 6222 exited with return value 0
[+46.66s] DEBUG: XServer 0: X server stopped
[+46.66s] DEBUG: Releasing VT 7
[+46.66s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+46.66s] DEBUG: Seat seat0: Display server stopped
[+46.66s] DEBUG: Seat seat0: Stopped
[+46.66s] DEBUG: Display manager stopped
[+46.66s] DEBUG: Stopping daemon
[+46.66s] DEBUG: Exiting with return value 0

Entering the username or switching to my user isn't that inconvenient but other people that use my computer don't know how to read English nor know that they can switch to the tb user

Thanks.

Edit:

this is the config (/etc/lightdm/lightdm.conf)

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
# backup-logs = True to move add a .old suffix to old log files when opening new ones
# dbus-service = True if LightDM provides a D-Bus service to control it
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-check-graphical=true
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=$XDG_DATA_DIRS/lightdm/greeters:$XDG_DATA_DIRS/xgreeters
#backup-logs=true
#dbus-service=true

#
# Seat configuration
#
# Seat configuration is matched against the seat name glob in the section, for example:
# [Seat:*] matches all seats and is applied first.
# [Seat:seat0] matches the seat named "seat0".
# [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client".
#
# type = Seat type (local, xremote)
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option)
# xserver-config = Config file to pass to X server
# xserver-layout = Layout to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[Seat:*]
#type=local
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xmir-command=Xmir
#xserver-config=
#xserver-layout=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
greeter-session=lightdm-gtk-greeter
greeter-hide-users=false
greeter-allow-guest=false
greeter-show-manual-login=false
#greeter-show-remote-login=true
user-session=startxfce4
#allow-user-switching=true
allow-guest=false
#guest-session=slick-greeter
session-wrapper=/etc/lightdm/Xsession
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=/etc/X11/Xsession
#session-cleanup-script=/usr/bin/pkill -9 -u tb
#autologin-guest=false
#autologin-user=
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=
#exit-on-failure=false

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# listen-address = Host/address to listen for XDMCP connections (use all addresses if not present)
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
# hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#listen-address=
#key=
#hostname=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# listen-address = Host/address to listen for VNC connections (use all addresses if not present)
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#listen-address=
#width=1024
#height=768
#depth=8

I commented out the clean up command, hoping that it can solve the problem, but I'm not sure. IT WAS NOT COMMENTED WHEN I CAUGHT THE PROBLEM

Hello all!

I am new to void, I installed it as of this guide: https://docs.voidlinux.org/installation/guides/fde.html

I use UEFI therefore I mount my boot partition to /boot/efi and I installed grub there

It works as expected but the problem is that when I type the password to decrypt the LUKS1 partition it takes about 15-20 seconds to decrypt before it actually starts booting and this is on SSD.

Is there a solution or some way to make it faster? Do I have to use another bootloader other than GRUB?

Thanks for reading!

its like a 50/50 chance my touchpad works perfectly after a reboot

if it's not, it's stuttery and has trouble recognizing touch to click and double taps

it's a synaptics touch pad on a ThinkPad

Recently bought YubiKey and thought if I could use it to decrypt my laptop instead of password. Did anyone have a success with this?

Hi yall

I'm a complete newbie to this. I have a laptop that runs on Void and I use Network Manager for wifi. Until about a month ago, all was fine. Now it keeps disconnecting and it's not detecting any wifi, I can't connect to anything (besides by plugging in). Today it happened again. I restarted the router and the laptop and it worked for an hour then it disconnected again. Rebooting does nothing. I tried the F8 button, doesn't help. Making updates either. I've tried different commands I found online, there is no hard or soft block or interfering program (to my knowledge). I've read it could be a driver issue. How do I make sure of that and update that?

What else can be the cause?

Do they not want to provide people with encryption and security? Why not update the installer?

https://preview.redd.it/cv73j5zld6ah1.png?width=2560&format=png&auto=webp&s=728367c478815d3186f4ce4d0b57a4d8981750a7

Why do you use Void? I'm currently using Debian, but am considering moving to a systemd less distro. While I know they have not implemented age verification they have place the ground work to one day possible make that a reality. From what I understand systemd does help make distros run smoothly by doing many different things. I looked into Devuan, as I'm already using Debian, but thought I might branch out. What other systemdless distros did you try and why did you land on VOID?

Hello, after the big AUR hack, I've decided to switch from arch (artix with dinit) to void. however, i'm having trouble getting niri to launch. I've installed niri and seatd like this:

sudo xbps-install niri seatd xwayland-satellite mesa mesa-dri dbus
sudo ln -s /etc/sv/seatd /var/service/
sudo ln -s /etc/sv/dbus /var/service/
sudo usermod -a -G _seatd <user>
sudo reboot

Afterwards, I ran niri with niri --session. I encountered a RuntimeDirNotSet error, and set it with export XDG_RUNTIME_DIR=/run/user/$(id -u).

Afterwards, I encounter a PermissionDenied error. the output also shows a lot of libinput errors for various plugins, plugin never regisered, unloading plugin that may be relevant. If someone could help me find out what the issue is, it would be greatly appreciated!

I want to use Dualshock 4 PS controller (either USB or Bluetooth is fine). I followed Gentoo Wiki how to connect/pair the controller, but it doesn't seem to work. (I'm trying to use it with BSNES Emulator.

I'm thinking that Void's default kernel doesn't have the support for Dual Shock controller enabled. Is this the case? How can I check if the kernel config used by the default kernel?

Has anyone successfully used DualShock4 controller? Thanks!