Upgrades to 18.04 fail due to systemd-shim

[Kees Cook]

[Impact]

 * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart.

 * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package.

[Test Case]

 * monitor drop-off of upgrades with below reported problem

 * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie.

lxc launch ubuntu-daily:xenial test-shim-upgrade
lxc exec test-shim-upgrade
apt update
apt install systemd-shim
wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
apt install ./systemd-shim_10-3_amd64.deb
sed 's/xenial/bionic/' -i /etc/apt/sources.list
apt update
apt install systemd

this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this:

The following packages will be REMOVED:
  systemd-shim
...
Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim'
...

[Regression Potential]

 * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state.

[Other Info]

 * original bug report

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  systemd-shim
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 71.7 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 632222 files and directories currently installed.)
Removing systemd-shim (9-1bzr4ubuntu1) ...
Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim'
dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed
dpkg: error processing package systemd-shim (--remove):
 subprocess installed post-removal script returned error exit status 2
Errors were encountered while processing:
 systemd-shim
E: Sub-process /usr/bin/dpkg returned an error code (1)

Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade.

[Steve Langasek (vorlon)]

The error complains that files will be overwritten, but this code runs in the systemd-shim postrm script, which is after systemd-shim's files have been removed from disk. What does 'dpkg -S /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' report in this situation?

[Shane Synan (digitalcircuit)]

I just ran into this situation myself. After I received the error report and let the upgrade recover, running the dpkg command gives me...

diversion by systemd-shim from: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
diversion by systemd-shim to: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
systemd: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service

[Shane Synan (digitalcircuit)]

Apologies for the double-comment.

Following the guide from here...
https://askubuntu.com/questions/838491/systemd-shim-error-after-upgrading-from-16-04-to-16-10/838673#838673

I was able to continue upgrading with these commands:

[let upgrader bail out and run dpkg configure]
sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

Then, to optionally finish cleaning up, check what packages are no longer supported using the command from...
https://askubuntu.com/questions/691051/how-to-get-the-list-of-the-unsupported-packages-mentioned-during-the-os-upgrade

awk -F\' '/demoted/ {gsub(/ /,"\n",$2); print $2}' /var/log/dist-upgrade/main.log

The system in question appears to work fine now, just the usual cleanup of changes for any major OS upgrade.

[Steve Langasek (vorlon)]

On Sun, Jun 10, 2018 at 07:38:26PM -0000, Shane Synan wrote:
> I just ran into this situation myself. After I received the error
> report and let the upgrade recover, running the dpkg command gives me...

> diversion by systemd-shim from: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
> diversion by systemd-shim to: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> systemd: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service

Thanks for the information. And does the file
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service exist on
your system? If so, please attach it to the bug report so we can see its
contents and try to figure out where it came from.

[Steve Langasek (vorlon)]

Thanks, that confirms that the file existed before the upgrade. I would still need a copy of this file to try to understand where it came from.

[Kees Cook (kees)]

# cat /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
[D-BUS Service]
Name=org.freedesktop.systemd1
User=root
Exec=/usr/lib/x86_64-linux-gnu/systemd-shim

[Steve Langasek (vorlon)]

That certainly matches the copy of the file shipped in systemd-shim in xenial. But I'm at a loss to explain why it's present on your system after dpkg has removed the package.

[Kees Cook (kees)]

# dpkg -L systemd-shim
/.
/usr
/usr/lib
/usr/lib/i386-linux-gnu
/usr/lib/i386-linux-gnu/systemd-shim
/usr/lib/i386-linux-gnu/systemd-shim-cgroup-release-agent
/usr/lib/systemd
/usr/lib/systemd/ntp-units.d
/usr/lib/systemd/ntp-units.d/systemd-shim.list
/usr/share
/usr/share/dbus-1
/usr/share/dbus-1/system-services
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
package diverts others to: /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
/usr/share/doc
/usr/share/doc/systemd-shim
/usr/share/doc/systemd-shim/copyright
/usr/share/doc/systemd-shim/changelog.Debian.gz

# cat /var/lib/dpkg/info/systemd-shim.postrm
#!/bin/sh

set -e

if [ "$1" = remove -o "$1" = purge ]; then
        dpkg-divert --package systemd-shim --remove --rename --divert \
                /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd \
                /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service
fi

# Automatically added by dh_installdeb
dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.systemd-shim.conf 8-4 systemd-shim -- "$@"
# End automatically added section
# Automatically added by dh_installdeb
dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.systemd1.conf 6-2 systemd-shim -- "$@"
# End automatically added section

The error was:

Removing systemd-shim (9-1bzr4ubuntu1) ...
Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim'
dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed

I have no idea what the dpkg-divert error means there, but I assume there's some interaction I'm not following with the divert...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Richard Eames (naddiseo)]

I ran into this running a `do-release-upgrade -d` on a xenial machine at $work. The upgrade failed partway through leaving the system in a partial upgrade state afaict; lsb-release -a reports 18.04, but the apt sources are still xenial.

[Simmo Saan (sim642)]

I just ran into this during do-release-upgrade from 16.04.5 to 18.04.1 as well among other issues. The suggested mv solution worked.

I ended up in a situation where some to-be-upgraded packages like network-manager-gnome were removed at first but never reinstalled, which turned out to be problematic, although I'm not certain it was this interruption's fault that apt somehow "forgot".

[udippel (udippel)]

I have tried with mine: bug #1787367.
Okay, the usual update / upgrade runs through now, though what got was just the removal of the systemd-shim, and nothing else. feh and flowblade have been kept back. OpenOffice 6.0 (just as example) remains uninstalled. How can I know what else remains missing? The awk command lists a dozen of rather irrelevant stuff.

Thanks anyway for the trick to remove the systemd-shim blocker!

[David Anderson (davea42)]

I thought one aspect of the bug that nobody specifically highlighted was interesting:

dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed

Notice the replacement has an extra .systemd on the end of the name.

The fix instructions reported above worked for me.

[Marco Trevisan (Treviño) (3v1n0)]

A friend of mine also got this on upgrade (he's not skilled so was quite critical to him):

Whole error on further upgrades were (sorry for italian locale):

I seguenti pacchetti NUOVI saranno installati:
  libmsgpackc2 tmate
0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati.
1 non completamente installati o rimossi.
È necessario scaricare 0 B/259 kB di archivi.
Dopo quest'operazione, verranno occupati 652 kB di spazio su disco.
Continuare? [S/n] s
(Lettura del database... 402540 file e directory attualmente installati.)
Rimozione di systemd-shim (9-1bzr4ubuntu1)...
Rimozione di "deviazione di /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd da systemd-shim"
dpkg-divert: errore: la rinomina comprende il sovrascrivere "/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service" con
   il file "/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd", non consentito
dpkg: errore nell'elaborare il pacchetto systemd-shim (--remove):
 installed systemd-shim package post-removal script subprocess returned error exit status 2
Si sono verificati degli errori nell'elaborazione:
 systemd-shim
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Laurent Bigonville (bigon)]

Just upgraded today from 16.04 to 18.04 and I got the same issue.

The systemd-shim package was still installed, the only way I had to uninstall it was to force remove systemd, then I was able to purge systemd-shim and reinstall systemd

I made sure that xenial was up2date before starting the update (using update-manager) to bionic

[Dimitri John Ledkov (xnox)]

systemd-shim removed from the archive, so cannot be fixed really.

[Mark Fraser (launchpad-mfraz)]

Just upgraded my server from 16.04 to 18.04 and I also came across this error.

Managed to carry on by doing /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak

[elowney (erik-lowney-b)]

Just another "me too". Renamed the file to bak, and had a semi-working system. Also had to reinstall Nvidia driver since i was stuck at 640x480, that was fun....

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 239-7ubuntu10

---------------
systemd (239-7ubuntu10) cosmic; urgency=medium

  * units: Disable journald Watchdog (LP: #1773148)
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)

 -- Dimitri John Ledkov <email address hidden> Thu, 04 Oct 2018 15:58:51 +0100

[José Enrique (atreides1960)]

Hy, in this moment I can't update my laptop or install any package or
program
Greetings

El mié., 17 oct. 2018 23:11, Brian Murray <email address hidden> escribió:

> ** Tags added: bugpattern-written
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> In Progress
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial.
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
> systemd-shim
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 71.7 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 632222 files and directories currently installed.)
> Removing systemd-shim (9-1bzr4ubuntu1) ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
> dpkg: error processing package systemd-shim (--remove):
> subprocess installed post-removal script returned error exit status 2
> Errors were encountered while processing:
> systemd-shim
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Commenting out the dpkg-divert in systemd-shim's postrm solved this
> for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

[Alejandro (vertanes)]

Histill having the same problem  with the "systemd-shim"I don't know how to fix it May be I will format everything and reinstall Ubuntu 18 againgreetings

      From: José Enrique <email address hidden>
 To: <email address hidden>
 Sent: Thursday, October 18, 2018 3:10 AM
 Subject: Re: [Bug 1773859] Re: upgrades to 18.04 fail

Hy, in this moment I can't update my laptop or install any package or
program
Greetings

El mié., 17 oct. 2018 23:11, Brian Murray <email address hidden> escribió:

> ** Tags added: bugpattern-written
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  In Progress
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial.
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing their removal via conflicts should bring the system into
>  an expected state.
>
>  [Other Info]
>
>    * original bug report
>
>
>  $ sudo apt upgrade
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Calculating upgrade... Done
>  The following packages will be REMOVED:
>    systemd-shim
>  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>  1 not fully installed or removed.
>  After this operation, 71.7 kB disk space will be freed.
>  Do you want to continue? [Y/n] y
>  (Reading database ... 632222 files and directories currently installed.)
>  Removing systemd-shim (9-1bzr4ubuntu1) ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
>    different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>  dpkg: error processing package systemd-shim (--remove):
>    subprocess installed post-removal script returned error exit status 2
>  Errors were encountered while processing:
>    systemd-shim
>  E: Sub-process /usr/bin/dpkg returned an erro...

[Colin Belton (colinbelton)]

I got mine fixed with the following:

Firstly removed gdm:

sudo apt purge gdm gdm3 etc

Then installed:
sudo apt-get install --reinstall ubuntu-desktop
sudo reboot

On Mon, Oct 22, 2018 at 8:52 AM Alejandro <email address hidden>
wrote:

> Histill having the same problem with the "systemd-shim"I don't know how
> to fix it May be I will format everything and reinstall Ubuntu 18
> againgreetings
>
> From: José Enrique <email address hidden>
> To: <email address hidden>
> Sent: Thursday, October 18, 2018 3:10 AM
> Subject: Re: [Bug 1773859] Re: upgrades to 18.04 fail
>
> Hy, in this moment I can't update my laptop or install any package or
> program
> Greetings
>
> El mié., 17 oct. 2018 23:11, Brian Murray <email address hidden> escribió:
>
> > ** Tags added: bugpattern-written
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1792241).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> > upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> > Fix Released
> > Status in systemd-shim package in Ubuntu:
> > Won't Fix
> > Status in systemd source package in Bionic:
> > In Progress
> > Status in systemd-shim source package in Bionic:
> > Won't Fix
> > Status in systemd source package in Cosmic:
> > Fix Released
> > Status in systemd-shim source package in Cosmic:
> > Won't Fix
> >
> > Bug description:
> > [Impact]
> >
> > * Some systems fail to upgrade due to conflicts between systemd and
> > the (now removed from the archive) systemd-shim / upstart.
> >
> > * Instead of trying to work out what's the problem in ordering /
> > removal of diverts, ensure that systemd is never unpacked whilst
> > systemd-shim/upstart are still on disk. Thus declare conflicts against
> > systemd-shim/upstart packages in systemd package.
> >
> > [Test Case]
> >
> > * monitor drop-off of upgrades with below reported problem
> >
> > * Check that it is possible to upgrade to bionic's libpam-systemd
> > from xenial with systemd-shim installed on xenial.
> >
> > [Regression Potential]
> >
> > * systemd-shim/upstart are both removed and not supported in bionic,
> > thus forcing their removal via conflicts should bring the system into
> > an expected state.
> >
> > [Other Info]
> >
> > * original bug report
> >
> >
> > $ sudo apt upgrade
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Calculating upgrade... Done
> > The following packages will be REMOVED:
> > systemd-shim
> > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> > 1 not fully installed or removed.
> > After this operation, 71.7 kB disk space will be freed.
> > Do you want to continue? [Y/n] y
> > (Reading database ... 632222 files and directories currently installed.)
> > Removing systemd-shim (9-1bzr4ubuntu1) ...
> > Removing 'diversion of
> > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> >
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> > by systemd-shim'
> > dpkg-divert: error: rename involves overwriting
> > '/usr/share/dbus-1/sy...

[Jacob Ngalya (ngalya-2018.)]

this package failed to upgrade when is upgrading to ubuntu 18.04, may you help me to resolve this issue

[Colin Belton (colinbelton)]

Sure, happy to try
On Thu, Oct 25, 2018 at 2:05 PM Jacob Ngalya <email address hidden>
wrote:

> this package failed to upgrade when is upgrading to ubuntu 18.04, may
> you help me to resolve this issue
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1793916).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> In Progress
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial.
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
> systemd-shim
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 71.7 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 632222 files and directories currently installed.)
> Removing systemd-shim (9-1bzr4ubuntu1) ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
> dpkg: error processing package systemd-shim (--remove):
> subprocess installed post-removal script returned error exit status 2
> Errors were encountered while processing:
> systemd-shim
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Commenting out the dpkg-divert in systemd-shim's postrm solved this
> for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

[Nick Kirkendall (nrk)]

Did this upgrade fail to happen because of the age of my desktop? It's a Core 2

[Łukasz Zemczak (sil2100)]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Jason M. (jason-ubuntu)]

Similar experience on a DO instance. Initial do-release-upgrade failure due to bug #1793932: exim4 deprecated conffile issue. Now recovery is systemd-shim (9-1bzr4ubuntu1) blocked. @digitalcircuit's 2018-06-10 suggestion above did not work for me. Will restore 16.04 and try again later.

Details:
$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  cgmanager libcryptsetup4 rename
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  debconf debconf-i18n exim4-base exim4-daemon-heavy libapparmor-perl libgdbm-compat4 libgdbm5 libhtml-parser-perl
  liblocale-gettext-perl libmailutils5 libnet-ssleay-perl libpam-systemd libperl5.26 libreadline7 libsocket6-perl libssl1.1
  libtext-charwidth-perl libtext-iconv-perl networkd-dispatcher perl perl-base perl-modules-5.26 perl-openssl-defaults
  systemd
Suggested packages:
  debconf-doc debconf-utils libterm-readline-gnu-perl libgtk3-perl libnet-ldap-perl libqtgui4-perl libqtcore4-perl eximon4
  exim4-doc-html | exim4-doc-info spf-tools-perl swaks gdbm-l10n libdata-dump-perl perl-doc libterm-readline-gnu-perl
  | libterm-readline-perl-perl systemd-container policykit-1
The following packages will be REMOVED:
  libperl5.22 perl-modules-5.22 systemd-shim
The following NEW packages will be installed:
  libgdbm-compat4 libgdbm5 libmailutils5 libperl5.26 libreadline7 libssl1.1 networkd-dispatcher perl-modules-5.26
  perl-openssl-defaults
The following packages will be upgraded:
  debconf debconf-i18n exim4-base exim4-daemon-heavy libapparmor-perl libhtml-parser-perl liblocale-gettext-perl
  libnet-ssleay-perl libpam-systemd libsocket6-perl libtext-charwidth-perl libtext-iconv-perl perl perl-base systemd
15 upgraded, 9 newly installed, 3 to remove and 389 not upgraded.
3 not fully installed or removed.
Need to get 0 B/14.9 MB of archives.
After this operation, 3,000 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
(Reading database ... 97832 files and directories currently installed.)
Removing systemd-shim (9-1bzr4ubuntu1) ...
Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim'
dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed
dpkg: error processing package systemd-shim (--remove):
 subprocess installed post-removal script returned error exit status 2
Errors were encountered while processing:
 systemd-shim

[José Enrique (atreides1960)]

Thanks a lot for your help. I resolved my problem erasing systemd-shim and
updating.
I'll try new solution in another pc.
Kind regards

El lun., 19 nov. 2018 15:11, Łukasz Zemczak <email address hidden>
escribió:

> Hello Kees, or anyone else affected,
>
> Accepted systemd into bionic-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed. Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: systemd (Ubuntu Bionic)
> Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed verification-needed-bionic
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Fix Committed
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial.
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading...

[José Enrique (atreides1960)]

I solved problem sttoping services and erasing systemd-shim upon console.
After I could updating my pc, also, from console
Kind regards

El mié., 17 oct. 2018 23:11, Brian Murray <email address hidden> escribió:

> ** Tags added: bugpattern-written
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> In Progress
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial.
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
> systemd-shim
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 71.7 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 632222 files and directories currently installed.)
> Removing systemd-shim (9-1bzr4ubuntu1) ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
> dpkg: error processing package systemd-shim (--remove):
> subprocess installed post-removal script returned error exit status 2
> Errors were encountered while processing:
> systemd-shim
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Commenting out the dpkg-divert in systemd-shim's postrm solved this
> for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/177385...

[Jason M. (jason-ubuntu)]

CONFIRM: @digitalcircuit's 2018-06-10 recommendation works to complete do-release-upgrade from 16.04.5 to 18.04.1, after addressing exim4 issue.

[Łukasz Zemczak (sil2100)]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Alejandro (vertanes)]

Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make this test in the last weeks I will make them as soon as possibleRegardsAlejandro

      From: Łukasz Zemczak <email address hidden>
 To: <email address hidden>
 Sent: Tuesday, November 20, 2018 9:21 AM
 Subject: [Bug 1773859] Please test proposed package

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

--
You received this bug notification because you are subscribed to a
duplicate bug report (1796221).
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The...

[José Enrique (atreides1960)]

Lo siento Alejandro, no soy Lucas
 Saludos

El mar., 27 nov. 2018 18:51, Alejandro <email address hidden>
escribió:

> Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> this test in the last weeks I will make them as soon as
> possibleRegardsAlejandro
>
> From: Łukasz Zemczak <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, November 20, 2018 9:21 AM
> Subject: [Bug 1773859] Please test proposed package
>
> Hello Kees, or anyone else affected,
>
> Accepted systemd into bionic-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed. Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1796221).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Fix Committed
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial, ie.
>
> lxc launch ubuntu-daily:xenial test-shim-upgrade
> lxc exec test-shim-upgrade
> apt update
> apt install systemd-shim
> wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> apt install ./syste...

[Alejandro (vertanes)]

José Enrique,disculpa y gracias por contestarme.Quería pedirte si me puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se cómo accederloMuchas graciasAlejandro
      -
      -
         -

      -
         - -----------------
José Enrique <email address hidden>

      -
      - Nov 19 at 2:01 PM

   - To <email address hidden>
      -

Message body
Thanks a lot for your help. I resolved my problem erasing systemd-shim and
updating.
I'll try new solution in another pc.
Kind regards

      From: José Enrique <email address hidden>
 To: <email address hidden>
 Sent: Tuesday, November 27, 2018 3:01 PM
 Subject: Re: [Bug 1773859] Please test proposed package

Lo siento Alejandro, no soy Lucas
 Saludos

El mar., 27 nov. 2018 18:51, Alejandro <email address hidden>
escribió:

> Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> this test in the last weeks I will make them as soon as
> possibleRegardsAlejandro
>
>      From: Łukasz Zemczak <email address hidden>
>  To: <email address hidden>
>  Sent: Tuesday, November 20, 2018 9:21 AM
>  Subject: [Bug 1773859] Please test proposed package
>
> Hello Kees, or anyone else affected,
>
> Accepted systemd into bionic-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1796221).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  Fix Committed
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-...

[b0w (kiwifunk)]

Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how
to fix it, but if in 7 days it will be available for everyone i will just
wait the update.
Greetings!

On Thu, Nov 29, 2018 at 12:31 PM Alejandro <email address hidden>
wrote:

> José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se
> cómo accederloMuchas graciasAlejandro
> -
> -
> -
>
>
> -
> - -----------------
> José Enrique <email address hidden>
>
> -
> - Nov 19 at 2:01 PM
>
>
> - To <email address hidden>
> -
>
> Message body
> Thanks a lot for your help. I resolved my problem erasing systemd-shim and
> updating.
> I'll try new solution in another pc.
> Kind regards
>
>
> From: José Enrique <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, November 27, 2018 3:01 PM
> Subject: Re: [Bug 1773859] Please test proposed package
>
> Lo siento Alejandro, no soy Lucas
> Saludos
>
> El mar., 27 nov. 2018 18:51, Alejandro <email address hidden>
> escribió:
>
> > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > this test in the last weeks I will make them as soon as
> > possibleRegardsAlejandro
> >
> > From: Łukasz Zemczak <email address hidden>
> > To: <email address hidden>
> > Sent: Tuesday, November 20, 2018 9:21 AM
> > Subject: [Bug 1773859] Please test proposed package
> >
> > Hello Kees, or anyone else affected,
> >
> > Accepted systemd into bionic-proposed. The package will build now and be
> > available at
> > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> > hours, and then in the -proposed repository.
> >
> > Please help us by testing this new package. See
> > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> > to enable and use -proposed. Your feedback will aid us getting this
> > update out to other Ubuntu users.
> >
> > If this package fixes the bug for you, please add a comment to this bug,
> > mentioning the version of the package you tested and change the tag from
> > verification-needed-bionic to verification-done-bionic. If it does not
> > fix the bug for you, please add a comment stating that, and change the
> > tag to verification-failed-bionic. In either case, without details of
> > your testing we will not be able to proceed.
> >
> > Further information regarding the verification process can be found at
> > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> > advance for helping!
> >
> > N.B. The updated package will be released to -updates after the bug(s)
> > fixed by this package have been verified and the package has been in
> > -proposed for a minimum of 7 days.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1796221).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> > upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> > Fix Released
> > Status in systemd-shim package in Ubuntu:
> > Won't Fix
> > Status in systemd source package in Bionic:...

[b0w (kiwifunk)]

Is there any package available that fix this thing?

[José Enrique (atreides1960)]

Hola mira esta solución.

Saludos.

El jue., 29 nov. 2018 22:51, b0w <email address hidden> escribió:

> Yo tambien tengo dudas de como resolverlo! I Still have some doubts on how
> to fix it, but if in 7 days it will be available for everyone i will just
> wait the update.
> Greetings!
>
> On Thu, Nov 29, 2018 at 12:31 PM Alejandro <email address hidden>
> wrote:
>
> > José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> > puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No
> se
> > cómo accederloMuchas graciasAlejandro
> > -
> > -
> > -
> >
> >
> > -
> > - -----------------
> > José Enrique <email address hidden>
> >
> > -
> > - Nov 19 at 2:01 PM
> >
> >
> > - To <email address hidden>
> > -
> >
> > Message body
> > Thanks a lot for your help. I resolved my problem erasing systemd-shim
> and
> > updating.
> > I'll try new solution in another pc.
> > Kind regards
> >
> >
> > From: José Enrique <email address hidden>
> > To: <email address hidden>
> > Sent: Tuesday, November 27, 2018 3:01 PM
> > Subject: Re: [Bug 1773859] Please test proposed package
> >
> > Lo siento Alejandro, no soy Lucas
> > Saludos
> >
> > El mar., 27 nov. 2018 18:51, Alejandro <email address hidden>
> > escribió:
> >
> > > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > > this test in the last weeks I will make them as soon as
> > > possibleRegardsAlejandro
> > >
> > > From: Łukasz Zemczak <email address hidden>
> > > To: <email address hidden>
> > > Sent: Tuesday, November 20, 2018 9:21 AM
> > > Subject: [Bug 1773859] Please test proposed package
> > >
> > > Hello Kees, or anyone else affected,
> > >
> > > Accepted systemd into bionic-proposed. The package will build now and
> be
> > > available at
> > > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> > > hours, and then in the -proposed repository.
> > >
> > > Please help us by testing this new package. See
> > > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on
> how
> > > to enable and use -proposed. Your feedback will aid us getting this
> > > update out to other Ubuntu users.
> > >
> > > If this package fixes the bug for you, please add a comment to this
> bug,
> > > mentioning the version of the package you tested and change the tag
> from
> > > verification-needed-bionic to verification-done-bionic. If it does not
> > > fix the bug for you, please add a comment stating that, and change the
> > > tag to verification-failed-bionic. In either case, without details of
> > > your testing we will not be able to proceed.
> > >
> > > Further information regarding the verification process can be found at
> > > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you
> in
> > > advance for helping!
> > >
> > > N.B. The updated package will be released to -updates after the bug(s)
> > > fixed by this package have been verified and the package has been in
> > > -proposed for a minimum of 7 days.
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > d...

[José Enrique (atreides1960)]

Mira esta solucion
Saludos

El jue., 29 nov. 2018 19:31, Alejandro <email address hidden>
escribió:

> José Enrique,disculpa y gracias por contestarme.Quería pedirte si me
> puedes contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se
> cómo accederloMuchas graciasAlejandro
> -
> -
> -
>
>
> -
> - -----------------
> José Enrique <email address hidden>
>
> -
> - Nov 19 at 2:01 PM
>
>
> - To <email address hidden>
> -
>
> Message body
> Thanks a lot for your help. I resolved my problem erasing systemd-shim and
> updating.
> I'll try new solution in another pc.
> Kind regards
>
>
> From: José Enrique <email address hidden>
> To: <email address hidden>
> Sent: Tuesday, November 27, 2018 3:01 PM
> Subject: Re: [Bug 1773859] Please test proposed package
>
> Lo siento Alejandro, no soy Lucas
> Saludos
>
> El mar., 27 nov. 2018 18:51, Alejandro <email address hidden>
> escribió:
>
> > Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> > this test in the last weeks I will make them as soon as
> > possibleRegardsAlejandro
> >
> > From: Łukasz Zemczak <email address hidden>
> > To: <email address hidden>
> > Sent: Tuesday, November 20, 2018 9:21 AM
> > Subject: [Bug 1773859] Please test proposed package
> >
> > Hello Kees, or anyone else affected,
> >
> > Accepted systemd into bionic-proposed. The package will build now and be
> > available at
> > https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> > hours, and then in the -proposed repository.
> >
> > Please help us by testing this new package. See
> > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> > to enable and use -proposed. Your feedback will aid us getting this
> > update out to other Ubuntu users.
> >
> > If this package fixes the bug for you, please add a comment to this bug,
> > mentioning the version of the package you tested and change the tag from
> > verification-needed-bionic to verification-done-bionic. If it does not
> > fix the bug for you, please add a comment stating that, and change the
> > tag to verification-failed-bionic. In either case, without details of
> > your testing we will not be able to proceed.
> >
> > Further information regarding the verification process can be found at
> > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> > advance for helping!
> >
> > N.B. The updated package will be released to -updates after the bug(s)
> > fixed by this package have been verified and the package has been in
> > -proposed for a minimum of 7 days.
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1796221).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> > upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> > Fix Released
> > Status in systemd-shim package in Ubuntu:
> > Won't Fix
> > Status in systemd source package in Bionic:
> > Fix Committed
> > Status in systemd-shim source package in Bionic:
> > Won't Fix
> > Status in systemd source package in Cosmic:
> > Fix Releas...

[Dimitri John Ledkov (xnox)]

systemd now correctly conflicts with systemd-shim, and installing both simultaniously is now even harder:

$ sudo apt install systemd-shim
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  python3-netifaces
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  cgmanager cgroup-lite libcgmanager0 libnih-dbus1
Suggested packages:
  pm-utils
The following packages will be REMOVED:
  cloud-init friendly-recovery init libnss-systemd libpam-systemd netplan.io nplan plymouth plymouth-theme-ubuntu-text policykit-1 snapd
  systemd systemd-sysv ubuntu-minimal ubuntu-standard
The following NEW packages will be installed:
  cgmanager cgroup-lite libcgmanager0 libnih-dbus1 systemd-shim
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  init systemd-sysv (due to init)
0 upgraded, 5 newly installed, 15 to remove and 0 not upgraded.
Need to get 147 kB of archives.
After this operation, 77.6 MB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] ^C
ubuntu@ubuntu:~$ dpkg-query -W systemd
systemd 237-3ubuntu10.10

Thus it should also cause removal of systemd-shim on upgrades. Marking as validation done.

[Brian Murray (brian-murray)]

The upload of systemd that was purported to fix this bug report was superseded by a security update of systemd so the fix is no longer available.

[juan angel Mora (peloblanco)]

Muchas gracias por la información.
Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago
y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a
la ultima versión 16. y no lo hago por miedo a que se me desbarate todo
de nuevo, cual es tu consejo?
Un saludo

El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
escribió:

> The upload of systemd that was purported to fix this bug report was
> superseded by a security update of systemd so the fix is no longer
> available.
>
> ** Changed in: systemd (Ubuntu Bionic)
> Status: Fix Committed => Triaged
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1787843).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Triaged
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial, ie.
>
> lxc launch ubuntu-daily:xenial test-shim-upgrade
> lxc exec test-shim-upgrade
> apt update
> apt install systemd-shim
> wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> apt install ./systemd-shim_10-3_amd64.deb
> sed 's/xenial/bionic/' -i /etc/apt/sources.list
> apt update
> apt install systemd
>
> this currently passes, however, systemd-shim remains installed. It
> should be removed instead. Apt install systemd should have lines like
> this:
>
> The following packages will be REMOVED:
> systemd-shim
> ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> ...
>
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
> systemd-shim
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or remo...

[José Enrique (atreides1960)]

Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
quieras perder y actualizarla a 18-04.
Funcionar funciona pero estás a punto de que no se actualice más, y puedes
tener problemas de seguridad, ojo se trata de una actualización importante,
que debes realizar, seguramente en dos pasos, dos actualizaciones
parciales. Primero a 16 y luego a 18-04.
Configura el gestor de actualizaciones a versiones LTS, no obstante la
18-04 tiene soporte para 10 años.
Saludos

El mar., 29 ene. 2019 22:15, juan angel Mora <email address hidden>
escribió:

> Muchas gracias por la información.
> Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago
> y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a
> la ultima versión 16. y no lo hago por miedo a que se me desbarate todo
> de nuevo, cual es tu consejo?
> Un saludo
>
>
> El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
> escribió:
>
> > The upload of systemd that was purported to fix this bug report was
> > superseded by a security update of systemd so the fix is no longer
> > available.
> >
> > ** Changed in: systemd (Ubuntu Bionic)
> > Status: Fix Committed => Triaged
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1787843).
> > https://bugs.launchpad.net/bugs/1773859
> >
> > Title:
> > upgrades to 18.04 fail
> >
> > Status in systemd package in Ubuntu:
> > Fix Released
> > Status in systemd-shim package in Ubuntu:
> > Won't Fix
> > Status in systemd source package in Bionic:
> > Triaged
> > Status in systemd-shim source package in Bionic:
> > Won't Fix
> > Status in systemd source package in Cosmic:
> > Fix Released
> > Status in systemd-shim source package in Cosmic:
> > Won't Fix
> >
> > Bug description:
> > [Impact]
> >
> > * Some systems fail to upgrade due to conflicts between systemd and
> > the (now removed from the archive) systemd-shim / upstart.
> >
> > * Instead of trying to work out what's the problem in ordering /
> > removal of diverts, ensure that systemd is never unpacked whilst
> > systemd-shim/upstart are still on disk. Thus declare conflicts against
> > systemd-shim/upstart packages in systemd package.
> >
> > [Test Case]
> >
> > * monitor drop-off of upgrades with below reported problem
> >
> > * Check that it is possible to upgrade to bionic's libpam-systemd
> > from xenial with systemd-shim installed on xenial, ie.
> >
> > lxc launch ubuntu-daily:xenial test-shim-upgrade
> > lxc exec test-shim-upgrade
> > apt update
> > apt install systemd-shim
> > wget
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> > apt install ./systemd-shim_10-3_amd64.deb
> > sed 's/xenial/bionic/' -i /etc/apt/sources.list
> > apt update
> > apt install systemd
> >
> > this currently passes, however, systemd-shim remains installed. It
> > should be removed instead. Apt install systemd should have lines like
> > this:
> >
> > The following packages will be REMOVED:
> > systemd-shim
> > ...
> > Removing 'diversion of
> > /usr/share/dbus-1/system...

[juan angel Mora (peloblanco)]

La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
LTS.
Vale la pena actualizarla?
Graacias

El mar., 29 ene. 2019 a las 22:30, José Enrique (<email address hidden>)
escribió:

> Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
> quieras perder y actualizarla a 18-04.
> Funcionar funciona pero estás a punto de que no se actualice más, y puedes
> tener problemas de seguridad, ojo se trata de una actualización importante,
> que debes realizar, seguramente en dos pasos, dos actualizaciones
> parciales. Primero a 16 y luego a 18-04.
> Configura el gestor de actualizaciones a versiones LTS, no obstante la
> 18-04 tiene soporte para 10 años.
> Saludos
>
> El mar., 29 ene. 2019 22:15, juan angel Mora <email address hidden>
> escribió:
>
> > Muchas gracias por la información.
> > Si no es mucho consultarte, a veces cuando me pide actualizaciones las
> hago
> > y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a
> > la ultima versión 16. y no lo hago por miedo a que se me desbarate todo
> > de nuevo, cual es tu consejo?
> > Un saludo
> >
> >
> > El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
> > escribió:
> >
> > > The upload of systemd that was purported to fix this bug report was
> > > superseded by a security update of systemd so the fix is no longer
> > > available.
> > >
> > > ** Changed in: systemd (Ubuntu Bionic)
> > > Status: Fix Committed => Triaged
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1787843).
> > > https://bugs.launchpad.net/bugs/1773859
> > >
> > > Title:
> > > upgrades to 18.04 fail
> > >
> > > Status in systemd package in Ubuntu:
> > > Fix Released
> > > Status in systemd-shim package in Ubuntu:
> > > Won't Fix
> > > Status in systemd source package in Bionic:
> > > Triaged
> > > Status in systemd-shim source package in Bionic:
> > > Won't Fix
> > > Status in systemd source package in Cosmic:
> > > Fix Released
> > > Status in systemd-shim source package in Cosmic:
> > > Won't Fix
> > >
> > > Bug description:
> > > [Impact]
> > >
> > > * Some systems fail to upgrade due to conflicts between systemd and
> > > the (now removed from the archive) systemd-shim / upstart.
> > >
> > > * Instead of trying to work out what's the problem in ordering /
> > > removal of diverts, ensure that systemd is never unpacked whilst
> > > systemd-shim/upstart are still on disk. Thus declare conflicts
> against
> > > systemd-shim/upstart packages in systemd package.
> > >
> > > [Test Case]
> > >
> > > * monitor drop-off of upgrades with below reported problem
> > >
> > > * Check that it is possible to upgrade to bionic's libpam-systemd
> > > from xenial with systemd-shim installed on xenial, ie.
> > >
> > > lxc launch ubuntu-daily:xenial test-shim-upgrade
> > > lxc exec test-shim-upgrade
> > > apt update
> > > apt install systemd-shim
> > > wget
> > >
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> > > apt install ./systemd-shim_10-3_amd64.deb
> > > sed 's/xenial/bionic/' -i...

[José Enrique (atreides1960)]

Si claro, luego te dirá de pasar a la 18-04.
Saludos

El mar., 29 ene. 2019 22:50, juan angel Mora <email address hidden>
escribió:

> La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
> LTS.
> Vale la pena actualizarla?
> Graacias
>
>
> El mar., 29 ene. 2019 a las 22:30, José Enrique (<
> <email address hidden>>)
> escribió:
>
> > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
> > quieras perder y actualizarla a 18-04.
> > Funcionar funciona pero estás a punto de que no se actualice más, y
> puedes
> > tener problemas de seguridad, ojo se trata de una actualización
> importante,
> > que debes realizar, seguramente en dos pasos, dos actualizaciones
> > parciales. Primero a 16 y luego a 18-04.
> > Configura el gestor de actualizaciones a versiones LTS, no obstante la
> > 18-04 tiene soporte para 10 años.
> > Saludos
> >
> > El mar., 29 ene. 2019 22:15, juan angel Mora <<email address hidden>
> >
> > escribió:
> >
> > > Muchas gracias por la información.
> > > Si no es mucho consultarte, a veces cuando me pide actualizaciones las
> > hago
> > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero
> actualizar a
> > > la ultima versión 16. y no lo hago por miedo a que se me desbarate
> todo
> > > de nuevo, cual es tu consejo?
> > > Un saludo
> > >
> > >
> > > El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
> > > escribió:
> > >
> > > > The upload of systemd that was purported to fix this bug report was
> > > > superseded by a security update of systemd so the fix is no longer
> > > > available.
> > > >
> > > > ** Changed in: systemd (Ubuntu Bionic)
> > > > Status: Fix Committed => Triaged
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to a
> > > > duplicate bug report (1787843).
> > > > https://bugs.launchpad.net/bugs/1773859
> > > >
> > > > Title:
> > > > upgrades to 18.04 fail
> > > >
> > > > Status in systemd package in Ubuntu:
> > > > Fix Released
> > > > Status in systemd-shim package in Ubuntu:
> > > > Won't Fix
> > > > Status in systemd source package in Bionic:
> > > > Triaged
> > > > Status in systemd-shim source package in Bionic:
> > > > Won't Fix
> > > > Status in systemd source package in Cosmic:
> > > > Fix Released
> > > > Status in systemd-shim source package in Cosmic:
> > > > Won't Fix
> > > >
> > > > Bug description:
> > > > [Impact]
> > > >
> > > > * Some systems fail to upgrade due to conflicts between systemd
> and
> > > > the (now removed from the archive) systemd-shim / upstart.
> > > >
> > > > * Instead of trying to work out what's the problem in ordering /
> > > > removal of diverts, ensure that systemd is never unpacked whilst
> > > > systemd-shim/upstart are still on disk. Thus declare conflicts
> > against
> > > > systemd-shim/upstart packages in systemd package.
> > > >
> > > > [Test Case]
> > > >
> > > > * monitor drop-off of upgrades with below reported problem
> > > >
> > > > * Check that it is possible to upgrade to bionic's libpam-systemd
> > > > from xenial with systemd-shim installed on xenial, ie.
> > > >
> > > > lxc launch ...

[José Enrique (atreides1960)]

Una cosa.
Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden
con el 18
Si es un equipo moderno sin problemas.
También puedes valorar en utilizar escritorios más ligeros con equipos
antiguos XCFE Xubuntu o LXDE Lubuntu.
Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en
un Netbook con 1 Giga Lubuntu.
Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de la 18
04.
Saludos

El mar., 29 ene. 2019 22:50, juan angel Mora <email address hidden>
escribió:

> La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
> LTS.
> Vale la pena actualizarla?
> Graacias
>
>
> El mar., 29 ene. 2019 a las 22:30, José Enrique (<
> <email address hidden>>)
> escribió:
>
> > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
> > quieras perder y actualizarla a 18-04.
> > Funcionar funciona pero estás a punto de que no se actualice más, y
> puedes
> > tener problemas de seguridad, ojo se trata de una actualización
> importante,
> > que debes realizar, seguramente en dos pasos, dos actualizaciones
> > parciales. Primero a 16 y luego a 18-04.
> > Configura el gestor de actualizaciones a versiones LTS, no obstante la
> > 18-04 tiene soporte para 10 años.
> > Saludos
> >
> > El mar., 29 ene. 2019 22:15, juan angel Mora <<email address hidden>
> >
> > escribió:
> >
> > > Muchas gracias por la información.
> > > Si no es mucho consultarte, a veces cuando me pide actualizaciones las
> > hago
> > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero
> actualizar a
> > > la ultima versión 16. y no lo hago por miedo a que se me desbarate
> todo
> > > de nuevo, cual es tu consejo?
> > > Un saludo
> > >
> > >
> > > El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
> > > escribió:
> > >
> > > > The upload of systemd that was purported to fix this bug report was
> > > > superseded by a security update of systemd so the fix is no longer
> > > > available.
> > > >
> > > > ** Changed in: systemd (Ubuntu Bionic)
> > > > Status: Fix Committed => Triaged
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to a
> > > > duplicate bug report (1787843).
> > > > https://bugs.launchpad.net/bugs/1773859
> > > >
> > > > Title:
> > > > upgrades to 18.04 fail
> > > >
> > > > Status in systemd package in Ubuntu:
> > > > Fix Released
> > > > Status in systemd-shim package in Ubuntu:
> > > > Won't Fix
> > > > Status in systemd source package in Bionic:
> > > > Triaged
> > > > Status in systemd-shim source package in Bionic:
> > > > Won't Fix
> > > > Status in systemd source package in Cosmic:
> > > > Fix Released
> > > > Status in systemd-shim source package in Cosmic:
> > > > Won't Fix
> > > >
> > > > Bug description:
> > > > [Impact]
> > > >
> > > > * Some systems fail to upgrade due to conflicts between systemd
> and
> > > > the (now removed from the archive) systemd-shim / upstart.
> > > >
> > > > * Instead of trying to work out what's the problem in ordering /
> > > > removal of diverts, ensure that systemd is never unpacked whilst
> > > > systemd-shim/upstart are still on disk. T...

[juan angel Mora (peloblanco)]

¡Gracias!

El mié., 30 ene. 2019 a las 12:21, José Enrique (<email address hidden>)
escribió:

> Una cosa.
> Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden
> con el 18
> Si es un equipo moderno sin problemas.
> También puedes valorar en utilizar escritorios más ligeros con equipos
> antiguos XCFE Xubuntu o LXDE Lubuntu.
> Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en
> un Netbook con 1 Giga Lubuntu.
> Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de la 18
> 04.
> Saludos
>
> El mar., 29 ene. 2019 22:50, juan angel Mora <email address hidden>
> escribió:
>
> > La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
> > LTS.
> > Vale la pena actualizarla?
> > Graacias
> >
> >
> > El mar., 29 ene. 2019 a las 22:30, José Enrique (<
> > <email address hidden>>)
> > escribió:
> >
> > > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que
> no
> > > quieras perder y actualizarla a 18-04.
> > > Funcionar funciona pero estás a punto de que no se actualice más, y
> > puedes
> > > tener problemas de seguridad, ojo se trata de una actualización
> > importante,
> > > que debes realizar, seguramente en dos pasos, dos actualizaciones
> > > parciales. Primero a 16 y luego a 18-04.
> > > Configura el gestor de actualizaciones a versiones LTS, no obstante la
> > > 18-04 tiene soporte para 10 años.
> > > Saludos
> > >
> > > El mar., 29 ene. 2019 22:15, juan angel Mora <
> <email address hidden>
> > >
> > > escribió:
> > >
> > > > Muchas gracias por la información.
> > > > Si no es mucho consultarte, a veces cuando me pide actualizaciones
> las
> > > hago
> > > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero
> > actualizar a
> > > > la ultima versión 16. y no lo hago por miedo a que se me desbarate
> > todo
> > > > de nuevo, cual es tu consejo?
> > > > Un saludo
> > > >
> > > >
> > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray (<email address hidden>)
> > > > escribió:
> > > >
> > > > > The upload of systemd that was purported to fix this bug report was
> > > > > superseded by a security update of systemd so the fix is no longer
> > > > > available.
> > > > >
> > > > > ** Changed in: systemd (Ubuntu Bionic)
> > > > > Status: Fix Committed => Triaged
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (1787843).
> > > > > https://bugs.launchpad.net/bugs/1773859
> > > > >
> > > > > Title:
> > > > > upgrades to 18.04 fail
> > > > >
> > > > > Status in systemd package in Ubuntu:
> > > > > Fix Released
> > > > > Status in systemd-shim package in Ubuntu:
> > > > > Won't Fix
> > > > > Status in systemd source package in Bionic:
> > > > > Triaged
> > > > > Status in systemd-shim source package in Bionic:
> > > > > Won't Fix
> > > > > Status in systemd source package in Cosmic:
> > > > > Fix Released
> > > > > Status in systemd-shim source package in Cosmic:
> > > > > Won't Fix
> > > > >
> > > > > Bug description:
> > > > > [Impact]
> > > > >
> > > > > * Some systems fail to upgrade due to conflicts between systemd
> > a...

[loluchayjose (loluchayjose)]

Looks like I can't install anything (or most things) until this gets fixed. Is there a consensus on the proper way to uninstall systemd-shim?

[José Enrique (atreides1960)]

Good night looking for internet, there are many solutions. The treat can
help you. Kind regards.
Buenas noches, busca en Internet hay muchas soluciones a este problema,
creo que este hilo puede ayudarte.
Saludos

El mié., 10 abr. 2019 22:11, loluchayjose <email address hidden>
escribió:

> Looks like I can't install anything (or most things) until this gets
> fixed. Is there a consensus on the proper way to uninstall systemd-shim?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Triaged
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial, ie.
>
> lxc launch ubuntu-daily:xenial test-shim-upgrade
> lxc exec test-shim-upgrade
> apt update
> apt install systemd-shim
> wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> apt install ./systemd-shim_10-3_amd64.deb
> sed 's/xenial/bionic/' -i /etc/apt/sources.list
> apt update
> apt install systemd
>
> this currently passes, however, systemd-shim remains installed. It
> should be removed instead. Apt install systemd should have lines like
> this:
>
> The following packages will be REMOVED:
> systemd-shim
> ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> ...
>
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via conflicts should bring the system into
> an expected state.
>
> [Other Info]
>
> * original bug report
>
> $ sudo apt upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
> systemd-shim
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 71.7 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 632222 files and directories currently installed....

[loluchayjose (loluchayjose)]

Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es "sudo apt purge gdm etc."... "etc." que?

Varios dicen "borrar"... borrar como?

Tu dijiste: "I solved problem sttoping services and erasing systemd-shim upon console.
After I could updating my pc, also, from console"... Qué servicios paraste, y como? Tengo que hacerlo en Safe Mode?

Uno de los últimos dice: "The upload of systemd that was purported to fix this bug report was superseded by a security update of systemd so the fix is no longer available." Así que por lo que se ve, esa solucion ya no sirve.

[José Enrique (atreides1960)]

Hola creo recordar que utilicé estos comandos:
sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop
.systemd1. servicio / usr / share / dbus-1 / system- servicios /
org.freedesktop .systemd1. Servicio. bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

A mi me funcionó correctamente, pero no lo almacené.
Puede ser otro problema con el mismo resultado.
Otra solución, que apliqué en un laptop fue sacar un back-up de los
archivos de usuario, documentos, descargas...
Y reinstalar la nueva versión desde 0
Sañudos

El jue., 11 abr. 2019 0:45, loluchayjose <email address hidden>
escribió:

> Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es
> "sudo apt purge gdm etc."... "etc." que?
>
> Varios dicen "borrar"... borrar como?
>
> Tu dijiste: "I solved problem sttoping services and erasing systemd-shim
> upon console.
> After I could updating my pc, also, from console"... Qué servicios
> paraste, y como? Tengo que hacerlo en Safe Mode?
>
> Uno de los últimos dice: "The upload of systemd that was purported to
> fix this bug report was superseded by a security update of systemd so
> the fix is no longer available." Así que por lo que se ve, esa solucion
> ya no sirve.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Triaged
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial, ie.
>
> lxc launch ubuntu-daily:xenial test-shim-upgrade
> lxc exec test-shim-upgrade
> apt update
> apt install systemd-shim
> wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> apt install ./systemd-shim_10-3_amd64.deb
> sed 's/xenial/bionic/' -i /etc/apt/sources.list
> apt update
> apt install systemd
>
> this currently passes, however, systemd-shim remains installed. It
> should be removed instead. Apt install systemd should have lines like
> this:
>
> The following packages will be REMOVED:
> systemd-shim
> ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.system...

[Hontvári József Levente (hontvari)]

This worked for me in quite a few upgrades. Before starting the upgrade to 18.04, still on 16.04:

mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service{,.bak}
apt purge systemd-shim

It does not work in the opposite order! If you try that way, apt purge will complain about the service file.

[Alejandro (vertanes)]

 I ended up uninstalling everything and installing the 18.04 from sctratch.Thanks for your help

    On Thursday, April 11, 2019, 12:26:08 PM GMT-3, José Enrique <email address hidden> wrote:

 Hola creo recordar que utilicé estos comandos:
sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop
.systemd1. servicio / usr / share / dbus-1 / system- servicios /
org.freedesktop .systemd1. Servicio. bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

A mi me funcionó correctamente, pero no lo almacené.
Puede ser otro problema con el mismo resultado.
Otra solución, que apliqué en un laptop fue sacar un back-up de los
archivos de usuario, documentos, descargas...
Y reinstalar la nueva versión desde 0
Sañudos

El jue., 11 abr. 2019 0:45, loluchayjose <email address hidden>
escribió:

> Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es
> "sudo apt purge gdm etc."... "etc." que?
>
> Varios dicen "borrar"... borrar como?
>
> Tu dijiste: "I solved problem sttoping services and erasing systemd-shim
> upon console.
> After I could updating my pc, also, from console"... Qué servicios
> paraste, y como? Tengo que hacerlo en Safe Mode?
>
> Uno de los últimos dice: "The upload of systemd that was purported to
> fix this bug report was superseded by a security update of systemd so
> the fix is no longer available." Así que por lo que se ve, esa solucion
> ya no sirve.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  Triaged
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial, ie.
>
>  lxc launch ubuntu-daily:xenial test-shim-upgrade
>  lxc exec test-shim-upgrade
>  apt update
>  apt install systemd-shim
>  wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>  apt install ./systemd-shim_10-3_amd64.deb
>  sed 's/xenial/bionic/' -i /etc/apt/sources.list
>  apt update
>  apt install systemd
>
>  this currently passes, however, systemd-shim remains installed. It
>  should be removed instead. Apt install systemd should have lines like
>  this:
>
>  The following packages will be REMOVED:
>    sy...

[L-reimann (l-reimann)]

Still affects me on release upgrade from latest 16.04 LTS with hwe installed...

[Steve Langasek (vorlon)]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Kees Cook (kees)]

Hmm, I don't have any systems left with systemd-shim installed, so I can't do a "real world" test of this. The test case is the description seems reasonable, so if that passes, I would consider this bug fixed. :) Thanks!

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Balint Reczey (rbalint)]

Verified with systemd 237-3ubuntu10.31:

root@x-lp1773859:~# apt install ./systemd-shim_10-3_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'systemd-shim' instead of './systemd-shim_10-3_amd64.deb'
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
Suggested packages:
  pm-utils
The following packages will be upgraded:
  systemd-shim
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 0 B/20.0 kB of archives.
After this operation, 6144 B of additional disk space will be used.
Get:1 /root/systemd-shim_10-3_amd64.deb systemd-shim amd64 10-3 [20.0 kB]
(Reading database ... 25776 files and directories currently installed.)
Preparing to unpack .../systemd-shim_10-3_amd64.deb ...
Leaving 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim'
Unpacking systemd-shim (10-3) over (9-1bzr4ubuntu1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.4) ...
Setting up systemd-shim (10-3) ...
N: Can't drop privileges for downloading as file '/root/systemd-shim_10-3_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
root@x-lp1773859:~# sed 's/xenial/bionic/' -i /etc/apt/sources.list
root@x-lp1773859:~# apt update
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
...

Get:32 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [2428 B]
Fetched 19.7 MB in 3s (5284 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
396 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@x-lp1773859:~# sed -i s/backports/proposed/ /etc/apt/sources.list
root@x-lp1773859:~# apt update
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease [242 kB]
Hit:4 http://security.ubuntu.com/ubuntu bionic-security InRelease
...
Get:12 http://archive.ubuntu.com/ubuntu bionic-proposed/multiverse Translation-en [572 B]
Fetched 401 kB in 1s (349 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
396 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@x-lp1773859:~# apt install systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cgmanager libcgmanager0 libfreetype6
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libargon2-0 libc-bin libc6 libcryptsetup12 libgcrypt20 libgpg-error0 libip4tc0 libjson-c3 libpam-systemd
  libsystemd0 locales networkd-dispatcher
Suggested packages:
  glibc-doc rng-tools iw | wireless-tools systemd-container
The following packages will be REMOVED:
  systemd-shim
The following NEW packages will be installed:
  libargon2-...

[Balint Reczey (rbalint)]

https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=systemd&period=month&version=237-3ubuntu10.31

For the record the 16.04 -> 18.04 upgrade issue is still seen:

https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=systemd&period=month&version=237-3ubuntu10.31

While the added Conflicts does work in the test case it does not seem to fix the upgrade in all cases and a follow-up fix may be needed.

[Steve Langasek (vorlon)]

Yes, based on the analysis that the failure is caused by buggy *rm scripts in an obsolete and already-uninstalled version of the systemd-shim package, I expected to still see failures with the new version.

But this should not block the SRU, even though the Conflicts is not actually doing anything.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 237-3ubuntu10.31

---------------
systemd (237-3ubuntu10.31) bionic; urgency=medium

  [ Dimitri John Ledkov ]
  * Add conflicts with upstart and systemd-shim. (LP: #1773859)
  * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
    - units: Disable journald Watchdog (LP: #1773148)
  * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
    - cryptsetup: add support for sector-size= option (LP: #1776626)
  * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
    - systemctl: correctly proceed to immediate shutdown if scheduling fails
      (LP: #1670291)
  * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
    - networkd: add support to set IPv6MTUBytes (LP: #1671951)

 -- Balint Reczey <email address hidden> Mon, 30 Sep 2019 17:23:17 +0200

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Jacob Ngalya (ngalya-2018.)]

Ok, thanks.

On Thu, 10 Oct 2019 at 05:51, Launchpad Bug Tracker <
<email address hidden>> wrote:

> This bug was fixed in the package systemd - 237-3ubuntu10.31
>
> ---------------
> systemd (237-3ubuntu10.31) bionic; urgency=medium
>
> [ Dimitri John Ledkov ]
> * Add conflicts with upstart and systemd-shim. (LP: #1773859)
> * d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
> - units: Disable journald Watchdog (LP: #1773148)
> * d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
> - cryptsetup: add support for sector-size= option (LP: #1776626)
> * d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
> - systemctl: correctly proceed to immediate shutdown if scheduling
> fails
> (LP: #1670291)
> * d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
> - networkd: add support to set IPv6MTUBytes (LP: #1671951)
>
> -- Balint Reczey <email address hidden> Mon, 30 Sep 2019 17:23:17 +0200
>
> ** Changed in: systemd (Ubuntu Bionic)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
> upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
> Fix Released
> Status in systemd-shim package in Ubuntu:
> Won't Fix
> Status in systemd source package in Bionic:
> Fix Released
> Status in systemd-shim source package in Bionic:
> Won't Fix
> Status in systemd source package in Cosmic:
> Fix Released
> Status in systemd-shim source package in Cosmic:
> Won't Fix
>
> Bug description:
> [Impact]
>
> * Some systems fail to upgrade due to conflicts between systemd and
> the (now removed from the archive) systemd-shim / upstart.
>
> * Instead of trying to work out what's the problem in ordering /
> removal of diverts, ensure that systemd is never unpacked whilst
> systemd-shim/upstart are still on disk. Thus declare conflicts against
> systemd-shim/upstart packages in systemd package.
>
> [Test Case]
>
> * monitor drop-off of upgrades with below reported problem
>
> * Check that it is possible to upgrade to bionic's libpam-systemd
> from xenial with systemd-shim installed on xenial, ie.
>
> lxc launch ubuntu-daily:xenial test-shim-upgrade
> lxc exec test-shim-upgrade
> apt update
> apt install systemd-shim
> wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> apt install ./systemd-shim_10-3_amd64.deb
> sed 's/xenial/bionic/' -i /etc/apt/sources.list
> apt update
> apt install systemd
>
> this currently passes, however, systemd-shim remains installed. It
> should be removed instead. Apt install systemd should have lines like
> this:
>
> The following packages will be REMOVED:
> systemd-shim
> ...
> Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
> ...
>
>
> [Regression Potential]
>
> * systemd-shim/upstart are both removed and not supported in bionic,
> thus forcing their removal via...

[Dave Pusey (davepusey)]

This is still broken as of today.

Tried to upgrade a fully up-to-date 1604 LTS system to 1804 LTS using "do-release-upgrade" and it failed with this exact issue.

Had to use the steps from comment #3 above to get it working...

mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
apt-get -f install
apt-get dist-upgrade

[Erik Larsson (catacombae)]

I had this exact error when upgrading a 16.04 (amd64) with HWE (all packages up-to-date) to 18.04 today. So I wouldn't say this is fixed. Now trying to salvage it by moving the relevant file while the upgrade is going on...

[thethirdnut (leeandang)]

Just did an do-release-upgrade from 16.04 to 18.04 and ran into this issue as well. The following fixed it like mentioned above.

sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

[Ronny Svedman (ronny-ronnysvedman)]

This bit me today, 16.04LTS to 18.04 LTS

[Damiön la Bagh (kat-amsterdam)]

Can confirm that these steps BEFORE REBOOTING lead to a working 18.04 system after the 16.04 upgrade fails.

Maybe these steps could be added to the upgrade script

In psudocode:

if [ error due to systemd1.service ] then;

sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

exit
fi

[Chris (chris-n17)]

I got nipped by this bug today moving from 16.04LTS to 18.04 LTS

[Ray Satiro (raysatiro)]

I also had this problem. I was upgrading from 16 LTS -> 18 LTS -> 20 LTS

sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service{,.bak}
sudo apt purge systemd-shim

Do you want to continue? [Y/n] y
Abort.
(Not sure why that happened and I had to run it again to actually get it to purge).

sudo apt-get update
sudo apt-get upgrade

(Software updater upgrade button does nothing...)

The following packages have been kept back:
  python-oauthlib python-openssl

sudo apt-get remove python-oauthlib python-openssl

Then it worked from GUI