Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 462191 - reversed if condition in scim's xinput settings script
Summary: reversed if condition in scim's xinput settings script
Keywords:
Status: CLOSED DUPLICATE of bug 448268
Alias: None
Product: Fedora
Classification: Fedora
Component: scim
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peng Huang
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-13 19:14 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2008-09-13 19:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-13 19:20:42 UTC


Attachments (Terms of Use)
Patch to fix broken if logic (deleted)
2008-09-13 19:14 UTC, Dominik 'Rathann' Mierzejewski
no flags Details | Diff

Description Dominik 'Rathann' Mierzejewski 2008-09-13 19:14:00 UTC
Created attachment 316673 [details]
Patch to fix broken if logic

Description of problem:
After enabling scim in System->Preferences->Personal->Input Method, scim icon in GNOME notification area remains inactive and hotkeys which enable it have no effect. That's because /etc/X11/xinitrc/xinput.d/scim.conf script fails to set GTK_IM_MODULE to scim/scim-bridge due to reversed if statement logic.

Version-Release number of selected component (if applicable):
scim-1.4.7-23.fc9.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Enable SCIM
2. Re-log
3. Try to activate SCIM using, for example, Ctrl+space
  
Actual results:
Nothing happens.

Expected results:
SCIM's toolbar should appear.

Additional info:
It worked fine in F-8 with scim-1.4.7-7.fc8. Looks like the correct scim.conf was posted in bug 448268, but a broken version made it into the update. Bug 456490 could also be related to this issue.

Comment 1 Dominik 'Rathann' Mierzejewski 2008-09-13 19:20:42 UTC
Looks like I haven't noticed I was looking at -23, not -24. Closing as duplicate, sorry for the noise.

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


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