It seems I stumbled on a workaround. Just install the kernel that comes
in the 18.04.2 ISO:
https://launchpad.net/ubuntu/+source/linux-hwe
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Bionic)
Status: New => Fix Released
Using VirtualBox 6 and VMSVGA as recommended by Eric I still can't
reproduce the bug. But I think I can see why now: Ubuntu 18.04.2 comes
with kernel 4.18
Let me try 18.04.1...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
I can reproduce this bug by creating a guest OS using a 18.04.1 .iso I
downloaded last year and attempting to update.
I created another guest OS using the 18.04.2 .iso I downloaded yesterday works
fine after updating.
--
You received this bug notification because you are a member of Ubuntu
It also sounds like VirtualBox might allow me to reproduce the bug...
** Changed in: mutter (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
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
** Changed in: mutter (Ubuntu Bionic)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
My reproducer:
1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force
the OS
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point
of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.
I think the next step is really to find what userspace change started
all this so we can
or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)
I think the next step is really to find what userspace
Daniel van Vugt (vanvugt),
Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
I have strong believe, that something userspace has been changed and no
longer interact well with the vmware driver since then.
Just to look at our
The patchset is significant already without knowing yet what is missing to
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into
Ubuntu 4.15.
I can't SRU this as-is, now knowing this will introduce a regression.
I'll keep you guys posted.
- Eric
Thanks Pat.
That seems to confirm the 'regression-update' tag here. Although I
wouldn't be able to debug and fix the mutter change because I can't
reproduce the bug, using VMware. Mine just works :/
It sounds like good progress is being made in the kernel anyway. So I
think a fix there would be
Card archived: https://trello.com/c/gn0J5Qgb
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but installing kernel >=
v4.17-rc1
Daniel,
I didn't want to lose sight of your ask in comment #34.
I updated to the latest mainstream kernel, and then reverted the mutter
packages (as per comment #31).
That also fixes the problem.
Specifically, this configuration is working for me;
uname -a
Linux ubuntuvm1 4.15.0-52-generic
Display resizing works as expected on the hwe 4.18 kernel
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but installing kernel
Do you have the same display resizing situation with the hwe kernel 4.18
?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
As a side-effect, I've noticed that display resizing doesn't work the same.
I'm unable to resize the display to anything more than 1176 x 885 (4:3)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Great work Eric!
I installed your kernel build and it seems to work.
As confirmation of the kernel build level, here is uname -a output
immediately after install & reboot.
uname -a
Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190618b9-Ubuntu SMP Tue Jun 18
20:11:42 UTC 2019 x86_64 x86_64
I successully applied your latest patch above and it was fixed!
Thank you so much!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on
My test kernel can be found here, if one want to test:
sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update
version: 4.15.0-53.57+hf231164v20190618b9
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
It's working if I apply the whole chain of commit on top of Ubuntu-4.15
I'll need to talk with kernel team and see if this is feasible for an
SRU.
52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit
cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function
This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at
finding what other bits are missing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.
Stay tuned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.
So the kernel bisection is completed and found the right good commit
which is:
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
wbug: With Bug
wnbug: With No Bug
git bisect start '--term-old=wbug' '--term-new=wnbug' '--'
'drivers/gpu/drm/vmwgfx'
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a]
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.
- Eric
--
You
The status for mutter will remain incomplete till someone tries the
suggestion from comment #31.
Sorry, I still can't reproduce this bug myself.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
The problem I mentioned in comment #15 is now logged as bug 1833045.
It's clearly different to this one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never
Pat,
Re comment #19, your crash (hang) reports there seem to show the gnome-
shell process behaving normally (in poll) and not stuck at all. That
doesn't tell us much but it would support the theory in comment #31.
** Summary changed:
- Login screen never appears on vmwgfx but installing kernel
40 matches
Mail list logo
