Timo, your fix, together with a manual setting on Dan's code did the
trick for me. Thanks.
--
/dev/event* produces no output for any devices
https://bugs.launchpad.net/bugs/324382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
don't use evdev; set 'Option "AutoAddDevices" "false"' in the
ServerFlags section.
--
/dev/event* produces no output for any devices
https://bugs.launchpad.net/bugs/324382
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Thanks for the quick reply. I see you set the bug to fix released
however jaunty is not yet released... what am I supposed to tell users
of the software that are having issues? Is it possible to backport the
fix for intrepid?
--
/dev/event* produces no output for any devices
https://bugs.launchpa
and is fixed in jaunty, needs xserver 1.6 & evdev 2.1.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New => Fix Released
--
/dev/event* produces no output for any devices
https://bugs.launchpad.net/bugs/324382
You received this bug notification because you are a member of Ubunt
This is due to the way that the evdev xorg driver works I think. You can
monitor them if you stop Xorg. Not sure if it is considered a bug though
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Sourcepackagename: linux-meta => xserver-xorg-input-evdev
--
/dev/event* produces no output for any d
