Indeed there was a kernel update to 18.04 around the same time as the
mutter update which I thought was causing this bug.
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Bionic)
** No longer affects: mutter (Ubuntu Eoan)
** Also affects: linux (Ubuntu Eoan)
Testing upstream kernel, I can tell this situation is not a Ubuntu kernel
specific issue.
I can reproduce using upstream kernel.
This is where I'm at the moment:
BAD kernel : v4.16.18
GOOD kernel : v4.17-rc1
Leaving us to the following 'vmwgfx' commits to bisect:
$ git log
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
Thanks Pat.
Glad you had the same result as I did.
I will start the kernel bisect to find out the commit which introduce the fix
and confirm my potential good candidate that I found by doing a git log
inspection.
Will keep you guys posted.
--
You received this bug notification because you
Eric,
I installed the 4.18 kernel on one of my Ubuntu 18.04 VMs by doing 'sudo apt
install linux-generic-hwe-18.04'
As further evidence that you may be onto something...
The system boots up fine, presents a GUI login prompt, and I am able to login
and use the system as expected (without having
I marked this bug affecting the kernel 'linux', but I can't 'target to
series' and choose Bionic. It's not in the option list anymore
(something went wrong with that bug I think, but we can figure this out
later (when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
I marked this bug affect the kernel 'linux' project, but I can't 'target
to series' and choose Bionic, it's not in the option list (something
went wrong with that bug I think, but we can figure this out later
(when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
can someone impacted try v4.18 hwr kernel ? and let me know if it works
fine (without workarounds) just like it did for me ? I will perform the
kernel bisect next week to see what v4.15 is missing that 4.18 has to
fix this bug.
--
You received this bug notification because you are a member of
my bug report :
https://bugs.launchpad.net/bugs/1832903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but setting WaylandEnable=false
fixes it
I reported the exact same problem and was able to reproduce.
Only using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but need to run a bisection to confirm my assumption :
commit
Hi Daniel,
Sorry for the delay.
As requested, I reproduced the bug.
- I SSH'd into the VM
- /var/crash was empty
- 'pidof gnome-shell' returned a pid of 1423
- I ran 'sudo kill -ABRT 1423'
- two crash reports/files appeared in /var/crash
-rw-r- 1 gdm whoopsie 20574823 Jun 15 06:12
Daniel
After uncommenting the Wayland option the login appears, I can log in
but the desktop refuses to resize. This was working previously. Entering
full screen however works and doesn't crash the system.
The crash with kernel option nomodeset when resizing or attempting
fullscreen is probably
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug
Looking at hungboot.txt I am starting to think maybe the login screen
('gnome-shell' process) is actually running in Wayland mode but failing
to display. That would explain a lot...
Pat, can you please reproduce the bug again and while it is happening:
1. SSH into the VM.
2. Run 'pidof
I have been trying to reproduce this bug in VMware but have not been
able to. Ubuntu 18.04 always starts up with a login screen successfully
for me.
What it does not do successfully is offer the "Ubuntu on Wayland" option
most of the time. So I expect that's the same root cause as this bug.
Jussi,
That sounds like maybe a different bug. Although "commenting out the
Wayland" is also not what you need to do. You need to change:
#WaylandEnable=false
to:
WaylandEnable=false
If that doesn't fix the problem for you then you have a different bug.
In that case please open a new bug
** Changed in: mutter (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but setting
18.04.2LTS as guest of course. Here is dmesg listing after I bring up
the gnome via safe mode on the local WS 15 Pro.
** Attachment added: "dmesg_wspro15.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+attachment/5270271/+files/dmesg_wspro15.txt
--
You received this bug
This workaround of commenting out the Wayland does not work on both my
setups, W10 Enterprise running WMvare 15 Pro and remote ESXi 6.5. with
18.04.2LTS host.
I am able to login via safe mode -> login as root -> return to grub ->
resume and keep VMware in windowed mode. Attempt to switch to full
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Eoan)
CONFIRMED: Same situation running 18.04.2 on VMWare 12.5.9. After
uncommenting the WaylandEnable=false line and rebooting, then I see the
login prompt as expected and I can then log in and use the system
normally again.
--
You received this bug notification because you are a member of Ubuntu
If I had to guess then I would guess the most likely cause is the
changes I made in the latest update:
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems like a bionic updates regression. Duplicate bug 1832320 confirms
the same date.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
Hi Daniel,
It doesn't appear anything has actually crashed when this scenario happens.
/var/crash is empty
The contents of my /var/lib/whoopsie/whoopsie-id is;
d0d31e5e858096f38cba06e106ab0375a0e96fd9fda7031d320fa3966f0064bba364acdc53d42bce08a29148a49314d352455fe8b6cb716c20dbf804d8711876
There
Thanks. That log is shorter than I expected.
Maybe something crashed in the startup process. Can you please try these
instructions?
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of
Hi Daniel,
Here is the hungboot.txt file you requested.
** Attachment added: "hungboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+attachment/5269842/+files/hungboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In order to debug this problem we would need you to reintroduce it. That
means:
1. Comment out again:
WaylandEnable=false
2. Reboot and ensure you don't see the login screen.
3. Log in via SSH while the problem is happening and run:
journalctl -b0 > hungboot.txt
and send us the
** Summary changed:
- Login freeze during boot after upgrade
+ Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: vmware
**
31 matches
Mail list logo
