Try the xorg-x11-server-Xorg-setuid package. Regards,
On Sun, Oct 17, 2010 at 6:59 AM, Tomasz Sterna <[email protected]> wrote: > Dnia 2010-10-16, sob o godzinie 12:35 +0200, Tomasz Sterna pisze: >> At the end of my .log I noticed the following lines: >> [ 465.418] config/udev: failed to bind the udev monitor >> [ 465.456] [config] failed to initialise udev >> >> Could this be the cause that the Xorg server does not detect any >> devices? >> This might be related to the fact we have Xorg server running as meego >> user not root, and it does not have permission to bind udev monitor. > > This is definitely the case. > When I start Xorg server as root my devices are detected and configured > correctly. > > Am I the first one to notice this bug? > How do other MeeGo ports detect the hardware? > Are you not using devices autodetection? > > > log snippet when running under root account: > [...] > [ 350.854] (II) config/udev: Adding input device synaptics_capsensor > (/dev/event1) > [ 350.862] (**) synaptics_capsensor: Applying InputClass "default" > [ 350.869] (**) synaptics_capsensor: Applying InputClass "Keyboard" > [ 350.875] (II) LoadModule: "evdev" > [ 350.886] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so > [ 350.902] (II) Module evdev: vendor="X.Org Foundation" > [ 350.909] compiled for 1.9.0, module version = 2.4.99 > [ 350.918] Module class: X.Org XInput Driver > [ 350.925] ABI class: X.Org XInput driver, version 11.0 > [ 350.931] (**) synaptics_capsensor: always reports core events > [...] > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
