Re: Re: about systemd service leftovers

[Patrice Duroux <patrice.duroux@gmail.com>]

Hi,

Nice I found some similar cases to your one.

But I have even more strange cases like:

$ systemctl list-units --all "alsa*"
  UNIT                 LOAD      ACTIVE   SUB  DESCRIPTION         
● alsa-restore.service not-found inactive dead alsa-restore.service
● alsa-state.service   not-found inactive dead alsa-state.service

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of
SUB.
        SUB    → The low-level unit activation state, values depend on unit
type.

2 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

$ find /etc/systemd /usr/lib/systemd $HOME/.config/systemd -name "alsa*"
(nothing)

$ apt-file search --regex '/alsa-.*\.service'
alsa-utils: /lib/systemd/system/alsa-restore.service
alsa-utils: /lib/systemd/system/alsa-state.service
alsa-utils: /lib/systemd/system/alsa-utils.service
alsa-utils: /lib/systemd/system/sound.target.wants/alsa-restore.service
alsa-utils: /lib/systemd/system/sound.target.wants/alsa-state.service
alsa-utils: /usr/lib/systemd/system/alsa-restore.service
alsa-utils: /usr/lib/systemd/system/alsa-state.service
alsa-utils: /usr/lib/systemd/system/alsa-utils.service
alsa-utils: /usr/lib/systemd/system/sound.target.wants/alsa-restore.service
alsa-utils: /usr/lib/systemd/system/sound.target.wants/alsa-state.service

$ LANG=C dpkg-query -s alsa-utils
dpkg-query: package 'alsa-utils' is not installed and no information is
available
Use dpkg --info (= dpkg-deb --info) to examine archive files.


This package was installed but removed days ago (many reboots since then).

Thanks,
Patrice


ps: on my side, everything started with hacking the following:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053245#20


where it is like a "ghost" service:

$ dpkg-query -s fluidsynth
Package: fluidsynth
Status: install ok installed
Priority: optional
Section: sound
Installed-Size: 112
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Architecture: amd64
Source: fluidsynth (2.3.4-1)
Version: 2.3.4-1+b3
Replaces: iiwusynth
Provides: iiwusynth
Depends: init-system-helpers (>= 1.52), libc6 (>= 2.34), libfluidsynth3 (>=
2.2.0), libglib2.0-0t64 (>= 2.12.0), libpipewire-0.3-0t64 (>= 0.3.6), libsdl2-
2.0-0 (>= 2.0.12), libsystemd0
Recommends: qsynth
Conflicts: iiwusynth
Conffiles:
 /etc/default/fluidsynth 4c778b27917c9dfdd8b0396841d6a390
Description: Real-time MIDI software synthesizer
 Fluidsynth is a real-time midi synthesizer based on the soundfont (sf2 and sf3)
 specifications. It can be used to render MIDI input or MIDI files to audio.
 The MIDI events are read from a MIDI device. The sound is rendered in
 real-time to the sound output device.
Homepage: https://github.com/Fluidsynth/fluidsynth

$ systemctl list-units --all "fluid*"
  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

$ find /etc/systemd /usr/lib/systemd $HOME/.config/systemd -name "fluid*"
/etc/systemd/user/default.target.wants/fluidsynth.service
/usr/lib/systemd/user/fluidsynth.service


but the service is started at least once during the session logging.

Bizarre...