package wireshark-common 2.0.2+ga16e22e-1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wireshark (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
System problem detected while removing wireshark from computer
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wireshark-common 2.0.2+ga16e22e-1
ProcVersionSign
Uname: Linux 4.4.0-75-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
wireshark: Purge
wireshark-qt: Remove
wireshark-common: Purge
NULL: ConfigurePending
Architecture: amd64
Date: Sun Apr 30 22:40:54 2017
ErrorMessage: subprocess installed post-removal script returned error exit status 128
InstallationDate: Installed on 2014-08-07 (998 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageV
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: wireshark
Title: package wireshark-common 2.0.2+ga16e22e-1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2016-07-31 (273 days ago)
CVE References
tags: | removed: need-duplicate-check |
Thank you for the report.
The postrm script could not remove the wireshark system group because it is not a system group:
https:/ /launchpadlibra rian.net/ 317773706/ DpkgTerminalLog .txt :
Removing wireshark-common (2.0.2+ga16e22e-1) ...
Purging configuration files for wireshark-common (2.0.2+ga16e22e-1) ...
Removing wireshark group...
The group `wireshark' is not a system group. Exiting.
Could not remove wireshark group.
dpkg: error processing package wireshark-common (--purge):
subprocess installed post-removal script returned error exit status 128
Most likely the group has been created manually and not by the wireshark-common's postinst.
Please remove the wireshark group manually using:
sudo delgroup wireshark
The root cause of failure in postinst is using "echo" instead of a debconf note and the fix will correct this.