Dev1 Galaxy Forum / [SOLVED] libsystemd0 remains

Re: [SOLVED] libsystemd0 remains

dummy@example.com (vlax) — Mon, 06 Jul 2020 02:54:12 +0000

vlax wrote:

elogind libelogind0 libpam-elogind are in "kept back"

I found an alternative solution in another post -> https://dev1galaxy.org/viewtopic.php?pid=23250#p23250 : it's just install the packages

Re: [SOLVED] libsystemd0 remains

dummy@example.com (vlax) — Sat, 04 Jul 2020 14:06:07 +0000

gipi wrote:

UPDATE
After upgrading the linux kernel image (from 4.19.0-8 to 4.19.0-9), I had to move to libelogind0 because X would break, thus removing libsystemd0.
In relation to my previous post, consolekit and policykit-1 didnt have anything to do with fixing the error.

thanks for share your experience; the situation with elogind is similar to mine after upgrading to beowulf in a Refracta (XFCE)

elogind libelogind0 libpam-elogind are in "kept back"

$ apt search libsystemd0
libsystemd0/stable,now 241-7~deb10u4 amd64 [instalado, automático]
  systemd utility library

$ uname -a
 4.19.0-6-amd64 

$ sudo apt upgrade 
...
Los siguientes paquetes se han retenido:
  elogind libelogind0 libpam-elogind
0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 3 no actualizados.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (gipi) — Sat, 13 Jun 2020 07:42:48 +0000

UPDATE

After upgrading the linux kernel image (from 4.19.0-8 to 4.19.0-9), I had to move to libelogind0 because X would break, thus removing libsystemd0.
In relation to my previous post, consolekit and policykit-1 didnt have anything to do with fixing the error.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (gipi) — Thu, 04 Jun 2020 20:03:07 +0000

golinux wrote:

Why are systemd files present in Devuan?
That was before elongind replaced libsystemd. There shouldn't be any libsystemd0 in beowulf.

Technically, there isn't, its a dummy package, but its there as a package.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (golinux) — Thu, 04 Jun 2020 19:46:02 +0000

Why are systemd files present in Devuan?

That was before elongind replaced libsystemd. There shouldn't be any libsystemd0 in beowulf.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (larsH) — Thu, 04 Jun 2020 19:37:15 +0000

libsystemd0 is the one part of systemd it is allmost impossible to avoid being based on debian. But it does not matter. You are still not using systemd for anything practical. But removing this little library would be a huge task with no practical benefit (except avoiding using it).

Have a nice day
Lars H

Re: [SOLVED] libsystemd0 remains

dummy@example.com (Head_on_a_Stick) — Thu, 04 Jun 2020 19:30:08 +0000

gipi wrote:

Turns out it wasn't ok.

Oops, sorry about that.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (gipi) — Thu, 04 Jun 2020 18:14:20 +0000

Head_on_a_Stick wrote:

Yeah, that looks fine — the only package slated for removal is libsystemd0, which is replaced by libelogind0.
Go ahead and run that command as root and without the --simulate switch.

Turns out it wasn't ok. I rand the command and rebooted and X wouldn't work (Can't run in framebuffer mode).
I ended up reinstalling libsystemd0, which installed consolekit and some other libraries (consolekit libcgmanager0 libck-connector0 libnih-dbus1 libnih1 libpam-ck-connector libpolkit-agent-1-0 libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0, I think - got these by seeing what happens when I attempt to purge policykit-1) which removed elogind.
I will just stick with this now.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (Head_on_a_Stick) — Thu, 04 Jun 2020 17:46:05 +0000

Yeah, that looks fine — the only package slated for removal is libsystemd0, which is replaced by libelogind0.

Go ahead and run that command as root and without the --simulate switch.

Re: [SOLVED] libsystemd0 remains

dummy@example.com (gipi) — Thu, 04 Jun 2020 17:43:27 +0000

Head_on_a_Stick wrote:

gipi wrote:
However, when attempting to install elogind (or packages dependent on it, such as pulseaudio), apt states that libsystemd0 will be removed.
The elogind package replaces systemd-logind and provides libelogind0 so that should be fine.
If you're not sure then check (or post) the full output of
apt install --simulate elogind

I ran the command. Here is the output:

# apt install --simulate elogind
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libelogind0 libpam-elogind libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-backend-elogind-1-0 libpolkit-gobject-1-0 libpolkit-gobject-elogind-1-0
  policykit-1 policykit-1-gnome
The following packages will be REMOVED:
  libsystemd0
The following NEW packages will be installed:
  elogind libelogind0 libpam-elogind libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-backend-elogind-1-0 libpolkit-gobject-1-0
  libpolkit-gobject-elogind-1-0 policykit-1 policykit-1-gnome
0 upgraded, 10 newly installed, 1 to remove and 0 not upgraded.
Remv libsystemd0 [241-7~deb10u4] [xserver-xorg-core:amd64 sane-utils:amd64 libapt-pkg5.0:amd64 libprocps6:amd64 rsyslog:amd64 samba-libs:amd64 xserver-xephyr:amd64 libpulse0:amd64 ]
Inst libelogind0 (241.4-2 Devuan:3.0/stable [amd64])
Conf libelogind0 (241.4-2 Devuan:3.0/stable [amd64])
Inst elogind (241.4-2 Devuan:3.0/stable [amd64])
Inst libpam-elogind (241.4-2 Devuan:3.0/stable [amd64])
Inst libpolkit-gobject-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-gobject-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Inst libpolkit-agent-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-backend-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst libpolkit-backend-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Inst policykit-1 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Inst policykit-1-gnome (0.105-7 Devuan:3.0/stable [amd64])
Conf elogind (241.4-2 Devuan:3.0/stable [amd64])
Conf libpam-elogind (241.4-2 Devuan:3.0/stable [amd64])
Conf libpolkit-gobject-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-gobject-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Conf libpolkit-agent-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-backend-elogind-1-0 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf libpolkit-backend-1-0 (0.105-25+devuan8 Devuan:3.0/stable [all])
Conf policykit-1 (0.105-25+devuan8 Devuan:3.0/stable [amd64])
Conf policykit-1-gnome (0.105-7 Devuan:3.0/stable [amd64])
#

I don't actually need elogind (or at least I think I don't), I don't use GNOME, KDE or Wayland. I do however use some gnome icon themes (gnome-extra-icons, gnome-icon-theme, gnome-themes-extra and libsoup-gnome2.4-1), is that related? I can't remove these either because they too pull xorg with them (nor do I want to, I am using arc-theme which depends on gnome-themes-extra).

Re: [SOLVED] libsystemd0 remains

dummy@example.com (Head_on_a_Stick) — Thu, 04 Jun 2020 17:12:04 +0000

gipi wrote:

However, when attempting to install elogind (or packages dependent on it, such as pulseaudio), apt states that libsystemd0 will be removed.

The elogind package replaces systemd-logind and provides libelogind0 so that should be fine.

If you're not sure then check (or post) the full output of

apt install --simulate elogind

[SOLVED] libsystemd0 remains

dummy@example.com (gipi) — Thu, 04 Jun 2020 15:59:25 +0000

I have migrated from Buster to Beowulf, but before I migrated, I already had systemd replace by sysv-init. When I migrated, I managed to remove most of remaining systemd related stuff, but libsystemd0 can't be removed directly because it pulls with itself 54 other packages, including (but not limited to) xorg, xinit and apt.
However, when attempting to install elogind (or packages dependent on it, such as pulseaudio), apt states that libsystemd0 will be removed. I have not followed through with installing elogind, so I don't know if removing libsystemd0 this way would have the same effect as directly attempting to remove it.