Bug 844037

Summary: [kde] ibus icon is systray non-responsive
Product: [Fedora] Fedora Reporter: Ed Greshko <ed.greshko>
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: gcarter, i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-06 02:02:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ed Greshko 2012-07-28 06:13:07 UTC
Description of problem: Left or Right click on ibus icon in KDE systray fails to bring up menu.

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

ibus-1.4.99.20120428-2.fc17.x86_64


How reproducible: Always at current update level


Steps to Reproduce:
1. Left or Right click on ibus icon
2.
3.
  
Actual results:  No menus produced 


Expected results: Right click produces "Preferences" menu, Left click allows Language selection.


Additional info: Worked correctly on fresh F17 install.  Broke on update.  GNOME works OK.

Comment 1 gcarter 2012-08-02 20:18:15 UTC
Confirmed, happens as well as I had to write a letter in Chinese to a friend of mine and ibus input is no longer functional under kde Fedora 17.

-gc

Comment 2 Ed Greshko 2012-08-02 20:37:03 UTC
FWIW, gcarter, ibus entry is still possible on my system.  I just use Ctrl-space to activate.  I just can't use the mouse to interact.  Sometimes when I login the keyboard icon looks "strange" I have to issue   /usr/bin/ibus-daemon -r --xim at the command line to restart instead of using "right click' on the icon and picking "restart".

Comment 3 fujiwara 2012-08-06 02:02:29 UTC

*** This bug has been marked as a duplicate of bug 716358 ***