su: The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-4FE4X3/control

Even if this is not the problem here, it's still a problem, gnome-keyring is a pain. It gets off-sync with the user (and their credentials) over the course of builds/installs. Username/password changes on install but nothing corrects the info in gnome-keyring. This is what causes a browser error that is legend now for all it's years of being a bug.

if ! pgrep -x elogind-daemon > /dev/null

to

if ! pgrep -x elogind > /dev/null

and the error message goes away.

Script works to remove cruft in /sys/fs/cgroups, but it doesn't fix a different problem I have in the freia desktop-live iso - gparted works on first login but does not start on subsequent logins. Message in /var/log/auth.log is "The gnome keyring socket is not owned with the same credentials as the user login: /home/devuan/.cache/keyring-4FE4X3/control"  I'm not sure if it's supposed to fix that.

1. install devuan 6 standard setting (xfce desktop)
2. after some time "switch" to mate via tasksel (sudo tasksel) > select mate additionally via (x) and probably selected also "console tools".
3. "sudo apt install desktop-mate*" or similar
after reboot and since then presented with the delay.

since then, uninstalled xfce, updated to devuan 7, but the issue reamain.

will check for xorg.log next time, i suppose  need to use "sudo killall xorg"

Something else is messing with your layout.

You have two options:
- Try to track down what other process is doing this. Look for anything installed that has to do with input methods, keyboards, or languages.
- Just set your own setxkbmap command to run on startup. This is a "duct tape solution" but it should work.

modified

disks=$(sudo smartctl --scan 2>/dev/null | grep -i realtek | sed 's/ .*$//')

to

disks=$(smartctl --scan 2>/dev/null | grep -i realtek | sed 's/ .*$//')

In the meantime, another similar project has been announced:

https://www.theregister.com/os-platform … os/5306589

This time based on NetBSD, with the goal being to avoid LLM generated code.

As a BSD user, I have to admit that I don't see the point in these "vanity" projects.  NetBSD in particular could do with more contributors, not pointless derivatives.

https://www.devuan.org/os/explore lists every page that is available on the site.

I am off to food and AFK now.

i have moved the two files to /etc/ssl/certs

ls -la /etc/ssl/certs just 4 lines shown

lrwxrwxrwx 1 root root     49 Oct 19 18:23  Izenpe.com.pem -> /usr/share/ca-certificates/mozilla/Izenpe.com.crt
-rw-rw-r-- 1 root root   1438 Oct 30 18:38  kiro-optiplex7010-chain.pem
-rw-rw-r-- 1 root root    828 Oct 30 18:38  kiro-optiplex7010.pem
lrwxrwxrwx 1 root root     69 Oct 19 18:23  Microsec_e-Szigno_Root_CA_2009.pem -> /usr/share/ca-certificates/mozilla/Microsec_e-Szigno_Root_CA_2009.crt

from looking at this i need to creat a link to /usr/share/ca-certificates/mozilla/kiro-optiplex7010.crt
do i need to create the kiro-optiplex7010.crt file or will it be created when i make the link?

we have staged/production setup and would like to test all updates on staging before deploying them on production.

Ideally, we would like to pin the exact state of which packages are installed on staging, e.g. by date when installed, so that we get exactly the same on production.

In Debian there is snapshot.debian.org which could be used to do so.

Is there some way to do so in Devuan?

Further questions in respect to differences between Debian and Devuan:

- Are the security updates, except of rebuilds as necessary, identical to Debian?
- Are security updates also collected in point releases like in Debian?

best regards,
Markus

https://files.catbox.moe/11i7lz.png