Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No keyboard input #459

Open
vanlooverenkoen opened this issue Nov 7, 2024 · 1 comment
Open

No keyboard input #459

vanlooverenkoen opened this issue Nov 7, 2024 · 1 comment

Comments

@vanlooverenkoen
Copy link

vanlooverenkoen commented Nov 7, 2024

I don't have any keyboard input. When the app is running. When I type on the keyboard the text is typed in the cli that is still open behind/underneath the flutter app.

I am using a logitech K400 (azerty be) and the mouse does work perfectly. But the keyboard input does not work. I have also already tried with another keyboard (Keychron k3 wired) and that does not work either. What should I do?

I have configured my locale as en_GB as you can see here

➜  config locale
LANG=en_GB
LANGUAGE=en_GB
LC_CTYPE="en_GB"
LC_NUMERIC="en_GB"
LC_TIME="en_GB"
LC_COLLATE="en_GB"
LC_MONETARY="en_GB"
LC_MESSAGES="en_GB"
LC_PAPER="en_GB"
LC_NAME="en_GB"
LC_ADDRESS="en_GB"
LC_TELEPHONE="en_GB"
LC_MEASUREMENT="en_GB"
LC_IDENTIFICATION="en_GB"
LC_ALL=en_GB

When I run in desktopmode the keyboard does work in rasbian desktop (without flutter-pi).

I can see this when I run.

keyboard.c: Could not create compose table from locale.
user_input.c: Could not initialize keyboard configuration. Flutter-pi will run without text/raw keyboard input.
[text_input] warning: flutter requested native autocorrect, whichis not supported by flutter-pi.

My Full output

➜  pi: flutterpi_tool run --release -d pi
Launching lib/main.dart on pi in release mode...
Building Flutter-Pi bundle...                                           
Installing app on device...                                      2,339ms
modesetting.c: Could not set DRM client universal planes capable. drmSetClientCap: Operation not supported
flutter-pi.c: Could not create drmdev from device at "/dev/dri/card0". Continuing.
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:39:34: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:40:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:41:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:42:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:43:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:44:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:45:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:46:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:47:27: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:48:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: string literal is not a valid UTF-8 string
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: too many errors
xkbcommon: ERROR: /usr/share/X11/locale/iso8859-1/Compose:49:29: failed to parse file
keyboard.c: Could not create compose table from locale.
user_input.c: Could not initialize keyboard configuration. Flutter-pi will run without text/raw keyboard input.
[text_input] warning: flutter requested native autocorrect, whichis not supported by flutter-pi.
@vanlooverenkoen
Copy link
Author

vanlooverenkoen commented Nov 13, 2024

if I launch the app with flutterpi_tool (from my machine) the keyboard does not work. I launch the app with flutter-pi (after using flutterpi_tool to install it on the pi) it works. but it also types in the terminal that is still open behind (resulting in the escape button not working because it kills the app in the terminal behind the app)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant