Public bug reported:
Binary package hint: linux-restricted-modules-2.6.17-11-generic
An aptitude update some days ago, broke. I can still upgrade other packages,
but have no idea about the state of the kernel now:
$ sudo aptitude upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Setting up linux-restricted-modules-2.6.17-11-generic (2.6.17.7-11.2) ...
ld_static: core/*: No such file: Not a directory
Bus error (core dumped)
dpkg: error processing linux-restricted-modules-2.6.17-11-generic (--configure):
subprocess post-installation script returned error exit status 135
Errors were encountered while processing:
linux-restricted-modules-2.6.17-11-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up linux-restricted-modules-2.6.17-11-generic (2.6.17.7-11.2) ...
ld_static: core/*: No such file: Not a directory
Bus error (core dumped)
dpkg: error processing linux-restricted-modules-2.6.17-11-generic (--configure):
subprocess post-installation script returned error exit status 135
Errors were encountered while processing:
linux-restricted-modules-2.6.17-11-generic
** Affects: linux-restricted-modules-2.6.17 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Packages fails to install on amd64
https://launchpad.net/bugs/90081
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
