You are not logged in.
I just realized that the rc1 desktop-live iso is still using lightdm. I made a new iso today and made sure slim was installed. It seems to be fixed. Please test.
https://files.devuan.org/devuan_excalib … p-live.iso
sha256sum
186c0f8a994d7a1223c16f3cee2763c099e2a4e29fcab9fdef3dbee7a48dc824 devuan_excalibur_6.0.0-rc2_amd64_desktop-live.isoEdit: This one has the wrong version of the Release Notes. I'll wait to hear about slim before I make a new iso.
"Maybe someone who actually knows what they are doing can fix this?"
That quote sounds familiar, as in - I wrote that regarding merging some branches in the documentation section of our git repo. I'm not sure how to best do it without screwing up the repo. It had nothing to do with slim unless someone else said the same words.
Try the version of slim in excalibur-proposed-updates. 1.4.1-1devuan1+excalibur1
code can be fount here: https://git.devuan.org/devuan/slim/src/ … ed-updates
Clarification: Debian and Devuan packages are not incompatible. They are exactly the same packages. We filter out and fork the packages that require systemd. If you use debian sources with devuan sources, you'll still get mostly the same packages, but you won't have the filter, and you'll probably screw up your system by installing things that do require systemd.
zip it into a single file and then encrypt it with gpg. There is gpg for windows.
anacron is useful for systems that are not running 24 hours a day, like laptops for example, so that scheduled cron jobs will run somewhat according to their schedules. It's safe to remove it if you don't need it.
Here's a thought. If you only run the computer for short times, you might be shutting down while it's trying to run a job. Only way I can think of to check this would be to look in syslog right before you shut down. If cron is active, wait for it to finish and then see if shutdown is faster.
The only thing I can help with is zoom. I always refuse the app and eventually there's a link way down at the bottom of the page in small print that says something like "enter zoom with your browser". Works fine with chromium.
Fixed in trixie and forky/sid. (i.e. excalibur and freia/ceres) Older versions not affected.
https://security-tracker.debian.org/tra … 2025-32463
(I duck-searched the CVE with the words 'debian security' - first hit.)
...or with ifupdown it would be
sudo ifdown eth0
sudo ifup eth0Oh, interesting. I don't have that one. I have:
ii acpi-fakekey 0.143-5.1 amd64 tool to generate fake key events
ii acpi-support 0.143-5.1 all scripts for handling many ACPI events
ii acpi-support-base 0.143-5.1 all scripts for handling base ACPI events such as the power button
ii acpid 1:2.0.33-2+b1 amd64 Advanced Configuration and Power Interface event daemonI don't know what you need, but -support and -support-base are probably good ones to try first.
This is just a guess, but you could start by seeing what acpi packages are already installed and compare that to what's available in the repo. Post the output of the first command and maybe someone can tell you what's missing.
# show what's installed
dpkg -l | grep acpi
# see what's available
apt-cache search acpiI think there is a significant security risk - if there's a vulnerability in some piece of software that gives an attacker access to your session, they don't have to bother with escalating privileges because they're already root. Imagine running a web browser as root and allowing all unknown entities to run javascript as root on your machine. Up until recently, xorg always ran as root. It was changed because it was a security risk.
Suse used to allow root login to desktop. I don't know if it's still the case. The default desktop background for root was a picture of a bomb. Good reminder.
The only time I ever log into the desktop as root is if I can't do it as user, and I want to narrow down the problem.
See if this fixes it:
gpg --keyserver keyserver.ubuntu.com --refresh-keysOK, I confirmed the pileup of lease files when there's no system-connections file for eth0. I think I'll include this in the main part of the script. I can put the creation of the generic system-connections file in where the other network configs get removed. That way, if they turn off that section (with netconfig_opt="ip=frommedia" in refractasnapshot.conf) they won't lose their connections file. Removal of all the lease files would be outside of that so it's not turned off. Or probably those should be listed in the rsync excludes file. Tell me if any of this doesn't make sense.
I'm still not understanding this "Wired connection" file. I can't tell if it does anything or not.
I have "Ethernet connection 1.nmconnection" and I moved it out of the way and deleted all the lease files in /var/lib/NetworkManager and rebooted. The missing nmconnection file did not get regenerated, but I do have a working ethernet connection. And note that mine does not have the same name that yours does. This is in daedalus on a laptop and /e/n/i only has the loopback interface defined.
The name of the package is fontsnaps. It's one of the few native devuan packages, but it doesn't have "devuan" in the version string because only forked packages get that.
$ dpkg -S /usr/share/applications/LARGER_FONTS.desktop
fontsnaps: /usr/share/applications/LARGER_FONTS.desktopI think it means that you have to do one of two things - either set the system locale to one that uses UTF-8 or else set the environment variable in that program as explained in the README they mention.
To set the system locale, run dpkg-reconfigure locales as root.
or
To set the locale in the program... (do whatever it says in the README.)
You could try this iso which works on my netbook that has a 32-bit intel atom processor, but it's built from devuan (excalibur) so it will have the same browsers as pure devuan or debian.
For browsers, this iso has lynx, links2 and dillo installed. Firefox and chromium will give you the same error message. Maybe falkon will work. If you already have daedalus installed, falkon is available in the repo and you don't need this iso to try it.
The -0, -1, or -10 at the end of the filename corresponds to the $DISPLAY that was used.
If you switch to console without stopping the desktop, log in and then start a second desktop on :1, you'll get another file in ~/.dbus/session-bus with the same number as /var/lib/dbus/machine-id except with -1 at the end, but only if there's a number in dbus/machine-id. If you delete that file first, you won't get another one in your home unless you also restart dbus. (e.g. cycle through 'init 1' and 'ctrl-d')
> ctrl-alt-f1 to get to console
> log in as user
Run:
startx -- :1 Greenjeans: that is weird about the 21 files with the same time/date. I have no ideas about that.
This will nuke them all:
find / -type f -wholename "*.dbus/session-bus/*" -exec rm {} \;If you have both ceres and freia in sources.list, you will only get ceres packages unless you pin ceres to a lower priority than freia.
There's no -security for ceres or freia, and excalibur-security won't have package versions that match what's in freia/ceres right now.
Excalibur is currently in the twilight zone between testing and stable. It hasn't been declared Stable yet, but it has been disconnected from the unstable to testing pipeline, and it's based on Debian Trixie which is their stable release. That's why freia exists, which will be our next testing suite.
I see a mini.iso in the netboot directory here: https://pkgmaster.devuan.org/devuan/dis … nt/images/
And I checked one of our forked packages (util-linux) and there's one for riscv64 that's the same version as excalibur amd64.
https://pkgmaster.devuan.org/devuan/poo … til-linux/
So it looks like it's possible. The mini.iso is the same as what debian calls (or called?) business card iso. It's like the netinstall but doesn't have firmware in the iso. If you try it, please report back and let us know if it worked. Thanks.
I should have mentioned this in my last post. Default behavior in devuan is for /var/lib/dbus/machine-id to be replaced on reboot. This can be disabled to revert to the upstream default by commenting the line that says: IDTYPE="RANDOM" in /etc/default/dbus. If you do that, the id number will be constant. I don't know if there are other situations where it will change. Maybe on update of dbus packages? That's just a guess.
Nice find. I'll add it to the excludes file. You should probably keep the newest one, but the rest can be deleted.
I've got over 200 of them and I hardly ever reboot. The file name is your dbus machine-id which changes on every reboot in devuan unless you edit /etc/default/dbus or run a script that changes it for you. (I have one)
OK, I just ran my script and changed /var/lib/dbus/machine-id. The file in ~/.dbus/session-bus did not change, but when I switched to root in a terminal, the new id was in /root/.dbus/session-bus. I guess if I log out and in, then user will get the new number.
Maybe this needs another line or two. (Note: Most of this code was borrowed from a live-config script.)
EDIT: Note 2: no guarantee that it won't screw something up that needs a consistent machine-id. Also no guarantee that it will prevent your machine from being identified.
#!/bin/sh
# update-machineid
# Change /var/lib/dbus/machine-id manually.
MACHINEID=/var/lib/dbus/machine-id
UUIDGEN=/usr/bin/dbus-uuidgen
UUIDGEN_OPTS=--ensure
if [ "$(id -u)" -ne 0 ] ; then
echo " You need to be root."
exit 1
fi
if [ -f "${MACHINEID}" ] && [ -x "$UUIDGEN" ] ; then
OLD_ID=$(cat $MACHINEID)
rm -f "${MACHINEID}"
$UUIDGEN $UUIDGEN_OPTS
NEW_ID=$(cat $MACHINEID)
notify-send -t 5000 "Changed dbus machine-id
old: $OLD_ID
new: $NEW_ID"
fi
exit 0b) IDTYPE="RANDOM"
Feature.
e) ntpsec-ntpdate
I'm not sure if that one runs when you reboot. I have a script to run it when I think my time has drifted. Fuzzy, I know.
For full synchronization, use the ntp package.