This thread is for the purpose of trying to diagnose the crashes that some people are experiencing with Budgie 10.9.3. The upstream issue for these crashes is here.
Please keep all discussion here focused on the issue.
What we know
Some users are experiencing crashes following the update to Budgie 10.9.3. The crash seems to stem from the loading of a panel applet.
What we don't know
It is currently unknown what applet or applets trigger the crash. Testing by team members which involved installing all applets available in the Solus repository and adding them all to a panel did not result in a crash. It is unknown if multiple instances of an applet on a panel, say, spacers, could be involved.
What we need
Short of a full coredump with debug symbols, which would be huge and not easy to share, what we really need is a solid way to get the problem to occur so members of the Solus and Budgie teams can get it to happen, and see exactly where the issue is occurring.
If the crash is happening to you, it will be helpful to know what applets are on your panels.
Generating a backtrace
Before generating a backtrace, please make sure you have installed debug symbols and gdb:
sudo eopkg install gdb budgie-desktop-dbginfo libpeas-2-dbginfo libgtk-3-dbginfo glib2-dbginfo glibc-dbginfo
To get a backtrace with the relevant information, run the following from a terminal or console:
sudo coredumpctl gdb budgie-panel
This will put you in a gdb session with a prompt. From here, do the following to save it to a file:
set logging file <path/to/file>
set logging enabled
thread apply all backtrace full
Press 'c' and "Enter" to show all test without scrolling or paging. The session is exited by typing q in the prompt and hitting Enter on your keyboard.
