Bug 867237 - can not change "IM" when I put the cursor into the"search bar " on the desktop
Summary: can not change "IM" when I put the cursor into the"search bar " on the desktop
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-17 06:15 UTC by lnie
Modified: 2013-09-24 02:48 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-24 02:48:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lnie 2012-10-17 06:15:11 UTC
Description of problem:

I have type some Chinese ,then I move the cursor into the "search box"to search sth but I can not change the"IM" use"ctrl+space" as usual. Actually,I also try to change English to Chinese,also failed 

Version-Release number of selected component (if applicable):
f18 x86-64 beta TC4  


How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Peng Wu 2012-10-17 07:01:36 UTC
CC Takao Fujiwara.

Comment 2 fujiwara 2012-10-17 08:10:55 UTC
I also noticed this issue recently.
This was fixed in ibus-gjs in f17.

For the keypress events on the shell box, I could use 'captured-event' signal of global.statge:
https://github.com/fujiwarat/ibus-gjs/blob/master/js/ui/status/ibus/ibusPanel.js#L795

Comment 3 Elad Alfassa 2012-10-17 10:26:14 UTC
This is related to gnome3.6 integration with input methods, since gnome-settings-daemon is the thing that handles keyboard shortcuts but the shell has a grab on the keyboard. See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=643111



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 lnie 2012-11-27 04:24:16 UTC
Still happens in Fedora 18 Beta RC1.


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