Why the eval? The agent is directly executable.

A simpler approach is to just add this line to ~/.xsessionrc:

/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 &

Reference: https://wiki.debian.org/Xsession

In what way does your current configuration differ from this? How is it lacking? I can see that tap-to-click is disabled, is that what you want?

What does "erratic" mean, exactly? It is almost impossible to help you if I can't understand what the problem is.

I would actually recommend switching from the crusty old synaptics & evdev drivers to the newer libinput version:

# apt install xserver-xorg-input-{libinput,synaptics-,evdev-}

If you're a fan of multi-touch gestures then xserver-xorg-input-mtrack is another possibility.

No.

What "refuses to show its files"? Is it the file manager?

Can you mount the stick manually:

sudo mount /dev/sdXY /mnt
ls /mnt
sudo umount /mnt # wait until this command returns the prompt before removing the stick

Replace X & Y with the drive letter and partition number for the USB stick (eg, /dev/sdb1). GParted should show this, I think. If not then check dmesg just after plugging the stick in.

@MLEvD: I only have a very vague idea of how sysvinit scripts work or I would have shared an attempt.

I could share an OpenRC script that would work but that's not very useful for our (now absent) OP.

EDIT: and even then all that /etc/rc?.d/ crap confuses me so it's probably best I don't

.targets ftw!

Manual version here:

https://wiki.archlinux.org/index.php?ti … 407#Debian

The signed kernels can start with SecureBoot enabled but the unsigned versions cannot unless you sign them with your own key and enrol that into the UEFI firmware. The signature in question has been approved by Microsoft.

So you don't see the errors with other distributions that use the 5.15 kernel?

That kernel version is considered "stable" by the developers: https://www.kernel.org/. De{vu,bi}an use an LTS kernel version to suit their "stable" releases for which the API version should not change (which is what "stable" means in that context — it is not a synonym for "reliability" even though that tends to be a happy side-effect).

You can try it but I'm pretty sure the ACPI interface will be the same as for the De{vu,bi}an kernels of the same API version (ie, 5.15).

Actually I've just checked the script and it won't work for Devuan because it runs lsb_release -cs to check the distribution version.

This will modify the script to make it work:

curl 'https://liquorix.net/add-liquorix-repo.sh' | sed 's/^codename=.*/codename=bullseye/' | sudo bash

The apt-transport-https package can be removed afterwards though because the source uses http and that package is no longer needed for https sources in chimaera. I should probably tell the Liquorix folks about that...

It's correct, the quote is so curl parses it correctly. The command still works without the apostrophes though.

I would advise checking the script for any malicious code before piping it through to a privileged shell. I've vetted it myself but you shouldn't trust random people on the interweb

If the new kernels don't help at all go back to the original with

# apt install linux-image-amd64=5.10.84-1 linux-{image,headers}-liquorix-amd64-

Then remove the added sources and the file at /etc/apt/trusted.gpg.d/liquorix-keyring.gpg and run apt update.

See https://bbs.archlinux.org/viewtopic.php?id=266085 & https://bugzilla.kernel.org/show_bug.cgi?id=213023

tl;dr: your motherboard firmware ("BIOS") is somewhat crappy and this is interfering with the new kernel's ACPI interface.

You could try updating the firmware but that can be risky (as seen in the Arch forums thread) and you could also try adding acpi=off as a kernel command line parameter but that might break other stuff. Other acpi= options are available: https://github.com/torvalds/linux/blob/ … ers.txt#L1

The kernel bug report suggests this has been fixed in later versions so perhaps try the backported kernel metapackage and see if that works better. The Liquorix kernel is another option (they have Debian bullseye packages that should be compatible) and that is updated faster than backports so will be better in respect of security.

Because the resume device was set in the initramfs image when you installed Devuan but when you installed another distribution the installer re-formatted the swap partition which changed the UUID that the initramfs image was using to find the swap.

If the initramfs image can't find the resume device (swap) during boot it waits 30 seconds just in case it is slow to attach, hence the delay.

Just to confirm: do you see the message "gave up waiting for suspend/resume device" during the boot delay?

Do you not know how to use a search engine?

I entered that exact message into the search box at startpage.com and this was the top result:

https://forums.debian.net/viewtopic.php?p=703288

And arochester's answer gives this link which explains exactly why that message is totally irrelevant:

https://unix.stackexchange.com/question … 0k-cal-pci

https://lists.debian.org/debian-user/20 … 00866.html

You will have to repeat those steps whenever the swap partition is re-formatted, which most distributions do when they're installed.

EDIT: and if you had actually answered this question the thread would be a lot shorter and you wouldn't have wasted other people's time:

The "gave up waiting for suspend/resume device" message should have been shown during the delay and I would have known exactly what it meant and how to fix it.

No idea about Xfce but systemd runs alsactl store on shutdown and alsactl restore on boot.

/etc/rc.local can be used to run alsa-restore so try that and see if it's enough. Perhaps Xfce runs alsactl store itself.

If the state isn't stored automatically you'll have to add scripts to /ect/rc6.d/ & /etc/rc0.d/ to run alsactl store at reboot and shutdown, respectively. Or create an init script in /etc/init.d/ to add the commands to the appropriate runlevels then run update-rc.d $name_of_script deafults to activate it.

I think pwmconfig just needs to be run once to generate the configuration file (hence the name). So you don't need to start it automatically or keep it running at all.

To cool down the machine after it has operated with the fans disabled by pwmconfig when it attempts to test if it has control over them.

It's not a problem because the /usr/sbin/fancontrol daemon should set the speed of the fans.

Disclaimer: I've never used fancontrol so perhaps wait for steve_v to correct me.

I only claim true love to wind up the h8ers. Sorry to disappoint.

EDIT: oh, you're being ironic. D'oh!