Upgrade from 24.04 to 26.04 ... some desktop problems

Budgie Desktop
1

Hi all,

I just upgraded from Budgie 24.04 to 26.04 and

The keyboard layout in settings is correct but it is not; even adding a second layout changing and setting back it remains probably uk ( at the login screen (gdm3) the layout seems to be correct because the login password is correctly accepted)

The highlight and paste does not works anymore

The “focus follows mouse” does not works anymore even if I re-set it in settings

In desktop settings and Budgie settings something works and something does not

I know it is probably the switching from X11 to Wayland, but, does anyone solved these issues ?

Thnks

2

what is the output of ps -ef | grep -i budgie

Need to check all the relevant services are running.

I’m not sure about gdm3 as the login manager - that is really a specific login manager for gnome-shell now - it starts gnome-shell specific components.

4 
# ps -ef | grep -i budgie
user1         6156    5045  0 21:59 tty2     00:00:00 /usr/libexec/gdm-wayland-session --handle-registration /usr/bin/startbudgielabwc
user1         6165    6156  1 21:59 tty2     00:01:51 labwc --config-dir /home/user1/.config/budgie-desktop/labwc -S budgie-desktop
user1         7194    6165  0 21:59 tty2     00:00:00 /usr/libexec/budgie-session-binary --builtin --session=org.buddiesofbudgie.BudgieDesktop   
user1         7202    7194  0 21:59 tty2     00:00:00 /usr/bin/org.buddiesofbudgie.Services
user1         7593    7194  0 21:59 tty2     00:00:31 /usr/bin/budgie-panel
user1         8024    7194  0 21:59 tty2     00:00:01 /usr/bin/budgie-daemon
user1         8025    7194  0 21:59 tty2     00:00:00 /usr/libexec/budgie-desktop/budgie-polkit-dialog
user1         8087       1  0 21:59 tty2     00:00:00 swayidle -w timeout 30 dbus-send --type=method_call --dest=org.buddiesofbudgie.BudgieScreenlock /org/buddiesofbudgie/Screenlock org.buddiesofbudgie.BudgieScreenlock.Dim resume dbus-send --type=method_call --dest=org.buddiesofbudgie.BudgieScreenlock /org/buddiesofbudgie/Screenlock org.buddiesofbudgie.BudgieScreenlock.Undim timeout 600 wlopm --off \* resume wlopm --on \* before-sleep swaylock -Fklf -i /home/user1/.local/share/backgrounds/plain-smooth-green-deb_inside.jpg timeout 900 if dbus-send --print-reply=literal --dest=org.buddiesofbudgie.BudgieScreenlock /org/buddiesofbudgie/Screenlock org.buddiesofbudgie.BudgieScreenlock.OnBattery | grep "boolean true" > /dev/null; then dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:false; fi
user1         8112    7194  0 21:59 tty2     00:00:00 /usr/bin/budgie-extras-daemon
user1         8120    7194  0 21:59 tty2     00:00:00 /usr/libexec/budgie-desktop/budgie-power-dialog
user1         8126    7194  0 21:59 tty2     00:00:01 /usr/bin/org.buddiesofbudgie.budgie-desktop-view
user1         8260    7194  0 21:59 tty2     00:00:00 /usr/bin/org.buddiesofbudgie.sendto -d
user1         9211    7194  0 21:59 tty2     00:00:00 /usr/libexec/budgie-desktop/budgie-screenshot-dialog 
user1        41068    8024  0 22:11 tty2     00:00:00 swaybg -i /run/user/1000/budgie_wallpaper_bordered.jpg --mode fill
root       98347   97655  0 23:35 pts/2    00:00:00 grep --color=auto -i budgie
5

interesting. At a minimum the labwc budgie bridge is not running.

What happens if you run

python3 /usr/libexec/budgie-desktop/labwc_bridge.py

6 
 python3 /usr/libexec/budgie-desktop/labwc_bridge.py
Traceback (most recent call last):
  File "/usr/libexec/budgie-desktop/labwc_bridge.py", line 17, in <module>
    from systemd.journal import JournalHandler
ModuleNotFoundError: No module named 'systemd'
7

looks like python3-systemd is not installed

sudo apt install python3-systemd

Install that and try running that command again. If no errors, logout and login and test again that the bridge is running.

8 
# apt install python3-systemd
python3-systemd is already the newest version (235-1build9).
python3-systemd set to manually installed.
Summary:                    
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
9

I can add that to solve some bad behaviour with the windows I run

im-config and choose not to use IBUS …

(IBUS was anyway not running …)

10

this is very odd - there is something wrong with your python setup.

what is the output of

which python
python --version
11

If I remember good I had some problem with the ubuntu python package and I installed it from source …

 which python
/usr/bin/python

# python --version
Python 3.13.12
12

Yeah - you have a mismatch - ubuntu 26.04 python version should be 3.14.4

I’m afraid I don’t know how to resolve your python setup.

13

ok, just a question, IBUS should be enabled or it has to be disabled ?

14

out of the box ibus isn’t installed. But I suppose that it depends if you need the ibus capabilities. Again - that isn’t something I know about - I did put a call out for someone to help with configuring and using ibus but I’m sorry to say I didn’t get any volunteers by the time of the release

15

Hi, I solved the issue deleting every instance of the source installed python