Zed Ibus error on Ubuntu 25.04 X11

[nuxlight]

Summary

Impossible to write something after Ibus error pop after some seconds

Description

Hello,

I'm encountering an issue with Zed on Ubuntu 25.04, but only when using the X11 session (Wayland works fine, but I need to stay on X11 for compatibility reasons).

When launching the Zed application, after a few seconds, an Ubuntu error popup appears reporting an IBus-related error. From that point on, typing in the app becomes impossible. Occasionally, the application remains responsive for a bit longer, but the issue still eventually occurs.

This problem does not happen on Ubuntu 24.04 LTS (I tested it there).

Thanks!

Zed Version and System Specs

Zed: v0.187.5 (Zed) OS: Linux X11 ubuntu 25.04 Memory: 11.1 GiB Architecture: x86_64 GPU: AMD Radeon RX 570 Series (RADV POLARIS10) || radv || Mesa 25.0.3-1ubuntu2

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.

Zed.log

[jansol]

Do you have IBus installed & running?

Figuring out what's going on here is going to require relevant logs (most likely found in journalctl if you search for ibus).

[nuxlight]

Here is my journalctl output just at the crash moment (only few seconds)

mai 27 10:50:23 desktop-linux sudo[216280]: pam_unix(sudo:session): session opened for user root(uid=0) by thibaud(uid=1000)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): EDID vendor "RIS", prod id 2105
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Using hsync ranges from config file
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Using vrefresh ranges from config file
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Printing DDC gathered Modelines:
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 -hsync +vsync (67.5 kHz eP)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
mai 27 10:50:25 desktop-linux /usr/libexec/gdm-x-session[3098]: (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:25 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:29 desktop-linux update-notifier-crash[215169]: realloc(): invalid next size
mai 27 10:50:31 desktop-linux update-notifier-crash[215168]: Aborted (core dumped)
mai 27 10:50:32 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:32 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:32 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:32 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
mai 27 10:50:33 desktop-linux kernel: [drm] scheduler comp_1.1.0 is not ready, skipping

[nuxlight]

And i have this version of ibus : ibus/plucky,now 1.5.32~rc2-1 amd64

[jansol]

Hmm, nothing directly relevant looking in that log, if you only ran journalctl after the crash it will only show log messages that got emitted after that...

That said, those gdm-x-session messages look like the X.org server's startup messages which is pretty suspicious. If you can still go back to that log and look at what happened before those gdm-x-session[3089]: (II) AMDGPU(0): lines there might be something interesting there.