package nut-client 2.7.1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1444944 reported by Andrea on 2015-04-16
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nut (Ubuntu)
High
Unassigned
Nominated for Utopic by Alberto Salvia Novella

Bug Description

This message always appears when I update the system

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nut-client 2.7.1-1ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.3
Architecture: amd64
Date: Thu Apr 16 12:44:19 2015
DuplicateSignature: package:nut-client:2.7.1-1ubuntu3:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-01-19 (86 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: nut
Title: package nut-client 2.7.1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Andrea (brentolax) wrote :
tags: removed: need-duplicate-check
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nut (Ubuntu):
status: New → Confirmed
Changed in nut (Ubuntu):
importance: Undecided → High
kaha (kaha) wrote :

Any news ?

I got the same problem.
With a working 14.10 configuration i got a error while using nut.
The client daemon seems to miss something.

When i try to start it i got :
Failed to start nut-client.service: Unit nut-client.service failed to load: No such file or directory.

And it was also the message apt-get give me when i try to reinstall the package.

The 2.7.1-1ubuntu4 package don't resolve the bug.

Allen Webb (vertago1-s) wrote :

I think the problem is a dangling symlink:
/etc/systemd/system/nut-client.service -> /lib/systemd/system/nut-monitor.service

You can try this, but it doesn't fix the underlying problem it it just makes it so the package scripts don't fail. I was able to remove nut-client by running this command before removing it:
sudo touch /lib/systemd/system/nut-monitor.service

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers