Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
Simon, thanks for the extensive reply. > If this isn't implicated in any user-visible problem, then it's almost > certainly harmless, and definitely not Severity: important. The main user-visible problem on my computer these days is that X11 is used instead of Wayland, and the only big action of mine was upgrading to Debian 12 from Debian 11 (with a few packages from Debian 12). Before we get to the first Wayland-related message in the log in some yet-to-be-written bug report, we better deal with all the visible warnings, errors, and failures, one by one, that happen earlier because an issue happening at time 푡 may potentially be (and sometimes is) a consequence of failures happening at times < 푡. Dealing with issues one by one, starting with the earliest, is usually the technically most _proper_ way to deal with software. (Ideally, we'd better start even with the high-level architecture of the GUI, but it's too far from the specific topic here.) > The gdm display manager runs gnome-shell in a special mode to provide > its "greeter" (login prompt) user interface, but there isn't really > any state in that session that would be useful to save, so the fact that > gdm can't load a saved state is not doing anyone any harm. If my memory serves me right, at least the state of the Num Lock was saved in certain older Debian versions. I'm going to double check on this. > Arguably the fact that it tries to load a saved session file and logs a > message while in this special mode is a minor bug, but gnome-shell is a > large, user-facing component with many more users than developers, and > as a result, a very large number of bug reports that are more serious > than this one. > > If this offends you, then you could do the research into why this is > appearing and send a merge request upstream to silence it; but please > bear in mind that even if you take the time to do that, the time needed > for a developer to review whether that contribution is correct would be > time that they cannot spend on something with a higher impact, like for > example diagnosing and fixing a crash. A crash is sometimes (of course, not always) a consequence of an accumulation of issues which happened earlier. (What I personally learned by looking into the documentation of failures of safety-critical or security-critical applications is that for such applications, a hard failure can _always_, to the extent of my knowledge, be contributed to a combination of issues, and that these hidden issues are very difficult to figure out only from the user-visible symptoms; sometimes the root causes are never found.) What you said, essentially, means that resources (here, time) might lack to develop a system the proper way. I fully and completely understand; no argument here. At the same time, this lack of resources is more an organizational problem and less a technical one. (The question of how to organize software development, in particular open-source software development, in such a way that the technically ideal path will be followed with little resources available is both extremely important and difficult. In my view, the sheer multitude of > 80K bugs on www.debian.org/Bugs is not only due to the size of Debian but also a result of the inability to find and follow the technically ideal path. This is not specific to Debian; other software projects suffer similarly. In short, the situation is already bad, and it will get only worse if the current method of software development continues. I'm not going to discuss this question here further, as this would lead us too far away from the topic.) Practically and pragmatically, given the fact that some folks develop a piece of software (here: Gnome) mainly because this is what they want to do (and not only because they have to do it, e.g., to get paid), I hope that I'm providing these folks with feedback. Given that I'm dealing with tons of issues myself, I'm probably doing already more than the majority of Gnome users. It's impossible for me to do more now (otherwise I simply run out of time, sleep, health, and money); even reporting all the red-colored failures in the journal is highly likely to be out of my reach. I hope that if at any point a developer decides to look into any particular issue or a combination of issues, he/she gets the logs he/she needs. In this case, the corresponding bug report(s) will be of help. I apologize if my bug reports sound too harsh (I guess, I have felt simply overwhelmed and extremely helpless; I promise to express myself more professionally). > This is unlikely to be fixed as a Debian-specific change. Any change has a > risk of causing regressions, so we have to weigh up that risk against the > benefit of fixing a bug. If the bug is minor, then the maximum possible > benefit is very small, so any risk at all would be a problem. I get it. At the same time, in my understanding, this is what Debian
Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
Control: severity -1 minor Control: tags -1 + wontfix On Wed, 17 May 2023 at 18:43:48 +, Al Ma wrote: > In my journal I discovered a message that a saved session file could not be > parsed: ... > Mai 17 20:03:29 AnonymizedComputerName org.gnome.Shell.desktop[1049]: Window > manager warning: Failed to parse saved session file: Datei »/var/lib/gdm3 > /.config/mutter/sessions/1012a34d79e815c63f1684346606817667001010.ms« > konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden If this isn't implicated in any user-visible problem, then it's almost certainly harmless, and definitely not Severity: important. The gdm display manager runs gnome-shell in a special mode to provide its "greeter" (login prompt) user interface, but there isn't really any state in that session that would be useful to save, so the fact that gdm can't load a saved state is not doing anyone any harm. Arguably the fact that it tries to load a saved session file and logs a message while in this special mode is a minor bug, but gnome-shell is a large, user-facing component with many more users than developers, and as a result, a very large number of bug reports that are more serious than this one. If this offends you, then you could do the research into why this is appearing and send a merge request upstream to silence it; but please bear in mind that even if you take the time to do that, the time needed for a developer to review whether that contribution is correct would be time that they cannot spend on something with a higher impact, like for example diagnosing and fixing a crash. This is unlikely to be fixed as a Debian-specific change. Any change has a risk of causing regressions, so we have to weigh up that risk against the benefit of fixing a bug. If the bug is minor, then the maximum possible benefit is very small, so any risk at all would be a problem. smcv
Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
severity 1036232 important thanks Same or similar bug on the current Debian stable 12 “bookworm” (so raising severity a tiny bit): Jun 20 03:23:14 AnonymizedComputerName org.gnome.Shell.desktop[1077]: kmsro: driver missing Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Files' unit='tracker-miner-fs-3.service' requested by ':1.3' (uid=119 pid=1032 comm="/usr/libexec/tracker-extract-3") Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Device '/dev/dri/card0' prefers shadow buffer Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Added device '/dev/dri/card0' (ast) using atomic mode setting. Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Device '/dev/dri/card1' prefers shadow buffer Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting tracker-miner-fs-3.service - Tracker file system data miner... Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName tracker-miner-f[1139]: Unable to get XDG user directory path for special directory Ignoring this location. Jun 20 03:23:14 AnonymizedComputerName avahi-daemon[869]: Server startup complete. Host name is AnonymizedComputerName.local. Local service cookie is 156463880. Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Added device '/dev/dri/card1' (nouveau) using non-atomic mode setting. Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Created gbm renderer for '/dev/dri/card0' Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Created gbm renderer for '/dev/dri/card1' Jun 20 03:23:14 AnonymizedComputerName gnome-shell[1077]: Boot VGA GPU /dev/dri/card1 selected as primary Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.11' (uid=119 pid=1139 comm="/usr/libexec/tracker-miner-fs-3") Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor... Jun 20 03:23:14 AnonymizedComputerName systemd[1]: Started gpm.service - Console Mouse manager. Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Started gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor. Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.11' (uid=119 pid=1139 comm="/usr/libexec/tracker-miner-fs-3") Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor... Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor' Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Started gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor. Jun 20 03:23:14 AnonymizedComputerName dbus-daemon[1037]: [session uid=119 pid=1037] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.11' (uid=119 pid=1139 comm="/usr/libexec/tracker-miner-fs-3") Jun 20 03:23:14 AnonymizedComputerName systemd[1013]: Starting
Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
Package: gnome-shell Version: 42.3.1-2 In my journal I discovered a message that a saved session file could not be parsed: Mai 17 20:03:28 AnonymizedComputerName org.gnome.Shell.desktop[1157]: glamor: No eglstream capable devices found Mai 17 20:03:28 AnonymizedComputerName gnome-shell[1049]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Mai 17 20:03:28 AnonymizedComputerName gnome-shell[1049]: Will monitor session c1 Mai 17 20:03:28 AnonymizedComputerName dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.35' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:28 AnonymizedComputerName systemd[1]: Starting Locale Service... Mai 17 20:03:29 AnonymizedComputerName dbus-daemon[793]: [system] Successfully activated service 'org.freedesktop.locale1' Mai 17 20:03:29 AnonymizedComputerName wpa_supplicant[812]: wlp179s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE Mai 17 20:03:29 AnonymizedComputerName systemd[1]: Started Locale Service. Mai 17 20:03:29 AnonymizedComputerName /usr/libexec/gdm-wayland-session[998]: dbus-daemon[998]: [session uid=119 pid=998] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1113] policy: auto-activating connection 'AnonymizedWiFiName' (AnonymizedHexID) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1121] device (wlp179s0): Activation: starting connection 'AnonymizedWiFiName' (AnonymizedHexID) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1123] device (wlp179s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName /usr/libexec/gdm-wayland-session[998]: dbus-daemon[998]: [session uid=119 pid=998] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1146] device (wlp179s0): set-hw-addr: reset MAC address to AnonymizedMACAddress (preserve) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1155] device (wlp179s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1160] device (wlp179s0): Activation: (wifi) access point 'AnonymizedWiFiName' has security, but secrets are required. Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1161] device (wlp179s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1164] sup-iface[db9ea4b039e47a74,0,wlp179s0]: wps: type pbc start... Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1289] device (wlp179s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1296] device (wlp179s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1301] device (wlp179s0): Activation: (wifi) connection 'AnonymizedWiFiName' has security, and secrets exist. No new secrets needed. Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'ssid' value 'AnonymizedWiFiName' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'scan_ssid' value '1' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'bgscan' value 'simple:30:-70:86400' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'auth_alg' value 'OPEN' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'psk' value '' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1795] device (wlp179s0): supplicant interface state: disconnected -> scanning Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1795] device (p2p-dev-wlp179s0): supplicant management interface state: disconnected -> scanning Mai 17 20:03:29 AnonymizedComputerName dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.35' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:29 AnonymizedComputerName systemd[1]: Starting Location Lookup Service... Mai 17 20:03:29 AnonymizedComputerName polkitd(authority=local)[800]:
