kernel-packages team mailing list archive

[Konrad Zapałowicz <konrad.zapalowicz@xxxxxxxxxxxxx>]

This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.

** Changed in: bluez (Ubuntu)
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/658471

Title:
  udev fails to call hid2hci for Logitech USB Bluetooth adapter

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: udev

  This bug is related to Bug #444420, but I was told to file it as a new
  bug here.

  Here are the rules I have for Logitech USB Bluetooth dongles in
  /lib/udev/rules.d/70-hid2hci.rules:

  # Logitech devices
  KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[35e]", \
    RUN+="hid2hci --method=logitech-hid --devpath=%p"
  KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[4abc]|c71[34bc]", \
    RUN+="hid2hci --method=logitech-hid --devpath=%p"

  This is an upgrade from Lucid (on which hid2hci was called) to
  Maverick (at which point, hid2hci was no longer called).

  As seen in lsusb output, my adapter should have matched the second
  line:

  Bus 001 Device 006: ID 046d:c70c Logitech, Inc. BT Mini-Receiver (HID proxy mode)
  Bus 001 Device 005: ID 046d:c70b Logitech, Inc. BT Mini-Receiver (HID proxy mode)
  Bus 001 Device 003: ID 046d:0b02 Logitech, Inc. BT Mini-Receiver (HID proxy mode)

  I removed the KERNEL condition from the rules file:

  # Logitech devices
  ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[35e]", \
    RUN+="hid2hci --method=logitech-hid --devpath=%p"
  ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[4abc]|c71[34bc]", \
    RUN+="hid2hci --method=logitech-hid --devpath=%p"

  I restarted udev and re-inserted the adapter.  While everything seems
  to work correctly now, I am told that this is wrong because it could
  somehow overmatch something.

  Attached is the output of `udevadm monitor` when udev is running with
  the original Maverick 70-hid2hci.rules file and the adapter is
  inserted.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: udev 162-2
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Oct 11 11:16:01 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b8e395c0-dc79-4ec7-8100-3d7b33afb2e4 ro quiet splash
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: udev
  dmi.bios.date: 02/24/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D PREMIUM
  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.:bvr0703:bd02/24/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58DPREMIUM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/658471/+subscriptions