Hi, >>DEBUGINFOD_URLS="https://debuginfod.debian.net"; coredumpctl gdb Partial output as below and full output as per link. Thanks.
https://drive.google.com/file/d/19pahjyQSf_PRw-zQDwtC9FWRPcGQvUfo/view?usp=sharing # DEBUGINFOD_URLS="https://debuginfod.debian.net"; coredumpctl gdb PID: 1720 (gnome-shell) UID: 117 (Debian-gdm) GID: 122 (Debian-gdm) Signal: 11 (SEGV) Timestamp: Sat 2023-09-09 19:13:27 +08 (1 day 12h ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-117.slice/session-c1.scope Unit: session-c1.scope Slice: user-117.slice Session: c1 Owner UID: 117 (Debian-gdm) Boot ID: db5045b3be454eabaf40ab7634cdd15f Machine ID: e2ff68e6a046472b82838d16f35a6e1f Hostname: meixian Storage: /var/lib/systemd/coredump/core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst (present) Size on Disk: 6.4M Message: Process 1720 (gnome-shell) of user 117 dumped core. Module libudev.so.1 from deb systemd-254.1-2.amd64 Module libsystemd.so.0 from deb systemd-254.1-2.amd64 Stack trace of thread 1720: #0 0x00007f9e956ced54 meta_display_get_x11_display (libmutter-12.so.0 + 0xced54) #1 0x00007f9e956f9a3b n/a (libmutter-12.so.0 + 0xf9a3b) #2 0x00007f9e95e95f8f g_initable_new_valist (libgio-2.0.so.0 + 0x7df8f) #3 0x00007f9e95e96069 g_initable_new (libgio-2.0.so.0 + 0x7e069) #4 0x00007f9e956f9dda n/a (libmutter-12.so.0 + 0xf9dda) #5 0x00007f9e956fd5ce n/a (libmutter-12.so.0 + 0xfd5ce) #6 0x00007f9e956fd62d n/a (libmutter-12.so.0 + 0xfd62d) #7 0x00007f9e9568b04e meta_cursor_tracker_get_sprite (libmutter-12.so.0 + 0x8b04e) #8 0x00007f9e94d4cf7a n/a (libffi.so.8 + 0x6f7a) #9 0x00007f9e94d4c40e n/a (libffi.so.8 + 0x640e) #10 0x00007f9e94d4cb0d ffi_call (libffi.so.8 + 0x6b0d) Regards, Hor Jiun Shyong 何俊雄 Simon McVittie <s...@debian.org> 于2023年9月11日周一 01:40写道： > 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 >
