Bug#916212: elogind: when upgrading /run/elogind.pid believed even if actual process had died
Arthur Marsh
arthur.marsh at internode.on.net
Tue Dec 11 14:24:42 GMT 2018
Package: elogind
Version: 239.3-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
aptitude upgrade:
[UPGRADE] elogind:amd64 239.1+20181115-1 -> 239.3-1
[UPGRADE] libelogind0:amd64 239.1+20181115-1 -> 239.3-1
[UPGRADE] libpam-elogind:amd64 239.1+20181115-1 -> 239.3-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
When attempting to restart the new version of elogind, there would
be an error message based on the existence of the /run/elogind.pid file,
even when the process did not exist. I had to manually remove
/run/elogind.pid to be able to start the new elogind
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Distributor ID: Devuan
Description: Devuan GNU/Linux beowulf/ceres
Release: 10
Codename: n/a
Architecture: x86_64
Kernel: Linux 4.20.0-rc6 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
Versions of packages elogind depends on:
ii dbus 1.12.10-1+devuan1
ii debconf 1.5.69
ii libacl1 2.2.52-3+b1
ii libc6 2.28-2
ii libelogind0 239.3-1
ii libselinux1 2.8-1+b1
pn libudev1 <none>
ii lsb-base 10.2018112800
Versions of packages elogind recommends:
ii policykit-1 0.105-22
elogind suggests no packages.
-- no debconf information
More information about the Debian-init-diversity
mailing list