1. It appears nobody requested this fix for xenial so I wouldn't expect
anyone interested in testing it.
2. I can't see the bug ID documented in any proposed xenial kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
This bug was fixed in the package linux - 4.15.0-55.60
---
linux (4.15.0-55.60) bionic; urgency=medium
* linux: 4.15.0-55.60 -proposed tracker (LP: #1834954)
* Request backport of ceph commits into bionic (LP: #1834235)
- ceph: use atomic_t for ceph_inode_info::i_shared_gen
Tested bionic-proposed with both original VM that exhibited the problem
on upgrade and a separate VM used to test the work-around (uncommenting
WaylandEnable=false in /etc/gdm3/custom.conf).
Both VMs upgraded and ran successfully using
https://wiki.ubuntu.com/Testing/EnableProposed.
I have also tested the updated kernel from bionic-proposed using the VM
in which the original problem was first experienced.
'uname -a' after adding bionic-proposed to /etc/apt/sources.list and doing
'sudo apt update; sudo apt upgrade'
Linux ubuntuvm1 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
The testing phase where the kernel will land in bionic-proposed pocket is due
around :
08-Jul - 19-Jul Bug verification & Regression testing
This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.
- Eric
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as
described in previous comment.
- Eric
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx using
Todd, The fix will land in the next kernel cycle.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
Status
I am running into the same situation:
Running Ubuntu 18.04 in VMWare Fusion 10.1.6 on macOS 10.14.5
After I updated I received the 4.15.0-52-geeneric kernel, and the login
screen no longer shows. I was able to successfully use the workaround
"WaylandEnable=false" to get it to show.
--
You
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux-hwe (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Disco)
kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland,
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
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
Additional confirmation...
Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:
Having performed the workaround of uncommenting the
WaylandEnable=false...
- Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen
- Using your
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Desktop
Eric,
your new test kernel works for... and screen-resizing works this time too.
To confirm, I am running the correct kernel build;
uname -a
Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP
Thu Jun 20 13:18:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
You received this
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if
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
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
Workaround for mutter proposed here:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...
I am now able to reproduce and debug the problem. Indeed it is what I
said in comment #31.
The vmwgfx driver in this old kernel is telling lies. It says the next
screen refresh is in 49 years from now. It should be within 16.6
milliseconds.
** Summary changed:
- Login screen never appears on
34 matches
Mail list logo
