Error creating IO channel that might be the cause of a complete GNOME crash
Earlier today, I got a complete GNOME crash.
When looking at journalctl
logs, I found that line:
Apr 02 14:31:27 T470-clement tracker-miner-fs-3[202146]: (tracker-extract-3:202146): GLib-GIO-WARNING **: 14:31:27.396: Error creating IO channel for /proc/self/mountinfo: Invalid argument (g-io-error-quark, 13)
around the time the crash happened. Nothing else relevant seems to appear (only logs from Graphical applications getting broken pipes and the like).
EDIT: I might actually have been carried away a little: there are occurrences of this line in logs prior to that one and the crash. Log line got to be cared for anyway I think, by could it cause more important problems?
What happened right after was this:
Apr 02 14:31:28 T470-clement gnome-shell[1486]: Shutting down GNOME Shell
Apr 02 14:31:28 T470-clement firefox.desktop[25079]: [GFX1-]: VideoBridgeParent receives IPC close with reason=AbnormalShutdown
Apr 02 14:31:28 T470-clement systemd[1049]: org.gnome.SettingsDaemon.XSettings.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 14:31:28 T470-clement systemd[1049]: org.gnome.SettingsDaemon.XSettings.service: Failed with result 'exit-code'.
Apr 02 14:31:28 T470-clement systemd[1049]: org.gnome.SettingsDaemon.XSettings.service: Consumed 5.103s CPU time, 170.2M memory peak, 20.5M memory swap peak.
Apr 02 14:31:29 T470-clement systemd[1049]: org.gnome.SettingsDaemon.XSettings.service: Scheduled restart job, restart counter is at 1.
Apr 02 14:31:29 T470-clement systemd[1049]: Starting GNOME XSettings service...
But it's unrelated to tracker, and I don't get what would show the reason for a crash in here…