Bug 1711646

> running `sudo ibus write-cache --system` results in the same error when called over SSH.

I cannot reproduce your problem. The `ibus write-cache` does not use the X11 connection.
Probably I guess one of your IBus engines could use the X11 connection but not ibus core.

You can move all xml files in /usr/share/ibus/component/ and run the command again so that you check which xml file effects your problem.

It's caused by ibus-typing-booster-2.6.1-1. Changing the component accordingly.
Thanks for your help, fujiwara!

The problem also occurs on (re)installing ibus-typing booster as it has the same scriptlets.

I think this is a bug.

I cannot reproduce this.

I just found out that it only happens when X11 forwarding is active. (I have this as default for my own machines so I didn't realize it earlier.)

If you want to reproduce you will need:

 - On your host in /etc/ssh/sshd_config:
   X11Forwarding yes

 - Restart sshd (Untested: sudo systemctl restart sshd)

 - Ssh into your machine (client and host can be the same or different machines) with the -X flag.

 - sudo dnf reinstall ibus-typing-booster


I see now, that this is quite an edge-case so feel free to just close this as wontfix if you do not want to spend time on it.

I can see the "Connection refused" warnings:

```
# /usr/libexec/ibus-engine-typing-booster --xml
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
<engines>
    <engine>
        <name>typing-booster</name>
        <longname>Typing Booster</longname>
        <language>t</language>
...
</engines>
```

(In reply to fujiwara from comment #6)
> I can see the "Connection refused" warnings:
> 
> ```
> # /usr/libexec/ibus-engine-typing-booster --xml
> Unable to init server: Could not connect: Connection refused
> Unable to init server: Could not connect: Connection refused
> <engines>
>     <engine>
>         <name>typing-booster</name>
>         <longname>Typing Booster</longname>
>         <language>t</language>
> ...
> </engines>

Unfortunately I cannot reproduce this.

$ env -u DISPLAY /usr/libexec/ibus-engine-typing-booster --xml
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
<engines>
    <engine>
        <name>typing-booster</name>
        <longname>Typing Booster</longname>
        <language>t</language>
        <license>GPL</license>
        <author>Mike FABIAN &lt;mfabian&gt;, Anish Patil &lt;anish.developer@gmail.
com&gt;</author>
        <icon>/usr/share/ibus-typing-booster/icons/ibus-typing-booster.svg</icon>
        <layout>default</layout>
        <description>A completion input method to speedup typing.</description>
        <symbol>🚀</symbol>
        <setup>/usr/libexec/ibus-setup-typing-booster</setup>
        <icon_prop_key>InputMode</icon_prop_key>
    </engine>
</engines>

FEDORA-2021-d0315c0d74 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2021-23444a781e has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2021-dc40c874a1 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-dc40c874a1

FEDORA-2021-ba329e760f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ba329e760f

FEDORA-2021-97349467f8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-97349467f8

FEDORA-2021-97349467f8 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-97349467f8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-97349467f8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-ba329e760f has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ba329e760f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ba329e760f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-dc40c874a1 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-dc40c874a1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-dc40c874a1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2021-97349467f8 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2021-dc40c874a1 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2021-ba329e760f has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Thank you! No more warnings at `dnf update` :)