switch monitor configurations crash-freezes desktop

[Rachel Greenham]

I hit <Super>p by accident. I'll be removing the keybinding now I found it, in org.gnome.mutter.keybindings switch-monitor. It's too common a keystroke I hit when working under macOS that I'm just too likely to hit it by accident. But that's my problem.

But it wouldn't be a problem if it didn't crash the system. When I do so, the overlay comes up offering Mirror, Join, External-only, Internal-only options, then the screens blank for a moment, and when they come back, the desktop is completely frozen and unresponsive. Including the pointer, which is immovable.

My setup is running a Gnome/Wayland session using nvidia-387 drivers (which apart from this is working perfectly!) I have two monitors, but they're different resolutions, and are currently set to different scaling factors (hence trying so hard to run Wayland on nVidia).

I see this in syslog from just before the crash:

Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Failed to apply DRM plane transform 0: Invalid argument
Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Failed to apply DRM plane transform 0: Invalid argument
Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Ignoring length property that isn't a number at line 732, col 24
Oct 5 16:17:12 fleetfoot gnome-shell[1757]: message repeated 2 times: [ Ignoring length property that isn't a number at line 732, col 24]
Oct 5 16:17:26 fleetfoot gnome-shell[1757]: [AppIndicatorSupport-FATAL] unable to lookup icon for state-ok
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct 5 16:18:43 fleetfoot rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="940" x-info="http://www.rsyslog.com"] start

... and then I hit reset. It was unresponsive.

I tried it again, and saw something slightly different. The one thing in common seems to be the gnome-shell "Failed to apply DRM plane transform 0: Invalid" messages.

Oct 5 16:19:11 fleetfoot dbus-daemon[1652]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service'
Oct 5 16:19:11 fleetfoot systemd[1638]: Starting Virtual filesystem metadata service...
Oct 5 16:19:11 fleetfoot dbus-daemon[1652]: Successfully activated service 'org.gtk.vfs.Metadata'
Oct 5 16:19:11 fleetfoot systemd[1638]: Started Virtual filesystem metadata service.
Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: namespace error : xmlns:ms: ' urn:microsoft-com:wmc-1-0' is not a valid URI
Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: xmlns:ms=" urn:microsoft-com:wmc-1-0"
Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: ^
Oct 5 16:19:11 fleetfoot dleyna-renderer-service[2319]: New media server /com/intel/dLeynaRenderer/server/0
Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Failed to apply DRM plane transform 0: Invalid argument
Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Failed to apply DRM plane transform 0: Invalid argument
Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Ignoring length property that isn't a number at line 732, col 24
Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Ignoring length property that isn't a number at line 732, col 24
Oct 5 16:19:14 fleetfoot gsd-a11y-keyboa[1923]: The program 'gsd-a11y-keyboard' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadRRCrtc (invalid Crtc parameter)'.#012 (Details: serial 178 error_code 148 request_code 140 (RANDR) minor_code 20)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the GDK_SYNCHRONIZE environment#012 variable to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the gdk_x_error() function.)
Oct 5 16:19:14 fleetfoot kernel: [ 35.456063] do_trap: 20 callbacks suppressed
Oct 5 16:19:14 fleetfoot kernel: [ 35.456065] traps: gsd-a11y-keyboa[1923] trap int3 ip:7f6e22471921 sp:7ffd7f3536b0 error:0 in libglib-2.0.so.0.5400.0[7f6e22421000+111000]
Oct 5 16:19:16 fleetfoot gnome-session[1654]: gnome-session-binary[1654]: WARNING: Application 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' killed by signal 5
Oct 5 16:19:16 fleetfoot gnome-session-binary[1654]: WARNING: Application 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' killed by signal 5
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct 5 16:19:40 fleetfoot rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="857" x-info="http://www.rsyslog.com"] start
Oct 5 16:19:40 fleetfoot rsyslogd: rsyslogd's groupid changed to 108
Oct 5 16:19:40 fleetfoot rsyslogd: rsyslogd's userid changed to 104

(And then I hit the reset button. I'm afraid I lost patience and didn't go looking for another machine to ssh in from.)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: mutter 3.26.0+20170925~ea214fb-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4
Uname: Linux 4.13.0-14-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 5 16:31:45 2017
InstallationDate: Installed on 2017-07-30 (66 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: mutter
UpgradeStatus: Upgraded to artful on 2017-08-22 (44 days ago)

[Marius Gedminas (mgedmin)]

Upstream bugs that look similar to this one:

- https://bugzilla.gnome.org/show_bug.cgi?id=787637
- https://bugzilla.gnome.org/show_bug.cgi?id=788764

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[kolorafa (kolorafa)]

it crashes when i switch (from multihead to mirror)

when using META+P

https://pastebin.com/Jass9QrU

and from settings:

https://pastebin.com/hJhDPn1Q

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Launchpad Janitor (janitor)]

[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]