Diagnosing Budgie 10.9.3 crash

EbonJaeger

I tried adding a bunch of spaces and separators to a panel, but it still didn't crash.

brent

EbonJaeger 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. If you generate a backtrace, please make sure you have installed debug symbols:

sudo eopkg install budgie-desktop-dbginfo libpeas-2-dbginfo libgtk-3-dbginfo glib2-dbginfo

love it, thanks for this.
I can install the dbg stuff.

Walk me (us) through the correct way/procedure to furnish the kind of backtrace log you need and I will get on this tomorrow.

I am rollbacked now. I probably should update it and crash it before I do this I am guessing
edit/spell

EbonJaeger

Added instructions on the first post for getting a backtrace with symbols.

brent

EbonJaeger
I updated my rollback to crash it,
Installed all the stuff.
did that exact coredump command from buddies.
but no way to save it.

EbonJaeger set logging file <path/to/file>
set logging enabled
thread apply all backtrace full

writing this down and will try now.
brb 🙂

brent

EbonJaeger the extra instructions helped. posted my backtrace at Buddies, thank you

brent

brent set logging file <path/to/file>

I did that: /home/brent/
told me "is a directory"
so named it /home/brent/panel.log
accepted.
set logging enabled
ok
thread apply all backtrace full
--fail
fought with a lot of RET or QUIT options. Always ret/extend.
RESULT: no log saved al all
no option to save a log at all just a lotta RET or Keep going stuff.

thought I'd crawl thru the trenches to fix but the trenches is crawling thru me
panel.log does not exist

ugh. swear words. lager

brent

brent maybe it hated .log and wanted .txt?

anyway it's been hours of self-torture tonight to make the OS run right

[Solus Devs and Maintainers: "Hours? Hold My Beer"]

rainlessness

Here is my backtrace, hope i did it right

panel-crash.txt

MOD EDIT: Modified post to prevent link preview since it is so long.

Sebastian

I have tested the spacer theory further. After having 4 or 5 spacers in top panel, trying to add additional spacer crashes Budgie desktop settings app. Sometimes the session panel crashes too but restarts right away.Sometimes sessison crashes. When I get Oh no soemthing went wrong message, I could log out and re-login.
Then I also tried adding spacers to my bottom panel, which is in dock mode. Trying to add spacers there made crash the Budgie desktop settings app again. But when I added a seperater first, I could add a spacer without crash.
I then added 3 spacers to bottom panel, and somehow managed to get session crash with Oh no something went wrong screen. (Don't know the exact step what caused this) But this time the Oh no something went screen persist. Can't re-login, even after restart. I am fine with this, since I have also GNOME and niri installed as fallback.
I will now try to get the backtrace. Might need assistance for that.

Sebastian

[Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib64/libthread_db.so.1". Core was generated by/usr/bin/budgie-panel'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc52f9a926a in g_type_check_instance_is_fundamentally_a (fundamental_type=80, type_instance=0x55a5684b77d0)
at ../gobject/gtype.c:3917

warning: 3917 ../gobject/gtype.c: File or directory not found
[Current thread is 1 (Thread 0x7fc52d7cfc00 (LWP 12396))]
warning: File "/home/sebi/.gdbinit" auto-loading has been declined by your auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /home/sebi/.gdbinit

Edit: this is my backtrace. Hope I did it right.

Sebastian

After resetting Budgie panel with dconf reset -f /com/solus-project/budgie-panel/ I can log-in to Budgie without crash again for now.

brent

Harvey I assume the adding/loading has a chance to cause it.

but I have only two spacers and I can't even login. yet 🙂

Sebastian dconf reset -f /com/solus-project/budgie-panel/

is that ^ command preferable or identical to nohup budgie-panel --reset --relace & ?

Harvey

I had added heap of spacers in testing to try reproduce it prior, even recreated the panel of someone with the issue based on a screenshot and it would not crash.

So given Sebastian's example this time I created a new top panel and added a tonne of spacers (Maybe 20+), still no crash, then I added a few full more to the default bottom panel and it crashed.

Recreated it again this time it was 17 spacers to the default bottom panel (no other panels) and it crashed.

I assume the adding/loading has a chance to cause it.

brent

I'm still locked out of budgie. the reset panel plan seems inconclusive i.e. it will break again.

plan B. which is rollback is successful but eventually one has to update, so moot.

meanwhile at Buddies all is still up in the air (https://github.com/BuddiesOfBudgie/budgie-desktop/issues/766) but solution getting closer.

Good things come to those who wait. Patience.

Axios

I am just adding this if it is not of importance ignore it
When I updated My doc would not auto hide found 2 packs broken repaired and it works now.
(gnome-app-list and xorg-driver-input-libinput)
Dont remb which previous update it was I had to change my icons theme because in the system tray
they where not showing or showed funky. (Using korla-pgrey now)
My main doc is still plank.
Just seems strange the things surrounding the doc/apps so I tthought I would mention it.

This isnt another mutter issue?

EbonJaeger

Axios This is definitely an issue with applets and the applet loader in Budgie panel. Not related to Mutter or anything else external.

brent

EbonJaeger This is definitely an issue with applets and the applet loader

if we reset panel I wonder if we could try to crash it on our own. i.e. knowing what applet(s) exactly did this might have value? or parameters too narrow?

EbonJaeger

I've built a version of Budgie with the above patch. If people experiencing the crash could install both of these packages, and report if the crashes still occur, that would be very much appreciated.

brent

EbonJaeger how should I get into budgie to try this? panel reset method or rollback? thanks

EbonJaeger

brent If you install the packages via the virtual console and reboot, we should know immediately. Either it will work, or it will not.

sudo eopkg install https://shared.getsol.us/ebonjaeger/packages/budgie-desktop-10.9.4-280-1-x86_64.eopkg https://shared.getsol.us/ebonjaeger/packages/budgie-desktop-dbginfo-10.9.4-280-1-x86_64.eopkg