touch-packages team mailing list archive

[Bug Watch Updater <1332444@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=70734.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-10-21T20:13:58+00:00 Michal Navratil wrote:

Hello,
when a rudder pedals (e.g. 06a3:0763 Saitek PLC Pro Flight Rudder Pedals) are connected, the /dev/input/jsX and /dev/input/eventX are created. The problem is, that while jsX device has 644 permissions (enybody can read), the eventX device is available only to root, while any other joystick-like device receives ACLs for the current user.

If I'm not mistaken, the culprit is in the joystick detection heuristics
- it looks for some axes and buttons, while these devices have only
three axes.

Would it be possible to either extend the joystick detection heuristics
to handle such devices (CH products pedals reportedly behave the same)
or to create some exceptions for them, so these devices would work out
of the box?

Please let me know if you need any more informations.
Kind regards,

Michal Navratil

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/comments/0

------------------------------------------------------------------------
On 2014-03-05T08:44:28+00:00 Martin Pitt wrote:

Yes, we should certainly extend input_id's logic to also cover these
devices. Can you please find the eventX that belongs to that device, and
give me the output of

  udevadm info --name=input/eventX

Please copy the device path from the first output line ("P:"), and run
input id in debug mode:


  udevadm test-builtin input_id /devices/...

Finally, please run

  udevadm info --attribute-walk --name=input/eventX

and copy&paste the output here.

Thanks!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/comments/1

------------------------------------------------------------------------
On 2014-03-07T21:47:11+00:00 Michal Navratil wrote:

Created attachment 95318
Requested udev info on Saitek rudder pedals.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/comments/2

------------------------------------------------------------------------
On 2014-03-10T07:46:22+00:00 Martin Pitt wrote:

> # udevadm info --name=input/event12
> [...]
> E: ID_INPUT_JOYSTICK=1

Err, that's what we want to achieve.. I suppose you have some local udev
rule which attaches that property to the pedals, so that it works for
you?

> capabilities/ev raw kernel attribute: 9

That means it's capable of sending ABS and SYN events, not that
surprising.

> capabilities/abs raw kernel attribute: 23

== ABS_X, ABS_Y, ABS_RZ

I was hoping that the device would be capable of something distinct like
ABS_THROTTLE, ABS_RUDDER, ABS_WHEEL, ABS_GAS, or ABS_BRAKE. I'm afraid I
don't really know what ABS_RZ is supposed to mean, the official
documentation (https://www.kernel.org/doc/Documentation/input/event-
codes.txt) does not mention it and googling for it doesn't help much
either.

However, touch screens, touchpads, and accelerometers do *not* use all
these "fancy" axes, they really are quite unique to joysticks and
similar game controllers.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/comments/3

------------------------------------------------------------------------
On 2014-03-10T07:58:27+00:00 Martin Pitt wrote:

Fixed in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=2658624399 . If
you have a chance to test, I'd appreciate, but this ought to match at
least your device (and presumably a lot of similar devices).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/comments/4


** Changed in: systemd
       Status: Unknown => Fix Released

** Changed in: systemd
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1332444

Title:
  CH Pedals are not working in 14.04

Status in systemd:
  Fix Released
Status in “systemd” package in Ubuntu:
  Fix Committed

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)

  
  ------
  michael@michael-ubuntu:~$ lsb_release -rd
  Description:	Ubuntu 14.04 LTS
  Release:	14.04
  michael@michael-ubuntu:~$ 

  ----
  michael@michael-ubuntu:~$ apt-cache policy udev
  udev:
    Installed: 204-5ubuntu20.2
    Candidate: 204-5ubuntu20.2
    Version table:
   *** 204-5ubuntu20.2 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       204-5ubuntu20 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  michael@michael-ubuntu:~$ 

  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
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  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)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=2c43c000-7e14-4304-9dd6-e10fe2810f92 ro
  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.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd08/19/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1332444/+subscriptions