[Bug] Panel crash when loading plugins

[EbonJaeger]

Description

Reported on the Solus forums. After installing updates after the Week 45 sync introducing GNOME 49 and Budgie 10.9.3 and rebooting, the panel crashes upon login, showing the Fail Whale. The backtrace indicates a failure on trying to get a plugin's information in the panel plugin manager code.

Budgie version

10.9.3

Operating System

Solus 4.7

Steps to reproduce the issue

1. Attempt to log in

Actual result

The Fail Whale appears before getting to a Budgie session.

Expected result

That Budgie starts normally and does not crash.

Additional information

Provided backtrace:

Stack trace of thread 1290:
                                               #0  0x00007f7e1b0c726a g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0 + 0x1e26a)
                                               #1  0x000055e731c0e435 get_plugin_info (/usr/bin/budgie-panel + 0x3c435)
                                               #2  0x000055e731c0eb86 budgie_panel_plugin_manager_load_applet_instance (/usr/bin/budgie-panel + 0x3cb86)
                                               #3  0x000055e731bf0930 budgie_panel_load_applets (/usr/bin/budgie-panel + 0x1e930)
                                               #4  0x000055e731be4767 budgie_panel_manager_load_panel (/usr/bin/budgie-panel + 0x12767)
                                               #5  0x000055e731be90d1 budgie_panel_manager_load_panels (/usr/bin/budgie-panel + 0x170d1)
                                               #6  0x00007f7e1ac5a052 n/a (libffi.so.8 + 0x9052)
                                               #7  0x00007f7e1ac58c01 n/a (libffi.so.8 + 0x7c01)
                                               #8  0x00007f7e1ac592dd ffi_call (libffi.so.8 + 0x82dd)
                                               #9  0x00007f7e1b0c4d83 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x1bd83)
                                               #10 0x00007f7e1b0b9eae g_closure_invoke (libgobject-2.0.so.0 + 0x10eae)
                                               #11 0x00007f7e1af761f7 own_with_closures_on_name_acquired (libgio-2.0.so.0 + 0x1761f7)
                                               #12 0x00007f7e1af75cbd actually_do_call (libgio-2.0.so.0 + 0x175cbd)
                                               #13 0x00007f7e1af75ef7 call_acquired_handler (libgio-2.0.so.0 + 0x175ef7)
                                               #14 0x00007f7e1af6dec4 emit_signal_instance_in_idle_cb (libgio-2.0.so.0 + 0x16dec4)
                                               #15 0x00007f7e1ace18db g_main_dispatch (libglib-2.0.so.0 + 0x808db)
                                               #16 0x00007f7e1ace2948 g_main_context_dispatch_unlocked (libglib-2.0.so.0 + 0x81948)
                                               #17 0x00007f7e1ace2bb7 g_main_loop_run (libglib-2.0.so.0 + 0x81bb7)
                                               #18 0x00007f7e1a925130 gtk_main (libgtk-3.so.0 + 0x325130)
                                               #19 0x000055e731be31f8 _vala_main (/usr/bin/budgie-panel + 0x111f8)
                                               #20 0x00007f7e1a02b569 n/a (libc.so.6 + 0x2b569)
                                               #21 0x00007f7e1a02b61a __libc_start_main (libc.so.6 + 0x2b61a)
                                               #22 0x000055e731be3245 _start (/usr/bin/budgie-panel + 0x11245)

User states that they have a stock panel, with the addition of the Trash applet.

Last known snapshot of user's setup:

[brent111]

as the user who is mentioned, there are no inaccuracies. this was the immediate (save for reboots) post-update conditon. the 9/17 picture of panel is the same as 11/7 today.
thank you.

[fossfreedom]

Can you please install your distros debug symbols package and generate a gdb based back-trace? That will help with the diagnoses of what is being passed and at what point - get_plugin_info is being called in a few places in plugin-manager.c

[rainlessness]

Same issue here. Adding my journal from start of the update to the rollback. And my panel-applets ss.

update-journal.log

[brent111]

Should I try to recover my Solus Budgie with the reset panel command?
what is the reset panel command (?) as well. Thank you.

[fossfreedom]

nohup budgie-panel --reset --replace &

[brent111]

Can you please install your distros debug symbols package and generate a gdb based back-trace?

got all the debug packages and generated a journalctl log last night. Do you want me to attach it (its in gisthub)? Or are you asking for something different?

[fossfreedom]

A gdb backtrace is a txt file so you can attach it here

[brent111]

journal222.log

journal222.txt

these are both the same thanks

[fossfreedom]

Sadly this is a journalctl file, not a gdb backtrace of your crash file. Please consult your distro maintainers how to generate a trace from your distro crash file.

[brent111]

Sadly this is a journalctl file, not a gdb backtrace of your crash file. Please consult your distro maintainers how to generate a trace from your distro crash file.

so don't do it this way?: https://docs.buddiesofbudgie.org/developer/workflow/providing-backtraces/
or should I ask solus? thanks for your patience with me

[fossfreedom]

In this case please ask your maintainers of the Solus distro.

[brent111]

I will thanks.

[corn-bean]

Using Chatgpt I was able to produce this backtrace using gdb on the running budgie-wm that crashed

budgie-backtrace.txt

I couldn't tell ya what it means, but hopefully it helps. I currently also have the "Oh! Something went wrong" screen and using i3 for now 😢 I seen that it had something to do with budgie-panel via journalctl just like Brent here.

Also, it's crazy that a panel crash can nuke the whole WM no?

Thanks for your help 🙏

Edit: Also, I'll say that I'm guessing the crash is due to applets from the Ubuntu budgie team maybe using python2. I know I had the weather panel applet and given that python2 is gutted now this has caused the crash? Just my suspicions...

[EbonJaeger]

@corn-bean Unfortunately, you need to attach to budgie-panel, not budgie-session, so there doesn't appear to be anything useful in that trace.