Package: libgtk-3-0 Followup-For: Bug #1034289 Please note: inkscape upstream currently plans to workaround this issue by disabling the GTK XIM input method when it is detected as selected in the user's environment settings. That change is currently planned[1] to be included in the v1.3.1 release of inkscape.
>From that version onwards, this bug should become no-longer-reproducible. For anyone curious to approximate the workaround before then, XIM can be temporarily disabled within a single inkscape session by specifying a different GTK input method module; for example: $ GTK_IM_MODULE=gtk-im-context-simple inkscape (quoted as a workaround in the upstream bug thread[2]) (also, happy 20th birthday[3], Inkscape!) [1] - https://gitlab.com/inkscape/inkscape/-/merge_requests/5236 [2] - https://gitlab.com/inkscape/inkscape/-/issues/3664 [3] - https://inkscape.gitlab.io/inkscape-docs/awesome-web-pages/20th_anniversary/
