Are the entire contents of the supplied tarball present in the directory along with the executable? The tarball includes the shared libraries which are needed to run the browser.

The error message in the OP suggests that the browser is looking in /usr/local/share/ for the libraries, which might happen if they're not in the same directory as the executable.

Use this to upload the log file to a pastebin:

curl -F 'f:1=<-' ix.io < ~/.local/share/xorg/Xorg.0.log

And I see that Flatpak no longer relies on systemd so you should probably try that instead when we've fixed this.

Hint: the "src" in the "deb-src" repository lines is short for "source code"

KVM is a kernel module, you want QEMU instead. As you appear to be CLI-phobic then you will probably prefer virt-manager.

Another hint: read the Debian wiki page to which I linked earlier

Thanks!

Well actually...

empty@E485 ~ % cat /proc/1/comm
systemd
empty@E485 ~ %

I can't stand GUI text editors, I use vim. The ed thing was actually intended as a joke but you've clearly had a sense of humour bypass, my condolences.

^ The OP should already have that version, it's pulled in by the linux-image-amd64 metapackage.

What does "used" mean, exactly? Which command(s) did you run?

How, exactly? Which command(s) did you run?

Why not? What happened when you tried? Logs are always useful for troubleshooting that sort of thing.

That tool is obsolete, don't use it. You probably just need to remove any and all X.Org configuration files.

You have no driver (kernel module) for the device. Unfortunately there is no jessie-backports kernel image (AFAICT) so I think you're out of luck.

Can we see

lspci -knn | grep -A2 Audio
aplay -Ll

35MiB used, Alpine Linux (64-bit) & dwm with slstatus for the bar information:

EDIT: I think that system was running openrc-init as PID1 instead of busybox.

The eno interface names are the new "predictable" nomenclature, they are based on the firmware ("BIOS") provided index numbers for on-board devices. This is the first preference for systemd/udev when choosing a name.

See https://www.freedesktop.org/wiki/Softwa … faceNames/

Create that file yourself, it will continue to be honoured in any system that is not using the "predictable" nomenclature.

For Devuan edit the file at /etc/default/grub and add the desired parameter to the GRUB_CMDLINE_LINUX line then run update-grub (as root).

Well the situation is markedly better for new AMD cards because AMD themselves are effectively writing the open source drivers and they now out-perform the proprietary version for most tasks.

For beowulf you will need something like this:

deb http://deb.devuan.org/merged beowulf main
#deb-src http://deb.devuan.org/merged beowulf main

deb http://deb.devuan.org/merged beowulf-security main
#deb-src http://deb.devuan.org/merged beowulf-security main

deb http://deb.devuan.org/merged beowulf-updates main
#deb-src http://deb.devuan.org/merged beowulf-updates main

Un-comment the deb-src lines if you ever need to patch packages, the contrib & non-free components can be added after main if you want them (heathen!).

It's more reliable than VB and *much* more secure (VB relies on blobs).

Apparently virt-manager is quite good but I've never used it myself. CLI ftw!

Use apt source to download the source packages, which will include the upstream tarball from which the binary packages are derived.

ed, man! man ed!

https://pkginfo.devuan.org/stage/beowul … .15-1.html

GUIs are for suckers...

Catalyst ("fglrx") doesn't work any more.

So what is the output of lsb-release -a on your system?

If it's not a Devuan problem then I can submit a PR to neofetch with a correction if needed, Dylan is a very receptive developer.