Bug 1493551

Summary: The candidate bar's location of ibus is wrong( HiDPI)
Product: [Fedora] Fedora Reporter: robberphex
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 26CC: i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ibus-1.5.16-11.fc26 ibus-1.5.16-11.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-23 20:22:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
candidate bar at hidpi screen
none
candidate bar at hidpi screen, example 2
none
candidate bar at normal screen none

Description robberphex 2017-09-20 13:11:09 UTC
Created attachment 1328439 [details]
candidate bar at hidpi screen

Description of problem:

with HiDPI, ibus's candidate bar's location is wrong.

Version-Release number of selected component (if applicable):

gtk3-3.22.19-1.fc26.x86_64
ibus-1.5.16-9.fc26.x86_64
ibus-gtk3-1.5.16-9.fc26.x86_64
gnome-session-3.24.2-1.fc26.x86_64

How reproducible:

open gedit,
switch to ibus-pinyin, input something.

Steps to Reproduce:
1. open gedit,
2. switch to ibus-pinyin
3. type "ni", wait candidate bar

Actual results:

the candidate bar's location offseted to left-top.

Expected results:

the candidate bar should be near to current cursur.

Additional info:

It looks like the location's x and y, is half of expected value.

Comment 1 robberphex 2017-09-20 13:13:11 UTC
Created attachment 1328440 [details]
candidate bar at hidpi screen, example 2

Comment 2 robberphex 2017-09-20 13:13:45 UTC
Created attachment 1328441 [details]
candidate bar at normal screen

Comment 3 fujiwara 2017-09-21 04:53:13 UTC
Oops, the fix exists in gtk2 but I forgot it to gtk3.
It's critical since ibus-portal, C-S-u and this bug does not affect gtk3.

Comment 4 Fedora Update System 2017-09-21 05:54:49 UTC
ibus-1.5.16-11.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8603ec1846

Comment 5 Fedora Update System 2017-09-21 05:55:04 UTC
ibus-1.5.16-11.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8603ec1846

Comment 6 Fedora Update System 2017-09-21 05:55:25 UTC
ibus-1.5.16-11.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9684858af6

Comment 7 Fedora Update System 2017-09-21 05:55:34 UTC
ibus-1.5.16-11.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9684858af6

Comment 8 Fedora Update System 2017-09-21 23:57:13 UTC
ibus-1.5.16-11.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8603ec1846

Comment 9 Fedora Update System 2017-09-22 05:52:43 UTC
ibus-1.5.16-11.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9684858af6

Comment 10 Fedora Update System 2017-09-23 20:22:12 UTC
ibus-1.5.16-11.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2017-09-30 06:43:41 UTC
ibus-1.5.16-11.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.