Problem with budgie-core:amd64 10.6.1-1ubuntu2

Budgie Desktop
1

Hi…today we updated Budgie along with a bunch of other 22.04 updates.

After the update, none of our users could see their desktop. There was a message:

“Oh no! Something has gone wrong.
A problem has occurred and the system can’t recover.
Please log out and try again.”

There was a Log Out button which brought them back to the sddm or gdm greeter. The problem was repeatable on all the systems (neither logging out nor rebooting helped).

What was odd was that we could very briefly see the desktops and desktop icons just after clicking the Log Out button (before being returned to the log in screen).

We bypassed the problem by using aptitude to downgrade budgie-core:

Aptitude 0.8.13: log report
Wed, Nov 16 2022 10:19:27 -0800

  IMPORTANT: this log only lists intended actions; actions which fail
  due to dpkg problems may not be completed.

Will install 1 packages, and remove 0 packages.
1024 B of disk space will be freed
========================================
[DOWNGRADE] budgie-core:amd64 10.6.1-1ubuntu2 -> 10.6.1-1
========================================

Log complete.

After this the users could log in and see their desktops normally.

2

ok - I have tried to reproduce the issue - I started from a clean 22.04.1 ISO - then used software updater to install all updates.

This didn’t install budgie-desktop, budgie-core etc v10.6.1-1ubuntu2. This was due to phasing - I’m obviously not in the phased group.

So I’ve forced the upgrade

sudo apt install budgie-desktop budgie-core libbudgietheme0 libbudgie-private0 libbudgie-plugin0 libraven0 gir1.2-budgie-1.0

Logged out and logged in - this was Ok - no crashes. However the showtime applet was not visible on my desktop.

So I’ve asked the archive-admins to stop the phasing for now.

This leaves trying to find out what is going on with your system(s)

The crash should have created a /var/crash file for budgie-core - please can you try to report this - something like

ubuntu-bug /var/crash/FILENAME.crash

If you reinstall budgie-core v 10.6.1-1ubuntu2 - login to get to the crash

Then switch to a TTY - login and run

journalctl -ae | grep budgie > ~/debug.txt

I need to see the output that should be piped into that file in your home folder

3

@fossfreedom thank you I will attempt those steps

4

@fossfreedom I looked at the two systems that had the problem this morning (both are in use so I can’t make changes to them right now).

Neither one has anything in /var/crash from today (though one machine has something unrelated from two weeks ago, so I’m presuming if a crash file had been created this morning it would still be there).

However the journalctl output does appear to contain useful information about the crash. There were segfaults in libmutter among other errors. Here’s an excerpt from one of the crash cycles:

Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-budgie-desktop:/etc/xdg
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/budgie-desktop.mandatory.path
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting DESKTOP_SESSION=budgie-desktop
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=budgie-desktop
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/budgie-desktop.default.path
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/budgie-desktop:/usr/share/gnome:/home/lgt/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop
Nov 16 09:43:05 ATG /usr/libexec/gdm-x-session[2728]: dbus-update-activation-environment: setting GDMSESSION=budgie-desktop
Nov 16 09:43:06 ATG budgie-wm[2959]: Running Mutter(Budgie) (using mutter 42.5) as a X11 window and compositing manager
Nov 16 09:43:07 ATG budgie-wm[2959]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:07 ATG budgie-wm[2959]: ibus.vala:47: ibus-daemon unsupported on this system
Nov 16 09:43:07 ATG kernel: budgie-wm[2959]: segfault at fffffffffffffff0 ip 00007f05ca7edb12 sp 00007ffd2e868278 error 5 in libmutter-10.so.0.0.0[7f05ca78e000+143000]
Nov 16 09:43:08 ATG gnome-session[2507]: gnome-session-binary[2507]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:08 ATG gnome-session-binary[2507]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:08 ATG budgie-wm[2988]: Running Mutter(Budgie) (using mutter 42.5) as a X11 window and compositing manager
Nov 16 09:43:08 ATG budgie-wm[2988]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:09 ATG budgie-wm[2988]: ibus.vala:47: ibus-daemon unsupported on this system
Nov 16 09:43:09 ATG kernel: budgie-wm[2988]: segfault at fffffffffffffff0 ip 00007f5056e4bb12 sp 00007ffeb6b181d8 error 5 in libmutter-10.so.0.0.0[7f5056dec000+143000]
Nov 16 09:43:10 ATG gnome-session[2507]: gnome-session-binary[2507]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:10 ATG gnome-session[2507]: gnome-session-binary[2507]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Nov 16 09:43:10 ATG gnome-session-binary[2507]: Unrecoverable failure in required component budgie-wm.desktop
Nov 16 09:43:10 ATG gnome-session-binary[2507]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:10 ATG gnome-session-binary[2507]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Nov 16 09:43:10 ATG budgie-panel[3009]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:10 ATG dbus-daemon[2348]: [session uid=1001 pid=2348] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.64' (uid=1001 pid=3009 comm="budgie-panel " label="unconfined")
Nov 16 09:43:10 ATG dbus-daemon[2348]: [session uid=1001 pid=2348] Activating service name='org.gnome.ScreenSaver' requested by ':1.64' (uid=1001 pid=3009 comm="budgie-panel " label="unconfined")
Nov 16 09:43:11 ATG budgie-panel[3009]: notifications_view.vala:170: Unable to connect to notifications dispatcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.budgie_desktop.Notifications was not provided by any .service files
Nov 16 09:43:11 ATG budgie-daemon[3055]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:11 ATG budgie-polkit-d[3059]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:11 ATG polkitd(authority=local)[1178]: Registered Authentication Agent for unix-session:3 (system bus name :1.111 [budgie-polkit-dialog], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 16 09:43:11 ATG dbus-daemon[2348]: [session uid=1001 pid=2348] Activating service name='org.gnome.ScreenSaver' requested by ':1.64' (uid=1001 pid=3009 comm="budgie-panel " label="unconfined")
Nov 16 09:43:11 ATG budgie-extras-d[3081]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:25 ATG budgie-extras-d[3081]: budgie_extras_DaemonNameLost: assertion 'conn != NULL' failed
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-budgie-desktop:/etc/xdg
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/budgie-desktop.mandatory.path
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting DESKTOP_SESSION=budgie-desktop
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=budgie-desktop
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/budgie-desktop.default.path
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/budgie-desktop:/usr/share/gnome:/home/lgt/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop
Nov 16 09:43:53 ATG /usr/libexec/gdm-x-session[5469]: dbus-update-activation-environment: setting GDMSESSION=budgie-desktop
Nov 16 09:43:55 ATG budgie-wm[5693]: Running Mutter(Budgie) (using mutter 42.5) as a X11 window and compositing manager
Nov 16 09:43:55 ATG budgie-wm[5693]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:55 ATG budgie-wm[5693]: ibus.vala:47: ibus-daemon unsupported on this system
Nov 16 09:43:55 ATG kernel: budgie-wm[5693]: segfault at fffffffffffffff0 ip 00007f3ae6590b12 sp 00007ffeb8eb5458 error 5 in libmutter-10.so.0.0.0[7f3ae6531000+143000]
Nov 16 09:43:56 ATG gnome-session-binary[5192]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:56 ATG gnome-session[5192]: gnome-session-binary[5192]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:56 ATG budgie-wm[5718]: Running Mutter(Budgie) (using mutter 42.5) as a X11 window and compositing manager
Nov 16 09:43:57 ATG budgie-wm[5718]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:57 ATG budgie-wm[5718]: ibus.vala:47: ibus-daemon unsupported on this system
Nov 16 09:43:57 ATG kernel: budgie-wm[5718]: segfault at fffffffffffffff0 ip 00007f32b8f29b12 sp 00007ffc5fc677c8 error 5 in libmutter-10.so.0.0.0[7f32b8eca000+143000]
Nov 16 09:43:58 ATG gnome-session-binary[5192]: Unrecoverable failure in required component budgie-wm.desktop
Nov 16 09:43:58 ATG gnome-session-binary[5192]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:58 ATG gnome-session[5192]: gnome-session-binary[5192]: WARNING: Application 'budgie-wm.desktop' killed by signal 11
Nov 16 09:43:58 ATG gnome-session[5192]: gnome-session-binary[5192]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Nov 16 09:43:58 ATG gnome-session-binary[5192]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Nov 16 09:43:58 ATG budgie-panel[5739]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:58 ATG dbus-daemon[4970]: [session uid=1001 pid=4970] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.63' (uid=1001 pid=5739 comm="budgie-panel " label="unconfined")
Nov 16 09:43:59 ATG dbus-daemon[4970]: [session uid=1001 pid=4970] Activating service name='org.gnome.ScreenSaver' requested by ':1.63' (uid=1001 pid=5739 comm="budgie-panel " label="unconfined")
Nov 16 09:43:59 ATG budgie-panel[5739]: notifications_view.vala:170: Unable to connect to notifications dispatcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.budgie_desktop.Notifications was not provided by any .service files
Nov 16 09:43:59 ATG budgie-daemon[5787]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:59 ATG budgie-polkit-d[5790]: Failed to load module "appmenu-gtk-module"
Nov 16 09:43:59 ATG polkitd(authority=local)[1178]: Registered Authentication Agent for unix-session:6 (system bus name :1.199 [budgie-polkit-dialog], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Nov 16 09:43:59 ATG dbus-daemon[4970]: [session uid=1001 pid=4970] Activating service name='org.gnome.ScreenSaver' requested by ':1.63' (uid=1001 pid=5739 comm="budgie-panel " label="unconfined")
Nov 16 09:43:59 ATG budgie-extras-d[5817]: Failed to load module "appmenu-gtk-module"
Nov 16 09:44:36 ATG budgie-extras-d[5817]: budgie_extras_DaemonNameLost: assertion 'conn != NULL' failed
Nov 16 09:44:36 ATG budgie-polkit-d[5790]: polkitdialog.vala:335: Unable to respond to session manager! The connection is closed
Nov 16 09:44:36 ATG budgie-panel[5739]: manager.vala:195: Unable to respond to session manager! The connection is closed
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-budgie-desktop:/etc/xdg
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/budgie-desktop.mandatory.path
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting DESKTOP_SESSION=budgie-desktop
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=budgie-desktop
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/budgie-desktop.default.path
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/budgie-desktop:/usr/share/gnome:/home/lgt/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop:/var/lib/snapd/desktop
Nov 16 09:45:28 ATG /usr/libexec/gdm-x-session[8801]: dbus-update-activation-environment: setting GDMSESSION=budgie-desktop
Nov 16 09:45:29 ATG budgie-wm[9023]: Running Mutter(Budgie) (using mutter 42.5) as a X11 window and compositing manager
Nov 16 09:45:29 ATG budgie-wm[9023]: Failed to load module "appmenu-gtk-module"

I then logged into another system that had the update applied today (but had not been logged into since then) and it did not exhibit the crash (same as your test system did not exhibit the crash).

The difference with that system is that it’s a fairly new installation of 22.04 Budgie (that machine had never run 16.04 or 18.04 for example) so possibly the issue on the other two systems has something to do with the fact that they have been upgraded several times and have had other desktop environments installed?

We greatly appreciate your help. Since both affected users are able to use their machines now, it’s not a critical issue though we’d obviously like to be able to apply the budgie-core update at some point.

5

hmm - I am curious about this in the log

ibus.vala:47: ibus-daemon unsupported on this system

that occurs just before the budgie-wm crash.

Please let me know more about your ibus setup - do you have multiple languages/locales installed? if so what are they?

Are the machines exhibiting issues are logging in with a non en_US / en_GB language?

what is the output of

locale
6

In addition - what is the login manager you are using for the machines that are exhibiting crashes? lightdm? sddm? gdm3?

7

One of the machines that exhibited the crash is running sddm, the other runs gdm3 (and the machine that did not exhibit the crash is also gdm3).

I recall that both the problematic machines had display manager problems after the 22.04 upgrade when they switched to Wayland/gdm3. (The one running sddm in particular had Nvidia issues until we switched it to sddm.)

All three systems run US English. I don’t believe they have other languages installed. Here is sample locale output from one of them:

~$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

We greatly appreciate your help David. Are there other commands you’d like us to run to better enumerate any ibus issues?

8

ok - you should not be running gdm3 at all - that is specifically for GNOME Shell and breaks fundamental capabilities in budgie such as screenlocking and the ability to log out.

If you don’t need to have gnome-shell installed then you can remove gdm3 as follows:

sudo apt purge gdm3 gnome-shell-common gnome-shell

I will need to try a reinstall - this time say that I am in “new york” to see if I can reproduce your issue again

1 Like
9

Note - the message “ibus-daemon unsupported on this system” means that the package ibus is not installed

Thtas a little odd - it should be. What happens if you install the package ibus, logout and login? Does the log still contain that message afterwards?

1 Like
10

The good news is that I’ve found uninstalling ibus causes a crash in this new version of budgie-core.

It didn’t previously. Ok - so we’ll look at that - will ping you when done.

As I said before - ibus was/still is expected so I’m not sure how you have managed to uninstall ibus.

1 Like
11

Thanks again David–that’s way beyond the call of duty. Will do the ibus test later today.

Two of the three machines (the ones that exhibited the problem after the budgie-core update) had previously been running Unity (12.04 and 16.04) and then Gnome (20.04 and 22.04) so that’s how they ended up with gdm3.

Both the problematic machines had problems with the 22.04 upgrade. There were display manager and Nvidia driver problems, and both machines had missing desktop icons and other issues until we switched to Budgie. It’s possible that ibus got uninstalled during prior attempts to recover from those failures.

We sometimes help users that still run Ubuntu Gnome so we wanted to be able to switch to it, but at this point we’re committed to Budgie and are encouraging the other users to do so as well.

12

Hi David,

You solved it–it turns out that neither of the problem machines had ibus installed. I hadn’t noticed that in the journalctl output. We used aptitude to install both ibus and the budgie-core update - no more desktop crashes.

Thank you VERY MUCH for your help with this. We’ll look out for this error in the future. Please let us know if you would like any other tests or output.