nut-server fails if modemmanager is scanning serial ports

Bug #1176548 reported by Lupe Christoph on 2013-05-05

This bug report will be marked for expiration in 48 days if no further activity occurs. (find out why)

This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
nut (Ubuntu)

Bug Description

Similar to whatPaavo Leinonen reported in 031601ce2a49$20b2efe0$6218cfa0$ on the NUT mailing list. See also my mail in reply.

Ubuntu runs modemmanager as a native upstart service. nut-server ends up running in parallel (on my system, probably a matter of timing). When modemmanager scans the serial ports for modems, upsd is unable to open the port configured for an UPS. (It might be possible to exclude some ports from the scan, I didn't check because I have no modem it could configure, I just kicked the package.

Please convert nut-server to a native upstart service to be able to have it wait for modemmanager. (I hope upstart is clever enough to have a service wait for an optional package and let it proceed if not installed.)

Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

IMHO, a more robust approach would be to make sure that modemmanager is using locks, and having upsd wait a small amount of time for the lock before giving up (possibly as a configurable option).

This mechanism would work across all packages that contend for the serial ports, rather than for us to have to deal with every single possible conflict individually.

Changed in nut (Ubuntu):
importance: Undecided → Medium
summary: - nut-server collides with modemmanager
+ nut-server fails if modemmanager is scanning serial ports
Changed in nut (Ubuntu):
status: New → Triaged
Changed in nut (Ubuntu):
status: Triaged → Incomplete
Changed in modemmanager (Ubuntu):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers