michael@michael-ubuntu:~$ ls -l /dev/input/js*
crw-r--r-- 1 root root 13, 0 Aug 5 09:44 /dev/input/js0
crw-rw-r--+ 1 root root 13, 1 Aug 5 09:44 /dev/input/js1
michael@michael-ubuntu:~$ sudo synaptic
[sudo] password for michael:
michael@michael-ubuntu:~$ evtest
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event14: CH PRODUCTS CH FLIGHT SIM YOKE USB
Select the device event number [0-18]: ^C
michael@michael-ubuntu:~$
________________________________
From: Martin Pitt <email address hidden>
To: <email address hidden>
Sent: Tuesday, August 5, 2014 8:51 AM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04
Sorry, the setfacl call is a gaping security hole, not your custom rule.
But /lib/udev/rules.d/50-udev-default.rules already gives world-read
permissions on joysticks, so neither is required in the first place.
To find out more, it would also be good if you could install the
"evtest" program, run "evtest" (as user), select your Rudder Pedals, and
see if you get any events. Or copy&paste the complete output of the
program if it doesn't work. Thanks!
Bug description:
I've created a rule in lib/udev/rules.d as 99-xplane.rules:
# CH PRO PEDALS USB
KERNEL=="event*", ATTRS{idProduct}=="00f2", ATTRS{idVendor}=="068e", MODE="0666"
and even do at every x-plane start:
cd /dev/input
sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *
but still my CH Pedals are often not working. (sometimes yes but not
always)
no pedals:
michael@ michael- ubuntu: ~$ ls -l /dev/input/js* michael- ubuntu: ~$ sudo synaptic michael- ubuntu: ~$ evtest michael- ubuntu: ~$
crw-r--r-- 1 root root 13, 0 Aug 5 09:44 /dev/input/js0
crw-rw-r--+ 1 root root 13, 1 Aug 5 09:44 /dev/input/js1
michael@
[sudo] password for michael:
michael@
No device specified, trying to scan all of /dev/input/event*
Not running as root, no devices may be available.
Available devices:
/dev/input/event14: CH PRODUCTS CH FLIGHT SIM YOKE USB
Select the device event number [0-18]: ^C
michael@
_______ _______ _______ _______ ____
From: Martin Pitt <email address hidden>
To: <email address hidden>
Sent: Tuesday, August 5, 2014 8:51 AM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04
Sorry, the setfacl call is a gaping security hole, not your custom rule. rules.d/ 50-udev- default. rules already gives world-read
But /lib/udev/
permissions on joysticks, so neither is required in the first place.
To find out more, it would also be good if you could install the
"evtest" program, run "evtest" (as user), select your Rudder Pedals, and
see if you get any events. Or copy&paste the complete output of the
program if it doesn't work. Thanks!
-- /bugs.launchpad .net/bugs/ 1332444
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
CH Pedals are not working in 14.04
Status in “systemd” package in Ubuntu:
Incomplete
Bug description: }=="00f2" , ATTRS{idVendor} =="068e" , MODE="0666"
I've created a rule in lib/udev/rules.d as 99-xplane.rules:
# CH PRO PEDALS USB
KERNEL=="event*", ATTRS{idProduct
and even do at every x-plane start:
cd /dev/input
sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *
but still my CH Pedals are often not working. (sometimes yes but not
always)
------ michael- ubuntu: ~$ lsb_release -rd michael- ubuntu: ~$
michael@
Description: Ubuntu 14.04 LTS
Release: 14.04
michael@
---- michael- ubuntu: ~$ apt-cache policy udev ch.archive. ubuntu. com/ubuntu/ trusty-updates/main amd64 Packages dpkg/status
204-5ubuntu20 0 ch.archive. ubuntu. com/ubuntu/ trusty/main amd64 Packages michael- ubuntu: ~$
michael@
udev:
Installed: 204-5ubuntu20.2
Candidate: 204-5ubuntu20.2
Version table:
*** 204-5ubuntu20.2 0
500 http://
100 /var/lib/
500 http://
michael@
I expect my CH pedals to work out of the box like on Windows.
But even with the above they only work sometimes.-
ProblemType: Bug gnature: Ubuntu 3.13.0- 29.53-generic 3.13.11.2 Modules: nvidia edia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Line: BOOT_IMAGE= /boot/vmlinuz- 3.13.0- 29-generic. efi.signed root=UUID= 2c43c000- 7e14-4304- 9dd6-e10fe2810f 92 ro asset.tag: To be filled by O.E.M. version: Rev 1.xx asset.tag: Asset-1234567890 vendor: Chassis Manufacture version: Chassis Version MegatrendsInc. :bvr1405: bd08/19/ 2013:svnASUS: pnAllSeries: pvrSystemVersio n:rvnASUSTeKCOM PUTERINC. :rnZ87- PRO:rvrRev1. xx:cvnChassisMa nufacture: ct3:cvrChassisV ersion: version: System Version
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.2
ProcVersionSi
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernel
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jun 20 09:46:31 2014
InstallationDate: Installed on 2014-04-19 (61 days ago)
InstallationM
MachineType: ASUS All Series
ProcKernelCmd
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1405
dmi.board.
dmi.board.name: Z87-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: All Series
dmi.product.
dmi.sys.vendor: ASUS
To manage notifications about this bug go to: /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1332444/ +subscriptions
https:/