#1112091 applications hang

Package:
scim
Source:
scim
Description:
smart common input method platform
Submitter:
Simon Richter
Date:
2025-08-27 00:35:01 UTC
Severity:
normal
#1112091#5
Date:
2025-08-26 08:13:08 UTC
From:
To:
Hi,

since the trixie upgrade, I find that applications using input methods
often hang until I run "killall -9 scim-panel-gtk". Normal SIGTERM is
not sufficient.

This is happening on several machines for me, with both systemd and
sysvinit as pid 1, with ratpoison as window manager. Xterm, GTK and Qt
applications are all affected, this appears to happen randomly, even
when no IM hotkey is used.

Machines running bookworm are fine.

I'm using scim-anthy as backend.

   Simon
#1112091#10
Date:
2025-08-26 14:45:43 UTC
From:
To:

Hi Simon,

Thank you for the report. Please try the following workaround:

  - SCIM is too X11-specific, so use X11 instead of Wayland (e.g., log in
with "GNOME on Xorg").
  - scim-panel-gtk seems to cause issues in daemon mode. Try launching it
without daemon mode.
    The simplest approach is to create a systemd service file to launch
scim-panel-gtk explicitly:

# begin of ~/.config/systemd/user/scim-panel-gtk.service
[Unit]
Description=Launch scim-panel-gtk
Before=gnome-shell.service graphical-session.target

[Service]
ExecStart=/usr/lib/scim-1.0/scim-panel-gtk
Restart=on-failure

[Install]
WantedBy=default.target
# end of ~/.config/systemd/user/scim-panel-gtk.service

Then use systemctl to enable and start the service.

I have started refactoring SCIM to be more backend-agnostic and migrate to
GTK4, but progress has been slow.
I hope this workaround helps in the meantime.

Thanks,
Tz-Huan
#1112091#15
Date:
2025-08-26 14:45:43 UTC
From:
To:

Hi Simon,

Thank you for the report. Please try the following workaround:

  - SCIM is too X11-specific, so use X11 instead of Wayland (e.g., log in
with "GNOME on Xorg").
  - scim-panel-gtk seems to cause issues in daemon mode. Try launching it
without daemon mode.
    The simplest approach is to create a systemd service file to launch
scim-panel-gtk explicitly:

# begin of ~/.config/systemd/user/scim-panel-gtk.service
[Unit]
Description=Launch scim-panel-gtk
Before=gnome-shell.service graphical-session.target

[Service]
ExecStart=/usr/lib/scim-1.0/scim-panel-gtk
Restart=on-failure

[Install]
WantedBy=default.target
# end of ~/.config/systemd/user/scim-panel-gtk.service

Then use systemctl to enable and start the service.

I have started refactoring SCIM to be more backend-agnostic and migrate to
GTK4, but progress has been slow.
I hope this workaround helps in the meantime.

Thanks,
Tz-Huan
#1112091#20
Date:
2025-08-26 23:56:40 UTC
From:
To:
Hi,

This is not a GNOME session, but normal X11 started via startx running
the Xsession script.

According to pstree, it's not running in daemon mode:

   ├─scim-helper-man
   ├─scim-im-agent
   ├─scim-launcher -d -c simple -e all -f socket --no-stay
   ├─scim-launcher -d -c socket -e socket -f x11
   ├─scim-panel-gtk --no-stay --display :0.0 -c socket -d
   │   └─2*[{scim-panel-gtk}]

    Simon
#1112091#25
Date:
2025-08-27 00:31:20 UTC
From:
To:
Hi,

Good, so it's not the wayland issue for your case.

           ^^^^^