group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1540008@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package nut - 2.7.4-5ubuntu4

---------------
nut (2.7.4-5ubuntu4) artful; urgency=medium

  * d/p/fix-snmp-driver-compile-options.patch: fix cflags/ldflags
    mismatch (LP: #1711092).
  * d/libnutclient0.symbols: fix symbols in regard to gcc-7 (LP: #1711091).

 -- Christian Ehrhardt <christian.ehrhardt@xxxxxxxxxxxxx>  Wed, 16 Aug
2017 12:44:26 +0200

** Changed in: nut (Ubuntu)
       Status: Triaged => Fix Released

-- 
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/1540008

Title:
  USB permissions not set at install time (udevd name changed?)

Status in nut package in Ubuntu:
  Fix Released
Status in nut source package in Trusty:
  Confirmed
Status in nut source package in Xenial:
  Triaged
Status in nut source package in Yakkety:
  Triaged
Status in nut source package in Zesty:
  Triaged
Status in nut package in Debian:
  New

Bug description:
  1) $ lsb_release -rd
  Description:	Ubuntu 14.04.3 LTS
  Release:	14.04

  2) nut-server: 2.7.1-1ubuntu1; udev: 204-5ubuntu20.15

  3) On a fresh install of Ubuntu 14.04 (amd64), I installed the nut-
  server package while the UPS was already connected via USB. After
  installation, the permissions described by /lib/udev/rules.d/52-nut-
  usbups.rules should have changed the group of the corresponding
  /dev/bus/usb/*/* node to 'nut'.

  4) The owner/group for the /dev/bus/usb node remained root:root.
  Manually running 'udevadm trigger --subsystem-match=usb
  --action=change' changed the group to 'nut'. (From past experience
  tracking down related udev+nut bugs, unplugging and re-plugging the
  USB cable would yield similar results.)

  However, that udevadm command is included in the postinst for nut-
  server, and it is guarded with a pidof check for 'udevd':

  # ask udev to check for new udev rules
  [ -x /etc/init.d/udev ] && pidof udevd > /dev/null \
        && udevadm trigger --subsystem-match=usb --action=change

  This most likely needs to be amended to include the current process
  name, 'systemd-udevd'. I checked the control files, and unless the
  udevd process name has changed back, I believe this will affect vivid,
  wily and xenial as well as trusty. (I will let someone else add those
  later tags if that turns out to be the case.)

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