permission to bind input_method denied

[Michael65589]

When I want to start the maliit-server I always get a permission denied message. This error occurs as non-root-user and as root-user as well.

maliit-server
WARNING: PulseAudioService: pa_context_connect() failed
WARNING: PulseAudioService: pa_context_connect() failed
zwp_input_method_v1@17: error 0: [ 139.491622] audit: type=1701 audit(1632379225.736:3): auid=4294967295 uid=1000 gid=1001 ses=4294967295 pid=813 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1
permission to bind input_method denied
FATAL: The Wayland connection experienced a fatal error: Protocol error
Aborted

Any suggestions?

[bhush9]

What compositor you're running against? And for Wayland you should use the maliit-keyboard directly, and not maliit-server

[Michael65589]

I use the Weston compositor. When I use maliit-keyboard directly I got the following message:
maliit-keyboard
wordengine.cpp plugin "/usr/lib/maliit/keyboard2/languages/en/libenplugin.so" loaded
PulseAudioService: pa_context_connect() failed
PulseAudioService: pa_context_connect() failed
inputmethod_p.h registerActiveLanguage(): activeLanguage is: "en"
in inputMethod.cpp setActiveLanguage() activeLanguage is: "en"
inputMethod::reset()
in clear preedit.. clearing word engine
keyboard is reporting : < 0 -8 0 8 > to the app manager.
maliit.connection.wayland: Maliit[ 4304.985544] audit: type=1701 audit(1632383391.232:8): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1172 comm="maliit-keyboard" exe="/usr/bin/maliit-keyboard" sig=6 res=1
::Wayland::InputMethod::InputMethod(MInputContextConnection*, wl_registry*, int)
zwp_input_method_v1@17: error 0: permission to bind input_method denied
The Wayland connection experienced a fatal error: Protocol error
Aborted

[Michael65589]

I follow this information for weston: http://maliit.github.io/news/2017/05/24/standalone-mode/

[Michael65589]

Hi Bhushan,

here is a log weston.log

[Michael65589]

I forgot to make the script executable.

/usr/bin/maliit-keyboard.sh

#!/bin/sh
export QT_WAYLAND_SHELL_INTEGRATION=inputpanel-shell
maliit-keyboard -platform wayland

After make it executable the weston.log looks
weston_1.log

It looks that maliit-keyboard is running but I can't see any keyboard on my screen.
ps aux | grep maliit
user 706 0.0 0.0 3440 900 ? S 08:17 0:00 /bin/sh /usr/bin/maliit-keyboard.sh
user 708 0.2 2.3 877436 46740 ? Sl 08:17 0:00 maliit-keyboard -platform wayland
user 857 0.0 0.1 6336 2012 ttymxc1 S+ 08:21 0:00 grep --color=auto maliit

[Michael65589]

ep 23 08:56:37 hmi daemon.info dbus-daemon[781]: [session uid=1000 pid=781] Activating service name='org.maliit.server' requested by ':1.10' (uid=1000 pid=1405 comm="./Maliit-Keyboard-Test ")
Sep 23 08:56:37 hmi daemon.info dbus-daemon[781]: [session uid=1000 pid=781] Activated service 'org.maliit.server' failed: Process org.maliit.server received signal 6

[jpetersen]

For Weston the virtual keyboard needs to be started from the compositor itself.

So in weston.ini there need to be a section
[input-method]
path=/path/to/maliit-keyboard

[Michael65589]

I changed the entry in weston.ini to your suggsetion but then the weston.log print the following
[16:45:02.483] Loading module '/usr/lib/weston/desktop-shell.so'
[16:45:02.485] launching '/usr/bin/maliit-keyboard'
[16:45:02.489] launching '/usr/libexec/weston-desktop-shell'
[16:45:02.765] input_method disconnected, respawning...
[16:45:02.765] launching '/usr/bin/maliit-keyboard'
[16:45:02.779] /usr/bin/maliit-keyboard died on signal 6
[16:45:02.890] input_method disconnected, respawning...
[16:45:02.890] launching '/usr/bin/maliit-keyboard'
[16:45:02.904] /usr/bin/maliit-keyboard died on signal 6
[16:45:03.023] input_method disconnected, respawning...
[16:45:03.023] launching '/usr/bin/maliit-keyboard'
[16:45:03.038] /usr/bin/maliit-keyboard died on signal 6
[16:45:03.145] input_method disconnected, respawning...
[16:45:03.145] launching '/usr/bin/maliit-keyboard'
[16:45:03.149] /usr/bin/maliit-keyboard died on signal 6
[16:45:03.273] input_method disconnected, respawning...
[16:45:03.273] launching '/usr/bin/maliit-keyboard'
[16:45:03.277] /usr/bin/maliit-keyboard died on signal 6
[16:45:03.390] input_method disconnected, giving up.
[16:45:03.392] /usr/bin/maliit-keyboard died on signal 6

:~$ which maliit-keyboard
/usr/bin/maliit-keyboard

Why is maliit-keybord died on signal6? How can I debug this?

[Michael65589]

Look what happend when I call maliit-keyboard manualy:

:~$ maliit-keyboard
wordengine.cpp plugin "/usr/lib/maliit/keyboard2/languages/en/libenplugin.so" loaded
PulseAudioService: pa_context_connect() failed
PulseAudioService: pa_context_connect() failed
"Rejected send message, 2 matched rules; type="method_call", sender=":1.14" (uid=1000 pid=864 comm="maliit-keyboard ") interface="net.connman.Manager" member="GetProperties" error name="(unset)" requested_reply="0" destination="net.connman" (uid=0 pid=780 comm="/usr/sbin/connmand -n ")"
"Rejected send message, 2 matched rules; type="method_call", sender=":1.14" (uid=1000 pid=864 comm="maliit-keyboard ") interface="net.connman.Manager" member="GetServices" error name="(unset)" requested_reply="0" destination="net.connman" (uid=0 pid=780 comm="/usr/sbin/connmand -n ")"
inputmethod_p.h registerActiveLanguage(): activeLanguage is: "en"
in inputMethod.cpp setActiveLanguage() activeLanguage is: "en"
inputMethod::reset()
in clear preedit.. clearing word engine
keyboard is reporting : < 0 -8 0 8 > to the app manager.
maliit.connection.wayland: Maliit::Wayland::InputMethod::InputMethod(MInputContextConnection*, wl_registry*, int)
zwp_input_method_v1@17: error 0: permission to bind input_method denied
The Wayland connection experienced a fatal error: Protocol error
Aborted
[ 807.474181] audit: type=1701 audit(1632416300.744:9): auid=4294967295 uid=1000 gid=1001 ses=4294967295 pid=864 comm="maliit-keyboard" exe="/usr/bin/maliit-keyboard" sig=6 res=1

I think that "zwp_input_method_v1@17: error 0: permission to bind input_method denied" is the problem.

[dobey]

I think that "zwp_input_method_v1@17: error 0: permission to bind input_method denied" is the problem.

Yes, as @jpetersen said in #73 (comment) you cannot simply run maliit-keyboard with weston, as it has to be started by weston itself. By default, weston starts its own keyboard, therefore preventing maliit from connecting.

[Michael65589]

Okay, thats the reason of the permission denied problem, but with the entry [input-method] in the weston.ini I thought this let weston start the maliit keyboard.
@jpetersen said that I should enter the path to maliit-keyboard binary. http://maliit.github.io/news/2017/05/24/standalone-mode/ tells me that I have to create a script and configure the path to this script in weston.ini

Okay, step by step.
I created the maliit-keyboard.sh as descriped in http://maliit.github.io/news/2017/05/24/standalone-mode/ .
I put the script to /usr/bin/.
I set the permissions to executable for all
I set the path to this script in weston.ini at [input-method] key

When I boot my system and weston starts I can see that maliit-keyboard is started as well

>:~$ ps aux | grep maliit
user         704  0.0  0.0   3440   936 ?        S    17:55   0:00 /bin/sh /usr/bin/maliit-keyboard.sh
user         706  1.3  2.2 877436 45120 ?        Sl   17:55   0:00 maliit-keyboard -platform wayland
user         805  0.0  0.1   6336  2080 ttymxc1  S+   17:56   0:00 grep --color=auto maliit

weston.log also tells me that the maliit-keyboard is starte
...
[17:55:47.463] Loading module '/usr/lib/weston/desktop-shell.so'
[17:55:47.465] launching '/usr/bin/maliit-keyboard.sh'
[17:55:47.469] launching '/usr/libexec/weston-desktop-shell'
...

When I start weston-terminal and click into the terminal nothing happens. Why is there no keyboard visible?

I create a simple QT-Application with only one TextInput Field.
I set QT_IM_MODULE=Maliit
Then I start my application.
...
~$ ./Maliit-Keyboard-Test
QML debugging is enabled. Only use this in a safe environment.
[ 322.377565] audit: type=1701 audit(1632420060.672:3): auid=1000 uid=1000 gid=1001 ses=1 pid=884 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1
[ 328.149124] audit: type=1701 audit(1632420066.444:4): auid=1000 uid=1000 gid=1001 ses=1 pid=888 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1
[ 334.060028] audit: type=1701 audit(1632420072.352:5): auid=1000 uid=1000 gid=1001 ses=1 pid=890 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1
...

Why is maliit-server finished with sig=6?

[dobey]

When I start weston-terminal and click into the terminal nothing happens. Why is there no keyboard visible?

I don't know. It might be trying to use the wrong text input protocol. But I also have not been able to get maliit keyboard to come up under wayland on any compositor running on top of Xorg on my system. I would very much like it to though, because it would make the testing I need to do currently, much easier.

Why is maliit-server finished with sig=6?

I also don't know. Have you tried attaching to the process with gdb and doing whatever is causing it to happen, and getting a stack trace?

[Michael65589]

@jpetersen
How is it possible to show the maliit-keyboard when I use wayland with weston?
Weston offers a terminal (weston-terminal) and I want to use a virtual keyboard to give input for that terminal. Weston uses the zwp_text_input_manager_v1 and zwp_input_method_v1. Maliit also speak zwp_input_method_v1. The connection between Maliit and Weston is the [input-method] key in the weston.ini. Weston starts maliit-keyboard but what happens when I open the weston-terminal and do a touch click into the terminal.
When starts the maliit-server? Should maliit-server start at all?
Is there a possibility to trace the input system (zwp_input_method_v1)?
I want to monitor the dbus traffic between maliit-server and maliit-keyboard but the maliit-server never starts. Does the maliit-server only start on demand?
I can see the maliit-keyboard in the process list but I can't see the maliit-server.
Can maliit-server generate log files? I want to know why it breaks.

On the other hand I want to use maliit-keyboard with Qt applications. Does this run out of the box when QT_IM_MODULE is set to Maliit?
Thanks

[Michael65589]

I set MALIIT_DEBUG=true in my environment.
When I start my Qt application:
./Maliit-Keyboard-Test
QML debugging is enabled. Only use this in a safe environment.
Creating Maliit input context
[ 6016.622837] audit: type=1701 audit(1632475329.964:15): auid=1000 uid=1000 gid=1001 ses=1 pid=2233 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1
MInputContext in virtual void MInputContext::update(Qt::InputMethodQueries)
MInputContext in virtual void MInputContext::update(Qt::InputMethodQueries)
MInputContext in virtual void MInputContext::setFocusObject(QObject*) QQuickRootItem(0xaaaad8ea78f0)
MInputContext in virtual void MInputContext::commit()
MInputContext in virtual void MInputContext::update(Qt::InputMethodQueries)
virtual void MInputContext::showInputPanel()
MInputContext in virtual void MInputContext::setFocusObject(QObject*) QQuickTextInput(0xaaaad8eb1d60)
MInputContext void MInputContext::updateInputMethodExtensions()
[ 6022.985018] audit: type=1701 audit(1632475336.328:16): auid=1000 uid=1000 gid=1001 ses=1 pid=2236 comm="maliit-server" exe="/usr/bin/maliit-server" sig=6 res=1

And journalctl says:
org.maliit.server[2233]: WARNING: Could not find the Qt platform plugin "xcb" in ""
org.maliit.server[2233]: FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
org.maliit.server[2233]: Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland.

So it looks that maliit-server should start as root. Is there a way to start it as user?