View Full Version : Cannot open keyboard: Permission denied

15th June 2006, 21:47
I finally had time to give Qtopia a try. To my disappointment, I encountered some problems while trying to run applications, for example any demo provided in the installation package..

I have downloaded and installed qtopia-core-opensource-src-4.1.3 on my Kubuntu Dapper. I followed the instructions for Installing Qtopia Core (http://doc.trolltech.com/4.1/qtopiacore-install.html). Framebuffer test passes fine and everything seems ok to me.

The next step i took was trying launching an example to see everything works as expected. Again, I followed the instructions (http://doc.trolltech.com/4.1/qtopiacore-running.html) provided.

jp@jaber:~$ cd /usr/local/Trolltech/QtopiaCore-4.1.3/demos/textedit/
jp@jaber:/usr/local/Trolltech/QtopiaCore-4.1.3/demos/textedit$ ./textedit -qws
Creating mouse "Auto"
Cannot open keyboard: Permission denied

jp@jaber:/usr/local/Trolltech/QtopiaCore-4.1.3/demos/textedit$ sudo ./textedit -qws
Qtopia Core data directory is not owned by user 0

The problem seems to be same than for example this:
Keyboard and mouse problem with Qtopia-Core-4.1.0 (http://qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=156&forum=5)

I haven't been able to find any answers to this, am I doing something wrong?

16th June 2006, 10:07
I'm not 100% sure, but I belive that the keyboard is a device (in the /dev directory) that Qtopia is attempting to open. Somehow the file access rights does not allow that.

17th June 2006, 01:01
Its possible it cant find the keboard dev.

export QWS_KEYBOARD=tty

by default, that opens /dev/tty0, you can specify the device like this:

export QWS_KEYBOARD=tty:/dev/input/event1

or whatever it may be.
if its a USB keyboard, try:

export QWS_KEYBOARD=usb

19th June 2006, 22:57
The problem seemed to be something else than I thought. I was thinking that the keyboard error prevented application from starting (I had nothing visible on the screen before). I managed to get the application visible after changing the console resolution, though. After setting the QWS_KEYBOARD environment variable properly I got also the keyboard working.