On Sat, 09 Sep 2023 at 12:40:53 +0800, Hor Jiun Shyong wrote:
> coredumpctl_gdb.txt.gz
The relevant part is:
#0 0x00007f9e956ced54 in meta_display_get_x11_display () from
/lib/x86_64-linux-gnu/libmutter-12.so.0
#1 0x00007f9e956f9a3b in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#2 0x00007f9e95e95f8f in g_initable_new_valist () from
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#3 0x00007f9e95e96069 in g_initable_new () from
/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x00007f9e956f9dda in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#5 0x00007f9e956fd5ce in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#6 0x00007f9e956fd62d in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#7 0x00007f9e9568b04e in meta_cursor_tracker_get_sprite () from
/lib/x86_64-linux-gnu/libmutter-12.so.0
#8 0x00007f9e94d4cf7a in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
but this is of limited usefulness since you don't have debug symbols for
mutter available.
The easiest way to get the debug symbols is to use:
DEBUGINFOD_URLS="https://debuginfod.debian.net"; coredumpctl gdb
and type "bt" at the (gdb) prompt when the symbols have finished
downloading.
Or you could enable the debug symbols apt repository (see
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols)
and install the libmutter-12-0-dbgsym package. We don't need any other
packages for this particular crash.
> core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst.gz
In general we can't get a useful backtrace from the actual compressed
core dump: that's something that the bug reporter needs to do. I tried to
get a useful backtrace from this with debug symbols, but it doesn't match
the result you sent and I'm not sure whether it really makes sense.
Sharing these core dumps is also a privacy risk because they can contain
private information, although in this case the crash was from the gdm
login screen before you had a chance to enter any passwords, so it's
probably harmless.
smcv
