forked from phuang/ibus
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The position of the Chinese candidate box is wrong #2522
Comments
I can reproduce this on both Debian testing with ibus 1.5.28-5 and (coming) Ubuntu 23.10 with ibus 1.5.28-5. Some notes:
|
I need to modify my observations:
|
It looks like 86d9bb9 fixes this issue. |
gunnarhj
referenced
this issue
Aug 20, 2023
For ibus-gtk4, use the Gdk functions to get the inner cursor location. The inner cursor location is translated by XTranslateCoordinates for X Window. For ibus-gtk3, use gdk_window_get_root_coords function to translate the inner cursor location for X Window. In Wayland, the set_cursor_location_relative function is called. In X Window, the set_cursor_location function is called. Fixes: d0a47c3 Fixes: a823161 BUG=#2549 BUG=https://gitlab.gnome.org/GNOME/gtk/-/issues/3024#note_987835
@gunnarhj Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Which distribution and version?:
Debian GNU/Linux 12 (bookworm)
Which desktop environment and version?:
GNOME 43.4
Which session type?:
X11
Which application and version?:
GNOME Files 43.2, GNOME Text Editor 43.2
Note: GNOME terminal 3.46.8 work fine
IBus version?:
IBus 1.5.27
Issue description:
The position of the Chinese candidate box is wrong. and the position will not change with the window.
Steps to reproduce:
Can you reproduce your problem when you restart ibus-daemon? (yes / no):
yes
Do you see any errors when you run ibus-daemon with the verbose option?:
no
Can you reproduce your problem with a new user account instead of the current your account?
not tested
The text was updated successfully, but these errors were encountered: