You are not logged in.
apt --no-install-recommends install nvidia-driver nvidia-cudo-mps nvidia-opencl-common nvidia-opencl-icdand/or any other parts you need without the metapackages that pull in nvidia-persistenced.
Looks like you need to install libreoffice-gnome and do not exclude Recommends to get libreoffice-gtk3 automatically.
Yeah, it's only a Recommends, not a Depends. You don't need it. If I remember correctly, it stores some settings or data between reboots.
sudo apt --no-install-recommends install <whatever>In devuan, /var/lib/dbus/machine-id gets replaced on every boot and /etc/machine-id does not exist. (It might be there if you migrated a debian install to devuan, but I'm not certain of that.) See /etc/default/dbus to turn that on or off.
You're not removing the files in your home directory (in ~/.dbus/session-bus/*) and neither does the default devuan installation. See https://dev1galaxy.org/viewtopic.php?pid=58117#p58117
I just have a single line in /etc/rc.local to remove the ones in my home so they get removed before I log in, and then a new one is created matching the one in /var/lib/dbus.
I don't mess with init scripts. I have a vague memory of making desktop buttons to start specific virtual machines with some vbox command that I don't remember. You could probably start it with a command right after user autologin after all necessary services are running.
(Warning. This was so long ago, I might be remembering something with vmware.)
man xsession says:
$HOME/.xsession
is a sequence of commands invoking X clients (or a session manager such as xsm(1)). See the manual page
for xinit for tips on writing an .xsession file.This page talks about the security risks of 'xhost +':
https://www.debian.org/doc/manuals/secu … 04.en.html
If you follow the (very bad) suggestion of many docs, you type xhost + on your machine. This allows any X client to connect to your system. For slightly better security, you can use the command xhost +hostname instead to only allow access from specific hosts.
I just upgraded an excalibur VM and it held back xserver-xlibre-video-amdgpu. I'm not sure if the old version I had was from xlibre-deb or xlibre-debian. There was a mix of packages so I finished upgrading to get all xlibre-debian - except that one package. I realized I didn't have backports enabled, and the instructions don't say which packages you need from backports. I think I figured it out. (the newer version installed without complaint)
apt -t excalibur-backports install mesa-common-dev mesa-libgallium mesa-vulkan-drivers
apt upgrade xserver-xlibre-video-amdgpudaedalus-security is fixed.
Components: main contrib non-free non-free-firmwareMaintenance of bookworm-security got moved to the LTS team. They'll probably hear about it soon and fix it. FWIW, you can still do upgrades, and the nonfree firmware doesn't change often, so you're probably not missing anything.
https://lists.debian.org/debian-announc … 00007.html
It's not listed here for daedalus-security like it is for the other daedalus repos.
https://pkgmaster.devuan.org/merged/dis … /InRelease
Origin: Devuan
Label: Devuan-Security
Suite: oldstable-security
Version: 5.0
Codename: daedalus-security
Date: Tue, 14 Jul 2026 18:50:06 UTC
Valid-Until: Tue, 21 Jul 2026 18:15:06 UTC
Architectures: amd64 arm64 armel armhf i386 ppc64el
Components: main contrib non-free <---- missing "non-free-firmware"I'm guessing it got left out by mistake. You didn't spell it wrong.
This is what I get searching for that device.
apt search BCM4312
broadcom-sta-common/stable 6.30.223.271-26 amd64
Common files for the Broadcom STA Wireless driver
broadcom-sta-dkms/stable 6.30.223.271-26 amd64
dkms source for the Broadcom STA Wireless driver
broadcom-sta-source/stable 6.30.223.271-26 amd64
Source for the Broadcom STA Wireless driver
firmware-b43-installer/stable 1:019-14 all
firmware installer for the b43 driverTry this page for instructions to use packages available in the devuan repository.
https://wiki.debian.org/bcm43xx
I'm not seeing much difference in df output with 6.1.0-48 vs. 6.1.0-50 and also 7.1.3 in freia. Only about 1-2mb difference. Try it without the '-h'.
/dev/mapper/root_fs 199450960 137851664 6.1.0-50
/dev/mapper/root_fs 199450960 137850896 6.1.0-48
/dev/mapper/sda4_crypt 199450960 137853112 7.x
/dev/sda5 29367400 24062932 6.1.0-50
/dev/sda5 29367400 24062712 6.1.0-48
/dev/sda5 29367400 24060396 7.1.3Another approach would be to only use 'xhost +' when you want to be the other user and then 'xhost -' when you're done. Put the following script in your path, make it executable and use it like this. I'm calling it 'swu'. You can call it whatever you like.
Open a terminal.
swu <otheruser>
(run some commands as the other user)
exitHere's the magic sauce:
#!/usr/bin/env bash
# swu
otheruser="$1"
xhost +
su "$otheruser"
xhost -
exit 0I switched to xlibre-debian a few months ago. At that time, there had not been any updates on xlibre-deb since the end of last year.
Here are the xlibre versions I have as of today (2026-07-09)
ii x11proto-dev 2025.1-1+xlibre1 all X11 extension protocols and auxiliary headers
ii xlibre 1:7.8+5 amd64 XLibre X Window System
ii xlibre-archive-keyring 1.0.0-1 all OpenPGP archive certificates of XLibre
ii xlibre-x11-common 1:7.8+5 all X Window System (X.Org) infrastructure
ii xlibre-xutils 1:7.8+5 all X Window System utility programs metapackage
ii xserver-xlibre 1:7.8+5 amd64 XLibre X server
ii xserver-xlibre-common 2:25.2.0-3 all common files used by various X servers
ii xserver-xlibre-core 2:25.2.0-3 amd64 XLibre X server - core server
ii xserver-xlibre-input-all 1:7.8+5 amd64 XLibre X server -- input driver metapackage
ii xserver-xlibre-input-libinput 1:25.0.1-1 amd64 XLibre X server -- libinput input driver
ii xserver-xlibre-video-all 1:7.8+5 amd64 XLibre X server -- output driver metapackage
ii xserver-xlibre-video-amdgpu 25.1.1-3 amd64 XLibre X server -- AMDGPU display driver
ii xserver-xlibre-video-ati 1:25.0.1-1 amd64 XLibre X server -- AMD/ATI display driver wrapper
ii xserver-xlibre-video-fbdev 2:25.0.0-1 amd64 XLibre X server -- fbdev display driver
ii xserver-xlibre-video-nouveau 2:25.0.0-1 amd64 XLibre X server -- Nouveau display driver
ii xserver-xlibre-video-qxl 1:25.0.0-1 amd64 XLibre X server -- QXL display driver
ii xserver-xlibre-video-radeon 1:25.0.1-1 amd64 XLibre X server -- AMD/ATI Radeon display driver
ii xserver-xlibre-video-vesa 2:25.0.0-1 amd64 XLibre X server -- VESA display driver
ii xserver-xlibre-video-vmware 2:25.0.0-1 amd64 XLibre X server -- VMware display driver
ii xserver-xlibre-xephyr 2:25.2.0-3 amd64 nested X serverApparently, I can only split off the posts that are on the same page into the same thread. To read the beginning of this thread, go to https://dev1galaxy.org/viewtopic.php?id=8088
This discussion is continued here:
https://dev1galaxy.org/viewtopic.php?id=8089
Read the last post in the bug thread I linked. The fix has been merged. Package soon.
This is just a guess, but maybe...
apt install intel-microcodeor if one had amd hardware...
apt install amd64-microcodeBut like I said, that's a guess. I could be way off-base. Maybe I don't really know what the question is.
@fredbird67: I just tried extrepo to install xlibre, and it didn't work. The install command gave me an error message about an undefined subroutine. I also figured out that I probably need to run 'extrepo enable xlibre' and it added a file to /etc/apt/sources.list.d/ that points to the wrong (unmaintained) xlibre repository.
The correct way to get xlibre in devuan is to follow the instructions here, provided by NexusSfan:
https://xlibre-debian.github.io/
That way you'll get updates as more things get fixed.
Thanks for the warning. I downloaded the 149.x version before doing the upgrade. Chromium-150 appears for a fraction of a second and disappears. No keyrings here. I get a message when I try to start it from command line:
$ chromium
[0706/080813.360978:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trapIf anyone knows what that means, I'd be interested to hear about it.
Meanwhile...
### Download these (or from your favorite debian mirror)
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium_149.0.7827.196-1~deb13u1_amd64.deb
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium-common_149.0.7827.196-1~deb13u1_amd64.deb
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium-sandbox_149.0.7827.196-1~deb13u1_amd64.deb
### And force-install them
dpkg --force-downgrade -i chromium*.debIt's been reported (multiple times) and there's a suggested patch.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1141488
I expect there will be a new version very soon.
I'm glad you got it installed. The netinstall iso gives you some software choices. The live install just gives you whatever is in the iso.
@Camtaf: The live installer does not need internet to work and does not download anything. If you notice that something is missing for it to work, let me know and I'll add it to the next build.
excalibur-backports tracks trixie-backports. Any delay should be no more than a couple hours. Are you sure it's really in trixie-backports? Searching at packages.debian.org still shows 2026.03.17-1~bpo13+1 in trixie-backports.
Regardless of that, any updates will likely be too late. I just copy the yt-dlp script to my user's bin/ so I don't have to be root to update it, and I update it whenever I use it. (run: yt-dlp -U)
From here: https://github.com/yt-dlp/yt-dlp
Sometimes the bootloader doesn't install correctly. If you know how to chroot, you could boot the live, chroot into the installed system and install grub and then run update-grub to get a boot menu. I left a few steps out of this.
Easier method might be to get the netinstall iso, boot into Rescue mode from the boot menu, and reinstall the bootloader. Those are all menu choices.
For more detailed instructions, we need to know if you're booting uefi or legacy bios (CSM) and whether or not you have a separate partition for /boot.
Thanks for that info. I made a note to myself to try a few different settings when I next make some live-isos. Faster builds and faster boots would be nice.
This is what I have for programs with logind in the name after a recent upgrade to excalibur. Make sure you have all of these.
$ dpkg -l | grep logind
ii elogind 255.17-2 amd64 user, seat and session management daemon
ii libelogind-compat:amd64 255.17-2 amd64 user, seat and session management library compatibility
ii libelogind0:amd64 255.17-2 amd64 user, seat and session management library
ii libpam-elogind:amd64 255.17-2 amd64 elogind PAM module
ii libpolkit-gobject-elogind-1-0:amd64 126-2devuan1+excalibur1 amd64 polkit Authorization API