On Sun, Jan 05, 2020 at 08:30:19PM -0500, tempforever wrote: > 'smee via Dng wrote:
> > When I ran dist-upgrade the first time, it downloaded and unpacked
> > everything okay but then failed with an error that dpkg had errored
> > out. /var/log/dpkg.log didn't give anything helpful but I ended up
> > finding the solution was to run 'apt --fix-broken install' just like
> > that without specifying any package. After running that, dist-upgrade
> > worked.
> The same thing happened with me also today with another ascii-to-beowulf
> upgrade. A problem with some java library, if I remember correctly. If
> needed, I can try to find exactly what it was. And had to manually install
> elogind and libelogind0 after the upgrade.
Just wondering -- did it refuse to boot or be otherwise seriously
unusable until you had installed elogind and libelogind0? Were your
text-only consoles affected? Or did it just interfere with desktops?
And just curious -- never heard of these before systemd. What do they