RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

imsettings-stop cannot stop IBus running in a case provided in steps.

Version-Release number of selected component (if applicable):
imsettings-0.108.0-3.2.el6.x86_64
RHEL Version:Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
Kernel:2.6.32-37.el6.x86_64


How reproducible:
everytime I have test.

Steps to Reproduce:
1. Enable IBus from im-chooser
2. type # imsettings-stop from a terminal
   (Stopped IBus)
3. type # imsettings-start from a terminal
   (Started none)
4. Enable IBus from im-chooser
5. type # imsettings-start from a terminal
   (Unable to keep Input method running)
6. type # imsettings-stop from a terminal
   (No Input Method running...)

Actual results:

Step3: Cannot start IBus by imsettings-start
Step6: Cannot stop IBus by imsettings-stop

Expected results:

Step3: Can start IBus by imsettings-start
Step6: Can stop IBus by imsettings-stop

Additional info:

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

(In reply to comment #0)
> 3. type # imsettings-start from a terminal
>    (Started none)

This is correct behaviour. you have to do imsettings-stop -n to avoid updating your .xinputrc.

> 4. Enable IBus from im-chooser
> 5. type # imsettings-start from a terminal
>    (Unable to keep Input method running)

This is also correct behaviour. you have to do imsettings-start --cond-start to avoid trying to invoke IM twice.

> 6. type # imsettings-stop from a terminal
>    (No Input Method running...)

Since imsettings is capable to keep the status of multiple IMs on track but one for one IM, this is also correct behaviour since imsettings thinks ibus session is closed by the error at step 5.