At this point, after some more testing and fiddling, my questions are:
1] why is systemd-shim necessary (see below, after original message)?
2] why is devuan installing xfce4-power-manager with its seemingly
unnecessary recommendation of systemd?
On 03/31/2016 03:52 PM, Boruch Baum wrote:
> Am I the only one who hasn't noticed this yet? What am I missing?
>
> ( posted in parallel at:
> https://git.devuan.org/devuan-packages/sysvinit/issues/14 )
>
> I installed the default devuan desktop package today, using the devuan
> installer, and on my first boot, instead of using the graphical
> installer, I proceeded to C-M-F1 for a command-line login. Upon logging
> in, I received a message:
>
> error message: systemd-logind[3096]: failed to start user service:
> unknown unit: user@???
>
> When I later escalated to su, I received a similar error message.
>
> ps -aux | grep systemd
> shows a root process for /lib/systemd/systemd-logind
>
> The same command on any Manjaro/OpenRC flavor I use yields no systemd
> processes whatsoever.
>
> dpkg -l |grep systemd
> systemd 215-17+deb8u3
> systemd-shim 9-1
> sysv-rc 2.88dsf-59.2+devuan2
> sysvinit-core 2.88dsf-59.2+devuan2
> sysviniit-utils 2.88dsf-59.2+devuan2
>
> Again, comparing with Manjaro/OpenRC, the only package with even a
> passing reference to systemd is:
>
> pacman -Q | grep systemd
> eudev-systemdcompat 228-1
>
> sources.list
> deb-src http://us.mirror.devuan.org/merged/ jessie main non-free
> contrib
> deb http://security.debian.org/ jessie/updates main contrib non-free
> deb-src http://security.debian.org/ jessie/updates main contrib
> non-free
> # jessie-updates, previously known as 'volatile'
> deb http://us.mirror.devuan.org/merged/ jessie-updates main
> contrib non-free
> deb-src http://us.mirror.devuan.org/merged/ jessie-updates main
> contrib non-free
> # jessie-backports, previously on backports.debian.org
> deb http://us.mirror.devuan.org/merged/ jessie-backports main
> contrib non-free
> deb-src http://us.mirror.devuan.org/merged/ jessie-backports
> main contrib non-free
>
Running:
# aptitude why systemd (result: xfce4-power-manager recommends systemd)
# apt-get remove xfce4-power-manager
# apt-get autoremove (removes not just systemd, but also systemd-shim
and its bunch of dependencies)
# apt-get --no-install-recommends install xfce4-power-manager
Upon laptop reboot, and gui login, the xfce4-power-manager functions to
the extent that it:
1] responds to the pressing the power button with it dialog, and that
dialog will successfully logout, suspend, shut sown, reboot.
1.1] However, hibernate did not seem to work. It flickered the screen,
and did a complete shutdown.
2] The xfce4 panel has a power manager widget. All of its functions
work. Hibernate is not offered there as an option.
3] 'xfce4-power-manager --customize' has options for responding to
laptop lid closure, which are not working (tested for options
'lock-screen' and 'suspend'. Running 'acpi_listen' shows that the lid
closure is being detected. Other acpi events are recognized and function
as expected, ie screen brightness.
Re-installing systemd-shim did not change any of this, so I'm curious
why at this point its needed. I uninstalled it a second time.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0