By chance (while developing some netplan code), I seem to have found a reproducer for this bug... I don't know what is going on, but calling the 'Trigger' method from the attached 'dbus.c' file will kill the GDM session in a reproducible way.
The invalid `kill(-1, SIGINT);` of line 21, seems to somehow crash the whole DBus/GDM and other services. So there must be some problem inside DBus's error handling, which is somehow triggered during the updates.
* WARNING: calling the Trigger method via busctl will kill your GDM session
*
* compile: gcc -o out dbus.c `pkg-config --cflags --libs libsystemd glib-2.0`
* execute: sudo ./out
* trigger: sudo busctl call io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan Trigger
By chance (while developing some netplan code), I seem to have found a reproducer for this bug... I don't know what is going on, but calling the 'Trigger' method from the attached 'dbus.c' file will kill the GDM session in a reproducible way.
The invalid `kill(-1, SIGINT);` of line 21, seems to somehow crash the whole DBus/GDM and other services. So there must be some problem inside DBus's error handling, which is somehow triggered during the updates.
* WARNING: calling the Trigger method via busctl will kill your GDM session
*
* compile: gcc -o out dbus.c `pkg-config --cflags --libs libsystemd glib-2.0`
* execute: sudo ./out
* trigger: sudo busctl call io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan Trigger