package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30

[Stéphane Gourichon]

Installation of package was requested through Ubuntu driver selection GUI.

Installation of package was motivated by investigation of bug 1547077.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bbswitch-dkms 0.8-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
Uname: Linux 4.4.0-7-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Wed Mar 2 08:14:21 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 30
InstallationDate: Installed on 2016-02-03 (27 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.4
SourcePackage: bbswitch
Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
UpgradeStatus: No upgrade log present (probably fresh install)

[Stéphane Gourichon (stephane-gourichon-lpad)]

# Analysis: currently running kernel is actually purged

From message in DpkgTerminalLog.txt:

> WARNING: missing /lib/modules/4.4.0-7-generic

I notice that I'm running

uname -a

Linux n551jk 4.4.0-7-generic #22-Ubuntu SMP Thu Feb 18 20:50:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Which packages have been removed in between (several days ago).

# Summary

So, it looks like the problem is: installing nVidia driver seemed to fail because running kernel has its packages purged.

# Is it a suitable reason for failure?

If driver requires a reboot to work, its install script should target the kernel that will be booted, not the currently running kernel, right?

# Good practice?

I regularly do:

sudo apt-get update ; sudo aptitude upgrade

Is is okay or is that a cause of trouble?

Should I do something different?

Thank you for your attention.

[Launchpad Janitor (janitor)]

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