group.of.nepali.translators team mailing list archive

[Simon Déziel <1099947@xxxxxxxxxxxxxxxxxx>]

Hi Christian,

Even on Trusty (*without* the -proposed package) I'm unable to repro the
original issue:

# tail -n 5 /etc/nut/ups.conf
[cyberpower]
        driver = usbhid-ups
        port = auto
        desc = "CyberPower CP685AVR-G"
        vendorid = 0764

# lsusb | grep Cyber
Bus 004 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

# ll /dev/bus/usb/004/002
crw-rw-r-- 1 root nut 189, 385 Aug 25 18:01 /dev/bus/usb/004/002

# find /lib/udev/rules.d/ -name '*nut*'
/lib/udev/rules.d/52-nut-usbups.rules

I will thus mark the Trusty task as invalid as well.

** Changed in: nut (Ubuntu Trusty)
       Status: Fix Committed => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1099947

Title:
  driver unable to connect to CyberPower UPS using usbhid-ups driver

Status in nut package in Ubuntu:
  Fix Released
Status in nut source package in Trusty:
  Invalid
Status in nut source package in Xenial:
  Invalid
Status in nut package in Debian:
  Fix Released
Status in nut package in Fedora:
  Unknown

Bug description:
  [Impact]

   * Plugging in a USB controlled UPS solution does fail to execute the udev 
     rules; Due to that the permissions are not set correctly

   * Fix is a backport from upstream which only changes the numbering on the 
     rule to execute at the right time.

  [Test Case]

   * Install nut-server
   * Plug in a usb controlled UPS of your choice
   * The device node created should be mode 664 and group "nut", but it is 
     not.
   * Install the proposed package
   * (It also fixes but 1540008, so no need to replug anymore to test if 
      successful)
   * it should now be created with proper permissions.

  [Regression Potential]

   * If people with the old set up have created something that would not be 
     able to access anymore that could cuase issues, but before it was 
     root:root and now nut:root; the group permission didn't change (was 6 
     before) - so anything before could only access with root and they still 
     can - therefore I consider this of low/no risk, yet in some obscure 
     setups it might be one.

  [Other Info]
   
   * n/a

  ---

  
  I hooked my new CyberPower UPS: CP685AVR-G on my Lucid server and got this error:

    Jan 15 12:06:33 xeon upsd[5441]: Can't connect to UPS [cyberpower] (usbhid-ups-cyberpower): No such file or directory
    Jan 15 12:06:38 xeon upsmon[5445]: Poll UPS [cyberpower@127.0.0.1] failed - Driver not connected

  After trying many things, I found
  https://bugzilla.redhat.com/show_bug.cgi?id=488368 that hint me in the
  right direction. The required change was to rename the udev rule like
  this:

    mv /lib/udev/rules.d/{5,6}2-nut-usbups.rules

  Now, everything works well, without requiring "user = root" in
  /etc/nut/ups.conf because the udev rule now ensures the device file is
  owned by the group "nut":

    # find /dev/bus/usb/ -ls
    1536    0 drwxr-xr-x  10 root     root          200 Jan 15 12:40 /dev/bus/usb/
    1579    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/008
    1580    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/008/001
    1573    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/007
    1574    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/007/001
    1567    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/006
    1568    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/006/001
    1561    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/005
    1562    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/005/001
    1555    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/004
    1556    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/004/001
    1549    0 drwxr-xr-x   2 root     root           80 Jan 15 12:40 /dev/bus/usb/003
    2163    0 crw-rw-r--   1 root     nut               Jan 15 12:49 /dev/bus/usb/003/002
    1550    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/003/001
    1543    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/002
    1544    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/002/001
    1537    0 drwxr-xr-x   2 root     root           60 Jan 15 12:40 /dev/bus/usb/001
    1538    0 crw-rw-r--   1 root     root              Jan 15 12:41 /dev/bus/usb/001/001

  Generic information:

  # lsb_release -rd
  Description:	Ubuntu 10.04.4 LTS
  Release:	10.04

  # apt-cache policy nut
  nut:
    Installed: 2.4.3-1ubuntu3.2
    Candidate: 2.4.3-1ubuntu3.2
    Version table:
   *** 2.4.3-1ubuntu3.2 0
          500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          500 http://archive.ubuntu.com/ubuntu/ lucid-security/main Packages
          100 /var/lib/dpkg/status
       2.4.3-1ubuntu3 0
          500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nut 2.4.3-1ubuntu3.2
  ProcVersionSignature: Ubuntu 2.6.32-45.102-server 2.6.32.60+drm33.26
  Uname: Linux 2.6.32-45-server x86_64
  Architecture: amd64
  Date: Tue Jan 15 12:43:46 2013
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: nut

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