Re: Re: Re: about systemd service leftovers

2024-04-13 Thread Andrey Rakhmatullin
On Sat, Apr 13, 2024 at 08:30:35PM +0200, Patrice Duroux wrote: > Ok so this is probably due to the version of the DHs used when generating the > postrm script during packaging. How? > On my system, the diversity is quite large regarding all the installed > packages > and the dh_installsystemd: >

Re: Re: Re: about systemd service leftovers

2024-04-13 Thread Patrice Duroux
Ok so this is probably due to the version of the DHs used when generating the postrm script during packaging. On my system, the diversity is quite large regarding all the installed packages and the dh_installsystemd: $ grep -ho 'dh_installsystemd/.\+' /var/lib/dpkg/info/*.postrm | cut -d '/' -

Re: Re: about systemd service leftovers

2024-04-08 Thread Patrice Duroux
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

Re: about systemd service leftovers

2024-04-07 Thread Davide Prina
Patrice Duroux wrote: > By the time on my Sid system, there is an accumulation of: > > $ systemctl list-units --all | grep '●' probably it is best to use $ systemctl list-units --all --state=not-found I try to understand where is the problem For example $ LANG=C dpkg -l podman dpkg-query: no p