You are not logged in.
- Topics: Active | Unanswered
#1 2025-03-23 04:29:12
- Chaseis4344
- Member
- Registered: 2024-06-29
- Posts: 6
[SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
I have been using Budgie for almost 8 months now without problem.
After a linux-firmware update and a reboot, I log into Budgie and get a fatal error screen, the rest of the budgie environment works, just the WM is dead.
When digging around in my journal, the WM tried to open ~/Desktop and failed, so I created ~/Desktop for it to open and operate, the next time I start up Budgie, instead of a Fatal Error splash and the rest of the Budgie ecosystem working, I get a black screen on which all my startup applications paint themselves on, any other applications that startup paint themselves on the black background.
I installed MATE to get it into a working state again, and dig around in the journal again, I found on startup that Mutter is getting shutdown with signal 5 by the kernel.
I tried reinstalling the whole Budgie Ecosystem a couple different way, but it just refuses to work and I have found no other docs on this.
systemd also provides a core-dump that I tried to read to no avail
Mar 23 00:08:45 Game-Machine budgie-wm[3575]: Running Mutter(Budgie) (using mutter 0.9.4) as a X11 window and compositing manager
Mar 23 00:08:45 Game-Machine wireplumber[3498]: spa.bluez5: BlueZ system service is not available
Mar 23 00:08:45 Game-Machine wireplumber[3498]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Mar 23 00:08:45 Game-Machine wireplumber[3498]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Mar 23 00:08:45 Game-Machine gsd-media-keys[3405]: Unable to get default sink
Mar 23 00:08:45 Game-Machine gsd-media-keys[3405]: Unable to get default source
Mar 23 00:08:45 Game-Machine budgie-wm[3575]: g_variant_get_string: assertion 'value != NULL' failed
Mar 23 00:08:45 Game-Machine budgie-wm[3575]: The mapping function given to g_settings_get_mapped() for key 'overlay-key' in schema 'org.gnome.mutter' returned FALSE when given a NULL value.
Mar 23 00:08:45 Game-Machine kernel: traps: budgie-wm[3575] trap int3 ip:7886e5d1c248 sp:7ffc75743760 error:0 in libglib-2.0.so.0.8400.0[63248,7886e5cd7000+a7000]
Mar 23 00:08:45 Game-Machine systemd-coredump[3597]: Process 3575 (budgie-wm) of user 1000 terminated abnormally with signal 5/TRAP, processing...
Mar 23 00:08:45 Game-Machine systemd[1]: Created slice Slice /system/systemd-coredump.
Mar 23 00:08:45 Game-Machine systemd[1]: Started Process Core Dump (PID 3597/UID 0).
Mar 23 00:08:46 Game-Machine systemd-coredump[3598]: [?] Process 3575 (budgie-wm) of user 1000 dumped core.
Stack trace of thread 3575:
#0 0x00007886e5d1c248 g_log_structured_array (libglib-2.0.so.0 + 0x63248)
#1 0x00007886e5d1c547 g_log_default_handler (libglib-2.0.so.0 + 0x63547)
#2 0x00007886e5d1c7cc g_logv (libglib-2.0.so.0 + 0x637cc)
#3 0x00007886e5d1cb54 g_log (libglib-2.0.so.0 + 0x63b54)
#4 0x00007886e5f62403 g_settings_get_mapped (libgio-2.0.so.0 + 0xf2403)
#5 0x00007886e5b71a87 meta_context_start (libmagpie-0.so.0 + 0xb6a87)
#6 0x000062445f1592a4 n/a (/usr/bin/budgie-wm + 0x82a4)
#7 0x00007886e53c4488 n/a (libc.so.6 + 0x27488)
#8 0x00007886e53c454c __libc_start_main (libc.so.6 + 0x2754c)
#9 0x000062445f159315 n/a (/usr/bin/budgie-wm + 0x8315)
Stack trace of thread 3581:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542ee74 n/a (libc.so.6 + 0x91e74)
#3 0x00007886e54a9a06 ppoll (libc.so.6 + 0x10ca06)
#4 0x00007886e5d7ae27 n/a (libglib-2.0.so.0 + 0xc1e27)
#5 0x00007886e5d17de7 g_main_loop_run (libglib-2.0.so.0 + 0x5ede7)
#6 0x00007886e5f84a04 n/a (libgio-2.0.so.0 + 0x114a04)
#7 0x00007886e5d4ea3e n/a (libglib-2.0.so.0 + 0x95a3e)
#8 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#9 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3578:
#0 0x00007886e54b488d syscall (libc.so.6 + 0x11788d)
#1 0x00007886e5d49350 g_cond_wait (libglib-2.0.so.0 + 0x90350)
#2 0x00007886e5cdedac n/a (libglib-2.0.so.0 + 0x25dac)
#3 0x00007886e5d4f9d2 n/a (libglib-2.0.so.0 + 0x969d2)
#4 0x00007886e5d4ea3e n/a (libglib-2.0.so.0 + 0x95a3e)
#5 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#6 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3579:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542ee74 n/a (libc.so.6 + 0x91e74)
#3 0x00007886e54a9a06 ppoll (libc.so.6 + 0x10ca06)
#4 0x00007886e5d7ae27 n/a (libglib-2.0.so.0 + 0xc1e27)
#5 0x00007886e5d16535 g_main_context_iteration (libglib-2.0.so.0 + 0x5d535)
#6 0x00007886e5d16592 n/a (libglib-2.0.so.0 + 0x5d592)
#7 0x00007886e5d4ea3e n/a (libglib-2.0.so.0 + 0x95a3e)
#8 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#9 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3582:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542ee74 n/a (libc.so.6 + 0x91e74)
#3 0x00007886e54a9a06 ppoll (libc.so.6 + 0x10ca06)
#4 0x00007886e5d7ae27 n/a (libglib-2.0.so.0 + 0xc1e27)
#5 0x00007886e5d16535 g_main_context_iteration (libglib-2.0.so.0 + 0x5d535)
#6 0x00007886e33642fe n/a (libdconfsettings.so + 0x62fe)
#7 0x00007886e5d4ea3e n/a (libglib-2.0.so.0 + 0x95a3e)
#8 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#9 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3584:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542f4bc n/a (libc.so.6 + 0x924bc)
#3 0x00007886e5431c0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4 0x00007886cdb003ee n/a (libgallium-25.0.2-arch1.2.so + 0x5003ee)
#5 0x00007886cdacaecc n/a (libgallium-25.0.2-arch1.2.so + 0x4caecc)
#6 0x00007886cdb0031d n/a (libgallium-25.0.2-arch1.2.so + 0x50031d)
#7 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#8 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3580:
#0 0x00007886e54b488d syscall (libc.so.6 + 0x11788d)
#1 0x00007886e5d4a067 g_cond_wait_until (libglib-2.0.so.0 + 0x91067)
#2 0x00007886e5cded75 n/a (libglib-2.0.so.0 + 0x25d75)
#3 0x00007886e5d504db n/a (libglib-2.0.so.0 + 0x974db)
#4 0x00007886e5d4ea3e n/a (libglib-2.0.so.0 + 0x95a3e)
#5 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#6 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3595:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542f4bc n/a (libc.so.6 + 0x924bc)
#3 0x00007886e5431c0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4 0x00007886cdb003ee n/a (libgallium-25.0.2-arch1.2.so + 0x5003ee)
#5 0x00007886cdacaecc n/a (libgallium-25.0.2-arch1.2.so + 0x4caecc)
#6 0x00007886cdb0031d n/a (libgallium-25.0.2-arch1.2.so + 0x50031d)
#7 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#8 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3591:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542f4bc n/a (libc.so.6 + 0x924bc)
#3 0x00007886e5431c0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4 0x00007886cdb003ee n/a (libgallium-25.0.2-arch1.2.so + 0x5003ee)
#5 0x00007886cdacaecc n/a (libgallium-25.0.2-arch1.2.so + 0x4caecc)
#6 0x00007886cdb0031d n/a (libgallium-25.0.2-arch1.2.so + 0x50031d)
#7 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#8 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
Stack trace of thread 3585:
#0 0x00007886e543abe2 n/a (libc.so.6 + 0x9dbe2)
#1 0x00007886e542ee33 n/a (libc.so.6 + 0x91e33)
#2 0x00007886e542f4bc n/a (libc.so.6 + 0x924bc)
#3 0x00007886e5431c0e pthread_cond_wait (libc.so.6 + 0x94c0e)
#4 0x00007886cdb003ee n/a (libgallium-25.0.2-arch1.2.so + 0x5003ee)
#5 0x00007886cdacaecc n/a (libgallium-25.0.2-arch1.2.so + 0x4caecc)
#6 0x00007886cdb0031d n/a (libgallium-25.0.2-arch1.2.so + 0x50031d)
#7 0x00007886e543270a n/a (libc.so.6 + 0x9570a)
#8 0x00007886e54b6aac n/a (libc.so.6 + 0x119aac)
ELF object binary architecture: AMD x86-64
Mar 23 00:08:46 Game-Machine systemd[1]: systemd-coredump@0-3597-0.service: Deactivated successfully.
Mar 23 00:08:46 Game-Machine systemd[1]: systemd-coredump@0-3597-0.service: Consumed 146ms CPU time, 97.7M memory peak.
Mar 23 00:08:46 Game-Machine budgie-session-binary[3315]: WARNING: Application 'org.buddiesofbudgie.BudgieWm.desktop' killed by signal 5Kinda new to troubleshooting on this level, but another stack trace like this happens the same way after Mutter tries to startup again.
I have no clue what the stack trace is saying or what the issue is and would love any help deemed necessary.
Thanks for your time.
Last edited by Chaseis4344 (2025-03-23 18:09:46)
Offline
#2 2025-03-23 07:08:26
- seth
- Member
- Registered: 2012-09-03
- Posts: 62,203
Re: [SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
I found on startup that Mutter is getting shutdown with signal 5 by the kernel.
Probably not 
The pocess aborts when reading its settings, this most likely happens because you just updated mutter to v48 - you may be more lucky w/ mutter46.
Cause is probably some "overlay-key"… key:
The mapping function given to g_settings_get_mapped() for key 'overlay-key' in schema 'org.gnome.mutter' returned FALSE when given a NULL value
This happens frequently, https://github.com/BuddiesOfBudgie/magpie/issues/32
Offline
#3 2025-03-23 18:10:29
- Chaseis4344
- Member
- Registered: 2024-06-29
- Posts: 6
Re: [SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
I downgraded to Mutter 46.5 and everything works correctly now, thanks for the help!
Last edited by Chaseis4344 (2025-03-23 18:10:46)
Offline
#4 2025-03-23 18:43:18
- Zoddo
- Member
- Registered: 2021-06-11
- Posts: 4
Re: [SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
Hello,
Having the exact same issue, how have you downgraded to mutter 46?
`pacman -S mutter46` doesn't work, because budgie-desktop explicitly depends of magpie-wm which in turns explicitly depends of mutter.
And anyway, mutter and mutter46 have different soname (libmutter-16.so vs libmutter-14.so) so they aren't compatible.
For now, I have downgraded to mutter 47.6-1 from the pacman cache, but that put me in a partial upgrade state I'd like to avoid if there is a proper solution to downgrade to mutter46.
Offline
#5 2025-03-23 20:48:32
- seth
- Member
- Registered: 2012-09-03
- Posts: 62,203
Re: [SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
https://wiki.archlinux.org/title/Downgrading_packages
if there is a proper solution to downgrade to mutter46
Not if
explicitly depends of mutter … different soname (libmutter-16.so vs libmutter-14.so)
and this would force you to symlink the library.
Make sure to file a bug upstream.
Offline
#6 2025-03-23 21:36:58
- Zoddo
- Member
- Registered: 2021-06-11
- Posts: 4
Re: [SOLVED]Budgie WM (Mutter) gets SIGTRAP killed on startup
Thanks, I'm aware of how to downgrade a package, but Chaseis4344's message implied that they were able to replace mutter with the mutter46 package on their system.
Hence my question.
Make sure to file a bug upstream.
The issue was reported to Ubuntu maintainers who already made a patch to budgie which was merged upstream, but it's not been released in any version yet.
I'll make an issue to the budgie-desktop package here to ask if the patch can be backported while waiting for the upstream to release a new version.
I know Arch usually avoids to patch upstream code, but since budgie-desktop completely crashes currently, I think such a patch may be exceptionally warranted.
Edit: Done: https://gitlab.archlinux.org/archlinux/ … -/issues/1
Last edited by Zoddo (2025-03-23 22:14:28)
Offline