| 15 Nov 2025 |
 Capypara | and with no log message, fun | 20:48:14 |
| Capypara | the compositor just says: good bye | 20:48:24 |
| Capypara | Nov 15 21:45:18 kirschbaum org.gnome.Fractal[9165]: 2025-11-15T20:45:18.230247Z WARN fractal::utils::media::image: Could not decode image: the server returned an error: [400 / M_UNKNOWN] Cannot fi>
Nov 15 21:45:43 kirschbaum systemd[2994]: Started Application launched by gnome-shell.
Nov 15 21:45:43 kirschbaum systemd[2994]: Started Application launched by gnome-shell.
Nov 15 21:45:43 kirschbaum pipewire[8028]: mod.x11-bell: X11 I/O error handler called on display :0
Nov 15 21:45:43 kirschbaum pipewire[8028]: mod.x11-bell: X11 display (:0) has encountered a fatal I/O error
Nov 15 21:45:43 kirschbaum fractal[9165]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum kgx[9676]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-calendar[8825]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum epiphany-search-provider[8833]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-control-center-search-provider[8823]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-control-center-global-shortcuts-provider[8221]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum io.github.alain[8214]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum xdg-desktop-portal-gnome[8069]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum evolution-alarm-notify[8020]: Error reading events from display: Broken pipe
Nov 15 21:45:43 kirschbaum gnome-software[8024]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum xdg-desktop-portal-gtk[8266]: Error reading events from display: Broken pipe
Nov 15 21:45:43 kirschbaum systemd[2994]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
| 20:49:01 |
 K900 | coredumpctl debug is probably the place to start looking then | 20:50:14 |
| Capypara | No idea what that is | 20:52:01 |
| Capypara | but I'll try | 20:52:13 |
| Capypara | but GNOME isn't segfaulting or anything like that | 20:54:00 |
| Capypara | it just exits | 20:54:01 |
| Capypara | As far as I can tell at least | 20:54:08 |
| K900 | The compositor is very likely crashing | 20:54:25 |
| Capypara | Is it supposed to break then when I hit coredumpctl debug and trigger the crash? | 20:54:56 |
| Capypara | because coredumpctl doesn't break | 20:55:13 |
| K900 | No, coredumpctl debug starts a debugger on the last core dump it has recorded | 20:55:35 |
| Capypara | okay but that is Spotify, so I guess GNOME is not segfaulting | 20:56:21 |
| K900 | You can use coredumpctl (no arguments) to see all the core dumps | 20:56:37 |
| K900 | And then use coredumpctl debug <pid> | 20:56:45 |
| Capypara | Last one is from yesterday. | 20:56:53 |
| K900 | Last or first? They're ordered oldest to newest | 20:57:08 |
| Capypara | Yeah the most recent one | 20:57:14 |
| Capypara | As I said, GNOME doesn't crash, the process just exits with exit code 0 | 20:57:24 |
| Capypara | ah no sorry | 20:58:45 |
| Capypara | Nov 15 21:53:27 kirschbaum systemd[2994]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
| 20:58:53 |
| Capypara | Was reading the wrong entry, it's SIGKILL | 20:59:04 |
| K900 | That sounds like OOM | 20:59:21 |
| Capypara | the kernel has no OOM report in its logs | 20:59:31 |
| Capypara | there is no log about anything unusual in general | 20:59:38 |
| K900 | systemd-oomd | 20:59:39 |
| Capypara | (in the kernel log) | 20:59:42 |
| Capypara | nope | 21:02:14 |
| Capypara | at least it has nothing in it's journal about it killing anything | 21:02:23 |
