Glad you got it fixed. For future reference, those GDBus errors complaining about missing .service files are just noise from programs that expect you to be running systemd, even though they may not require it. I see them often when I start programs from a terminal.

The watermark is barely visible in the gray field. It's the round peppermint candy. (And now I want one. Or a candy cane, but they're all gone.)

I bumped the request up to our traveling guru at dyne.org. Be patient. He moves faster than email.

The *.d directories are a place for the administrator to put customized configurations that will not be wiped out if a new version of the config file is installed/upgraded. Something is programmed to check for files in that directory, and it's letting you know that there's nothing there.

It should be safe to ignore. I don't have that directory on my chimaera or daedalus installations.

There's no metapackage for backports kernels like there is for the main kernel. The only updates you would get would be if the kernel version didn't change. I don't know if that happens with backports kernels.

I vote for staying in this thread. These things may all be related, and someone else might run into similar problems.

Is it a laptop? (Do we need to deal with lid switch and power-manager?)

Look in /var/log/pm-suspend.log to see information related to entering and leaving suspend state.
Look in /var/log/syslog for info about leaving suspend state. Find where it says PM: suspend entry (deep) to see what's happening when you leave suspend. I could not find anytihing in syslog to show when it went into suspend. (And I started with an empty syslog, so there's no way I missed it.)

If you're still having trouble with suspend after you get the packages all straightened out, you might take a look at this page: https://wiki.ubuntu.com/DebuggingKernelSuspend

Someone in IRC gave me the link. I haven't had a chance to read it, and I will be busy with other things today.

If you use apt or apt-get to install elogind and the others, it will put a lot of packages on the autoremove list, but it won't actually remove them. I'm pretty sure once you do that and libelogind0 is in the system, those packages will be taken off the autoremove list.

To see the autoremove list without removing anything.

apt -s autoremove

If it doesn't clear after libelogind0 is installed, you can reinstall consolekit, libpam-ck-connector and libelogind0. Then we can talk about setting up sudo for only shutdown/reboot.

If you use aptitude to install, then the packages will be automatically removed during the install. Don't do that here.

I'm glad you waited. Install libelogind0 first to replace libsystemd0, and that should prevent all those removals from happening. Then install elogind and the others.

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)?

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?

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 --nopidfile

Running xfce with lightdm here. What would you like me to check?