ubuntu wayland crashes when I attach secondary monitor

[Martin Vysny]

I have a notebook with dual graphic cards: Intel+Nvidia (handled by nouveau). The miniDP port is apparently connected to nvidia since it stops working when I use nouveau.modeset=0. I am able to start a Wayland session when there's no secondary monitor connected; as soon as I connect it to miniDP the wayland session crashes and falls back to the greeter. The greeter won't even start Wayland session - it immediately crashes back to the greeter. Workaround is to use the Xorg-based session which works properly with secondary monitor.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.27.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 13 22:34:37 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>']"
 b'org.gnome.shell' b'command-history' b"['r']"
 b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'chromium-browser.desktop', 'thunderbird.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
InstallationDate: Installed on 2016-09-05 (554 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-03-13 (0 days ago)

[Martin Vysny (vyzivus)]

syslog

[Martin Vysny (vyzivus)]

lspci:

00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1000M] (rev a2)
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
3e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)

[Daniel van Vugt (vanvugt)]

This is likely a known crash. We just need to figure out exactly which known crash...

Please look in /var/crash for crash files and then upload the relevant one(s) using this command:

  ubuntu-bug /var/crash/YOURFILE.crash

Then let us know the ID of the newly-created bug(s).

[Martin Vysny (vyzivus)]

Thank you very much for your quick reply! There are in fact two crash report files:

$ ubuntu-bug /var/crash/_usr_bin_Xwayland.1000.crash

reported that it's already reported as https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731911

$ ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash

I've reported this one as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755671

[Daniel van Vugt (vanvugt)]

Thanks. That is indeed a known crash. It's the #1 crash.

Duplicate of bug 1748450.