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:~$
the pedals are not working right now
________________________________
From: Martin Pitt <email address hidden>
To: <email address hidden>
Sent: Tuesday, August 5, 2014 8:48 AM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04
> drwxrw-rw-+ 2 root root 140 Aug 5 08:02 by-id
> drwxrw-rw-+ 2 root root 160 Aug 5 08:02 by-path
Your setfacl damaged the permissions of these two directories, so I
can't see what /dev/input/by-id/usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-
event-joystick point to. But anyway:
crw-r--r--+ 1 root root 13, 0 Aug 5 08:03 js0
crw-rw-rw-+ 1 root root 13, 1 Aug 5 08:02 js1
These permissions look a bit odd, but everyone can read from these
joysticks, so it should be fine. Can you please remove your custom rule
(which is a gaping security hole), unplug/replug the joystick, and show
"ls -l /dev/input/js*"? You should still have read permissons on those,
so I don't think your rule and setfacl calls make any difference wrt.
the permissions.
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)
After a reboot and without my script I get:
michael@ michael- ubuntu: ~$ ls -l /dev/input/js* 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@
the pedals are not working right now
_______ _______ _______ _______ ____
From: Martin Pitt <email address hidden>
To: <email address hidden>
Sent: Tuesday, August 5, 2014 8:48 AM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04
> drwxrw-rw-+ 2 root root 140 Aug 5 08:02 by-id
> drwxrw-rw-+ 2 root root 160 Aug 5 08:02 by-path
Your setfacl damaged the permissions of these two directories, so I by-id/usb- CH_PRODUCTS_ CH_FLIGHT_ SIM_YOKE_ USB-
can't see what /dev/input/
event-joystick point to. But anyway:
crw-r--r--+ 1 root root 13, 0 Aug 5 08:03 js0
crw-rw-rw-+ 1 root root 13, 1 Aug 5 08:02 js1
These permissions look a bit odd, but everyone can read from these
joysticks, so it should be fine. Can you please remove your custom rule
(which is a gaping security hole), unplug/replug the joystick, and show
"ls -l /dev/input/js*"? You should still have read permissons on those,
so I don't think your rule and setfacl calls make any difference wrt.
the permissions.
-- /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:/