Budgie Desktop not launching (login loop)

Budgie Desktop
1

I’ve been using Ubuntu Budgie 19.04 without issues for the past months, and I just upgraded to 19.10 with:

sudo do-release-upgrade -d

After reboot I could no longer login to the desktop with Budgie selected. After entering password, the screen goes blank with a cursor on it for a few seconds, then completely black and shortly after, back to the login screen.

The standard Ubuntu/gnome desktop, as well as Ubuntu on Wayland work normally.

The laptop is on Intel graphics, no other video cards/drivers exist.

sudo lspci -k | grep -EA3 ‘VGA|3D|Display’

00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915

Permission of .Xauthority and /tmp seems file (.ICEauthority doesn’t exist for some reason):

foxium@lenovo:~$ ls -lA .Xauthority
-rw------- 1 foxium foxium 57 Oct 9 14:26 .Xauthority
foxium@lenovo:~$ ls -ld /tmp
drwxrwxrwt 22 root root 12288 Oct 9 14:31 /tmp

I tried uninstalling “everything” to start from scratch:

sudo apt purge ubuntu-budgie-desktop budgie*

Restarted to make sure Budgie is gone, then from console:

sudo apt install ubuntu-budgie-desktop

Restarted again after making sure lightdm is selected as the default display manager, however the login loop persists.

journalctl log entries: https://pastebin.com/CsrFfk4h

Any ideas on how to fix this? Thanks for your help!

2

I need a clean paste.ubuntu.com trace for your journalctl log entries because you have too much login/logout stuff from the other sessions.

Please reboot. Switch to a TTY (CTRL+ALT+F3) and login. Switch back to the slick login manager (CTRL+ALT+F3) and attempt to login.

Switch back to the TTY and write out the journalctl log

journalctl -ae --full > output.txt

This will create journal entries in output.txt

3

Thanks @fossfreedom for the quick response.

I rebooted, logged into tty3, went back to GUI login with Budgie selected. After the said problem occurred again and screen returned back to login, I went to tty3 and collected the following log:

https://paste.ubuntu.com/p/x4jmwfWzzS/

Hope this helps determining the problem.

Thanks again! Really appreciate your help.

4

you have a number of issues that appear to be coming from the GNOME Stack

lenovo gsd-smartcard[22753]: specified class size for type 'GsdSmartcardService' is smaller than the parent type's 'GsdSmartcardServiceManagerSkeleton' class size
Oct 09 16:37:06 lenovo dbus-daemon[1273]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.385' (uid=1000 pid=22732 comm="/usr/lib/gnome-settings-daemon/gsd-rfkill " label="unconfined")
Oct 09 16:37:06 lenovo gsd-smartcard[22753]: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
Oct 09 16:37:06 lenovo gsd-smartcard[22753]: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
Oct 09 16:37:06 lenovo gsd-smartcard[22753]: g_once_init_leave: assertion 'result != 0' failed
Oct 09 16:37:06 lenovo gsd-smartcard[22753]: g_async_initable_new_valist_async: assertion 'G_TYPE_IS_ASYNC_INITABLE (object_type)' failed

That tells me that the package gnome-settings-daemon needs a rebuild - this will happen automatically in the next few days when the GNOME Stack 3.34.1 packages are released.

Oct 09 16:37:06 lenovo gsd-xsettings[22720]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist

That’s a mutter issue where it cannot read your display info - what are you connected to? a laptop screen or an external display?

Oct 09 16:37:06 lenovo gsd-media-keys[22733]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Oct 09 16:37:06 lenovo budgie-wm[22789]: Failed to start Xwayland: Failed to acquire window manager ownership
Oct 09 16:37:06 lenovo kernel: show_signal: 54 callbacks suppressed
Oct 09 16:37:06 lenovo kernel: traps: budgie-wm[22789] trap int3 ip:7fda85bc48f5 sp:7ffd6a023440 error:0 in libglib-2.0.so.0.6200.0[7fda85b89000+83000]
Oct 09 16:37:07 lenovo budgie-wm.desktop[22789]: Window manager warning: Display “:0” already has a window manager; try using the --replace option to replace the current window manager.
Oct 09 16:37:07 lenovo gnome-session[22676]: gnome-session-binary[22676]: WARNING: Application 'budgie-wm.desktop' killed by signal 5
Oct 09 16:37:07 lenovo gnome-session-binary[22676]: WARNING: Application 'budgie-wm.desktop' killed by signal 5
Oct 09 16:37:07 lenovo dbus-daemon[1273]: [system] Successfully activated service 'org.freedesktop.locale1'
Oct 09 16:37:07 lenovo systemd[1]: Started Locale Service.
Oct 09 16:37:07 lenovo dbus-daemon[4687]: [session uid=1000 pid=4687] Activating service name='ca.desrt.dconf' requested by ':1.54' (uid=1000 pid=22829 comm="budgie-panel " label="unconfined")
Oct 09 16:37:07 lenovo dbus-daemon[4687]: [session uid=1000 pid=4687] Successfully activated service 'ca.desrt.dconf'
Oct 09 16:37:07 lenovo budgie-wm[22840]: Failed to start Xwayland: Failed to acquire window manager ownership
Oct 09 16:37:07 lenovo kernel: traps: budgie-wm[22840] trap int3 ip:7f96d56be8f5 sp:7ffdf9ff70b0 error:0 in libglib-2.0.so.0.6200.0[7f96d5683000+83000]
Oct 09 16:37:07 lenovo budgie-wm.desktop[22840]: Window manager warning: Display “:0” already has a window manager; try using the --replace option to replace the current window manager.
Oct 09 16:37:07 lenovo gnome-session[22676]: gnome-session-binary[22676]: WARNING: Application 'budgie-wm.desktop' killed by signal 5
Oct 09 16:37:07 lenovo gnome-session-binary[22676]: WARNING: Application 'budgie-wm.desktop' killed by signal 5
Oct 09 16:37:07 lenovo gnome-session[22676]: gnome-session-binary[22676]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Oct 09 16:37:07 lenovo gnome-session-binary[22676]: WARNING: App 'budgie-wm.desktop' respawning too quickly
Oct 09 16:37:07 lenovo gnome-session-binary[22676]: Unrecoverable failure in required component budgie-wm.desktop
Oct 09 16:37:07 lenovo gnome-session[22676]: gnome-session-binary[22676]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 09 16:37:07 lenovo gnome-session-binary[22676]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 09 16:37:07 lenovo pulseaudio[4684]: ICE default IO error handler doing an exit(), pid = 4684, errno = 88

Then that above is the budgie window manager crash

Why the issue about XWayland I don’t know - mutter shouldn’t be trying to start XWayland but I strongly suspect its due to the "Failed to get current display configuration state: " message

5

Thanks again for the amazingly fast reply.

The laptop is connected to an external screen via it’s onboard HDMI port.

Apart from waiting for the gnome-settings-daemon, is there anything I can try at this point?

Thanks again.

6

Hi,
I’ve got the same problem.
Occurred after upgrading gnome-session today, before it worked fine.
Cheers

7

If you disconnect your external screen can you login just using your laptop display?

8

Disconnecting the external screen made no difference – same problem persists along with the same display configuration error:

Oct 09 18:34:40 lenovo gsd-xsettings[8902]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name “org.gnome.Mutter.DisplayConfig” does not exist

9

Whilst not really helpful - you are not alone with the observation - also occurs on earlier versions of Ubuntu as well

Can you boot into a live-session? Just wondering if there is something with your installation that is clashing - a live session is a clean environment.

10

Okay I will give it a try and report back.

11

ok - think I understand the issue now - its due to you have both gnome-shell and budgie-desktop installed.

I’ve thrown a bug-fix and hopefully it will be accepted soon. Will keep you informed.

1 Like
12

I’ve tried 19.10 live and it works fine, but it probably doesn’t matter now as you have already found the problem. I’ll remove gnome-shell when I have time to tinker, or just wait for the fix you pushed.

Really appreciate your help. Thanks again! This community is simply amazing.

13

Bug fix has now been released - it will take a while for the mirrors to pick up - but just update as normal and you should see the update come down the wires.

14

Working fine now after updating. Thank you fossfreedom.