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

Simon McVittie smcv at debian.org
Sat May 27 12:08:09 BST 2023


On Thu, 25 May 2023 at 23:57:17 +0000, Al Ma wrote:
> Who is the real culprit and what to do?

Any time you are seeing a segfault or other crash, a backtrace
<https://wiki.debian.org/HowToGetABacktrace> would be useful information.
systemd-coredump is usually the easiest way to get this:
<https://wiki.debian.org/HowToGetABacktrace#Core_dump>

However, since you are running a mixed stable/testing system, you are on
your own: Debian does not have the resources to support every possible
combination of packages.

> 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.

As I've said on another of your bug reports, mixing stable and testing is
not a supportable situation, and even if we found a fix for this crash,
if you don't upgrade then you will never receive that fix. Please upgrade
to a fully testing system and see whether the crash persists.

A mixed Debian stable/testing system or a non-up-to-date Debian testing
system are both higher-risk environments than an up-to-date system that is
entirely Debian testing. After you have got onto the "upgrade to testing"
train, you should stay on it until the next station.

Debian testing is currently in hard freeze and is expected to be released
as Debian 12 in mid June, with the same packages that are currently in
testing, so at the moment it is just as tightly-controlled as stable
normally is.

    smcv



More information about the pkg-gnome-maintainers mailing list