package brltty 5.3.1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brltty (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
This bug might be similar to #1533040, but I should note that this is Ubuntu Mate running on a Raspberry Pi 2 (Arm v7), so I don't know if the other bug is on the same CPU architecture or not. Feel free to mark it as a duplicate if true. I was attempting to upgrade to Ubuntu 16.04, and it appears as if I ran into some dependency errors. I'll see if I can get them sorted out with aptitude in the mean time. System is still stable and boots up fine, but I would imagine this will affect new installs until the dependency error is resolved.
Here is the error output;
sudo aptitude upgrade
The following partially installed packages will be configured:
brltty brltty-x11
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up brltty (5.3.1-1ubuntu3) ...
update-initramfs: deferring update (trigger activated)
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
That is where it stops. So far not even aptitude can fix this...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: brltty 5.3.1-1ubuntu3
Uname: Linux 4.1.13-v7+ armv7l
ApportVersion: 2.19.3-0ubuntu3
Architecture: armhf
Date: Thu Jan 21 13:41:50 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageV
dpkg 1.18.4ubuntu1
apt 1.1.10
SourcePackage: brltty
Title: package brltty 5.3.1-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Changed in brltty (Ubuntu): | |
importance: | Undecided → High |
Status changed to 'Confirmed' because the bug affects multiple users.