[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

2023-11-07 Thread Daniel van Vugt
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 ** Package changed: gnome-shell (Ubuntu) => gjs (Ubuntu) -- You received this bug notification because you are a

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

2023-11-07 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2041680 Title: Stack trace not included in GNOME Shell crash

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

2023-11-07 Thread Benjamin Drung
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? -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 2041680] Re: Stack trace not included in GNOME Shell crash report in JournalErrors

2023-11-07 Thread Daniel van Vugt
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. ** Tags added: mantic ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received