/org/gnome/gnome-session/auto-save-session true does not save the session
Affected version
- Fedora 32
- Mutter 3.36.1
- Wayland and XOrg
Bug summary
If I understand /org/gnome/gnome-session/auto-save-session
correctly it should restore the state from the last session at the start of the next session. However, this does not happen.
Steps to reproduce
- Set
/org/gnome/gnome-session/auto-save-session
to true - Open a
gnome-terminal
- Log out
- Log in again
What happened
An empty session the next time I log in.
What did you expect to happen
gnome-terminal
gets restored the next time I log in.
Relevant logs, screenshots, screencasts etc.
Not sure if it is related but this is in my log on every log out:
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1576:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1546:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be>
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: == Stack trace for context 0x55b7be94e6f0 ==
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55b7beb96170.
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: == Stack trace for context 0x55b7be94e6f0 ==
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be>
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55b7c127cfe0.
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be>
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: The offending signal was notify on NMDeviceWifi 0x55b7c0f422a0.
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: == Stack trace for context 0x55b7be94e6f0 ==
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: == Stack trace for context 0x55b7be94e6f0 ==
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: == Stack trace for context 0x55b7be94e6f0 ==
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be>
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: The offending signal was notify on NMActiveConnection 0x55b7c0f44340.
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be>
Apr 14 10:58:44 xps-9370 gnome-shell[24745]: The offending signal was state-changed on NMDeviceWifi 0x55b7c0f422a0.