From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Xuser has no permissions for event devices (no keyboard and mouse in X)
Date: Tue, 02 Apr 2013 14:08:59 -0700 [thread overview]
Message-ID: <515B48EB.6040209@linux.intel.com> (raw)
Current master atom-pc build + pending 3.8 kernel update us using
rootless X, but X fails to open the event devices. Do we need some kind
of default group permissions for the /dev/input/* devices?
root@atom-pc:/etc/X11# cat /var/log/Xorg.0.log | grep EE | grep "event"
[3430478.394] (EE) evdev: Power Button: Unable to open evdev device
"/dev/input/event2".
[3430478.398] (EE) evdev: Video Bus: Unable to open evdev device
"/dev/input/event3".
[3430478.401] (EE) evdev: Power Button: Unable to open evdev device
"/dev/input/event1".
[3430478.410] (EE) evdev: HP HP Wireless Mini Keyboard: Unable to open
evdev device "/dev/input/event5".
[3430478.414] (EE) evdev: HP HP Wireless Mini Keyboard: Unable to open
evdev device "/dev/input/event6".
[3430478.421] (EE) evdev: AT Translated Set 2 keyboard: Unable to open
evdev device "/dev/input/event4".
[3430478.434] (EE) synaptics: SynPS/2 Synaptics TouchPad: no synaptics
event device found
...
root@atom-pc:/etc/X11# cat /etc/group | grep xuser
tty:x:5:xuser
audio:x:29:xuser
video:x:44:xuser
xuser:x:1000:
root@atom-pc:/etc/X11# ls -la /dev/input/event
event0 event1 event2 event3 event4 event5 event6 event7
root@atom-pc:/etc/X11# ls -la /dev/input/event*
crw-r----- 1 root root 13, 64 Apr 2 20:38 /dev/input/event0
crw-r----- 1 root root 13, 65 Apr 2 20:38 /dev/input/event1
crw-r----- 1 root root 13, 66 Apr 2 20:38 /dev/input/event2
crw-r----- 1 root root 13, 67 Apr 2 20:38 /dev/input/event3
crw-r----- 1 root root 13, 68 Apr 2 20:38 /dev/input/event4
crw-r----- 1 root root 13, 69 Apr 2 20:52 /dev/input/event5
crw-r----- 1 root root 13, 70 Apr 2 20:52 /dev/input/event6
crw-r----- 1 root root 13, 71 Apr 2 20:38 /dev/input/event7
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
reply other threads:[~2013-04-02 21:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=515B48EB.6040209@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.