Bug 1038514 - [ALL LANG] Failed to switch Input Method: Current desktop isn't targeted by IMSettings.
Summary: [ALL LANG] Failed to switch Input Method: Current desktop isn't targeted by I...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: im-chooser
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Akira TAGOH
QA Contact: QE Internationalization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 09:11 UTC by Lijun Li
Modified: 2013-12-06 03:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-05 11:23:20 UTC
Target Upstream Version:


Attachments (Terms of Use)
Failed to switch Input Method: Current desktop isn't targeted by IMSettings (47.72 KB, image/png)
2013-12-05 09:14 UTC, Lijun Li
no flags Details

Description Lijun Li 2013-12-05 09:11:26 UTC
Description of problem:
[ALL LANG] Failed to switch Input Method: Current desktop isn't targeted by IMSettings.

Version-Release number of selected component (if applicable):
im-chooser-1.6.4-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install latest rhel7 beta build.
2. Run im-chooser from terminal.
3. Click on Use iBus.

Actual results:
Failed to switch Input Method: Current desktop isn't targeted by IMSettings.

Expected results:
Worked as normal.

Additional info:

Comment 1 Lijun Li 2013-12-05 09:14:34 UTC
Created attachment 833056 [details]
Failed to switch Input Method: Current desktop isn't targeted by IMSettings

Comment 3 Akira TAGOH 2013-12-05 11:23:20 UTC
(In reply to Lijun Li from comment #0)
> Actual results:
> Failed to switch Input Method: Current desktop isn't targeted by IMSettings.

This is the reason not working as *you* expected. but it is the expected behavior and is documented. this is NOTABUG.
Use gnome-control-center resion instead.

Comment 4 Satyabrata Maitra 2013-12-06 03:56:40 UTC
im-chooser is no more for gnome desktop. So, its an expected behaviour!


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