Ubuntu 26.04’s Wayland interface isn’t very stable.
The logout/shutdown/restart buttons on the graphical interface sometimes don’t work.Sometimes the work runs fine.
The button requires being used on the terminal to take effect when it is inactive.
Ubuntu 26.04’s Wayland interface isn’t very stable.
The logout/shutdown/restart buttons on the graphical interface sometimes don’t work.Sometimes the work runs fine.
The button requires being used on the terminal to take effect when it is inactive.
I haven’t noticed that.
Do you mean the AppMenu button?
If so, try using the User Indicator applet instead, or why not User Indicator Redux:
sudo apt update && sudo apt install budgie-user-indicator-redux-applet
This is a known issue with budgie’s “polkit” dialog.
I’ve got a version on my laptop which I’m testing. I’m hoping it does fix this. I’ll give it another week or two more testing. If it works I’ll propose it to upstream buddiesofbudgie.
Once accepted we can then SRU the fix back into 26.04 proper.
I encounter the same problem.
I will be happy when it will be solved and implemented.
If I package the proposed fix in a test PPA package - anyone willing to help me test it?
Sir, I, sir! ![]()
sudo add-apt-repository ppa:ubuntubudgie-dev/polkit
sudo apt full-upgrade
reboot –
to remove the PPA
sudo ppa-purge ppa:ubuntubudgie-dev/polkit
reboot –
This PPA is the same as 26.04 but includes a patch specifically for the polkit dialog - the dialog that displays when you try to use an app like gnome-disks / sddm-customize and it asks for a sudo username/password.
What I’m hoping is that this also resolves the logout/shutdown issues where the popup dialogs dont show.
If those issues still occurs then this is a separate issue that needs investigating.
It’s done. I’ll let you know if I run into any issues — to be honest, I’ve never had any problems using User Indicator Redux.
Hi folks - how are we doing with testing this patch?
I reinstalled User Indicator to access the “modern” exit menu, but sorry, it’s not because I’m not using the buttons “Log Out”, “Reboot” or “Shutdown”, I haven’t encountered any problems so far.
For this kind of test, I’d rather rely on @Marc_Driver, who I know from conversations with him occasionally runs into unexpected problems that I’ve never experienced.
Sometimes it takes a long time—over 30 seconds—to open the terminal before changes take effect. This situation typically occurs when installing daily software from the app store.
ubuntu@master:~$ tail -f /var/log/syslog
2026-06-20T13:32:35.682625+08:00 master wpa_supplicant[1685]: wlp4s0: Reject scan trigger since one is already pending
2026-06-20T13:32:40.504278+08:00 master dbus-daemon[3386]: [session uid=1000 pid=3386 pidfd=5] Activating via systemd: service name='org.xfce.Xfconf' unit='xfconfd.service' requested by ':1.313' (uid=1000 pid=636570 comm="/usr/bin/xfce4-terminal" label="unconfined")
2026-06-20T13:32:40.505835+08:00 master systemd[3333]: Starting xfconfd.service - Xfce configuration service...
2026-06-20T13:32:40.521066+08:00 master dbus-daemon[3386]: [session uid=1000 pid=3386 pidfd=5] Successfully activated service 'org.xfce.Xfconf'
2026-06-20T13:32:40.521175+08:00 master systemd[3333]: Started xfconfd.service - Xfce configuration service.
2026-06-20T13:33:41.916240+08:00 master budgie-session[3865]: budgie-session-binary[3865]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before timeout
2026-06-20T13:33:41.916483+08:00 master budgie-session-binary[3865]: WARNING: Client '/org/gnome/SessionManager/Client14' failed to reply before timeout
2026-06-20T13:33:49.569546+08:00 master at-spi-bus-launcher[3981]: dbus-daemon[3981]: Activating service name='org.a11y.atspi.Registry' requested by ':1.47' (uid=1000 pid=1236324 comm="/usr/bin/xfce4-terminal" label="unconfined")
2026-06-20T13:33:49.573054+08:00 master at-spi-bus-launcher[3981]: dbus-daemon[3981]: Successfully activated service 'org.a11y.atspi.Registry'
2026-06-20T13:33:49.573407+08:00 master at-spi-bus-launcher[1236440]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
2026-06-20T13:34:36.082670+08:00 master systemd[1]: Starting sddm-backgrounds-cache.service - Update SDDM user backgrounds cache from AccountsService...
2026-06-20T13:34:36.169702+08:00 master systemd[1]: sddm-backgrounds-cache.service: Deactivated successfully.
2026-06-20T13:34:36.169767+08:00 master systemd[1]: Finished sddm-backgrounds-cache.service - Update SDDM user backgrounds cache from AccountsService.
2026-06-20T13:34:36.169964+08:00 master update-sddm-backgrounds-cache[1250149]: SDDM backgrounds cache updated successfully
2026-06-20T13:34:36.169997+08:00 master update-sddm-backgrounds-cache[1250149]: Cache file: /usr/share/sddm/themes/ubuntu-budgie-login/cache/user-backgrounds.json
2026-06-20T13:34:36.170008+08:00 master update-sddm-backgrounds-cache[1250149]: QML file: /usr/share/sddm/themes/ubuntu-budgie-login/components/AccountsService.qml