-
-
Notifications
You must be signed in to change notification settings - Fork 474
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Windows:
usbhid-upscrashes inlibusb_close()during process/service shutdownservice/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugStatus: Open.- Status: Open.#3623 In networkupstools/nut;
- Status: Open.#3622 In networkupstools/nut;
PyNUT GetUPSCommands() requests CMDDESC using Python's bytes representation
AIFor good or bad, machine tools are upon us. Humans are still the responsible ones.For good or bad, machine tools are upon us. Humans are still the responsible ones.Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possibleStatus: Open.- Status: Open.#3620 In networkupstools/nut;
PyNUT disconnect() leaves the socket open on a retained client
AIFor good or bad, machine tools are upon us. Humans are still the responsible ones.For good or bad, machine tools are upon us. Humans are still the responsible ones.Connection stability issuesIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over timeIssues about driver<->device and/or networked connections (upsd<->upsmon...) going AWOL over timeportabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possibleStatus: Open.- Status: Open.#3618 In networkupstools/nut;
Vertiv GXT5 (10af:1000) not in belkin-hid.c device table — most values missing or wrongly scaled
impacts-release-2.8.5Issues reported against NUT release 2.8.5 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.5 (maybe vanilla or with minor packaging tweaks)Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)Status: Open.Config file ownership prevents upsd (nut-server.service) starting on AlmaLinux 10
impacts-release-2.8.2Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)RedHat Linux ecosystemRHEL, CentOS, Fedora, Rocky Linux, Oracle Linux... (RPM packaging)RHEL, CentOS, Fedora, Rocky Linux, Oracle Linux... (RPM packaging)service/daemon start/stopGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugGeneral subject for starting and stopping NUT daemons (drivers, server, monitor); also BG/FG/DebugStatus: Open.#3612 In networkupstools/nut;Definitions of SET and INSTCMD Error Codes are Nonexistent, Contradictory, or Outdated
refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warningsStatus: Open.Refactor pragma usage in C/C++ code by using dedicated include files
Low-hanging fruitA proposal or issue that is good for newcomers to codebase or otherwise a quick winA proposal or issue that is good for newcomers to codebase or otherwise a quick winportabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possiblerefactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warningsStatus: Open.