Page MenuHomeSolus

Budgie desktop fails to start
Closed, ResolvedPublic

Description

Hi,

After updating, budgie session fails to start.
It seems to have somtehing to do with mutter:

févr. 27 20:54:45 karyu budgie-wm.desktop[2170]: budgie-wm: symbol lookup error: /usr/lib/libmutter-9.so.0: undefined symbol: gbm_bo_write
févr. 27 20:54:45 karyu gnome-session[1935]: gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' exited with code 127
févr. 27 20:54:45 karyu gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' exited with code 127
févr. 27 20:54:45 karyu budgie-wm.desktop[2177]: budgie-wm: symbol lookup error: /usr/lib/libmutter-9.so.0: undefined symbol: gbm_bo_write
févr. 27 20:54:45 karyu gnome-session[1935]: gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' exited with code 127
févr. 27 20:54:45 karyu gnome-session[1935]: gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' respawning too quickly
févr. 27 20:54:45 karyu gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' exited with code 127
févr. 27 20:54:45 karyu gnome-session-binary[1935]: WARNING: App 'budgie-wm.desktop' respawning too quickly
févr. 27 20:54:45 karyu gnome-session-binary[1935]: Unrecoverable failure in required component budgie-wm.desktop

Related Objects

Event Timeline

Does going into a TTY, running sudo eopkg it --reinstall mesalib and rebooting fix the problem temporarily? If so this sounds like the same thing I've been dealing with for over a month now, but I've been unable to find any logs like this.

Yes, it works!

I also found this report (https://dev.getsol.us/R2066:86f0418fdcb982eeb99d2d3545d49597b2f87793) where someone had similar message when compiling Budgie

Many thanks.

Yeah, it all seems to be related, but no one has yet been able to figure out why. Whatever it is is Solus-specific.

We should take a look at updating mutter to 41.4 aswell, any Global Maintainer on gnome/budgie want to take a look?

@_dje i'd also be interested in seeing the output of your inxi -G and whether it matches EbonJaeger's system at all.

For reference, mine is:

Graphics:
  Device-1: AMD Baffin [Radeon RX 550 640SP / RX 560/560X] driver: amdgpu
    v: kernel
  Display: x11 server: X.Org 1.20.14 driver: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  OpenGL: renderer: AMD Radeon RX 560 Series (POLARIS11 DRM 3.42.0
    5.14.21-210.current LLVM 13.0.0)
    v: 4.6 Mesa 21.3.6

We should take a look at updating mutter to 41.4 aswell, any Global Maintainer on gnome/budgie want to take a look?

@ZachBacon is the GM for GNOME

Here is my inxi -G output:

Graphics:
  Device-1: Intel HD Graphics 620 driver: i915 v: kernel
  Device-2: Chicony XiaoMi USB 2.0 Webcam type: USB driver: uvcvideo
  Display: server: X.Org 1.20.14 driver: loaded: modesetting
    unloaded: fbdev,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.3.6

As an update, I haven't experienced this issue in months now.

Nice. There have been a lot of updates to our compiler toolchain, mesa, mutter, budgie, etc. since this issue first appeared so hopefully some of that finally fixed it

EbonJaeger claimed this task.

This seems to have been fixed a long time ago at this point, closing.