Skip to content
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

Mozc and IBus does not respect xinerama at all. #180

GoogleCodeExporter opened this issue Apr 22, 2015 · 1 comment

Mozc and IBus does not respect xinerama at all. #180

GoogleCodeExporter opened this issue Apr 22, 2015 · 1 comment


Copy link

GoogleCodeExporter commented Apr 22, 2015

If your problem or request can be applied to Google Japanese Input on
Windows and Mac OS X, please consider reporting it to the Google Japanese
Input product forum rather than Mozc's issue tracker, where we want to
handle Mozc-specific issues only.!forum/ime-ja

What steps will reproduce the problem?
1. Set up dual monitor, with different resolution (1680x1050 and 1920x1080) 
with the top aligned, IE so there's a gap on the bottom of the 1680x1050
2. Fullscreen gnome-terminal on the smaller monitor (1680x1050)
3. Run irssi, input should be on bottom row of gnome-terminal
4. enter ibus-mozc and type something, say "わたし" then press space to 
change it to kanji then use the up/down arrows to bring up a menu for selecting 
which one to convert to.
5. The menu is displaying below the input field, we can now only see a couple 
of pixels on screen, the rest is off screen. (This happens with both the ibus 
provided dialog, *AND* the mozc custom dialog. I think this is an ibus issue 
but if it also happen with the mozc custom dialog...)

What is the expected output?
The expected output is for the menu to display *above* the word being 
converted, this works properly on the (1920x1080) monitor, so it seems to 
indicate some form of xinerama issue with ibus menu dropdown.

What do you see instead?
The menu/selection hanging off screen

Original issue reported on by on 1 Mar 2013 at 2:15

Copy link

GoogleCodeExporter commented Apr 22, 2015

Thank you for the report. I can reproduce this issue on Ubuntu 12.10/Unity 
environment with Mozc 1.6.1187.102 built from source code.

I've attached a quick patch to fix this issue. I hope we can include full fix 
(including unit test) into the next release.


Original comment by on 3 Mar 2013 at 11:58

  • Changed state: Fixed
  • Added labels: OpSys-Linux


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant