Your message dated Fri, 17 Jul 2015 20:50:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#788856: joystick: jscal-store and jscal-restore can't 
find the product name or vendor anymore
has caused the Debian Bug report #788856,
regarding joystick: jscal-store and jscal-restore can't find the product name 
or vendor anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
788856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788856
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: joystick
Version: 1:1.4.8-1
Severity: important

Hello,

I used to be able to use jscal-store and jscal-restore normally a few months
ago (probably with kernel linux-image-3.16.0-4-amd64 version 3.16.7-ckt9-3),
but these programs don't work in a satisfactory way anymore:

# jscal-store /dev/input/js0
No product name or vendor available, calibration will be stored for the
given device name (js0) only!
# tail /var/lib/joystick/joystick.state

NAME="SAITEK CYBORG 3D USB"
VENDOR="06a3"
PRODUCT="0006"
jscal -u 
6,0,1,5,6,16,17,14,288,289,290,291,292,293,294,295,296,297,298,299,300,301
jscal -s 
6,1,0,90,101,9256113,9760991,1,0,87,94,9256113,8947575,1,1,75,93,10956215,8388352,1,1,87,87,7354172,7254791,1,0,0,0,-2147483648,536854528,1,0,0,0,-2147483648,536854528

DEVICE="js0"
jscal -u 
6,0,1,5,6,16,17,14,288,289,290,291,292,293,294,295,296,297,298,299,300,301
jscal -s 
6,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912
#

The paragraph starting with NAME="SAITEK CYBORG 3D USB" was already there; the
jscal-store call added the last paragraph, identified with DEVICE="js0", which
is not very reliable of course. The corresponding dmesg output is:

[    2.262075] usb 8-1.3: new low-speed USB device number 5 using ehci-pci
[    2.358626] usb 8-1.3: New USB device found, idVendor=06a3, idProduct=0006
[    2.358686] usb 8-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[    2.358756] usb 8-1.3: Product: CYBORG 3D USB
[    2.358804] usb 8-1.3: Manufacturer: SAITEK
[    2.364616] input: SAITEK CYBORG 3D USB as 
/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3/8-1.3:1.0/0003:06A3:0006.0002/input/input2
[    2.364938] hid-generic 0003:06A3:0006.0002: input,hidraw1: USB HID v1.00 
Joystick [SAITEK CYBORG 3D USB] on usb-0000:00:1a.7-1.3/input0

As expected, jscal-restore does not restore anything except when
/var/lib/joystick/joystick.state contains a paragraph identified with
DEVICE="js0" or similar, which by chance happens to correspond to the right
joystick (I checked this with 'jscal -p /dev/input/js0').

Thanks

-- Package-specific info:

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3/8-1.3:1.0/0003:06A3:0006.0002/input/input2/js0':
    KERNEL=="js0"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3/8-1.3:1.0/0003:06A3:0006.0002/input/input2':
    KERNELS=="input2"
    SUBSYSTEMS=="input"
    DRIVERS==""

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3/8-1.3:1.0/0003:06A3:0006.0002':
    KERNELS=="0003:06A3:0006.0002"
    SUBSYSTEMS=="hid"
    DRIVERS=="hid-generic"

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3/8-1.3:1.0':
    KERNELS=="8-1.3:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usbhid"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.3':
    KERNELS=="8-1.3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8/8-1':
    KERNELS=="8-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8':
    KERNELS=="usb8"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7':
    KERNELS=="0000:00:1a.7"
    SUBSYSTEMS=="pci"
    DRIVERS=="ehci-pci"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""


Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1/8-1.1.3/8-1.1.3:1.0/0003:0079:0006.0005/input/input9/js1':
    KERNEL=="js1"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1/8-1.1.3/8-1.1.3:1.0/0003:0079:0006.0005/input/input9':
    KERNELS=="input9"
    SUBSYSTEMS=="input"
    DRIVERS==""

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1/8-1.1.3/8-1.1.3:1.0/0003:0079:0006.0005':
    KERNELS=="0003:0079:0006.0005"
    SUBSYSTEMS=="hid"
    DRIVERS=="dragonrise"

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1/8-1.1.3/8-1.1.3:1.0':
    KERNELS=="8-1.1.3:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usbhid"

  looking at parent device 
'/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1/8-1.1.3':
    KERNELS=="8-1.1.3"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8/8-1/8-1.1':
    KERNELS=="8-1.1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8/8-1':
    KERNELS=="8-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7/usb8':
    KERNELS=="usb8"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"

  looking at parent device '/devices/pci0000:00/0000:00:1a.7':
    KERNELS=="0000:00:1a.7"
    SUBSYSTEMS=="pci"
    DRIVERS=="ehci-pci"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages joystick depends on:
ii  libc6            2.19-18
ii  libsdl1.2debian  1.2.15-11

Versions of packages joystick recommends:
ii  evtest       1:1.32-1
pn  inputattach  <none>

joystick suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Florent,

On Mon, 06 Jul 2015 12:50:30 +0200, Florent Rougon <[email protected]> wrote:
> Well, this problem seems to be sorted out now. Since the joystick
> package has received no update in the meantime, and I don't think I have
> upgraded the kernel after the last time I reproduced the bug, I suppose
> the fix may have been brought by a recent udev upgrade (221-1?).
> 
> From my POV, the bug may be closed.

Thanks for the update, I'm doing just that. (And sorry for the lack of
response before now!)

Regards,

Stephen

Attachment: pgplsUUUwPY2w.pgp
Description: OpenPGP digital signature


--- End Message ---

Reply via email to