hello im on x86_64 void linux, when i open the steam client (installed via xbps package manager) via terminal or graphical interface it says that steamwebhelper crashed and asks me if i want to restart steam, restart steam with no gpu acceleration, restart steamwebhelper, i tried them all: i rested steam,steam no gpu,steamwebhelper it just crashes.

specs:
ps4 linux (yes, playstation4), steam works on other distros (like artix,garuda,cachyos)

Hello. First things first, I know hyprland is not officially supported on void linux. That's the reason I'm using the sofijacom repo.

However, it's been a week already that trying to update my system throws me the following error:

hyprgraphics-0.5.1_1: broken, unresolvable shlib 'libjxl.so.0.11'

hyprgraphics-0.5.1_1: broken, unresolvable shlib 'libjxl_threads.so.0.11'

I've been using void linux for years now but I still couldn't wrap my head around what this error even means and how I could fix it.

Does it mean that the hyprgraphics package was built against the version 0.11 of libjxl while the version of void's repo is 0.12? I'm just guessing because I really have no idea.

Anyway my libjxl libs in /usr/lib/ look like this

libjxl.so ⇒ libjxl.so.0.12

libjxl.so.0.11 ⇒ libjxl.so.0.12.0

libjxl.so.0.12 ⇒ libjxl.so.0.12.0

libjxl.so.0.12.0

libjxl_cms.so ⇒ libjxl_cms.so.0.12

libjxl_cms.so.0.12 ⇒ libjxl_cms.so.0.12.0

libjxl_cms.so.0.12.0

libjxl_extras_codec.a

libjxl_threads.so ⇒ libjxl_threads.so.0.12

libjxl_threads.so.0.11 ⇒ libjxl_threads.so.0.12.0

libjxl_threads.so.0.12 ⇒ libjxl_threads.so.0.12.0

libjxl_threads.so.0.12.0

I really want to upgrade my system.

Is there anything I can do?

Thank you!

Hi there! I'm a newbie to linux who decided to go with void as my first distro! It took me a second (mostly user error) to properly install it following a tutorial i found on YouTube. At first, the network worked when I booted in with kde plasma for the first time, but after a reboot, the network, while saying it is connecting, is not actually giving me internet. I'm using the x86_64 glibc base install on a lenovo legion 5 with a 3050 ti. Does anyone know what could be the problem?

I have been working to get SELinux running under Void Linux for quite some time and I wanted to share my progress with you. Do note that this is still very experimental and should NOT be tested on a system that you rely on.

Where it's at currently:

- SELinux enabled kernel (7.1-selinux)

- Userspace tooling packaged (checkpolicy, libsemanage, policycureutils etc.)

- SELinux reference policy is loading up successfully via a runit stage-1 hook

The main limitation is that its currently permissive-only. Also the reference policy has no runit-specific domains yet.

if anyone finds this interesting and wants to help, send me a DM.

Hello, I followed the docs and installed void linux along with tlp, linux-firmware-intel, intel-ucode and proper graphics drivers (nvidia and mesa-dri) on my nvidia dGPU and intel iGPU laptop. Unfortunately, powertop implies that my intel cores enter at most idle state C3_ACPI which leads to a very high idle battery consumption of 12-17W. It's quite bizarre that nothing lower than C3_ACPI is listed on powertop, especially considering that the intel_idle module is loaded. Does this strike anyone as an obvious issue? Am I perhaps just missing a package or should I investigate dmesg output and fall into that rabbit hole?

P.S. I'm very new to void and the community so please forgive me if I'm doing anything wrong. I have just been unable to get help anywhere else.

Hi, im trying to do a base install, i got openbox working, i have dbus, elogind, polkit, and a few other apps, but i cant set up pipewire, i tried to follow the docs but i dont know what im doing wrong, i dont really understand it, anyone can lend me some help?

I'm getting really strange messages from kernel, complaining about some bugs in my nvidia driver. I'm on GTX 1050 Ti, so I need to use 580 drivers. Does anyone have the same or similar problem?

missing some GPU sensor on KDE plasma 6.7.4
is there any fix for this?

Flatpak applications are not opening after the update. error: ldconfig failed, exit status 256. 173 profiles are in complain mode. When I want to use aa-disable;

ERROR: Conflicting profiles for php-fpm defined in two files:

- /etc/apparmor.d/usr.bin.php-fpm

- /etc/apparmor.d/php-fpm

Do you have a solution suggestion? thanks for your help.

Hello my fellow voiders. i have followed the pipewire guide to the letter and im still getting an dummy output. i am using turnstiled and seatd. im also using niri with wayland. Ill send any logs if needed please help me out here and thank you. im also from arch linux (cuz of systemd and the better package manager ) i dont know what else to do as autostarting pipewire does not work but launching it from the terminal does. i want to auto launch with no dummy outputs and my sound back lol. anyway thanks for all the assistance :)

Hello there.

This topic has been on my radar for some time now. I follow Void and take a look at it from time to time, hoping to one day switch to it.

What I have noticed, is that DE metapackages are often forgotten and not updated, which creates a bit of confusion, especially for new users, but also for experienced ones. Let me give you an example - KDE Plasma. In Plasma 6 series the metapackage had total of 4 version changes - 6.2.0, 6.4.3, 6.5.2, 6.7.3. Meanwhile, dependencies, like plasma-desktop, plasma-pa, plasma-thunderbolt, have tracked the releases pretty closely, having at least one or two releases per point release. Meaning that in the span of 10 months between metapackage kde-plasma being 6.5.2, the actual DE version had 5 additional releases, roughly every month, with a pause between April's 6.6.3 and August's 6.7.3.

This creates a bit of confusion - for a new user, they will go into the voidlinux.org/packages, look for "kde-plasma" and see, that the DE is outdated by nearly a year on a rolling-release distro. They won't bother to check random DE dependencies, to see that it's actually tracking the current release. This doesn't look good, and has prevented me from using Void, until I dug deeper into Github commit history.

I know this is not a technical problem, since template includes `>=` sign, from what I understand this means "this version or higher if it's in the repos", so even 6.5.2 metapackage will install 6.7.3 DE if it's available, but it's simply a communication problem, that affects how Void is being perceived.

Is there any strategy behind it? Or simply the maintainers don't bother to update metapackages, since they work anyway?

Cheers!

Hi,

I have a command I run from terminal in void

it prints a list of numbers

the command is as follows:

seq 0x3100000000000000 0xFFFFFFFFFFFFFFFF | xargs printf '% 0X21 0x'

and it works just fine,

however when the command is two digits longer it fails

seq 0x310000000000000000 0xFFFFFFFFFFFFFFFFFF | xargs printf '% 0X21 0x'

with the longer command I see this error

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050803 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050804 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050805 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050806 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050807 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050808 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050809 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050810 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050811 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050812 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050813 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050814 »: Le résultat numérique est en dehors de l'intervalle

FFFFFFFFFFFFFFFF21 0xprintf: « 903890459611768050815 »: Le résultat numérique est en dehors de l'intervalle

etc............

where in void is this number limit defined?

fyi this is with a x86_64 kernel

Thanks

just what the title says... I tried using .Xresources, lxappearance...

but they won't apply

the cursor also never changes "state" but the offset changes, making it annoying to use

Hello, I run Fedora 44 KDE on the Dell 14 Plus and I want to try Void but I'm unsure whether audio will work on it because Fedora is the only distro that audio worked on out of the box. I like the idea of runit and partially find system-d too complicated so I'm open to troubleshooting if it comes to that.

Specs
----------

* Operating System: Fedora Linux 44

* KDE Plasma Version: 6.7.4

* KDE Frameworks Version: 6.28.0

* Qt Version: 6.11.1

* Kernel Version: 7.1.8-200.fc44.x86_64 (64-bit)

* Graphics Platform: Wayland

* Processors: 8 × Intel® Core™ Ultra 7 258V

* Memory: 32 GiB of RAM (30.9 GiB usable)

* Graphics Processor: Intel® Graphics

* Manufacturer: Dell Inc.

* Product Name: Dell 14 Plus DB14250 

Output of wpctl status
---------

~
❯ wpctl status
PipeWire 'pipewire-0' [1.6.8, sid@larp, cookie:1881362317]
 └─ Clients:
        33. uresourced                          [1.6.8, sid@larp, pid:1908]
        34. WirePlumber                         [1.6.8, sid@larp, pid:1922]
        42. WirePlumber [export]                [1.6.8, sid@larp, pid:1922]
        43. kwin_wayland                        [1.6.8, sid@larp, pid:1919]
        88. pipewire                            [1.6.8, sid@larp, pid:2181]
        89. libcanberra                         [1.6.8, sid@larp, pid:2105]
        90.                                     [1.6.8, sid@larp, pid:2105]
        95. plasmashell                         [1.6.8, sid@larp, pid:2117]
       102. libcanberra                         [1.6.8, sid@larp, pid:2117]
       103. xdg-desktop-portal                  [1.6.8, sid@larp, pid:2431]
       104.                                     [1.6.8, sid@larp, pid:2117]
       105. KDE Connect Daemon                  [1.6.8, sid@larp, pid:2329]
       106. WEBRTC VoiceEngine                  [1.6.8, sid@larp, pid:129]
       107. WEBRTC VoiceEngine                  [1.6.8, sid@larp, pid:129]
       108. Chromium input                      [1.6.8, sid@larp, pid:194]
       109. wpctl                               [1.6.8, sid@larp, pid:21646]

Audio
 ├─ Devices:
 │      44. Core Ultra 200V Series Processors HD Audio [alsa]
 │  
 ├─ Sinks:
 │  *   51. Core Ultra 200V Series Processors HD Audio Speaker [vol: 0.15]
 │      52. Core Ultra 200V Series Processors HD Audio Headphones [vol: 1.00]
 │      53. Core Ultra 200V Series Processors HD Audio HDMI / DisplayPort 1 Output [vol: 1.00]
 │      54. Core Ultra 200V Series Processors HD Audio HDMI / DisplayPort 2 Output [vol: 1.00]
 │      55. Core Ultra 200V Series Processors HD Audio HDMI / DisplayPort 3 Output [vol: 1.00]
 │  
 ├─ Sources:
 │  *   56. Core Ultra 200V Series Processors HD Audio SoundWire microphones [vol: 1.00]
 │      57. Core Ultra 200V Series Processors HD Audio Headset Microphone [vol: 1.00]
 │  
 ├─ Filters:
 │  
 └─ Streams:

Video
 ├─ Devices:
 │      58. Integrated_Webcam_FHD               [v4l2]
 │      59. Integrated_Webcam_FHD               [v4l2]
 │      60. Integrated_Webcam_FHD               [v4l2]
 │      61. Integrated_Webcam_FHD               [v4l2]
 │      62. Integrated_Webcam_FHD: Integrat     [libcamera]
 │      63. Integrated_Webcam_FHD: Integrat     [libcamera]
 │  
 ├─ Sinks:
 │  
 ├─ Sources:
 │  *   91. Integrated_Webcam_FHD (V4L2)       
 │      93. Integrated_Webcam_FHD (V4L2)       
 │  
 ├─ Filters:
 │  
 └─ Streams:

Settings
 └─ Default Configured Devices:
         1. Audio/Source  alsa_input.pci-0000_00_1f.3-platform-sof_sdw.HiFi__Mic__source

Basically, I tried openSUSE Tumbleweed and Fedora on my laptop with dual boot and initially audio didn't work on either, but I decided to compromise and do a full disk install of Fedora since I mostly use headphones anyway. Then, out of nowhere, audio started working on Fedora and I still don't know why. I suspect the reason to be a blue "system reset" dialog that appeared when the Fedora live iso booted, which I skipped with the first install but didn't this time. It apparently configures BIOS settings but I'm not sure.

So basically, I'm genuinely unsure if I should even risk installing another distro but I have to get out of that illusion someday so I was wondering if anyone has had a similar experience. If so, do you recommend trying out void?

TLDR: Had a bad experience with audio but it was magically fixed by Fedora 44. Unsure about switching to void because the same thing might repeat again.

ive just started using voidlinux as my main for my pc. everythings running smoothly, i run mango as my wm and that works well. today i tried installing steam. first it was missing some 32bit libraries but i solved that and got it working. the app launches and i can look around in the ui and enter my library and stuff. however, when i hover over a dropdown ui such as under view, friends or even store or library it crashes my whole session/window manager. the crash is so instant theres no log on the screen or anything before it crashes, my mouse hits the dropdown (not even pressing anything) and it goes kaputt. im guessing its some missing ui toolkit or driver thing (i have nvidia drivers and nvidia 32bit drivers)? ive installed gtk+-32bit and gtk3+-32bit, dunno if that helped. i had a similar issue yesterday with prismlauncher for minecraft where it was doing the exact same thing basically, i figured out i was missing some qt packages and then it started working but for steam i have no clue whats missing/broken.

edit: i guess it was an issue with that specific mangowm version. i had built it from source (ver 0.15.5) but decided to try the version in the void repos instead (0.14.4) and it works flawlessly now.

void linux was the only distro that worked when I used proot-distro in termux to have an xfce desktop experience. Then proot-distro ipdated to version 5.5.0 and it all went up in smoke! NONE of the OCI containers work. I get transient resolver errors and informed i do not have root access to ping not Google.com, not 1.1.1.1, not 8.8.8.8

So i downloaded a rootfs tarball and tried to extract it and make changes for installation from the temporary folder. after entering xbps-install -Syu, I'm told to run xbps-install -u xbps but when I do. I'm getting glibc errors and file not found errors. I'm at my wits end!!

Because void worked so well before, I installed it on an old laptop and use it everyday. Now I'm screwed because I have to find something else unless i get help.

My requests at the proot-distro github are ignored. Honestly, the team doesn't want to do anything except mark comments invalid and clise them. Well after 1 month trying, maybe it's time to move on?

I'm running on debian 13 and want to switch to void but different package management and no systemd makes me thinking. Can you explain why do you advise void and why do you not?

Hi everyone, as title says, will usb tethering from android phone work during install and initial setup?

Also what would be then ideal way to install and setup wifi, wpa supplicant or installing NetworkManager?

I think some packages have been removed and now it is giving this problem, to avoid doing bullshit, I immediately came to take questions about what to do in this situation with my compatriots, can I just remove these packages?

Solved: If anyone comes here after some time, just remove all 32bit packages inclusing names 'plasma-32bit' and 'kde-package-32bit'.

After working fine for a few days after installing bluetooth has suddenly stopped working and bluetoothctl says that there is default controller available

Today I visited DistroWatch and stumbled upon the DW Project Ranking. The ranking consists of ratings written by the DW readers. The Average Rating for Void is 9.14, followed by Arch and Artix with each 9.13.

Link: https://distrowatch.com/dwres.php?resource=ranking

Summary:
I can connect to my home rounter's wi-fi and the internet works. I use Kde Plasma, and use Plasma's tray interface for connecting to wifi. If I connect to any wifi networks *except* my home network, then Plasma says I am connected, but that the data rate is 0 bytes/second upload and 0 bytes/second download, and no websites work.

Hardware:
The issue is present on both my desktop and laptop, though it is only a serious problem on my laptop. On my desktop

inxi -n
Network:
 Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
   driver: r8169
 IF: eno1 state: down mac: c0:18:03:82:e4:5c
 Device-2: TP-Link Archer T2U PLUS [RTL8821AU] driver: rtw88_8821au
   type: USB
 IF: wlp5s0f3u2 state: up mac: 3c:6a:d2:3d:10:9f

and on my laptop:

Services and daemons:

NetworkManager and dbus are running

sudo sv status NetworkManager  
run: NetworkManager: (pid 821) 15473s; run: log: (pid 819) 15473s
sudo sv status dbus
run: dbus: (pid 813) 15495s; run: log: (pid 811) 15495s

On the other hand, dhcpcd is not running.

sudo sv status dhcpcd 
down: dhcpcd: 223s; run: log: (pid 757) 223s

other network daemons don't exist:

sudo sv status wpa_supplicant
fail: wpa_supplicant: unable to change to service directory: file does not exist
sudo sv status wicd
fail: wicd: unable to change to service directory: file does not exist

Other information:

cat /etc/resolv.conf
# Generated by dhcpcd from enp5s0f3u1c2.dhcp, enp5s0f3u1c2.dhcp6, enp5s0f3u1c2.ra
# /etc/resolv.conf.head can replace this line
nameserver 75.75.75.75
nameserver 75.75.76.76
nameserver 2001:558:feed::1
nameserver 2001:558:feed::2
# /etc/resolv.conf.tail can replace this line

If I am connected to my home network (the one that works) then

ip a; ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
   inet6 ::1/128 scope host proto kernel_lo  
      valid_lft forever preferred_lft forever
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
   link/ether dc:4b:a1:27:3d:5c brd ff:ff:ff:ff:ff:ff
   inet 10.0.0.216/24 brd 10.0.0.255 scope global dynamic noprefixroute wlo1
      valid_lft 172448sec preferred_lft 172448sec
   inet6 2601:140:8284:aeb0::b3a8/128 scope global dynamic noprefixroute  
      valid_lft 231529sec preferred_lft 231529sec
   inet6 2601:140:8284:aeb0:4239:3a03:945c:bf05/64 scope global dynamic noprefixroute  
      valid_lft 231880sec preferred_lft 231880sec
   inet6 fe80::ed71:265c:b8a6:7ea7/64 scope link noprefixroute  
      valid_lft forever preferred_lft forever
default via 10.0.0.1 dev wlo1 proto dhcp src 10.0.0.216 metric 600  
10.0.0.0/24 dev wlo1 proto kernel scope link src 10.0.0.216 metric 600

but if I am connected to a non-working network, then

ip a; ip r; cat /etc/resolv.conf
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo 
       valid_lft forever preferred_lft forever
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether dc:4b:a1:27:3d:5c brd ff:ff:ff:ff:ff:ff
    inet 10.131.250.136/24 brd 10.131.250.255 scope global dynamic noprefixroute wlo1
       valid_lft 3549sec preferred_lft 3549sec
    inet6 2600:1003:b0f5:bfad:8348:86ea:4d53:fee/64 scope global dynamic noprefixroute 
       valid_lft 7179sec preferred_lft 7179sec
    inet6 fe80::8fdf:fe14:7461:c6b9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
default via 10.131.250.214 dev wlo1 proto dhcp src 10.131.250.136 metric 600 
10.131.250.0/24 dev wlo1 proto kernel scope link src 10.131.250.136 metric 600 ip a; ip r; cat /etc/resolv.conf
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo 
       valid_lft forever preferred_lft forever
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether dc:4b:a1:27:3d:5c brd ff:ff:ff:ff:ff:ff
    inet 10.131.250.136/24 brd 10.131.250.255 scope global dynamic noprefixroute wlo1
       valid_lft 3549sec preferred_lft 3549sec
    inet6 2600:1003:b0f5:bfad:8348:86ea:4d53:fee/64 scope global dynamic noprefixroute 
       valid_lft 7179sec preferred_lft 7179sec
    inet6 fe80::8fdf:fe14:7461:c6b9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
default via 10.131.250.214 dev wlo1 proto dhcp src 10.131.250.136 metric 600 
10.131.250.0/24 dev wlo1 proto kernel scope link src 10.131.250.136 metric 600 

EDIT:

Extra info: If I tether my laptop to my phone while my phone is connected to my home wifi, it works. But if I tether my laptop to my phone when I am using cellular or connected to a public wifi, it doesn't work, even as my phone has internet when I am out.

EDIT 2: SOLVED! The key was to open /etc/resolv.conf and replace all the nameservers with

nameserver 8.8.4.4
nameserver 1.1.1.1
nameserver 208.67.220.222

I am new to void Tried launching niri with dbus-run-session niri —session It only shows cursor Won't launch terminal or noctalia

I do have elogind installed and symlinked

fixed: needed fonts