As root on the device (armv7hl paths):

```bash
devel-su
```

```bash
mkdir -p /usr/lib64/qt5/plugins/platforminputcontexts && ln -sf /usr/lib/qt5/plugins/platforminputcontexts/libmaliitplatforminputcontextplugin.so /usr/lib/qt5/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so /usr/lib64/qt5/plugins/platforminputcontexts/ && systemctl-user restart lipstick
```

The lipstick restart at the end closes all apps – it is needed for the processes that have already lost their input context; a reboot works too. When you remove FUTO again, remove the directory by hand as well:

```bash
rm -rf /usr/lib64
```

That is safe on armv7hl because `/usr/lib64` does not exist there otherwise – check with `ls /usr/lib64` first that only these symlinks are in it.

# All Qt apps lose their input method on armv7hl (and i486): compose wrapper hard-codes /usr/lib64 plugin paths

**Version:** futo-keyboard-sailfish 0.2.1 (armv7hl RPM from OpenRepos)
**Device / OS:** [device], Sailfish OS [version]
**Architecture:** armv7hl

## Symptoms

After installing the RPM, every application started afterwards has no keyboard at all: no input panel appears in any text field, independent of which layout is active (FUTO, Jolla layouts, third-party). After a reboot this includes lipstick itself. Apps that were already running before the installation keep their keyboard, which makes the problem look intermittent ("works in app A, not in app B") and hides it right after the install.

Uninstalling the RPM does not help until the affected apps and lipstick are restarted, because the plugin is already loaded in those processes.

## Root cause

`hardware/compose/futo_maliit_compose_wrapper.cpp`, lines 211–212:

```cpp
: m_maliitLoader(QStringLiteral("/usr/lib64/qt5/plugins/platforminputcontexts/libmaliitplatforminputcontextplugin.so")),
m_composeLoader(QStringLiteral("/usr/lib64/qt5/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so"))
```

On armv7hl and i486 `%{_libdir}` is `/usr/lib`, and the Makefile/spec correctly install the wrapper and the compose plugin to `/usr/lib/qt5/plugins/platforminputcontexts/`. The hard-coded `/usr/lib64` paths do not exist there, so `m_maliitLoader.instance()` returns null and `create()` returns `nullptr`.

Because `libafutomaliitcomposewrapper.so` sorts before `libmaliitplatforminputcontextplugin.so`, `QPlatformInputContextFactory::create("maliit")` picks the wrapper for the `maliit` key, and `qLoadPlugin` does not fall back to the next matching plugin when `create()` returns null. The process therefore ends up with no platform input context at all. Since `QT_IM_MODULE=Maliit` is set system-wide (`/etc/profile.d/maliit-server.sh`), this hits every Qt process, including lipstick.

## Suggested fix

Resolve the paths at runtime instead of hard-coding them, e.g.

```cpp
const QString pluginDir = QLibraryInfo::location(QLibraryInfo::PluginsPath)
+ QStringLiteral("/platforminputcontexts/");
```

which yields `/usr/lib/qt5/plugins` on 32-bit and `/usr/lib64/qt5/plugins` on aarch64. Alternatively pass the libdir at build time in `scripts/build-compose-plugin.sh`, the same way `-DX11_PREFIX="/usr"` is already passed (e.g. `-DFUTO_LIBDIR="/usr/lib"` for armv7hl/i486).

It would also be safer if the wrapper logged a warning when the stock plugin cannot be loaded; currently the failure is completely silent.

## Workaround for affected users

As root, until a fixed build is available:

```sh
mkdir -p /usr/lib64/qt5/plugins/platforminputcontexts
ln -sf /usr/lib/qt5/plugins/platforminputcontexts/libmaliitplatforminputcontextplugin.so /usr/lib/qt5/plugins/platforminputcontexts/libcomposeplatforminputcontextplugin.so /usr/lib64/qt5/plugins/platforminputcontexts/
systemctl-user restart lipstick
```

(The symlink directory has to be removed again by hand after uninstalling.)

I can send a PR for the `QLibraryInfo` variant if you prefer that.

Well, fighting forward, step 2.
1. Uninstalled okboard and futo, deleted all folders abd files about them from search from rootexplorer.
2. Installed futo.
3. Reboot.
4. After reboot in Storeman - no keyboard. In yast, xmatic - keyboard (built-in) exist.
5. Selected futo from Settings - Text input. Keyboard dissapear everywhere.
6. Moreover, wi-fi password of home router was cleaned!
7. Seems a very big problem with Sailfish secrets module. Try to disable all password integrity in next test version may be. (sure i disabled password saving from the beginning and never turned it on).

Also i had strange windows, which never saw before installing futo. About secrets, wrong password and deleting secrets, when start Storeman.

great!!!!

This is the best keyboard here since Nokia n9/n950times

Works very well. I have one question, though. How do you hide the keyboard when swipe mode is active?

Prediction and Swipe typing aren't working for me. What do I do wrong? (german)

Wow!! Collest keyboard ever on Sailfish!

But..

1. Russian keyboard not turning on (sure turned it on in settings of FUTO)

2. English predicting not turning on (sure downloaded english language pack of 8 Mb, it said that "installed")

3. Twemoji pack not turning on - empty square places for emojies in keyboard window (sure loaded twemoji pack from settings, it said that "installed"), if i press on empty squares - it types black-n-white emoji.

So, on armv7hl now works ONLY English keyboard without prediction, without swipe input.

And a question: Does russian prediction language pack not exist or it exist, but need to be ported on sailfish? And what about russian swipe prediction?

And, for understanding. We must turn off all other keyboards in settings, leaving only FUTO alone?

Armv7hl, Sony XA2, 5.1.0.11.