|Subject:||Bug upgrading kismet with sudo|
I encounter bug when upgrading kismet with sudo, and my user account name is different from username. Found on Ubuntu 16.04.
1) Attempt to upgrade kismet:
sergey@Supermedia:~$ sudo apt-get upgrade kismet
[sudo] password for sergey:
Reading package lists... Done
Building dependency tree
Reading state information... Done
kismet is already the newest version (2013.03.R1b-3build1).
Calculating upgrade... Done
The following packages have been kept back:
liboxideqt-qmlplugin liboxideqtcore0 liboxideqtquick0 oxideqt-codecs snapd
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up kismet (2013.03.R1b-3build1) ...
usermod: user 'Sergey' does not exist <<<<<<<<<<<<<<<<<<< bug
dpkg: error processing package kismet (--configure):
subprocess installed post-installation script returned error exit status 6
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
It is trying to refer to user Sergey, but account username is sergey:
sergey@Supermedia:~$ grep sergey /etc/passwd
It appears you are using account name instead of account username, which is different.
This bug will happen if you will upgrade not from root, and your account username set different from account name.