Re: aptitude why (Was: Re: After software update systemd runs into timeouts)

On 2020-08-06 at 07:24, Dan Ritter wrote: > Urs Thuermann wrote: > >> $ aptitude why libpam-systemd >> i systemd Recommends libpam-systemd >> $ aptitude why policykit-1 libpam-systemd >> i A policykit-1 Depends libpam-systemd >> >> But now I see reason: policykit-1 is also installed only becau

Re: aptitude why (Was: Re: After software update systemd runs into timeouts)

On Thu, Aug 6, 2020, 7:42 AM Dan Ritter wrote: > Urs Thuermann wrote: > > $ aptitude why libpam-systemd > > i systemd Recommends libpam-systemd > > $ aptitude why policykit-1 libpam-systemd > > i A policykit-1 Depends libpam-systemd > > > > But now I see reason: policykit-1 is also installed on

Re: aptitude why (Was: Re: After software update systemd runs into timeouts)

Urs Thuermann wrote: > $ aptitude why libpam-systemd > i systemd Recommends libpam-systemd > $ aptitude why policykit-1 libpam-systemd > i A policykit-1 Depends libpam-systemd > > But now I see reason: policykit-1 is also installed only because > virt-manager *recommends* libvirt-daemon-system

aptitude why (Was: Re: After software update systemd runs into timeouts)

David Wright writes: > On Wed 05 Aug 2020 at 22:53:26 (+0200), Urs Thuermann wrote: > > > Should this be considered a bug? Shouldn't 'aptitude why' show the > > packages that depend on it? > > Why not read the man page: > >Note >aptitude why does not perform full dependency >

Re: After software update systemd runs into timeouts

On Wed 05 Aug 2020 at 22:53:26 (+0200), Urs Thuermann wrote: > Should this be considered a bug? Shouldn't 'aptitude why' show the > packages that depend on it? Why not read the man page: Note aptitude why does not perform full dependency resolution; it only displays direct

Re: After software update systemd runs into timeouts

Andrei POPESCU writes: > It's of course possible to reopen the bug if it still exists, though > stretch is oldstable now and in LTS mode. I plan to upgrade to buster, but only after August 15th. > On a server it might be possible to simply not use systemd-logind. E.g. > (at least on buster)

Re: After software update systemd runs into timeouts

On Mi, 05 aug 20, 18:02:12, Urs Thuermann wrote: > Andrei POPESCU writes: > > > The package 'needrestart' hooks into APT and offers to restart any > > affected services. > > Thx, I didn't know needrestart until today, but learned about in in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7

Re: After software update systemd runs into timeouts

Andrei POPESCU writes: > The package 'needrestart' hooks into APT and offers to restart any > affected services. Thx, I didn't know needrestart until today, but learned about in in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823

Re: After software update systemd runs into timeouts

Greg Wooledge writes: > Google led me to > which, although it's for Arch Linux and not Debian, might possibly > be relevant for you. > > In particular, what does "ls -ld /var/run" say? The symlink /var/run -> /run is OK. My problem is probabl

Re: After software update systemd runs into timeouts

On Mi, 05 aug 20, 12:43:18, Urs Thuermann wrote: > I run a server with Debian 9 and haven't resisted the conversion to > systemd strong enough, therefore I now have a couple of problems with > stability and availability. > > One of them is, that often after software updates systemd-logind.service

Re: After software update systemd runs into timeouts

On Wed, Aug 05, 2020 at 12:43:18PM +0200, Urs Thuermann wrote: > Aug 5 11:06:06 bit systemd[1]: systemd-logind.service: Start operation timed > out. Terminating. > Aug 5 11:06:06 bit systemd[1]: Failed to start Login Service. > Aug 5 11:06:06 bit systemd[1]: systemd-logind.service: Unit entered

After software update systemd runs into timeouts

I run a server with Debian 9 and haven't resisted the conversion to systemd strong enough, therefore I now have a couple of problems with stability and availability. One of them is, that often after software updates systemd-logind.service fails to start and ssh logins take a very long time. I sus