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, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2041680 Title: Stack trace not included in GNOME Shell crash report in JournalErrors Status in gnome-shell package in Ubuntu: Invalid Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2041680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
