Budgie-panel keeps crashing despite repeated resets

Budgie Desktop
1

This has been happening for a very long time, and finally, I’m really fed up! I can see coredumps being created with budgie-panel-***cordeump. I checked journalctl only to find the following before after the panel crashed all together:

  #3  0x00007f62e19e9721 n/a (
                                                    #4  0x00007f62e1a11195 n/a (
                                                    #5  0x00007f62de7bc6db start
                                                    #6  0x00007f62e0e3e88f __clo
                                                    
                                                    Stack trace of thread 6603:
                                                    #0  0x00007f62e0e38839 sysca
                                                    #1  0x00007f62e1a2f89a g_con
                                                    #2  0x00007f62e19bc571 n/a (
                                                    #3  0x00007f62e19bcb2c g_asy
                                                    #4  0x00007f62e1a11c3e n/a (
                                                    #5  0x00007f62e1a11195 n/a (
                                                    #6  0x00007f62de7bc6db start
                                                    #7  0x00007f62e0e3e88f __clo
                                                    
                                                    Stack trace of thread 6056:
                                                    #0  0x00007f62e0e31bf9 __GI_
                                                    #1  0x00007f62e19e95c9 n/a (
                                                    #2  0x00007f62e19e9962 g_mai
                                                    #3  0x00007f62e1fd70e6 n/a (
                                                    #4  0x00007f62e1a11195 n/a (
                                                    #5  0x00007f62de7bc6db start
                                                    #6  0x00007f62e0e3e88f __clo
lines 1188-1210/1210 (END)
                                                    #3  0x00007f62e19e9721 n/a (libglib-2.0.so.0)
                                                    #4  0x00007f62e1a11195 n/a (libglib-2.0.so.0)
                                                    #5  0x00007f62de7bc6db start_thread (libpthread.so.0)
                                                    #6  0x00007f62e0e3e88f __clone (libc.so.6)
                                                    
                                                    Stack trace of thread 6603:
                                                    #0  0x00007f62e0e38839 syscall (libc.so.6)
                                                    #1  0x00007f62e1a2f89a g_cond_wait_until (libglib-2.0.so.0)
                                                    #2  0x00007f62e19bc571 n/a (libglib-2.0.so.0)
                                                    #3  0x00007f62e19bcb2c g_async_queue_timeout_pop (libglib-2.0.so.0)
                                                    #4  0x00007f62e1a11c3e n/a (libglib-2.0.so.0)
                                                    #5  0x00007f62e1a11195 n/a (libglib-2.0.so.0)
                                                    #6  0x00007f62de7bc6db start_thread (libpthread.so.0)
                                                    #7  0x00007f62e0e3e88f __clone (libc.so.6)
                                                    
                                                    Stack trace of thread 6056:
                                                    #0  0x00007f62e0e31bf9 __GI___poll (libc.so.6)
                                                    #1  0x00007f62e19e95c9 n/a (libglib-2.0.so.0)
                                                    #2  0x00007f62e19e9962 g_main_loop_run (libglib-2.0.so.0)
                                                    #3  0x00007f62e1fd70e6 n/a (libgio-2.0.so.0)
                                                    #4  0x00007f62e1a11195 n/a (libglib-2.0.so.0)
                                                    #5  0x00007f62de7bc6db start_thread (libpthread.so.0)
                                                    #6  0x00007f62e0e3e88f __clone (libc.so.6)

Any clue what’s wrong?
PS: I’ve already reset budgie panel twice till this date

2

Reset the panel but run for a while without any customisation on the panel. Does it crash?

Then gradually introduce your changes … hopefully this way we can identify the culprit change.

3

Well, I’ve found it. It’s the global menu applet which causes the entire budgie-panel to become unstable and crash. But I find this applet to be an everyday need, any recommendations?

4

what version of UB are you using? 18.04 or 19.10 ?

Is this issue with any specific application? Or is it with one application more than others? Any particular action you need to-do to make things crash?

5

I’m on 18.04 and it crashes randomly. There’s no need to do anything. I just use vscode + terminal. Don’t know what’s wrong

6

strictly speaking the crash dump file needs analysing to find out what the issue is causing the crash. Debug symbols needs to be installed first, then make it crash

https://wiki.ubuntu.com/DebuggingProgramCrash

Then once a good trace file is found pin-pointing a crash a fix (in theory) can be devised and pushed to the repos.

I’ve had a quick look to see if I can recompile the 19.10 version of vala-app-menu and vala-panel for 18.04 - unfortunately the version of meson is to new. Not really a big issue for a talented source compiler - need to grab a later version of meson and compile against that.

So - yes - two routes for 18.04 - both needs much more time and effort than I have at the moment :frowning:

7

Where is your global menu : left, middle or right of panel ?

Mine is at center and I don’t have any crash of panel.

I don’t pretend it’s the solution but hey, why not ?

( when placed at left or right of panel, global menu can’t display longer menus and truncates them, that may cause other issues as well… )

8

Drop me a link to the source. I use meson quite a bit, and I’ll try to figure it out.
PS: I already have debugging symbols installed, come on I’m a dev too!

9

I didn’t know! Great :slight_smile:

I use the package ubuntu-dev-tools

Then first pull-lp-source vala-panel to get the latest source

First trick is to get that to compile and install

Then the appmenu builds upon that - pull-lp-source vala-panel-appmenu

1 Like
10

Cool, I’ll do that as soon as possible and report back

11

Hmm, I’m back after a long time (was on a little break). I managed to see what was causing the crash from journalctl. This time it is pretty clear instead of random memory addresses:

-- 
-- Process 2974 (budgie-panel) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Dec 16 13:47:14 workstation budgie-panel.desktop[3677]: # Failed to load module "appmenu-gtk-module"
Dec 16 13:47:14 workstation dbus-daemon[2511]: [session uid=1000 pid=2511] Activating via systemd: service name='org.gnome.Terminal' unit='gnome
Dec 16 13:47:14 workstation systemd[2415]: Starting GNOME Terminal Server...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has begun starting up.
Dec 16 13:47:14 workstation gnome-terminal-[3726]: Failed to load module "appmenu-gtk-module"
Dec 16 13:47:14 workstation dbus-daemon[2511]: [session uid=1000 pid=2511] Successfully activated service 'org.gnome.Terminal'
Dec 16 13:47:14 workstation systemd[2415]: Started GNOME Terminal Server.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
12

Also doing: sudo apt list --installed | grep appmenu-gtk returns this:

appmenu-gtk-module-common/bionic,bionic,now 0.6.94-1 all [installed,automatic]
appmenu-gtk2-module/bionic,now 0.6.94-1 amd64 [installed,automatic]
appmenu-gtk3-module/bionic,now 0.6.94-1 amd64 [installed]
libappmenu-gtk2-parser0/bionic,now 0.6.94-1 amd64 [installed,automatic]
libappmenu-gtk3-parser0/bionic,now 0.6.94-1 amd64 [installed,automatic]
13

right - so its a buggy global menu issue - with the v0.6.94 version in the repos.

The next part of the investigation I guess is to compile the Focal version to see if it has the same issues.

14

Yeah this occurred to me too in the past; never knew it was the Global Menu, but once I switched over to a Windows like layout (no global menu) issue went away…