virtualbox's udev rule overwrite nut rule about group owner

Bug #328057 reported by Skool182
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nut (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: nut

In Intrepid and Jaunty, nut packages provides a rule for udev to allow the nut group to use UPS USB devices.
This rules has the ident number 52.

If you want to install virtualbox-2.1 (from the virtualbox website), the package creates a rule to allow the vboxusers group to access all USB devices, this rules has the ident number 60 and overwrites the nut rules, and usbhid-ups driver don't want to start.

This problem is probably inexistant if you uses virtualbox-ose from the ubuntu repository because the udev rules seems to have the ident number 50.

This rule is very important for nut usage, and seems to have no effects to other programs, is it possible to specify an ident greater than 60 for this rule ?

Thanks

Revision history for this message
Andreas Olsson (andol) wrote :

What makes this a bug in the Ubuntu nut packages, instead of being a bug in the Virtualbox virtualbox-2.1 package?

Changed in nut:
status: New → Incomplete
Revision history for this message
Arnaud Quette (aquette) wrote : Re: [Bug 328057] [NEW] virtualbox's udev rule overwrite nut rule about group owner

side notes:
- I had a user report last week, and uncovered the above issue,
- a temporary solution is to either change the nut primary group to the
generic vboxusers (in /etc/passwd) or to move the nut rule to a number
greater than the vbox one. The former allows to use your UPS in/out vbox
while the latter will not allow the use of your UPS inside of vbox... up to
you
- in the long run, we (NUT) have to address a few USB related issues in NUT.
And we'll possibly have to use generic groups (
http://lists.alioth.debian.org/pipermail/nut-upsdev/2009-January/003762.html
)

thanks for your feedback,
Arnaud

Chuck Short (zulcss)
Changed in nut (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
Revision history for this message
Arnaud Quette (aquette) wrote :

This has been fixed where it should, Ie in VirtualBox.
The fix seems to be available since VirtualBox 4.0:
https://www.virtualbox.org/ticket/7759

Arnaud

Changed in nut (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.