You are not logged in.
I assume you're already rebooted at least once since the upgrade. If not, try that first.
There might be a way to get it to work with consolekit, but I don't know what to tell you to do that. What I would do is install elogind and libpam-elogind and let apt remove consolekit and libpam-ck-connector.
Post the output of the following command to check what's installed:
dpkg -l | egrep "logind|consolekit|libpam|policykit|polkit|upower"What commands did you use to upgrade?
Do you have chimaera, chimaera-security and chimaera-updates all enabled in sources.list (or in synaptic)?
Yes, that's the section for Accessibility features. And the way it's written does sound weird to me. I haven't looked to see if similar wording is used upstream. Thanks for pointing it out.
Sounds like something went wrong in the install. Make sure policykit-1-gnome elogind and libpam-elogind are installed.
The default display manager with xfce is still slim.
How are you looking for it that you can't find it?
In my daedalus install, /etc/debian_version says "bookworm/sid". I think they switch to numbers when it goes stable, so it shows which point-release you are at.
I am unable to reproduce the problem. I just upgraded my daedalus with runit. The dbus version went from 1.12.something+devuan3 to 1.14.0-1devuan1, and my desktop still comes up after a reboot. Looks like it's all working ok.
This line is still present in the runscript:
exec chpst -umessagebus dbus-daemon --system --nofork --nopidfileRunning xfce with lightdm here. What would you like me to check?
Yes, this could be avoided in packaging, but I doubt you can change the debian devs on this. And nobody around here is going to fork the kernel. (that's my prediction)
You can avoid that and a lot of other cruft with this:
cat /etc/apt/apt.conf.d/00norecommends
APT::Install-Recommends "no";I don't know if adding '--no-install-recommends' will work with 'apt upgrade'. If so, that's another way to avoid it.
In debian/devuan, if the package includes runit scripts, runit will use those instead of the sysvinit scripts. Only a few packages include the runit scripts - the gettys, openssh-server and maybe a few others. You can add runscripts from other sources. (salsa.debian.org, antix, more)
Here are two more discussions.
https://dev1galaxy.org/viewtopic.php?id=4342
https://dev1galaxy.org/viewtopic.php?id=3716
I get leftover directories in /media occasionally and have one now. Looks like it's from pmount. I can't be sure if pmount made the error or if I did it by forgetting to pumount before unplugging the device or maybe by unmounting it as root. I just delete the leftovers when I find them.
With no removable media plugged in:
ls -la /media/sde2/
total 8
drwxr-xr-x 2 root root 4096 Apr 22 2021 .
drwxr-xr-x 4 root root 4096 Jan 12 16:36 ..
-rw------- 1 root root 0 Apr 22 2021 .created_by_pmountInteresting observation. I see that the run script for network-manager starts dbus first, and the one for lightdm starts dbus and elogind. So I guess if you write a new run script, you have to make sure you start anything that's needed first. It doesn't seem to be a problem that multiple scripts have 'sv start dbus' in them.
I think the obvious answer for now is that you gotta try it. See if you can break avahi and then fix it by editing /lib/runit/run_sysv_scripts to use /etc/service instead of /etc/sv.
There's also the pool1 iso (DVD) that has 5000 packages. That's in addition to the dvd installer iso. If those two isos don't have what you want, you could get the debian isos and carefully pull packages from there. That should work for anything that doesn't depend on systemd (directly or indirectly).
Great, I will research more about runit. Could also explain how sysvinit service management works?
No, I can't, and in my limited understanding, I thought sysvinit did not do service management, and that's why distros switched to a different init system.
I know this much:
service <service-name> start|stop|restart
or
/etc/init.d/<service-name> start|stop|restartIf you install runit, you only get run scripts for the gettys, and also for openssh-server if you install that. No setup or linking is needed.
There are run scripts available from a couple of locations outside the repository. They can be added after the install. Basic procedure is to copy the script dir for a service to /etc/sv/, stop the init script, and then run
update-service --add /etc/sv/<service>Where <service> is the name of the run script directory and is the same name as the init script.
Put your custom menuentry in /etc/grub.d/40_custom and then run the grub-mkconfig command to regenerate the menu. If you modify grub.cfg directly, your edits will be overwritten the next time the menu gets updated.
And if you have more than one hard disk, you're better off using UUIDs instead of /dev/sda2, in case the drives don't always come up in the same order.
set root='hd0,msdos2'
Really? Not 'hd0,gpt2'? You have msdos partition table with uefi instead of gpt?
Here's an explanation of the error message you got. It's beyond my understanding.
https://stackoverflow.com/questions/353 … cpu0-in-ts
I have a chimaera xfce with runit, and I can share a few data points. Maybe it will help.
If I use pm-suspend to put the system to sleep, it wakes normally when I raise the lid.
If I rely on xfce4-power-manager to put it to sleep when I close the lid, it does not suspend. And the screen is locked when I raise the lid. Both of those behaviors are contrary to the settings in the power manager.
No nvidia here. It's all intel. I don't think runit is the problem, but that's just a guess. FWIW, I have enabled runit scripts for the following services:
acpid connman dbus getty-tty1-6 getty-ttyS0 lightdm
anacron cron elogind irqbalance mdadm sshI have suspected that the installer does not do the same thing every time, but I usually blow through it so quickly, I'm not 100% sure that I really am doing the same thing. This is not new. This has been going on since Debian Lenny.
I've also noticed that if I abort an install and re-start it, some of my choices are saved. I don't know where they get saved, but I'm sure they do.
If you choose Expert install, you will get the choice of installing grub or not. If you let the installer install grub, it will make a boot entry for Void. If you don't let it add the bootloader, you will need to reboot into Void and do whatever it is you do there to add Devuan to the boot menu.
With uefi, each system that installs a bootloader will create a directory on the efi partition without removing any previous directoryies. If you install the Devuan bootloader and then want to go back to letting Void boot the computer, you can remove the Devuan entry with efibootmgr. It will be removed from the list of bootable devices that efibootmgr shows you, but the directory will still be there. You would have to do something extraordinary to screw it up permanently.
The -0500 is my time zone - five hours west of UTC.
If you got the output exactly how you want it, then you now know more about it than I do. ![]()
Edit /etc/rsyslog.conf and comment out the line that starts with $ActionFile... as I did below.
###########################
#### GLOBAL DIRECTIVES ####
###########################
#
# Use traditional timestamp format.
# To enable high precision timestamps, comment out the following line.
#
#$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormatThen run
service rsyslog restartAnd the time stamps will look like this:
2022-02-25T15:55:46.893072-05:00man rsyslogd or man rsyslog.conf for more info.
There's syslog-ng that's very flexible. And there are no plans to change the default syslogger in devuan.
Oh, no sudo. Then it's the minimal-live. Root password is toor and you should use 'su -' to get root, not just 'su' or else log in as root to begin with.
If a newer kernel is needed try one of the daedalus isos or try this iso with a backports kernel that I made for testing new hardware: https://get.refracta.org/files/experime … 0_2148.iso
Are you using the minimal-live or the desktop-live iso? The desktop-live already has firmware-amd-graphics installed. If that doesn't work for you, I'd like to know, thanks. How new is your hardware?
I've been using xfce4 for 10 years, and xscreensaver has always been the default. I never heard of xfce4-screensaver until now. The only bug listed for that package is the accidental upload to unstable. Maybe it'll be ready for daedalus by the time bookworm goes stable.
It's xscreensaver-systemd and the manpage for it says:
The xscreensaver-systemd program is a helper program launched by xscreensaver(1) for systemd(1) or elogind(8) integration. It does two things:
* When the system is about to go to sleep (e.g., the laptop lid has just been closed) it locks the screen just before the system sleeps, by running xscreensaver-command -suspend. When the system wakes up again, it runs xscreensaver-command -deactivate to make the unlock dialog appear immediately. It does this through the org.freedesktop.login1(5) D-Bus interface.
* When another process on the system asks for the screen saver to be inhibited (e.g. because a video is playing) this program periodically runs xscreensaver-command -deactivate to keep the display un-blanked. It does this until the other program asks for it to stop, or exits. It does this through the org.freedesktop.ScreenSaver(5) D-Bus interface.
I'm using nouveau in beowulf, and I have no /lib/firmware/nouveau or any nv98_fuc* files. And there are no error messages about missing firmware. The package you linked is over 10 years old. I don't think it exists now.
Make sure xserver-xorg-video-nouveau is installed. I have firmware-linux-free installed, but I don't see your missing files in it.
If you use a gui frontend network app like connman or network-manager, you should not configure the network in /etc/network/interfaces. They will likely fight with each other. Do one or the other.