[Bug 1201421] New: TW 20220710 and later: ibus not working
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 Bug ID: 1201421 Summary: TW 20220710 and later: ibus not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: Mathias.Homann@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since TW 20220710 (or possibly earlier) ibus isn't working anymore: - the ibus panel applet is not autostarting - after manually calling ibus-autostart, switching input method stops working after a few switches -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c1 --- Comment #1 from Fuminobu Takeyama <ftake@geeko.jp> --- 1. Which desktop environment do you use? 2. Do you use X11 or Wayland? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c2 --- Comment #2 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #1)
1. Which desktop environment do you use? 2. Do you use X11 or Wayland?
KDE/Plasma under X11 (I believe - I never actively switched to wayland) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c3 --- Comment #3 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #1)
1. Which desktop environment do you use? 2. Do you use X11 or Wayland?
Operating System: openSUSE Tumbleweed 20220714 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.9-2-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core��� i7-4771 CPU @ 3.50GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 Fuminobu Takeyama <ftake@geeko.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c4 Fuminobu Takeyama <ftake@geeko.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Mathias.Homann@opensuse.org Flags| |needinfo?(Mathias.Homann@op | |ensuse.org) --- Comment #4 from Fuminobu Takeyama <ftake@geeko.jp> --- Could you try to remove a line starting with "X-GNOME-Autostart-Phase=" from /etc/xdg/autostart/ibus-autostart.desktop ? I'm not sure systemd-xdg-autostart-generator is used on the current Tumbleweed, but it seems to ignore such desktop files. https://www.freedesktop.org/software/systemd/man/systemd-xdg-autostart-gener... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c5 Mathias Homann <Mathias.Homann@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Mathias.Homann@op | |ensuse.org) | --- Comment #5 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #4)
Could you try to remove a line starting with "X-GNOME-Autostart-Phase=" from /etc/xdg/autostart/ibus-autostart.desktop ?
did that, no change - ibus isn't starting. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c6 Fuminobu Takeyama <ftake@geeko.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Mathias.Homann@op | |ensuse.org) --- Comment #6 from Fuminobu Takeyama <ftake@geeko.jp> --- There might be another problem with your environment. I confirmed this problem has been resolved by removing that line. It seems that some applications including vdagent are not started due to the same reason. Can you check the output of the following commands? geeko2@localhost:~> cat /etc/xdg/autostart/ibus-autostart.desktop [Desktop Entry] Name=IBus GenericName=IBus Daemon Comment=Start IBus daemon Exec=ibus-autostart Icon=ibus-setup Terminal=false Type=Application StartupNotify=false NoDisplay=true X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false geeko2@localhost:~> echo $INPUT_METHOD ibus geeko2@localhost:~> systemctl --user list-unit-files | grep ibus app-ibus\x2dautostart@autostart.service generated - geeko2@localhost:~> systemctl status | grep ibus ��� ������app-ibus\x2dautostart@autostart.service ��� ��� ������2755 ibus-daemon --xim -d ��� ��� ������2783 /usr/lib64/ibus/ibus-dconf ��� ��� ������2784 /usr/lib64/ibus/ibus-ui-gtk3 ��� ��� ������2787 /usr/lib64/ibus/ibus-extension-gtk3 ��� ��� ������2795 /usr/lib64/ibus/ibus-x11 --kill-daemon ��� ��� ������2873 /usr/lib64/ibus/ibus-engine-simple ��� ��� ������3243 grep --color=auto ibus ��� ������2802 /usr/lib64/ibus/ibus-portal geeko2@localhost:~> systemctl status --user org.freedesktop.IBus.session.generic.service ��� org.freedesktop.IBus.session.generic.service - IBus Daemon for generic sessions Loaded: loaded (/usr/lib/systemd/user/org.freedesktop.IBus.session.generic.service; static) Active: inactive (dead) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c7 Mathias Homann <Mathias.Homann@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Mathias.Homann@op | |ensuse.org) | --- Comment #7 from Mathias Homann <Mathias.Homann@opensuse.org> --- hm this is getting ridiculous - without that "X-GNOME-AUTOSTART-Phae" line, my desktop computer works properly with ibus running, but on my laptop I have ibus running in the tray for a short moment, then it disappears and I can NOT type in yakuake anymore until i restart it. *WITH* that line, no ibus but I can type. If I start the ibus service manually, like so: systemctl --user start app-ibus\\x2dautostart@autostart.service it starts, stays running, and works. But only until I relog/reboot. anyway here's the output of all those commands: mathias@mio:~> cat /etc/xdg/autostart/ibus-autostart.desktop [Desktop Entry] Name=IBus GenericName=IBus Daemon Comment=Start IBus daemon Exec=ibus-autostart Icon=ibus-setup Terminal=false Type=Application StartupNotify=false NoDisplay=true X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false X-KDE-autostart-after=panel X-KDE-StartupNotify=false mathias@mio:~> echo $INPUT_METHOD ibus mathias@mio:~> systemctl --user list-unit-files | grep ibus app-ibus\x2dautostart@autostart.service generated - mathias@mio:~> systemctl status | grep ibus ��� ��� ������5288 grep --color=auto ibus "systemctl status --user" lists all the autostarted stuff, but there's no ibus in the list. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c8 --- Comment #8 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Mathias Homann from comment #7)
hm this is getting ridiculous - without that "X-GNOME-AUTOSTART-Phae" line, my desktop computer works properly with ibus running, but on my laptop I have ibus running in the tray for a short moment, then it disappears and I can NOT type in yakuake anymore until i restart it.
now my desktop is doing it that way, too. TW20220718 by now, btw. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c9 --- Comment #9 from Fuminobu Takeyama <ftake@geeko.jp> --- It looks ibus crashes soon after launched. Is there any error messages in journalctl? After ibus disappear from the tray, please run $ ibus-daemon -xdv in a terminal. Do you see any error messages in the terminal? I will open another report to track the problem with Plasma and "X-GNOME-Autostart-Phase" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c10 --- Comment #10 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #9)
It looks ibus crashes soon after launched.
Is there any error messages in journalctl? After ibus disappear from the tray, please run
$ ibus-daemon -xdv
none whatsoever - and ibus runs. I think the whole mess started with one of the more recent KDE/Plasma upgrades... but I'm not sure at all. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c11 --- Comment #11 from Mathias Homann <Mathias.Homann@opensuse.org> --- So I've modified /etc/xdg/autostart/ibus.desktop like this: kumiko:~ # diff -burNE /root/ibus-autostart.desktop /etc/xdg/autostart/ibus-autostart.desktop --- /root/ibus-autostart.desktop 2022-07-19 17:06:19.120630687 +0200 +++ /etc/xdg/autostart/ibus-autostart.desktop 2022-07-20 21:09:19.522177492 +0200 @@ -8,8 +8,9 @@ Type=Application StartupNotify=false NoDisplay=true -X-GNOME-Autostart-Phase=Applications X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false -X-KDE-autostart-after=panel +X-KDE-autostart-after=org.kde.plasmashell X-KDE-StartupNotify=false +X-KDE-autostart-phase=1 + and it still doesn't start. lemmy@kumiko:~> systemctl --user status app-ibus\\x2dautostart@autostart.service � app-ibus\x2dautostart@autostart.service - IBus Loaded: loaded (/etc/xdg/autostart/ibus-autostart.desktop; generated) Active: failed (Result: timeout) since Wed 2022-07-20 21:11:35 CEST; 2min 13s ago Docs: man:systemd-xdg-autostart-generator(8) Main PID: 2716 (code=exited, status=0/SUCCESS) CPU: 1.648s Jul 20 21:11:29 kumiko systemd[2317]: Starting IBus... Jul 20 21:11:35 kumiko systemd[2317]: app-ibus\x2dautostart@autostart.service: start operation timed out. Terminating. Jul 20 21:11:35 kumiko systemd[2317]: app-ibus\x2dautostart@autostart.service: Failed with result 'timeout'. Jul 20 21:11:35 kumiko systemd[2317]: Failed to start IBus. Jul 20 21:11:35 kumiko systemd[2317]: app-ibus\x2dautostart@autostart.service: Consumed 1.648s CPU time. going to try with "X-KDE-autostart-phase=1" next - it really seems to me as if the system simply starts ibus too soon, because i can manually start it once the session is up, and it looks as if it works fine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c12 --- Comment #12 from Mathias Homann <Mathias.Homann@opensuse.org> --- So now my /etc/xdg/autostart/ibus.desktop is patched like this: --- /root/ibus-autostart.desktop 2022-07-19 17:06:19.120630687 +0200 +++ /etc/xdg/autostart/ibus-autostart.desktop 2022-07-20 21:14:23.602093124 +0200 @@ -8,8 +8,9 @@ Type=Application StartupNotify=false NoDisplay=true -X-GNOME-Autostart-Phase=Applications X-GNOME-AutoRestart=false X-GNOME-Autostart-Notify=false -X-KDE-autostart-after=panel +X-KDE-autostart-after=org.kde.plasmashell X-KDE-StartupNotify=false +X-KDE-autostart-phase=2 and what do you know, it works properly. I'll try the same on my laptop tomorrow, and if that works we'll have a patch that only applies to ibus for TW. I'll fork&build once I know. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c13 --- Comment #13 from Mathias Homann <Mathias.Homann@opensuse.org> --- those modifications fix it on my laptop too. ibus with a patch for this is building in https://build.opensuse.org/package/show/home:lemmy04:branches:M17N/ibus, I'll do a SR once I've tested it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c14 --- Comment #14 from Mathias Homann <Mathias.Homann@opensuse.org> --- ok now it's getting weird, even with those modifications ibus is not starting on my laptop, and shows "failed due to timeouts", when i login first time after boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c15 --- Comment #15 from Mathias Homann <Mathias.Homann@opensuse.org> --- oh for crying out loud. a missing newline at the end of the .desktop file makes ibus crash on first login after boot, and work fine on each following login... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c16 --- Comment #16 from Mathias Homann <Mathias.Homann@opensuse.org> --- ok now i'm about to loose it here. It still does not work right on my laptop - and it looks a lot like a timing issue: when I reboot my laptop, and log in as soon as the login screen is there, ibus starts, and crashes after a few seconds. when I reboot my laptop, and give it a few seconds after the login screen appears, ibus works just fine. and that's even with the modified autostart desktop file. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 Fuminobu Takeyama <ftake@geeko.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1201728 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c17 --- Comment #17 from Fuminobu Takeyama <ftake@geeko.jp> --- I could reproduce this now. I guess ibus-autostart is not suitable for systemd. It calls ibus-daemon -d, which runs ibus-daemon as a daemon, and so it exits very quickly. The following modification should works. ``` --- /usr/bin/ibus-autostart 2022-05-08 16:43:36.000000000 +0900 +++ ibus-autostart 2022-07-21 21:45:30.356005384 +0900 @@ -11,5 +11,4 @@ # sleep for a little while to avoid duplicate startup # sleep 2 -ibus-daemon --xim -d -exit 0 +ibus-daemon --xim ``` But this modification will affects other desktop environment. So I'm wondering we should migrate to systemd service from *.desktop. We already have org.freedesktop.IBus.session.generic.service, which is not used for now. To use this service file, we need to modify it to * prevent from running when another input method framework (e.g., fcitx) is selected * work with X11 session because it is designed for Wayland session (no --xim) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c18 --- Comment #18 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #17)
I could reproduce this now. I guess ibus-autostart is not suitable for systemd.
It calls ibus-daemon -d, which runs ibus-daemon as a daemon, and so it exits very quickly. The following modification should works.
``` --- /usr/bin/ibus-autostart 2022-05-08 16:43:36.000000000 +0900 +++ ibus-autostart 2022-07-21 21:45:30.356005384 +0900 @@ -11,5 +11,4 @@ # sleep for a little while to avoid duplicate startup # sleep 2
-ibus-daemon --xim -d -exit 0 +ibus-daemon --xim ```
With this modification in /usr/bin/ibus-autostart **and** my modified .service file in /etc/xdg/autostart I have working ibus again. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c19 --- Comment #19 from Mathias Homann <Mathias.Homann@opensuse.org> --- I just rolled back to the ibus packages from TW (20220826), and ibus is still not autostarting. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c20 --- Comment #20 from Fuminobu Takeyama <ftake@geeko.jp> --- It will take long time to resolve this problem. Those who want to use IBus with KDE, please use start IBus via IBus's service file. $ systemctl --user enable org.freedesktop.IBus.session.generic.service $ systemctl --user start org.freedesktop.IBus.session.generic.service Or, alternatively, modify ibus-autostart.desktop and /usr/bin/ibus-autostart as mentioned above. I will soon change IBus so that systemd-xdg-autostart-generator ignores it again. https://bugzilla.suse.com/show_bug.cgi?id=1202841 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c21 --- Comment #21 from Mathias Homann <Mathias.Homann@opensuse.org> --- (In reply to Fuminobu Takeyama from comment #20)
It will take long time to resolve this problem. Those who want to use IBus with KDE, please use start IBus via IBus's service file.
$ systemctl --user enable org.freedesktop.IBus.session.generic.service $ systemctl --user start org.freedesktop.IBus.session.generic.service
lemmy@kumiko:~> systemctl --user enable org.freedesktop.IBus.session.generic.service The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: ��� A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. ��� A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. ��� A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). ��� In case of template units, the unit is meant to be enabled with some instance name specified. so that doesn't actually work, because the service definition is missing parts... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1201421 http://bugzilla.opensuse.org/show_bug.cgi?id=1201421#c22 Fuminobu Takeyama <ftake@geeko.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #22 from Fuminobu Takeyama <ftake@geeko.jp> --- I'm sorry to be late to fix this problem. I made ibus-autostart work with systemd xdg-autostart-generator. Now ibus is internally launched by systemd user service. Thank you for reporting. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com