GNOME Bugzilla – Bug 789166
Session logout after screen turned off
Last modified: 2021-07-05 14:25:57 UTC
Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Distribution: Ubuntu 16.10 Gnome versioon: 3.26 (of 3.26.1-0ubuntu3 package) Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 Here is the bug report in Ubuntu launchpad: https://bugs.launchpad.net/gnome-shell/+bug/1721428 Multiple users have the same issue. And there is report that by changing to KDE session actually fixed the problem.
(In reply to Koala Yeung from comment #0) > Whenever I turn off my screen, the computer (a desktop PC) logs me out of my > session. That's unlikely. You are probably using the wayland session and gnome-shell crashed, taking the session down with it. We'll need a backtrace to figure out what exactly is wrong though.
I have a crash report located as /var/crash/_usr_bin_gnome-shell.1000.crash which coincides with issue. apport-retrace doesn't want to play (I'm new to this...): apport-retrace --confirm --gdb --sandbox system --verbose --cache /tmp/cache/apport-retrace /var/crash/_usr_bin_gnome-shell.1000.crash ERROR: report file does not contain one of the required fields: Package Any tips on getting a stack trace from the CoreDump?
Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for details about how to get a backtrace.
I'm having the exact same issue. I discovered it when I unplugged my HDMI cable to plug in my other computer. I had a fresh install of ubuntu 17.10 running on my intel nuc7i5. I'm new to all of this, but I tried to run apport-retrace. I also ran it as the root user, using sudo -i. Also, I had to add `Package: gnome-shell` to the `.crash` file. This got me into gdb. Command I executed: ``` root@nuc7i5-small:~# apport-retrace --confirm --gdb --sandbox system --verbose --cache /tmp/cache/apport-retrace /var/crash/_usr_bin_gnome-shell.1000.crash ``` As it was getting packages, I noticed this: ``` WARNING: invalid Package/Dependencies line: gnome-shell ``` It continued dynamically loading packages, then I noticed this: ``` Installing extra package gnome-shell to get ExecutablePath ``` And then... ``` Extracting downloaded debs... Calling gdb command: /usr/bin/gdb --ex 'set debug-file-directory /tmp/apport_sandbox_OZqSDK/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport_sandbox_OZqSDK' --ex 'add-auto-load-safe-path /tmp/apport_sandbox_OZqSDK' --ex 'set solib-search-path /tmp/apport_sandbox_OZqSDK/lib/x86_64-linux-gnu' --ex 'file "/tmp/apport_sandbox_OZqSDK//usr/bin/gnome-shell"' --ex 'core-file /tmp/apport_core_vBzkXs' GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Reading symbols from /tmp/apport_sandbox_OZqSDK//usr/bin/gnome-shell...(no debugging symbols found)...done. [New LWP 20182] [New LWP 20184] [New LWP 20187] [New LWP 20185] [New LWP 20212] [New LWP 20213] [New LWP 20211] [New LWP 20218] [New LWP 20214] [New LWP 20219] [New LWP 20215] [New LWP 20216] [New LWP 20217] warning: Could not load shared library symbols for /usr/lib/x86_64-linux-gnu/libtxc_dxtn.so. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 238086
warning: Unexpected size of section `.reg-xstate/20182' in core file. Function "main" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Temporary breakpoint 1 (main) pending. Starting program: /tmp/apport_sandbox_OZqSDK/usr/bin/gnome-shell [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffdf67b700 (LWP 7693)] [Thread 0x7fffdf67b700 (LWP 7693) exited] [New Thread 0x7fffdf67b700 (LWP 7694)] Window manager warning: Unsupported session type [Thread 0x7ffff7f9f240 (LWP 7689) exited] [Inferior 1 (process 7689) exited with code 01] (gdb) list 1 ../sysdeps/x86/dl-procinfo.c: No such file or directory. (gdb) ``` I didn't save it, but I ran `backtrace` and it said no stack. I can do more debugging, I'll just need a little direction. Thanks.
gnome-shell 3.26.1-0ubuntu4 Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGTRAP, Trace/breakpoint trap.
+ Trace 238091
Thread 1 (Thread 0x7f270336e240 (LWP 1617))
(In reply to olsiron from comment #5) > gnome-shell 3.26.1-0ubuntu4 Some code is trying to access a non-existent GSettings key, which is a fatal error: > message=message@entry=0x563b7a0d4ac0 "Settings schema 'org.gnome.shell.overrides' does not contain a key named 'button-layout'", data=data@entry=0x0) There isn't any code that tries to read any 'button-layout' key in all of gnome-shell, so this is either a bug in an extension or in a downstream patch.
Yep it seems this extension is the culprit: https://extensions.gnome.org/extension/599/default-minimize-and-maximize/ Having said that... Should a faulty extension be able to pull down gnome-shell?
(In reply to olsiron from comment #7) > Having said that... Should a faulty extension be able to pull down > gnome-shell? You either give extensions access to all internals so they have the power to modify the shell in significant ways, or you restrict them to a narrow set of functions ("put an icon+menu in the top bar") to shield the system from bad code. (In reply to olsiron from comment #7) > https://extensions.gnome.org/extension/599/default-minimize-and-maximize/ Yikes, this extension has been obsolete for years (since https://git.gnome.org//browse/gnome-shell-extensions/commit?id=0ffaf62c4cdad0a to be precise)
Same problem. After turn off all extensions (in gnome-shell-extension-prefs), it disappeared. Syslog on gnome-shell crash: Oct 24 12:46:08 gnome-shell[14437]: JS ERROR: TypeError: this.primaryMonitor is undefined#012LayoutManager<._updateBoxes@resource:///org/gnome/shell/ui/layout.js:469:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012LayoutManager<._monitorsChanged@resource:///org/gnome/shell/ui/layout.js:503:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 Oct 24 12:46:08 kernel: [96417.371772] gnome-shell[14437]: segfault at 18 ip 00007fecb7364d94 sp 00007ffc5ba5cd78 error 4 in libmutter-1.so.0.0.0[7fecb72c6000+141000] Oct 24 12:46:08 update-notifier[15100]: Error reading events from display: Broken pipe Oct 24 12:46:08 gnome-terminal-[14998]: Error reading events from display: Broken pipe Oct 24 12:46:08 org.gnome.Shell.desktop[14437]: (EE) Oct 24 12:46:08 org.gnome.Shell.desktop[14437]: Fatal server error: Oct 24 12:46:08 org.gnome.Shell.desktop[14437]: (EE) failed to read Wayland events: Broken pipe Oct 24 12:46:08 org.gnome.Shell.desktop[14437]: (EE) Oct 24 12:46:08 gnome-session[14309]: gnome-session-binary[14309]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 24 12:46:08 gnome-session-binary[14309]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 24 12:46:08 gnome-session-binary[14309]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 24 12:46:08 gsd-media-keys[14598]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 12:46:08 gsd-keyboard[14602]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 12:46:08 kerneloops-applet.desktop[14731]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Created attachment 362138 [details] syslog on gnome-shell crash Seems there are lots of JS ERROR from gnome-shell.
Created attachment 362141 [details] gnome-shell-extensions-pref settings Problem reproduced even when all extensions disabled. Only disappear when the top switcher is OFF state. Here is the new syslog: Oct 24 14:04:41 ubuntu-SSD systemd[1]: Started System Logging Service. Oct 24 14:04:47 ubuntu-SSD dbus-daemon[10548]: Activating via systemd: service name='org.gnome.zeitgeist.Engine' unit='zeitgeist.service' Oct 24 14:04:47 ubuntu-SSD systemd[10385]: Starting Zeitgeist activity log service... Oct 24 14:04:47 ubuntu-SSD dbus-daemon[10548]: Activating via systemd: service name='org.gnome.zeitgeist.SimpleIndexer' unit='zeitgeist-fts.service' Oct 24 14:04:47 ubuntu-SSD dbus-daemon[10548]: Successfully activated service 'org.gnome.zeitgeist.Engine' Oct 24 14:04:47 ubuntu-SSD systemd[10385]: Started Zeitgeist activity log service. Oct 24 14:04:47 ubuntu-SSD systemd[10385]: Starting Zeitgeist full-text search indexer... Oct 24 14:04:47 ubuntu-SSD zeitgeist-daemon[11046]: #033[31m[06:04:47.250230 WARNING]#033[0m zeitgeist-daemon.vala:127: Unable to parse version info! Oct 24 14:04:47 ubuntu-SSD zeitgeist-daemon[11046]: #033[31m[06:04:47.250337 WARNING]#033[0m zeitgeist-daemon.vala:127: Unable to parse version info! Oct 24 14:04:47 ubuntu-SSD dbus-daemon[10548]: Successfully activated service 'org.gnome.zeitgeist.SimpleIndexer' Oct 24 14:04:47 ubuntu-SSD systemd[10385]: Started Zeitgeist full-text search indexer. Oct 24 14:04:47 ubuntu-SSD zeitgeist-daemon[11046]: #033[31m[06:04:47.262362 WARNING]#033[0m zeitgeist-daemon.vala:127: Unable to parse version info! Oct 24 14:04:47 ubuntu-SSD zeitgeist-datah[11053]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! Oct 24 14:04:50 ubuntu-SSD pulseaudio[10647]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Oct 24 14:04:54 ubuntu-SSD gsd-rfkill[10738]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput' Oct 24 14:04:54 ubuntu-SSD kernel: [ 4319.772328] rfkill: input handler disabled Oct 24 14:04:56 ubuntu-SSD gnome-shell[10638]: JS ERROR: TypeError: this.primaryMonitor is undefined#012LayoutManager<._updateBoxes@resource:///org/gnome/shell/ui/layout.js:469:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012LayoutManager<._monitorsChanged@resource:///org/gnome/shell/ui/layout.js:503:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 Oct 24 14:04:56 ubuntu-SSD kernel: [ 4322.089861] gnome-shell[10638]: segfault at 18 ip 00007fc82c10ed94 sp 00007fff046a09b8 error 4 in libmutter-1.so.0.0.0[7fc82c070000+141000] Oct 24 14:04:56 ubuntu-SSD gnome-session[10520]: gnome-session-binary[10520]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 24 14:04:56 ubuntu-SSD gnome-session-binary[10520]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Oct 24 14:04:56 ubuntu-SSD gnome-shell[11099]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Oct 24 14:04:56 ubuntu-SSD gnome-shell[11099]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 217]: reference to undefined property "MetaWindowGroup" Oct 24 14:04:56 ubuntu-SSD gnome-shell[11099]: JS ERROR: TypeError: this.primaryMonitor is undefined#012LayoutManager<._updateBoxes@resource:///org/gnome/shell/ui/layout.js:469:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012LayoutManager<._monitorsChanged@resource:///org/gnome/shell/ui/layout.js:503:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012LayoutManager<._init@resource:///org/gnome/shell/ui/layout.js:280:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:117:20#012_initializeUI@resource:///org/gnome/shell/ui/main.js:152:21#012start@resource:///org/gnome/shell/ui/main.js:126:5#012@<main>:1:31 Oct 24 14:04:56 ubuntu-SSD gnome-shell[11099]: Execution of main.js threw exception: JS_EvaluateScript() failed Oct 24 14:04:56 ubuntu-SSD gnome-session[10520]: gnome-session-binary[10520]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 24 14:04:56 ubuntu-SSD gnome-session[10520]: gnome-session-binary[10520]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 24 14:04:56 ubuntu-SSD gnome-session[10520]: gnome-session-binary[10520]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Oct 24 14:04:56 ubuntu-SSD gnome-session-binary[10520]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 24 14:04:56 ubuntu-SSD gnome-session-binary[10520]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 24 14:04:56 ubuntu-SSD gnome-session-binary[10520]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly Oct 24 14:04:56 ubuntu-SSD gnome-session-binary[10520]: CRITICAL: We failed, but the fail whale is dead. Sorry.... Oct 24 14:04:56 ubuntu-SSD gsd-rfkill[10738]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput' Oct 24 14:04:56 ubuntu-SSD kernel: [ 4322.549977] rfkill: input handler enabled Oct 24 14:04:56 ubuntu-SSD gnome-screensav[10624]: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-power[10735]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-wacom[10746]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-keyboard[10788]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD kerneloops-applet.desktop[10846]: kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-media-keys[10787]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-xsettings[10750]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-a11y-keyboa[10774]: gsd-a11y-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD org.a11y.atspi.Registry[10822]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 24 14:04:56 ubuntu-SSD org.a11y.atspi.Registry[10822]: after 33 requests (33 known processed) with 0 events remaining. Oct 24 14:04:56 ubuntu-SSD gnome-terminal-[10984]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-clipboard[10779]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:56 ubuntu-SSD gsd-color[10777]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Oct 24 14:04:57 ubuntu-SSD systemd[10385]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE Oct 24 14:04:57 ubuntu-SSD systemd[10385]: gnome-terminal-server.service: Unit entered failed state. Oct 24 14:04:57 ubuntu-SSD systemd[10385]: gnome-terminal-server.service: Failed with result 'exit-code'.
I did a new install of Ubuntu 17.10 on a brand new intel nuc7i5bnk. Here is the apport-retrace result. ``` Extracting downloaded debs... Calling gdb command: /usr/bin/gdb --ex 'set debug-file-directory /tmp/apport_sandbox_QvYzeO/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport_sandbox_QvYzeO' --ex 'add-auto-load-safe-path /tmp/apport_sandbox_QvYzeO' --ex 'set solib-search-path /tmp/apport_sandbox_QvYzeO/lib/x86_64-linux-gnu' --ex 'file "/tmp/apport_sandbox_QvYzeO//usr/bin/gnome-shell"' --ex 'core-file /tmp/apport_core_FJ_3Py' GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Reading symbols from /tmp/apport_sandbox_QvYzeO//usr/bin/gnome-shell...(no debugging symbols found)...done. [New LWP 1395] [New LWP 1397] [New LWP 1398] [New LWP 1400] [New LWP 1425] [New LWP 1426] [New LWP 1428] [New LWP 1429] [New LWP 1430] [New LWP 1432] [New LWP 1433] [New LWP 1431] [New LWP 1427] [New LWP 16301] warning: .dynamic section for "/tmp/apport_sandbox_QvYzeO/usr/lib/x86_64-linux-gnu/libicudata.so.57" is not at the expected address (wrong library or version mismatch?) warning: Could not load shared library symbols for /usr/lib/x86_64-linux-gnu/libtxc_dxtn.so. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 238103
1 ../sysdeps/x86/dl-procinfo.c: No such file or directory. (gdb) ``` This was a fresh install. And I used wired ethernet instead of wireless. I also reproduced the auto logging out when I was used Xorg to login. But it didn't create a crash report.
A workaround works for me: remove the dock extension. like gnome-shell-extension-ubuntu-dock, gnome-shell-extension-dashtodock, etc. On my pc (ubuntu 17.10), if the bottom dock exists, the problem exists, if disable the bottom dock, the problem disappeared.
Ubuntu 17.10 ii libmutter-1-0:amd64 3.26.1-2ubuntu2 amd64 ii gnome-shell 3.26.1-0ubuntu5 amd64 graphical shell for the GNOME desktop ii gnome-shell-common 3.26.1-0ubuntu5 all common files for the GNOME graphical shell ii gnome-shell-dbgsym 3.26.1-0ubuntu5 amd64 Debug symbols for gnome-shell ii gnome-shell-extensions 3.26.1-1 all Extensions to extend functionality of GNOME Shell Backtrace: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault.
+ Trace 238138
$1 = 0x56114cf54040 (gdb) p *window $2 = {parent_instance = {g_type_instance = {g_class = 0x56114cf35c00}, ref_count = 5, qdata = 0x56114e3aacd1}, display = 0x56114cdb0200, screen = 0x56114ca3c6b0, stamp = 4294967297, monitor = 0x0, workspace = 0x56114ca92c40, client_type = META_WINDOW_CLIENT_TYPE_WAYLAND, surface = 0x56114cb86cf0, xwindow = 0, frame = 0x0, depth = 24, xvisual = 0x0, desc = 0x56114f6bb8e0 "W1 (root@zhuha)", title = 0x56114cfaf140 "root@zhuhai-SSD: /tmp", icon = 0x56114d305820, mini_icon = 0x56114dd15400, type = META_WINDOW_NORMAL, res_class = 0x7fb624000b40 "gnome-terminal-server", res_name = 0x56114cf35df0 "gnome-terminal-server", role = 0x0, sm_client_id = 0x0, wm_client_machine = 0x0, startup_id = 0x0, mutter_hints = 0x0, sandboxed_app_id = 0x0, gtk_theme_variant = 0x0, gtk_application_id = 0x56114d00a2c0 "org.gnome.Terminal", gtk_unique_bus_name = 0x56114d00a210 ":1.73", gtk_application_object_path = 0x56114d00a2a0 "/org/gnome/Terminal", gtk_window_object_path = 0x56114ce77870 "/org/gnome/Terminal/window/1", gtk_app_menu_object_path = 0x56114d00a5c0 "/org/gnome/Terminal/menus/appmenu", gtk_menubar_object_path = 0x0, hide_titlebar_when_maximized = 0, net_wm_pid = -1, xtransient_for = 0, xgroup_leader = 0, xclient_leader = 0, transient_for = 0x0, initial_workspace = 0, initial_timestamp = 0, override_redirect = 0, maximized_horizontally = 1, maximized_vertically = 1, maximize_horizontally_after_placement = 0, maximize_vertically_after_placement = 0, minimize_after_placement = 0, tile_mode = 0, saved_maximize = 1, tile_monitor_number = -1, edge_constraints = {META_EDGE_CONSTRAINT_MONITOR, META_EDGE_CONSTRAINT_MONITOR, META_EDGE_CONSTRAINT_MONITOR, META_EDGE_CONSTRAINT_MONITOR}, tile_hfraction = -1, preferred_output_winsys_id = 50, shaded = 0, fullscreen = 0, urgent = 0, fullscreen_monitors = {top = 0x0, bottom = 0x0, left = 0x0, right = 0x0}, require_fully_onscreen = 1, require_on_single_monitor = 1, require_titlebar_visible = 1, on_all_workspaces = 0, on_all_workspaces_requested = 0, minimized = 0, tab_unminimized = 0, mapped = 1, hidden = 0, visible_to_compositor = 1, known_to_compositor = 1, pending_compositor_effect = 4, iconic = 0, initially_iconic = 0, initial_workspace_set = 0, initial_timestamp_set = 0, net_wm_user_time_set = 1, icon_geometry_set = 0, take_focus = 0, delete_window = 0, can_ping = 1, input = 1, mwm_decorated = 1, mwm_border_only = 0, mwm_has_close_func = 1, mwm_has_minimize_func = 1, mwm_has_maximize_func = 1, mwm_has_move_func = 1, mwm_has_resize_func = 1, decorated = 0, border_only = 0, always_sticky = 0, has_close_func = 1, has_minimize_func = 1, has_maximize_func = 1, has_shade_func = 0, has_move_func = 1, has_resize_func = 1, has_fullscreen_func = 1, skip_taskbar = 0, skip_pager = 0, wm_state_above = 0, wm_state_below = 0, wm_state_demands_attention = 0, has_focus = 1, placed = 1, denied_focus_and_not_transient = 0, showing_for_first_time = 0, unmanaging = 0, constructing = 0, is_in_queues = 0, keys_grabbed = 0, grab_on_frame = 0, all_keys_grabbed = 0, withdrawn = 0, calc_placement = 0, shaken_loose = 0, have_focus_click_grab = 0, disable_sync = 0, attached = 0, is_remote = 0, frame_bounds = 0x0, shape_region = 0x0, opaque_region = 0x0, input_region = 0x0, opacity = 255 '\377', extended_sync_request_counter = 0, struts = 0x0, sync_request_counter = 0, sync_request_serial = 0, sync_request_wait_serial = 0, sync_request_timeout_id = 0, sync_request_alarm = 0, unmaps_pending = 0, stable_sequence = 2, net_wm_user_time = 83651814, user_time_window = 0, has_custom_frame_extents = 0, custom_frame_extents = {left = 0, right = 0, top = 0, bottom = 0}, rect = {x = 0, y = 27, width = 1920, height = 1053}, saved_rect = {x = 145, y = 186, width = 814, height = 575}, unconstrained_rect = {x = 0, y = 27, width = 1920, height = 1053}, buffer_rect = {x = 0, y = 27, width = 1920, height = 1053}, icon_geometry = {x = 0, y = 0, width = 0, height = 0}, size_hints = {flags = 976, x = 0, y = 0, width = 0, height = 0, min_width = 360, min_height = 144, max_width = 2147483647, max_height = 2147483647, width_inc = 1, height_inc = 1, min_aspect = {x = 1, y = 2147483647}, max_aspect = {x = 2147483647, y = 1}, base_width = 0, base_height = 0, win_gravity = 1}, layer = META_LAYER_NORMAL, stack_position = 0, close_dialog = 0x0, group = 0x0, compositor_private = 0x56114f27a830, attached_focus_window = 0x0, tile_match = 0x0, bypass_compositor = 0, placement_rule = 0x0} (gdb) p window->monitor $3 = 0x0
A bit more info: I'm on Debian which recently switched to Wayland and have had this problem since GNOME 3.26. According to the journal, it crashes once I turn the screen on again, not when I turn it off. I get nothing in the log for half an hour, then when I turn on the monitor again, I get nov 09 13:10:06 rhythmbox[4862]: Error reading events from display: Broken pipe nov 09 13:10:06 empathy[1625]: Error reading events from display: Broken pipe nov 09 13:10:06 unknown[3108]: Error reading events from display: Broken pipe nov 09 13:10:06 systemd[1294]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE nov 09 13:10:06 systemd[1294]: gnome-terminal-server.service: Failed with result 'exit-code'. nov 09 13:10:06 org.gnome.Shell.desktop[1357]: (EE) nov 09 13:10:06 org.gnome.Shell.desktop[1357]: Fatal server error: nov 09 13:10:06 org.gnome.Shell.desktop[1357]: (EE) failed to read Wayland nov 09 13:10:06 org.gnome.Shell.desktop[1357]: (EE) nov 09 13:10:06 gnome-session[1326]: gnome-session-binary[1326]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 nov 09 13:10:06 org.gnome.SettingsDaemon.MediaKeys.desktop[1538]: xcb_connection_has_error() returned true nov 09 13:10:06 gnome-session-binary[1326]: Unrecoverable failure in required component org.gnome.Shell.desktop nov 09 13:10:06 gnome-session-binary[1326]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 nov 09 13:10:06 gsd-xsettings[1518]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without reply nov 09 13:10:06 gsd-xsettings[1518]: xft_settings_set_xresources: assertion 'dpy != NULL' failed nov 09 13:10:06 unknown[1499]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput' This is followed by systemd shutting down the session. The only extension I have enabled is Alternatetab. I hope Zuhai's backtrace is enough to figure out what's wrong.
Created attachment 364482 [details] [review] a patch for mutter A patch for mutter 3.26.1, ubuntu 17.10 I found another issue during test, and confirmed it's not caused by this patch( reproduced without this patch, even in gnome session on Xorg): 1. login 2. turn off monitor 3. press window key on keyboard then you will get a blank window in gray state, and cannot open any new apps.
I did some research on it: It happens for me in Ubuntu 17.10 and Arch using XFCE and Gnome at Intel on board Displayport. It happens only, if at least one application is open and if no monitor is plugged in. So if I first plug in/switch on a second monitor before unplugging the first one, everything works fine. Also, if I switch to a tty console before switching off a single monitor. So I think it has to do with rearranging windows while no monitor is available. Avoiding this, if no monitor is plugged in may help. But I don't know how to do this (is it controlled by udev?).
And: it happens same in Weston, so it's not really a Gnome only issue. While in Gnome there is a crash in libmutter, libgbm, libasound or somewhere else, XFCE and Weston just stop running. Process tree is there, but monitor remains black until kill. I hope, I'm posting here in the right thread.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.