Karjala's blog

Mine did, and since installing the acpi_call-dkms package from Void Linux the crashes stopped.

I bet there's the similarly-named package for your distro too.

(Will take this post down if laptop crashes again - hasn't happened yet).

List of files in this package:

/usr/share/acpi_call/asus1215n.sh
/usr/share/acpi_call/dellL702X.sh
/usr/share/acpi_call/graphic_card.sh
/usr/share/acpi_call/m11xr2.sh
/usr/share/acpi_call/query_dsdt.pl
/usr/share/acpi_call/turn_off_gpu.sh
/usr/share/acpi_call/windump.c
/usr/share/acpi_call/windump_hack/windump.c
/usr/share/acpi_call/windump_hack/xorg.conf
/usr/share/acpi_call/xorg.conf
/usr/share/doc/acpi_call-dkms/README.md
/usr/src/acpi_call-1.2.2/Makefile
/usr/src/acpi_call-1.2.2/acpi_call.c
/usr/src/acpi_call-1.2.2/dkms.conf

When the env var QT_QPA_PLATFORM is set to wayland-egl (as used to be suggested by this page), the KDE Caps Lock indicator icon in the systray would not appear, and the system settings window would not show the Virtual Desktops screen, as well as a few more systemsettings pages would not appear. Also the clipboard systray app of KDE would misbehave.

Changing its value to just wayland (as suggested by the above link now) fixes these problems.

I did a fresh install of KDE Plasma desktop (v6.4.3) on Void Linux today, and noticed this bug still exists:

• Weather app crashes when I try to configure my current location

I simply followed the instructions here:

https://www.reddit.com/r/voidlinux/comments/1gxae29/fixing_kde_plasma_sleep_suspend_with_void_linux/

You might be able to apply the same solution in other distros, if you happen to have the same problem.

Here's my review of Void linux, a summary of the good and the bad I saw after using this flavour of Linux for well over a year now.

First, install etckeeper.

Then create or edit /etc/.gitignore file to include files that shouldn't be versioned (such as resolv.conf).

Then as root run etckeeper init and etckeeper commit "first commit"

Then create a symbolic link from /etc/cron.daily/etckeeper to /etc/etckeeper/daily.

Then create these three executable files:

/usr/local/bin/xbps-install:

#!/usr/bin/env perl

use v5.40;
use English '$UID';

my $binary = trim((`which -a xbps-install`)[1]) or die "No deep xbps-install binary found";

!system('etckeeper pre-install') or die "Couldn't execute 'etckeeper pre-install'\n" unless $UID;
!system($binary, @ARGV) or die "Couldn't execute this: $binary @ARGV\n";
!system('etckeeper post-install') or die "Couldn't execute 'etckeeper post-install'\n" unless $UID;

/usr/local/bin/xbps-remove:

#!/usr/bin/env perl

use v5.40;
use English '$UID';

my $binary = trim((`which -a xbps-remove`)[1]) or die "No deep xbps-remove binary found";

!system('etckeeper pre-install') or die "Couldn't execute 'etckeeper pre-install'\n" unless $UID;
!system($binary, @ARGV) or die "Couldn't execute this: $binary @ARGV\n";
!system('etckeeper post-install') or die "Couldn't execute 'etckeeper post-install'\n" unless $UID;

/etc/cron.daily/01-record_manual_packages:

#!/bin/sh
xpkg -m > /etc/my_list_of_manual_pkgs

__DONE__

All I had to do was use the Steam package from Flathub instead of the official Void package. And it works fine.

Apparently setting CGROUP_MODE to unified is not at all bad for you, so you should follow all the instructions contained in the incus/README.voidlinux file, including that.

If you still have problems starting Incus containers after that, like I did, your problem could be that you have the elogind service enabled. As everyone on IRC says, you shouldn't have it enabled. Disable it.

You may now ignore my previous #incus-tagged post.

A huge variety of fonts used everywhere to be able to view webpages properly is contained in the following four packages:

noto-fonts-cjk - Chinese, Japanese, Korean
noto-fonts-emoji
noto-fonts-ttf
noto-fonts-ttf-extra

(Found out on IRC)

Void Linux is one of the best Linux distributions out there: It's not maintained by a company and doesn't even have or want sponsors, so it'll stay on the side of users forever. It doesn't use systemd (that many users hate) as its init system, its package manager is very fast (maybe the fastest around), and it's extremely minimal in the amount of software installed by default (good for CPU & disk, the environment, and user-choice of alternatives), and it's a rolling stable distro.

The downside is that it's not for beginners. You'll often need to read documentation (Void's official documentation does a great job) to get things done, and also end-up asking questions in Void's IRC channel to Void's more experienced users.

I did (and still do) a lot of the asking, so I'm providing the most important information I learned there in this series of blog posts tagged #void_linux.

Incus is the replacement of LXD one should use. For some reason it won't work well on Void out of the box after a while, and incus start <container-name> might stop doing anything. How do we fix it?

Looking at /usr/share/doc/incus/README.voidlinux it suggests the following:

Some container configurations may require that the `CGROUP_MODE`
variable in `/etc/rc.conf` be set to `unified`.

One way to solve it is that. I did another solution however, which I found at this github issue. I did the following:

I created this Perl script, called enable_incus somewhere:

#!/usr/bin/env perl

use v5.38;

! -d '/sys/fs/cgroup/systemd' or say("Incus already enabled. Skipping."), exit;

system('sudo mkdir /sys/fs/cgroup/systemd');
system('sudo mount -t cgroup -o none,name=systemd systemd /sys/fs/cgroup/systemd');

say 'OK';

Then I edited /etc/sv/incus/run and added this line near the top:

/path/to/enable_incus

...so that my script gets executed just before incus is launched.

This fixed the problem.