Bug 431195

Summary: can't select nabi in new im-chooser.
Product: [Fedora] Fedora Reporter: sangu <sangu.fedora>
Component: nabiAssignee: subhransu behera <sbehera>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 9CC: eng-i18n-bugs, petersen
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-25 14:48:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sangu 2008-02-01 14:20:18 UTC 
Description of problem:
Select nabi on im-chooser
$ im-chooser

(im-chooser:19699): IMSettings-WARNING **: Failed to invoke a method `StopIM':
  Errors detected, but forcibly stopped:
  * Couldn't send a signal to the xim process successfully.


(im-chooser:19699): IMSettings-WARNING **: Failed to invoke a method `StartIM':
  Failed to execute child process "nabi" (No such file or directory)


Version-Release number of selected component (if applicable):
0.99-1.fc9.i386

How reproducible:
always

Steps to Reproduce:
1. Launch im-chooser
2. Select nabi
3.
  
Actual results:


Expected results:


Additional info:
nabi-0.18-7.fc8.i386
Comment 1 Akira TAGOH 2008-02-02 04:22:24 UTC 
actually this is nabi's fault. XIM_PROGRAM has to contain the full path.
Comment 2 subhransu behera 2008-02-06 07:13:58 UTC 
Fixed in: nabi-0.18-8.fc9
Comment 3 Bug Zapper 2008-05-14 04:58:01 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping