package kismet 2013.03.R1b-3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück

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

Bug Description

Just running a normal install an the software breaks up during instalation

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: kismet 2013.03.R1b-3
ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
Uname: Linux 3.19.0-42-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.14.1-0ubuntu3.19
AptOrdering:
 kismet: Install
 kismet: Configure
Architecture: amd64
Date: Sun Dec 20 15:26:48 2015
DuplicateSignature: package:kismet:2013.03.R1b-3:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück
InstallationDate: Installed on 2015-12-18 (2 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt 1.0.1ubuntu2.10
SourcePackage: kismet
Title: package kismet 2013.03.R1b-3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 6 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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

You can see the problem in the end of DpkgTerminalLog.txt :

usermod: Benutzer »crash« ist nicht vorhanden.
dpkg: error processing kismet (--configure):
 subprocess installed post-installation script returned error exit status 6

You need to specify the user in a "space-separated" list, not a comma separated one.
Could you please purge the package:
  sudo apt-get purge kismet

and then install it again?

For the time being I'm marking it as a duplicate, since this issue has been already reported.

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.