the problem is how ibus integrates with Wayland. This results in DBus errors, wallpaper failures, and screensaver crash notifications. IBus should be called from the desktop session in Wayland. For KDE, you can launch systemsettings utility and go to “Input & Output” → “Keyboard” → “Virtual Keyboard” section and select “IBus wayland” icon and click “Apply” button to configure IBus in Wayland. For other desktop sessions, you can run ibus start command. Please refer each document about the “Wayland input method” configuration. Before you configure the “Wayland input method”, you should make sure that QT_IM_MODULE and GTK_IM_MODULE environment variables are unset in the desktop session. Reproducible: Always Steps to Reproduce: 1.Install Fedora 44 Budgie Rawhide 2. Log into Budgie (Wayland) 3.Use the default installed packages 4. Observe desktop startup and notifications Actual Results: IBus should be called from the desktop session in Wayland. For KDE, you can launch systemsettings utility and go to “Input & Output” → “Keyboard” → “Virtual Keyboard” section and select “IBus wayland” icon and click “Apply” button to configure IBus in Wayland. For other desktop sessions, you can run ibus start command. Please refer each document about the “Wayland input method” configuration. Before you configure the “Wayland input method”, you should make sure that QT_IM_MODULE and GTK_IM_MODULE environment variables are unset in the desktop session. Expected Results: Login should be smooth with no error message. Additional Information: rpm -q swaylock package swaylock is not installed yusufk@fedora:~$ which swaylock /usr/bin/which: no swaylock in (/home/yusufk/.local/bin:/home/yusufk/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin) yusufk@fedora:~$ rpm -q gtklock gtklock-4.0.0-2.fc44.x86_64 yusufk@fedora:~$ rpm -q budgie-screensaver package budgie-screensaver is not installed yusufk@fedora:~$ rpm -q budgie-session budgie-session-1.0.0-1.fc44.x86_64
Seems Fedora 44 switches Budgie to Wayland. https://fedoraproject.org/wiki/Changes/Budgie_10.10 I tried Fedora 43 Budgie Xorg not 44 yet. Reading the document, it uses labwc. https://docs.buddiesofbudgie.org/10.10/developer/workflow/building-budgie-desktop Probably you could use IBus Wayland input-method protocol V2 with `ibus start` command. I'm not sure if budgie-session runs ibus-daemon but you could the parent process of ibus-daemon with `ps -ef | grep ibus-daemon` and `pstree -asp $PID`. If yes, it would be a failure of the Budgie session and you need to terminate ibus processes at once: % ibus exit % ibus start --verbose Probably you could refer the XFCE - Labwc configuration: https://github.com/ibus/ibus/wiki/WaylandDesktop#xfce
Okay I think I have managed to pinpoint the issue. So IBus is loading these modules (QT_IM_MODULE and GTK_IM_MODULE) under some legacy x11 settings. Now that Budgie 10.10 is wayland only it has no need for them. Wayland uses a new "Text-Input" protocol where apps talk directly to the compositor (labwc), not to IBus via a module. File can be located at: grep -r "QT_IM_MODULE" /etc/ /usr/lib/environment.d/ 2>/dev/null /etc/X11/xinit/xinput.d/ibus.conf: QT_IM_MODULE=ibus /etc/X11/xinit/xinput.d/ibus.conf: QT_IM_MODULE=xim Either SDDM or budgie I think is activating Ibus to load these modules but we dont need them. env | grep IM_MODULE QT_IM_MODULE=ibus Expected Results: In a pure Wayland session (Budgie 10.10), no legacy IM_MODULE environment variables should be exported. The system should rely on the Wayland Text-Input Protocol handled by the compositor (labwc).
(In reply to fujiwara from comment #1) > Seems Fedora 44 switches Budgie to Wayland. > https://fedoraproject.org/wiki/Changes/Budgie_10.10 > > I tried Fedora 43 Budgie Xorg not 44 yet. > > Reading the document, it uses labwc. > https://docs.buddiesofbudgie.org/10.10/developer/workflow/building-budgie- > desktop > > Probably you could use IBus Wayland input-method protocol V2 with `ibus > start` command. > > I'm not sure if budgie-session runs ibus-daemon but you could the parent > process of ibus-daemon with `ps -ef | grep ibus-daemon` and `pstree -asp > $PID`. > > If yes, it would be a failure of the Budgie session and you need to > terminate ibus processes at once: > > % ibus exit > % ibus start --verbose > > Probably you could refer the XFCE - Labwc configuration: > https://github.com/ibus/ibus/wiki/WaylandDesktop#xfce @fujiwara Further clarify my findings. the following is the problem, based on the error notfication ibus should be configured through desktop session settings(budgie-desktop-services). Then Budgie 10.10 doesn't appear to have a graphical input method configuration UI like KDE or GNOME. The ibus labwc documentation shows "Labwc does not provide the session configuration(/etc/xdg/labwc) by default and it's available in /usr/share/doc/labwc directory and labwc-config(5)." so no auto-start. Requiring manual input of ibus start --type wayland. Also ensure environment variables are unset, any of the x11 dependent packages. GTK_IM_MODULE|QT_IM_MODULE|XMODIFIERS" XMODIFIERS=@im=ibus QT_IM_MODULE=ibus bhoward@fedora:~$ ps aux | grep ibus-daemon bhoward 10433 0.0 0.3 612988 14316 ? Sl 17:37 0:00 ibus-daemon --xim --panel disable bhoward 20723 0.0 0.0 231440 2572 pts/0 S+ 17:41 0:00 grep --color=auto ibus-daemon this shows the ibus-dameon is running but in GNOME x11 mode then within the ibus settings is imsettings which is just configured like so ... XIM_ARGS="-r --xim" # <- This is why ibus starts with --xim flag GTK_IM_MODULE=ibus QT_IM_MODULE=ibus NOT_RUN=gnome3 IMSETTINGS_IGNORE_SESSION=KDE-wayland # <- Only ignores KDE-wayland, not Budgie! Because of this x11 settings are being forced even though budgie 10.10 is now wayland only.
(In reply to yusufxkhalid from comment #2) > /etc/X11/xinit/xinput.d/ibus.conf: QT_IM_MODULE=ibus Budgie Wayland DE does not need ibus-xinit package and should be deleted. (In reply to yusufxkhalid from comment #3) > IMSETTINGS_IGNORE_SESSION=KDE-wayland # <- Only ignores KDE-wayland, not > Budgie! I don't think it's good solution to update that value by DE at present. If you still require ibus-xinit package, you could run im-chooser and disable ibus.
You still don't reply my query but added unnecessary needinfo flag: (In reply to fujiwara from comment #1) > I'm not sure if budgie-session runs ibus-daemon but you could the parent > process of ibus-daemon with `ps -ef | grep ibus-daemon` and `pstree -asp > $PID`. But probably your issue would not be ibus. (In reply to yusufxkhalid from comment #3) > The ibus labwc documentation shows "Labwc does not provide the session > configuration(/etc/xdg/labwc) by default and it's available in > /usr/share/doc/labwc directory and labwc-config(5)." so no auto-start. > Requiring manual input of ibus start --type wayland. I didn't indicate /etc file see the configuration: (In reply to fujiwara from comment #1) > Probably you could refer the XFCE - Labwc configuration: > https://github.com/ibus/ibus/wiki/WaylandDesktop#xfce