Public bug reported:

After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.

It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of failure.

Workaround:
- Access the machine via ssh or any other recovery approaches.
- Force the login screen to use x11:

File: /etc/gdm3/custom.conf
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false

I tried to reproduce the behaviour on my personal laptop, KVM guest, ...
without success.

So far it is only reproducible when the 'vgwfx' driver is in use in
combination with Wayland.

lspci -nnvvv
----
00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
 Latency: 64, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: I/O ports at 2040 [size=16]
 Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
 Region 2: Memory at fb800000 (32-bit, non-prefetchable) [size=8M]
 Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: [40] Vendor Specific Information: Len=00 <?>
 Capabilities: [44] PCI Advanced Features
  AFCap: TP+ FLR+
  AFCtrl: FLR-
  AFStatus: TP-
 Kernel driver in use: vmwgfx
 Kernel modules: vmwgfx
----

** Affects: gdm3 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: wayland (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: wayland (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

  After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
- screen doesn't work if it 'wayland' is in use (default) and if video
- kernel driver inside is 'vgwfx'.
+ screen doesn't work if 'Wayland' is in use (default) and if video kernel
+ driver is 'vgwfx'.
  
  It looks like the login screen got stuck, doesn't exit, and doesn't
  fallback to 'x11' by itself in case of failure.
  
  Workaround:
- Force the login screen to use x11:
+ - Access the machine via ssh or any other recovery approaches.
+ - Force the login screen to use x11:
  
- File: /etc/gdm3/custom.conf 
+ File: /etc/gdm3/custom.conf
  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false
  
- I tried to reproduce the behaviour on my personal laptop, KVM guest, ... 
without success.
- So far it is only reproducible when the 'vgwfx' driver is in use in 
combination with Wayland.
+ I tried to reproduce the behaviour on my personal laptop, KVM guest, ...
+ without success.
  
+ So far it is only reproducible when the 'vgwfx' driver is in use in
+ combination with Wayland.
+ 
+ lspci -nnvvv
  ----
  00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
-       Subsystem: VMware SVGA II Adapter [15ad:0405]
-       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
-       Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
-       Latency: 64, Cache Line Size: 32 bytes
-       Interrupt: pin A routed to IRQ 16
-       Region 0: I/O ports at 2040 [size=16]
-       Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
-       Region 2: Memory at fb800000 (32-bit, non-prefetchable) [size=8M]
-       Expansion ROM at 000c0000 [disabled] [size=128K]
-       Capabilities: [40] Vendor Specific Information: Len=00 <?>
-       Capabilities: [44] PCI Advanced Features
-               AFCap: TP+ FLR+
-               AFCtrl: FLR-
-               AFStatus: TP-
-       Kernel driver in use: vmwgfx
-       Kernel modules: vmwgfx
+  Subsystem: VMware SVGA II Adapter [15ad:0405]
+  Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
+  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
+  Latency: 64, Cache Line Size: 32 bytes
+  Interrupt: pin A routed to IRQ 16
+  Region 0: I/O ports at 2040 [size=16]
+  Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
+  Region 2: Memory at fb800000 (32-bit, non-prefetchable) [size=8M]
+  Expansion ROM at 000c0000 [disabled] [size=128K]
+  Capabilities: [40] Vendor Specific Information: Len=00 <?>
+  Capabilities: [44] PCI Advanced Features
+   AFCap: TP+ FLR+
+   AFCtrl: FLR-
+   AFStatus: TP-
+  Kernel driver in use: vmwgfx
+  Kernel modules: vmwgfx
  ----

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832903

Title:
  18.04.2 login screen doesn't work if it uses 'wayland' and if video
  kernel driver is 'vgwfx' kernel driver

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the
  login screen doesn't work if 'Wayland' is in use (default) and if
  video kernel driver is 'vgwfx'.

  It looks like the login screen got stuck, doesn't exit, and doesn't
  fallback to 'x11' by itself in case of failure.

  Workaround:
  - Access the machine via ssh or any other recovery approaches.
  - Force the login screen to use x11:

  File: /etc/gdm3/custom.conf
  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

  I tried to reproduce the behaviour on my personal laptop, KVM guest,
  ... without success.

  So far it is only reproducible when the 'vgwfx' driver is in use in
  combination with Wayland.

  lspci -nnvvv
  ----
  00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405] 
(prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
   Latency: 64, Cache Line Size: 32 bytes
   Interrupt: pin A routed to IRQ 16
   Region 0: I/O ports at 2040 [size=16]
   Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M]
   Region 2: Memory at fb800000 (32-bit, non-prefetchable) [size=8M]
   Expansion ROM at 000c0000 [disabled] [size=128K]
   Capabilities: [40] Vendor Specific Information: Len=00 <?>
   Capabilities: [44] PCI Advanced Features
    AFCap: TP+ FLR+
    AFCtrl: FLR-
    AFStatus: TP-
   Kernel driver in use: vmwgfx
   Kernel modules: vmwgfx
  ----

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832903/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to