Stack trace not included in GNOME Shell crash report in JournalErrors

[Benjamin Drung]

1. Use Ubuntu 23.10 with all updates
2. kill gnome-shell: killall -11 gnome-shell
3. log-in again
4. Wait for the apport crash window for reporting
5. Show details

The JournalErrors does not contain the stack trace, but now I found it in ShellJournal:

 [ 87.744546] ubuntu-2304-2 gnome-shell[1048]: GNOME Shell crashed with signal 11
 [ 87.744546] ubuntu-2304-2 gnome-shell[1048]: == Stack trace for context 0x56355c3ca0f0 ==
 [ 87.745201] ubuntu-2304-2 gnome-shell[1048]: #0 56355c491fe8 i resource:///org/gnome/shell/ui/init.js:21 (2b3376570ba0 @ 48)

The crash is not logged with a high enough severity to let it appear in JournalErrors.

[Daniel van Vugt (vanvugt)]

This just means the process was not active in JavaScript. Most of the time gnome-shell is running native C code (in mutter or in gnome-shell) so there is no JavaScript stack to display.

[Benjamin Drung (bdrung)]

This bug report is not about a too short stack trace. This report is about the stack trace being logged with lower severity than error.

Will the logged stack trace be logged as error if there is a JavaScript stack to display?

[Daniel van Vugt (vanvugt)]

Sorry I was trying to rush through 7 days of bugs and misread that. Looks like gjs is to blame:

https://gitlab.gnome.org/GNOME/gjs/-/blob/master/gjs/stack.cpp?ref_type=heads#L25