Bug#1036781: gnome-shell segfaults on boot shortly after realmd starts working

[Al Ma]

Package: gnome-shell
Version: 42.3.1-2
Severity: important
In the journal I've discovered a disturbing segfault:
Mai 25 23:43:55 AnonymizedComputerName dbus-daemon[820]: [system] Successfully activated service 'org.freedesktop.realmd'
Mai 25 23:43:55 AnonymizedComputerName systemd[1]: Started Realm and Domain Configuration.
Mai 25 23:43:55 AnonymizedComputerName realmd[1322]: claimed name on bus: org.freedesktop.realmd
Mai 25 23:43:55 AnonymizedComputerName kernel: show_signal_msg: 14 callbacks suppressed
Mai 25 23:43:55 AnonymizedComputerName kernel: gnome-shell[1068]: segfault at 0 ip 0000000000000000 sp 00007fffc9a8c8a8 error 14
Mai 25 23:43:55 AnonymizedComputerName kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Unfortunately, dmesg and syslog contain no additional information from the last moments before the segfault. In my understanding, this failure leads to the inability to start Wayland (and xorg kicks in instead).
Who is the real culprit and what to do? Any remedy or bugfix? Any (as small as possible) set of packages to upgrade?
I run Debian stable, kernel 5.10.0-23-amd64, with a few updated packages from testing. Probably related packages: linux-image-amd64 5.10.179-1, realmd 0.16.3-3, systemd 247.3-7+deb11u2, dbus 1.12.24-0+deb11u1.
The severity is raised because the bug is (in my understanding) a major reason for why Wayland is unusable on my machine.
Gratefully,
AlMa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20230525/9cb2a644/attachment.htm>