Bug 747532 - IME specific menu items do not work if ibus-gnome3 is enabled
Summary: IME specific menu items do not work if ibus-gnome3 is enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ibus
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: fujiwara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 08:06 UTC by Daiki Ueno
Modified: 2011-11-11 06:07 UTC (History)
4 users (show)

Fixed In Version: ibus-1.4.0-5.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-11 06:07:29 UTC
Type: ---


Attachments (Terms of Use)

Description Daiki Ueno 2011-10-20 08:06:56 UTC
Description of problem:

Clicking on IME specific items on the ibus-gnome3 menu has no effect.

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

ibus-libs-1.4.0-4.fc16.x86_64
ibus-1.4.0-4.fc16.x86_64
ibus-gnome3-1.4.0-4.fc16.x86_64
ibus-anthy-1.2.6-3.fc16.x86_64

How reproducible:
100%

Steps to Reproduce:
1. enable Input Method Indicator shell extension with gnome-tweak-tool
2. enable ibus-anthy on gedit
3. click "Preferences - Anthy" in the IBus menu
  
Actual results:
ibus-setup-anthy should be launched

Expected results:
nothing happens.

Additional info:

Comment 1 fujiwara 2011-10-20 08:46:54 UTC
Thanks for filing this.

In F15, I added a workaround not to move the input focus to ibus menu but the workaround does not work in F16.
After I discussed with upstream, it seems shell menu always have the global settings instead of input context settings.
So this part needs to be implemented again. I think it's a bit risk to fix this in F16 GA unfortunately.

Currently only IME selection is fixed.

Comment 2 Parag Nemade 2011-10-20 08:52:26 UTC
I too have noticed this problem.

Comment 4 fujiwara 2011-10-21 07:27:22 UTC
I think this will be fixed together with bug 747845.

Comment 5 Daiki Ueno 2011-11-11 06:07:29 UTC
Confirmed that this is fixed in the current stable version.  Closing.


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