package wireshark-common 2.0.2+ga16e22e-1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128

[Ronildo Quadros]

System problem detected while removing wireshark from computer

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: wireshark-common 2.0.2+ga16e22e-1
ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
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)
RelatedPackageVersions:
 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)

[Balint Reczey (rbalint)]

Thank you for the report.

The postrm script could not remove the wireshark system group because it is not a system group:

https://launchpadlibrarian.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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package wireshark - 2.4.0-1

---------------
wireshark (2.4.0-1) unstable; urgency=medium

  * Use debconf messages instead of "echo" in postinst/postrm (LP: #1687344)
  * New upstream release
    - release notes:
      https://www.wireshark.org/docs/relnotes/wireshark-2.4.0.html
    - security fixes:
      - deeply nested DAAP data may cause stack exhaustion
        (uncontrolled recursion) in the dissect_daap_one_tag function
        (CVE-2017-9617) (Closes: #870174)
      - PROFINET IO data with a high recursion depth allows remote
        attackers to cause a denial of service (stack exhaustion)
        in the dissect_IODWriteReq function. (CVE-2017-9766)
        (Closes: #870175)
      - the DOCSIS dissector could go into an infinite loop (CVE-2017-11406)
        (Closes: #870172)
      - the MQ dissector could crash (CVE-2017-11407) (Closes: #870172)
      - the AMQP dissector could crash (CVE-2017-11408) (Closes: #870172)
      - the WBXML dissector could go into an infinite loop, triggered
        by packet injection or a malformed capture file (CVE-2017-11410)
        (Closes: #870180)
      - the openSAFETY dissector could crash or exhaust system memory
        (CVE-2017-11411) (Closes: #870179)
  * Update shared library package names to match new .so versions
  * Refresh patches
  * Drop workaround to use system's nghttp2 since upstream does not
    ship the embedded copy anymore
  * Add build-dependency on libparse-yapp-perl, liblz4-dev, libsnappy-dev,
    libspandsp-dev, libxml2-dev and lynx to enable new upstream features
  * Update PO files about debconf templates

 -- Balint Reczey <email address hidden> Sun, 06 Aug 2017 13:22:45 -0400