No keyboard input on BeagleBone Black
-
Hello there,
I am using QT on BeagleBone Black to run an example widget aplication. My mouse works but the keyboard doesnt. I was trying to add a variables to the /etc/enviroment:QWS_MOUSE_PROTO=tslib:/dev/input/mouse0 QWS_KEYBOARD=linuxinput:/dev/input/event1 TSLIB_CALIBFILE=/etc/pointercal TSLIB_CONFFILE=/etc/ts.conf TSLIB_PLUGINDIR=/usr/lib/ts
event1 is my keyboard. I am not getting any input to the lineedit that i have in the application nor the system command line. The keyboard works normally outside qt application. How can I turn on the keyboard? I would really aprichiate all help in this matter!
-
Update:
So far I was running my application from the Qt creator. Now I have run the application nativelly in the command line using ./myapp -qws. In this situation, my keyboard input is going behind the application to the command line, instead of qt app... So even though im root, i typed sudo, and then keyboard started working. Thats weird for me. Is there a way to make the Qt app use sudo as well?Update2
When i run with sudo on the device- keyboard works. When i run with sudo through ssh, it doesnt. Why? -
Hi,
Which version of Qt are you using ? Do you have the rights to access the input devices ?
-
Hello,
My application rights are:
-rwxrwxrwx 1 root root 353100 Mar 2 2015 OvenViewerAnd the input device rights are:
crwxrwxrwt 1 root root 13, 65 Mar 1 21:45 event1I have set the rights in a file /etc/udev/rules.d/85-pure-data.rules:
KERNEL=="event1", MODE="777"My Qt version is 4.8.6:
QMake version 2.01a
Using Qt version 4.8.6 in /opt/qt-arm/lib -
Also there is one thing I have noticed thats suspicious for me. When I run the program remotelly at termination of it I always see a line:
bash: line 1: 653 Terminated DISPLAY=':0.0' QWS_KEYBOARD='/dev/tty' /home/debian/OvenViewer -qws
QWS_KEYBOARD is set to /dev/tty, even though I have changed it in the build variables to /dev/input/event1 as well as in .user and .pro.user files. But after some builds it becape /dev/tty again in .user file. Might this be the case? How does he know what variable to set?Also, why does the mouse work, but not keyboard...?
-
Starting the application from Qt Creator ?
-
Also one more thing. I have just implemented by hand a code that reads from
/dev/input/event1
and I have placed it in the main before MainWindow is created and it works, which means that the app has the rights to red the input, just the Qt doesnt interpret it, why?The code here after retrieving 20 events from
/dev/input/event1
continues to the Qt gui App: Keyboard test code -
Just to be entirely sure, Qt 4 series ?
-
Did I saw correctly ? You have "QWS_KEYBOARD='/dev/tty'" in either a bash script on your target or set in Qt Creator in the run environment panel
-
Look on the Run part of the Project panel in the Environment Variables
-
Strange, which version of Qt Creator are you using ?
-
Did you check with a more recent version ?
-
Sorry, I meant a more recent version of Qt Creator, as for Qt 4 the latest version is 4.8.7