package kismet 2013.03.R1b-3build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6

Bug #1632051 reported by JG
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kismet (Ubuntu)
New
Undecided
Unassigned

Bug Description

didn't install as a upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kismet 2013.03.R1b-3build1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Mon Oct 10 12:14:37 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 6
InstallationDate: Installed on 2016-08-23 (47 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: kismet
Title: package kismet 2013.03.R1b-3build1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 6
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
JG (1jg1) wrote :
Revision history for this message
Steve Beattie (sbeattie) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Steve Beattie (sbeattie) wrote :

Looks like it failed attempting to modify something for the user 'JG' which doesn't exist.

usermod: user 'JG' does not exist
dpkg: error processing package kismet (--configure):
 subprocess installed post-installation script returned error exit status 6

tags: removed: need-duplicate-check
Revision history for this message
Nick Andrik (andrikos) wrote :

Hi,

If you see in the log there is this message:
user 'JG' does not exist

Could you please specify a valid username when it requests for the users in the kismet group?
An easy solution is to uninstall and install kismet again.

This issue has been fixed in the newest version of kismet.
It is a duplicate of a previously reported bug and I'm marking it as such.
Please comment here if you need additional help

Kindest regards,
Nick

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.