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

Bug #1613693 reported by Nandish Bhatt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kismet (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

some software install error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: kismet 2013.03.R1b-3build1
ProcVersionSignature: Ubuntu 4.4.0-35.54-generic 4.4.16
Uname: Linux 4.4.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Aug 16 17:52:47 2016
DuplicateSignature:
 package:kismet:2013.03.R1b-3build1
 Setting up kismet (2013.03.R1b-3build1) ...
 usermod: user 'NB' does not exist
 dpkg: error processing package kismet (--configure):
  subprocess installed post-installation script returned error exit status 6
ErrorMessage: subprocess installed post-installation script returned error exit status 6
InstallationDate: Installed on 2016-07-20 (26 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
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
Nandish Bhatt (yesh-kumar123) wrote :
Tyler Hicks (tyhicks)
information type: Private Security → Public
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in kismet (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Andrik (andrikos) wrote :

Hi,

If you see in the log there is this message:
user 'NB' 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.