gnome-shell --wayland works only when --mode=initial-setup

[marco ghidinelli]

Package: gnome-shell
Version: 3.25.91-0ubuntu4

marcogh@fate:~$ lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

Since a couple of version of gnome-shell, --wayland doesn't work anymore.

When launching from console with:

  gnome-shell --wayland --display-server --mode=classic

the screen remains black, the cursor appears in the middle, and nothing else.

killing gnome-shell from remote ssh brings the console back, with no error.

Curiously, it works (and it's wayland) when i add

  --mode=initial-setup

The Xorg version works fine.

[Daniel van Vugt (vanvugt)]

Please run 'lspci -k' and paste the output here so we can tell what kind of graphics hardware you have.

[marco ghidinelli (marcogh)]

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
 Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
 Subsystem: Dell HD Graphics 620
 Kernel driver in use: i915
 Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 02)
 Subsystem: Dell Skylake Processor Thermal Subsystem
 Kernel driver in use: proc_thermal
 Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
 Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller
 Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
 Subsystem: Dell Sunrise Point-LP Thermal subsystem
 Kernel driver in use: intel_pch_thermal
 Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
 Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
 Kernel driver in use: intel-lpss
 Kernel modules: intel_lpss_pci
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
 Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller
 Kernel driver in use: intel-lpss
 Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
 Subsystem: Dell Sunrise Point-LP CSME HECI
 Kernel driver in use: mei_me
 Kernel modules: mei_me
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
 Kernel driver in use: pcieport
 Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
 Subsystem: Dell Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
 Subsystem: Dell Sunrise Point-LP PMC
 Kernel driver in use: intel_pmc_core
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
 Subsystem: Dell Device 075b
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
 Subsystem: Dell Sunrise Point-LP SMBus
 Kernel modules: i2c_i801
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
 Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter
 Kernel driver in use: ath10k_pci
 Kernel modules: ath10k_pci
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
 Subsystem: Dell RTS525A PCI Express Card ...

[marco ghidinelli (marcogh)]

sorry for the delay.

[Daniel van Vugt (vanvugt)]

Please try reproducing the problem again, and as soon as it happens switch VTs, login and take a copy of the system log:

   journalctl > journalctl.txt

and attach it here.

[Daniel van Vugt (vanvugt)]

Your log shows repeating errors from "gnome-shell --wayland ..."

set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched rules; type="error", sender=":1.1" (uid=0 pid=757 comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland --display-server --mode=clas")
set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched rules; type="error", sender=":1.1" (uid=0 pid=757 comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland --display-server --mode=clas")
set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched rules; type="error", sender=":1.1" (uid=0 pid=757 comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland --display-server --mode=clas")

That makes me think some extra environment is required to make it work. Either that or systemd-logind is preventing it from working and requires some custom syntax.

Have you tried waiting for a full minute or two on the black screen? If a DBus call is timing out then each one will require 25 seconds to unblock.

[Daniel van Vugt (vanvugt)]

The classic option requires you have it installed already, do you?...

  sudo apt install gnome-shell-extensions

Otherwise try running just:

  gnome-shell --wayland --display-server

or

  gnome-shell --wayland --display-server --sm-disable

[Daniel van Vugt (vanvugt)]

Did you try installing the required package?

  sudo apt install gnome-shell-extensions

[marcogh (marcogh-a)]

ii gnome-shell-extensions 3.25.91-1
all Extensions to extend functionality of GNOME Shell

the current package is installed since the 4th of september:

marcogh@fate:~$ grep gnome-shell-ext /var/log/dpkg.log
2017-09-04 22:46:26 upgrade gnome-shell-extensions:all 3.24.2-0ubuntu2
3.25.91-0ubuntu2
2017-09-04 22:46:26 status half-configured gnome-shell-extensions:all
3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all
3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all
3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all
3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all
3.25.91-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all
3.25.91-0ubuntu2

i just tried to uninstall and reinstall the package (just in case) but the
issue remains.

[marco ghidinelli (marcogh)]

ii gnome-shell-extensions 3.25.91-1 all Extensions to extend functionality of GNOME Shell

the current package is installed since the 4th of september:

marcogh@fate:~$ grep gnome-shell-ext /var/log/dpkg.log
2017-09-04 22:46:26 upgrade gnome-shell-extensions:all 3.24.2-0ubuntu2 3.25.91-0ubuntu2
2017-09-04 22:46:26 status half-configured gnome-shell-extensions:all 3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all 3.24.2-0ubuntu2
2017-09-04 22:46:26 status half-installed gnome-shell-extensions:all 3.24.2-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.25.91-0ubuntu2
2017-09-04 22:46:26 status unpacked gnome-shell-extensions:all 3.25.91-0ubuntu2

i just tried to uninstall and reinstall the package (just in case) but the issue remains.

[Daniel van Vugt (vanvugt)]

I can't reproduce the problem myself. 'gnome-shell' starts happily if I run it from a VT tty login. It looks and sounds like there's something peculiar about your system.

[marco ghidinelli (marcogh)]

I've checked now: other users can use wayland without problem, so it's specific to my user.

[marco ghidinelli (marcogh)]

I've checked now: other users can use wayland without problem, so it's specific to my user.

After further analysis i found that it's the "focusli" gnome extension.

thanks for the help.

[Daniel van Vugt (vanvugt)]

I can't seem to find "focusli" in the Ubuntu archive so assume you installed it manually.

Glad to hear your figured it out, but that would make the bug invalid for Ubuntu tasks at least.