Bug 1647316 - unable to change input mode from the top right dropdown menu
Summary: unable to change input mode from the top right dropdown menu
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-07 07:44 UTC by Ken Sugawara
Modified: 2018-11-08 03:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-08 03:33:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (35.25 KB, image/png)
2018-11-07 07:44 UTC, Ken Sugawara
no flags Details
gnome-shell system status area menu exhibiting the same symptom (275.33 KB, image/png)
2018-11-08 02:55 UTC, Ken Sugawara
no flags Details

Description Ken Sugawara 2018-11-07 07:44:41 UTC
Created attachment 1502858 [details]
screenshot

Description of problem:
When I try to change input mode from the top right dropdown menu (see the attached screenshot), I should be able to click on the line that says "Input Mode", and the list of input modes expands to show all the modes from which I can select one.
Now, even if I click on the "Input Mode" line, it does nothing so I cannot switch one mode to another within an IME (the screenshot is taken when ibus-kkc is active, but the same thing happens with ibus-mozc as well).

Version-Release number of selected component (if applicable):
ibus-1.5.19-7.fc29.x86_64
ibus-kkc-1.5.22-10.fc29.x86_64
ibus-mozc-2.23.2815.102-2.fc29.x86_64



How reproducible:
Always.

Steps to Reproduce:
1. Add Japanese input methods such as ibus-kkc and ibus-mozc
2. Activate the Japanese input method
3. Try to change Input Mode from the top right menu


Actual results:
Unable to switch between input modes


Expected results:
Able to switch from an input mode to another

Additional info:
Farther investigation revealed that the list of input modes *is* expanded but it fails to be rendered on the screen. If I click the right location where an input mode (e.g. Hiragana) is normally located after I click the "Input Mode", I can choose the input mode (quite difficult to use).

Comment 1 fujiwara 2018-11-07 08:38:14 UTC
I cannot reproduce your problem with ibus-kkc.
I know ibus-mozc has a bug with the mouse click.


(In reply to Ken Sugawara from comment #0)
> Additional info:
> Farther investigation revealed that the list of input modes *is* expanded
> but it fails to be rendered on the screen. If I click the right location
> where an input mode (e.g. Hiragana) is normally located after I click the
> "Input Mode", I can choose the input mode (quite difficult to use).

I guess you might register many input method engines or your screen height might be short.
If the length of the input modes meets the height, all modes can be shown at a time.
But you can drag the scrollbar in the pull down menu of the input method menu.

Comment 2 Ken Sugawara 2018-11-08 02:54:53 UTC
(In reply to fujiwara from comment #1)
> I cannot reproduce your problem with ibus-kkc.
> I know ibus-mozc has a bug with the mouse click.
> 
> 
> (In reply to Ken Sugawara from comment #0)
> > Additional info:
> > Farther investigation revealed that the list of input modes *is* expanded
> > but it fails to be rendered on the screen. If I click the right location
> > where an input mode (e.g. Hiragana) is normally located after I click the
> > "Input Mode", I can choose the input mode (quite difficult to use).
> 
> I guess you might register many input method engines or your screen height
> might be short.
> If the length of the input modes meets the height, all modes can be shown at
> a time.
> But you can drag the scrollbar in the pull down menu of the input method
> menu.

My screen height is 1080 which is plenty enough therefore there's no scrollbar, and it used to work just fine before updating.

I thought I made it clear that it is a rendering problem (I can click on the element which is invisible because it's no drawn on the screen), not the dimensions of the screen.

Having said that though, I discovered this was not an ibus problem. It is rather a gnome-shell problem, probably.

The menus associated with the gnome-shell system status area exhibits the exact same symptom.

I'm attaching a screenshot in which menus are not expanded (not rendered so) when I click on them.

I'm attaching a capture of the entire screen just so that it is perfectly clear that it has absolutely nothing to do with the screen height, BTW.

Comment 3 Ken Sugawara 2018-11-08 02:55:36 UTC
Created attachment 1503200 [details]
gnome-shell system status area menu exhibiting the same symptom

Comment 4 Ken Sugawara 2018-11-08 02:59:15 UTC
$ rpm -qa | grep gnome-shell
gnome-shell-extension-places-menu-3.30.1-1.fc29.noarch
gnome-shell-extension-alternate-tab-3.30.1-1.fc29.noarch
gnome-shell-extension-common-3.30.1-1.fc29.noarch
gnome-shell-extension-user-theme-3.30.1-1.fc29.noarch
gnome-shell-3.30.1-2.fc29.x86_64
gnome-shell-extension-window-list-3.30.1-1.fc29.noarch
gnome-shell-extension-launch-new-instance-3.30.1-1.fc29.noarch
gnome-shell-extension-background-logo-3.24.0-6.fc29.noarch
gnome-shell-extension-apps-menu-3.30.1-1.fc29.noarch

Comment 5 Ken Sugawara 2018-11-08 03:17:15 UTC
Additional information: The problem only occurs when there are multiple displays.
It appears to work fine when I disconnect the external displays.

$ xrandr 
Screen 0: minimum 320 x 200, current 3000 x 2493, maximum 8192 x 8192
XWAYLAND1 connected 1920x1080+1080+1413 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.96*+
XWAYLAND5 connected 1080x1920+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1080x1920     59.96*+
XWAYLAND6 connected 1920x1080+1080+333 (normal left inverted right x axis y axis) 530mm x 300mm
   1920x1080     59.96*+

The status area menu fails to expand when I set either one of non-rotated display as the primary, but it works when I make the rotated one the primary.


I tried a different configuration:

$ xrandr 
Screen 0: minimum 320 x 200, current 1920 x 2160, maximum 8192 x 8192
XWAYLAND1 connected 1920x1080+0+1080 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.96*+
XWAYLAND7 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1920x1080     59.96*+

It works fine no matter which display is the primary.

Also I tried this:
Screen 0: minimum 320 x 200, current 3000 x 2532, maximum 8192 x 8192
XWAYLAND1 connected 1920x1080+1080+1452 (normal left inverted right x axis y axis) 310mm x 170mm
   1920x1080     59.88*+
XWAYLAND8 connected 1080x1920+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1080x1920     59.96*+
 it 
It fails when XWAYLAND0, the non-rotated display the primary, but it works fine when the rotated XWAYLAND8 is the primary.

It seems to me that the symptom is exhibited only when I have a rotated display in the mix and the primary display is not rotated.

Comment 6 Ken Sugawara 2018-11-08 03:33:18 UTC
Never mind. I have absolutely no idea but the symptom disappeared after a reboot.
I'm closing this bug.
Thanks.


Note You need to log in before you can comment on or make changes to this bug.