bionic-proposed confirmation:
I have tested the updates in bionic-proposed with the VM I created for
this bug as described in comment #63 and can confirm this, like the test
in comment #75, also resolves the issue.
The login screen appears as expected after reboot (with kernel and
updated
Additional confirmation...
Looks like this updated kernel fixes the issue on the affected test VM I
created.
Using the detailed directions in comment #75, I was able to install the
new test kernel and reboot.
Verified the expected version value with uname and then installed the
packages that
Here is the last of the output after running the first test repo update
command in comment #73 on the Bug1832138VM.zip VM I built.
I'm guessing either there is an integrity issue upstream or more likely
there is a missing step so that a system that has been using the default
repo settings is
Because it was mentioned in comment #15 & #34 that this bug cannot be
reproduced, I decided to create a VMWare VM from scratch which managed
to be affected on my first attempt.
I started with ubuntu-18.04.1-desktop-amd64.iso
(19e10acddd14af9a9150399d876b02933c0ee724) and created a snapshot with
I have regular snapshots of my ESXi virtual machines and so using a
snapshot before updating packages, I was able to install as many
packages as I could before login broke in the way everyone is
describing. I got down to the following packages:
gir1.2-mutter-2/bionic-updates
