| 15 Nov 2025 |
 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 |
| Capypara | It's a mutter bug | 21:04:51 |
| Capypara | got confirmation from the GNOME matrix channel | 21:04:57 |
| Capypara | fixed in 49.1.1 | 21:04:59 |
| Capypara | mutter kills it's own process instead of the background app, lol | 21:05:15 |
| Capypara | Redacted or Malformed Event | 21:07:03 |
| Capypara | wait, we are on 49.1.1 | 21:08:24 |
| Capypara | for fucks sake | 21:18:25 |
| Capypara | it's a Flatpak bug actually | 21:18:29 |
| Capypara | https://github.com/flatpak/flatpak/pull/6375 | 21:18:30 |
| Capypara | Can also reproduce it under Fedora | 21:19:04 |
| Capypara | I just always run into the most cursed bugs somehow. | 21:19:49 |
| Capypara | I don't understand how the Linux desktop seemingly gets more broken every year, like what even | 21:21:34 |
| Capypara | I don't know much about how systemd slices/targets etc. actually work, but I guess the shell is running as PID 0 in some kind of PID namespace? Does systemd have no features to prevent a child process to send a SIGKILL in this context? | 21:25:56 |
| K900 | No | 21:26:22 |
| K900 | kill(0) is shortcut for "kill everything" | 21:26:36 |
| Capypara | Ahh right, right, I forgot. That's whats going on, of course. | 21:26:52 |
| Capypara | 0 kills everything. root PID is 1. | 21:27:04 |
