run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10

[ozymandias]

Ubuntu 9.04, Release 9.04

linux-image-2.6.28-13-generic:
  Installed: 2.6.28-13.44
  Candidate: 2.6.28-13.44
  Version table:
 *** 2.6.28-13.44 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status

On running update manager, the following files are downloaded but do not install:

E: linux-image-2.6.28-13-generic: subprocess post-installation script returned error exit status 10
E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty: dependency problems - leaving unconfigured
E: linux-image-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-generic: dependency problems - leaving unconfigured
E: linux-generic: dependency problems - leaving unconfigured

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 10
HibernationDevice: RESUME=UUID=a90270a2-355e-4237-9924-fd0aa77cdb9b
MachineType: Lenovo INVALID
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-13-generic 2.6.28-13.44
ProcCmdLine: root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux
Title: package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to install/upgrade: subprocess post-installation script returned error exit status 10

[Steffen Banhardt (steffenbanhardt)]

When I look at #386974, #386524, #391126 or #391164 there seems to be a problem with the menu.lst involved in this

[Steffen Banhardt (steffenbanhardt)]

Please post your menu.lst (which can be found at /boot/grub/menu.lst ), there seems to be a problem with this file for several users, reporting this bug.

[HeissFuss (heissfuss)]

#menu.lst
default 0

timeout 3

hiddenmenu

title Ubuntu 9.04, kernel 2.6.28-12-generic
root (hd0,0)
kernel /vmlinuz-2.6.28-12-generic root=/dev/mapper/pow-root ro quiet splash
initrd /initrd.img-2.6.28-12-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-12-generic (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.28-12-generic root=/dev/mapper/pow-root ro single
initrd /initrd.img-2.6.28-12-generic

title Ubuntu 9.04, kernel 2.6.28-11-generic
root (hd0,0)
kernel /vmlinuz-2.6.28-11-generic root=/dev/mapper/pow-root ro quiet splash
initrd /initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.28-11-generic root=/dev/mapper/pow-root ro single
initrd /initrd.img-2.6.28-11-generic

title Ubuntu 9.04, kernel 2.6.27-14-generic
root (hd0,0)
kernel /vmlinuz-2.6.27-14-generic root=/dev/mapper/pow-root ro quiet splash
initrd /initrd.img-2.6.27-14-generic
quiet

title Ubuntu 9.04, kernel 2.6.27-14-generic (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.27-14-generic root=/dev/mapper/pow-root ro single
initrd /initrd.img-2.6.27-14-generic

title Ubuntu 9.04, kernel 2.6.24-21-generic
root (hd0,0)
kernel /vmlinuz-2.6.24-21-generic root=/dev/mapper/pow-root ro quiet splash
initrd /initrd.img-2.6.24-21-generic
quiet

title Ubuntu 9.04, kernel 2.6.24-21-generic (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.24-21-generic root=/dev/mapper/pow-root ro single
initrd /initrd.img-2.6.24-21-generic

title Ubuntu 9.04, memtest86+
root (hd0,0)
kernel /memtest86+.bin
quiet

####

And here's relevant portions of my mtab if that helps:
/dev/mapper/pow-root / ext4 rw,noatime 0 0
udev /dev tmpfs rw,mode=0755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
/dev/sda1 /boot ext3 rw,noatime 0 0
/dev/mapper/pow-home /home ext4 rw,noatime 0 0
/dev/mapper/pow-var /var ext4 rw,noatime 0 0

[Chispa28 (mferrazuy)]

Here it is
title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 646f9a39-6f9a-4f2d-869b-db862964c360
kernel /boot/vmlinuz-2.6.28-11-generic
root=UUID=646f9a39-6f9a-4f2d-869b-db862964c360 ro quiet splash
usbserial.vendor=0x1c9e usbserial.product=0x6061
initrd /boot/initrd.img-2.6.28-11-generic
quiet

title Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid 646f9a39-6f9a-4f2d-869b-db862964c360
kernel /boot/vmlinuz-2.6.28-11-generic
root=UUID=646f9a39-6f9a-4f2d-869b-db862964c360 ro single
initrd /boot/initrd.img-2.6.28-11-generic

title Ubuntu 9.04, memtest86+
uuid 646f9a39-6f9a-4f2d-869b-db862964c360
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root

# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda1
title Microsoft Windows XP Professional
rootnoverify (hd0,0)
savedefault
makeactive
chainloader +1

2009/6/23 Steffen Banhardt <email address hidden>

> Please post your menu.lst (which can be found at /boot/grub/menu.lst ),
> there seems to be a problem with this file for several users, reporting
> this bug.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to
> install/upgrade: subprocess post-installation script returned error exit
> status 10
> https://bugs.launchpad.net/bugs/388923
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “linux” source package in Ubuntu: Incomplete
>
> Bug description:
> Ubuntu 9.04, Release 9.04
>
> linux-image-2.6.28-13-generic:
> Installed: 2.6.28-13.44
> Candidate: 2.6.28-13.44
> Version table:
> *** 2.6.28-13.44 0
> 500 http://us.archive.ubuntu.com jaunty-updates/main Packages
> 100 /var/lib/dpkg/status
>
> On running update manager, the following files are downloaded but do not
> install:
>
> E: linux-image-2.6.28-13-generic: subprocess post-installation script
> returned error exit status 10
> E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving
> unconfigured
> E: linux-restricted-modules-2.6.28-13-generic: dependency problems -
> leaving unconfigured
> E: linux-backports-modules-jaunty-generic: dependency problems - leaving
> unconfigured
> E: linux-backports-modules-jaunty: dependency problems - leaving
> unconfigured
> E: linux-image-generic: dependency problems - leaving unconfigured
> E: linux-restricted-modules-generic: dependency problems - leaving
> unconfigured
> E: linux-generic: dependency problems - leaving unconfigured
>
> ProblemType: Package
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ErrorMessage: subprocess post-installation script returned error exit
> status 10
> HibernationDevice: RESUME=UUID=a90270a2-355e-4237-9924-fd0aa77cdb9b
> MachineType: Lenovo INVALID
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-13-generic 2.6.28-13.44
> ProcCmdLine: root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro qui...

[B.B. Lauret (bblauret)]

When I ran update manager again, I chose to overwrite the menu.lst.
There seems to be no backup of the old one. Everything seems fine I believe.

Steffen Banhardt schreef:
> Please post your menu.lst (which can be found at /boot/grub/menu.lst ),
> there seems to be a problem with this file for several users, reporting
> this bug.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>

[Smot (smot-msn)]

Menu.lst (has been hand edited to include the new Linux kernel that came in the update package as the first entry in the list of choices.)

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=4e38dc89-4f28-4c0e-acd1-1d6f693e419d ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=()/ubuntu/disks

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot option...

[ozymandias (ozymandius)]

Here is my menu.lst:

gfxmenu /boot/grub/message.new

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0,
and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default
entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default
entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
color black/light-gray black/light-gray

#A splash image for the menu
splashimage=/boot/grub/splashimages/back1.xpm.gz

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive
editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=76220dad-3c11-49ff-87d6-da4190a1c0f3

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) ...

[ozymandias (ozymandius)]

Here is my menu.lst:

gfxmenu /boot/grub/message.new

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0,
and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default
entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default
entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
color black/light-gray black/light-gray

#A splash image for the menu
splashimage=/boot/grub/splashimages/back1.xpm.gz

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive
editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=76220dad-3c11-49ff-87d6-da4190a1c0f3

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) ...

[ozymandias (ozymandius)]

Here is my menu.lst as well:

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
color black/light-gray black/light-gray

#A splash image for the menu
splashimage=/boot/grub/splashimages/back1.xpm.gz

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
## password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=76220dad-3c11-49ff-87d6-da4190a1c0f3

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptio...

[Charlie (baka-animaster)]

Anyone has a working solution/workaround for this problem? It bugs me everytime I open the update manager.

[HeissFuss (heissfuss)]

I got around this by reinstalling the linux-image-2.6.28-13-generic .deb manually with dpkg. I noticed that some of the module dependencies it was complaining about were actually zero byte .ko files. After the manual reinstall, I reinstalled everything related to modules or image again with apt-get and everything seems to be working fine now.

[ozymandias (ozymandius)]

Hey. Could you describe the exact process (and commands) that you used? Did
you uninstall the linux-image-generic before reinstalling it? I had
previously tried this method using synaptic but it had not worked for me.
And I am a little unsure about using terminal commands, since I am afraid of
messing around with my install. Thanks a lot!

2009/6/26 HeissFuss <email address hidden>

> I got around this by reinstalling the linux-image-2.6.28-13-generic .deb
> manually with dpkg. I noticed that some of the module dependencies it
> was complaining about were actually zero byte .ko files. After the
> manual reinstall, I reinstalled everything related to modules or image
> again with apt-get and everything seems to be working fine now.
>
> --
> package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to
> install/upgrade: subprocess post-installation script returned error exit
> status 10
> https://bugs.launchpad.net/bugs/388923
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Ubuntu 9.04, Release 9.04
>
> linux-image-2.6.28-13-generic:
> Installed: 2.6.28-13.44
> Candidate: 2.6.28-13.44
> Version table:
> *** 2.6.28-13.44 0
> 500 http://us.archive.ubuntu.com jaunty-updates/main Packages
> 100 /var/lib/dpkg/status
>
> On running update manager, the following files are downloaded but do not
> install:
>
> E: linux-image-2.6.28-13-generic: subprocess post-installation script
> returned error exit status 10
> E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving
> unconfigured
> E: linux-restricted-modules-2.6.28-13-generic: dependency problems -
> leaving unconfigured
> E: linux-backports-modules-jaunty-generic: dependency problems - leaving
> unconfigured
> E: linux-backports-modules-jaunty: dependency problems - leaving
> unconfigured
> E: linux-image-generic: dependency problems - leaving unconfigured
> E: linux-restricted-modules-generic: dependency problems - leaving
> unconfigured
> E: linux-generic: dependency problems - leaving unconfigured
>
> ProblemType: Package
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ErrorMessage: subprocess post-installation script returned error exit
> status 10
> HibernationDevice: RESUME=UUID=a90270a2-355e-4237-9924-fd0aa77cdb9b
> MachineType: Lenovo INVALID
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-13-generic 2.6.28-13.44
> ProcCmdLine: root=UUID=76220dad-3c11-49ff-87d6-da4190a1c0f3 ro quiet splash
> ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
> SourcePackage: linux
> Title: package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to
> install/upgrade: subprocess post-installation script returned error exit
> status 10
>

--
"I shall die as my fathers died, and sleep as they sleep; even so.
For the glass of the years is brittle wherein we gaze for a span;
A little soul for a little bears up this corpse which is man.
So long I endure, no longer; and laugh not again, neither weep.
For there is no God found stronger than death; and death is a sleep."

[Matt Park (matthew-james-park)]

This is all related to having a nonstandard menu.lst file. I, for instance, have a windows dual boot and I don't want it to just overwrite my menu.lst every time the kernel updates. If you choose anything other than the overwrite option, it will crash. The fix at this point is not to reinstall the linux-image-generic or whatever you are talking about. Just edit the menu.lst manually or using the kgrubeditor to point grub to the new kernel. It works and only takes a minute.

so if your menu.lst looks like this:

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 646f9a39-6f9a-4f2d-869b-db862964c360
kernel /boot/vmlinuz-2.6.28-11-generic
root=UUID=646f9a39-6f9a-4f2d-869b-db862964c360 ro quiet splash
usbserial.vendor=0x1c9e usbserial.product=0x6061
initrd /boot/initrd.img-2.6.28-11-generic
quiet

just change all the 11s to 13s (or make a copy above it with all the 11s into 13s.)

title Ubuntu 9.04, kernel 2.6.28-13-generic
uuid 646f9a39-6f9a-4f2d-869b-db862964c360
kernel /boot/vmlinuz-2.6.28-13-generic
root=UUID=646f9a39-6f9a-4f2d-869b-db862964c360 ro quiet splash
usbserial.vendor=0x1c9e usbserial.product=0x6061
initrd /boot/initrd.img-2.6.28-13-generic
quiet

## Don't just copy and paste this or you will probably break your system JUST CHANGE THE 11s TO 13s.

[HeissFuss (heissfuss)]

My issue involved a dependency problem similar to the one in this bug:

E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty: dependency problems - leaving unconfigured
E: linux-image-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-generic: dependency problems - leaving unconfigured
E: linux-generic: dependency problems - leaving unconfigured

The solution for me was to manually install the linux-image-generic .deb package with dpkg, and then reinstall it with synaptic.

I suspect that the menu.lst issue with some of the bugs attached to this is not the same issue.

[ozymandias (ozymandius)]

I seem to be getting this error message:

User postinst hook script [/sbin/update-grub] exited with value 10

subprocess post-installation script returned error exit status 10

Does anyone know what exactly error exit status 10 means? And would a manual reinstall/editing of menu.lst work in this case?

[Matt Park (matthew-james-park)]

I'm starting to doubt that all of these should have been lumped together as dupes. Mine exited error status 3, not 10. In my case, everything seemed to install correctly, except the menu.lst was not regenerated with the new kernel information. The way you would check is to "ls -la /boot" (you may have to be root or admin user) and see if you have the new "initrd.img-2.6.28-13-generic" and "vmlinuz-2.6.28-13-generic". If so, you are good to edit the menu.lst (as above) with the new kernels and boot that way. If they're not there, then you would need to reinstall the new image. I'm not sure how one would go about doing that, I would think that you would be fine just waiting for the next kernel to come out and letting it auto install. I hope this helps.

[Charlie (baka-animaster)]

I have tried to change the menu.lst to point to the new kernel (from 2.6.28-12 to 2.6.28-13 in this case). When I tried to boot to the new kernel, I got a "kernel panic" error message and my machine was frozen.

The command "sudo ls -la /boot" gives me the following output:

-rw-r--r-- 1 root root 529118 2009-04-17 10:41 abi-2.6.28-11-generic
-rw-r--r-- 1 root root 528128 2009-05-02 04:34 abi-2.6.28-12-generic
-rw-r--r-- 1 root root 528128 2009-06-02 16:41 abi-2.6.28-13-generic
-rw-r--r-- 1 root root 96795 2009-04-17 10:41 config-2.6.28-11-generic
-rw-r--r-- 1 root root 96768 2009-05-02 04:34 config-2.6.28-12-generic
-rw-r--r-- 1 root root 96768 2009-06-02 16:41 config-2.6.28-13-generic
drwxr-xr-x 2 root root 4096 2009-06-29 09:39 grub
-rw-r--r-- 1 root root 7539528 2009-05-06 13:43 initrd.img-2.6.28-11-generic
-rw-r--r-- 1 root root 7549063 2009-05-19 02:17 initrd.img-2.6.28-12-generic
-rw-r--r-- 1 root root 128796 2009-03-28 00:15 memtest86+.bin
-rw-r--r-- 1 root root 1456232 2009-04-17 10:41 System.map-2.6.28-11-generic
-rw-r--r-- 1 root root 1449762 2009-05-02 04:34 System.map-2.6.28-12-generic
-rw-r--r-- 1 root root 1449762 2009-06-02 16:41 System.map-2.6.28-13-generic
-rw-r--r-- 1 root root 1074 2009-04-17 10:43 vmcoreinfo-2.6.28-11-generic
-rw-r--r-- 1 root root 1074 2009-05-02 04:36 vmcoreinfo-2.6.28-12-generic
-rw-r--r-- 1 root root 1074 2009-06-02 16:42 vmcoreinfo-2.6.28-13-generic
-rw-r--r-- 1 root root 3501776 2009-04-24 15:56 vmlinuz-2.6.28-11-generic
-rw-r--r-- 1 root root 3487792 2009-05-02 04:34 vmlinuz-2.6.28-12-generic
-rw-r--r-- 1 root root 3487792 2009-06-02 16:41 vmlinuz-2.6.28-13-generic

Any ideas on how to solve this problem?

[Kelly Harding (kelly-harding)]

My menu.lst

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=1072e213-6399-4173-885f-7d814797de76 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=16f251ec-64b3-4986-9a9c-4a7e65021c28

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts t...

[ops0603 (mike-perkins)]

Folks,

This problem can easily be resolved - and I have eliminated all the errors that previously appeared when attempting to apt-get update

Remove the other kernel versions - keep only the 2.6.28-13

It solved the problem immediately.

Cheers,
M.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Charlie
Sent: June-29-09 10:26 PM
To: <email address hidden>
Subject: [Bug 388923] Re: package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to install/upgrade: subprocess post-installation script returned error exit status 10

I have tried to change the menu.lst to point to the new kernel (from
2.6.28-12 to 2.6.28-13 in this case). When I tried to boot to the new
kernel, I got a "kernel panic" error message and my machine was frozen.

The command "sudo ls -la /boot" gives me the following output:

-rw-r--r-- 1 root root 529118 2009-04-17 10:41 abi-2.6.28-11-generic
-rw-r--r-- 1 root root 528128 2009-05-02 04:34 abi-2.6.28-12-generic
-rw-r--r-- 1 root root 528128 2009-06-02 16:41 abi-2.6.28-13-generic
-rw-r--r-- 1 root root 96795 2009-04-17 10:41 config-2.6.28-11-generic
-rw-r--r-- 1 root root 96768 2009-05-02 04:34 config-2.6.28-12-generic
-rw-r--r-- 1 root root 96768 2009-06-02 16:41 config-2.6.28-13-generic
drwxr-xr-x 2 root root 4096 2009-06-29 09:39 grub
-rw-r--r-- 1 root root 7539528 2009-05-06 13:43 initrd.img-2.6.28-11-generic
-rw-r--r-- 1 root root 7549063 2009-05-19 02:17 initrd.img-2.6.28-12-generic
-rw-r--r-- 1 root root 128796 2009-03-28 00:15 memtest86+.bin
-rw-r--r-- 1 root root 1456232 2009-04-17 10:41 System.map-2.6.28-11-generic
-rw-r--r-- 1 root root 1449762 2009-05-02 04:34 System.map-2.6.28-12-generic
-rw-r--r-- 1 root root 1449762 2009-06-02 16:41 System.map-2.6.28-13-generic
-rw-r--r-- 1 root root 1074 2009-04-17 10:43 vmcoreinfo-2.6.28-11-generic
-rw-r--r-- 1 root root 1074 2009-05-02 04:36 vmcoreinfo-2.6.28-12-generic
-rw-r--r-- 1 root root 1074 2009-06-02 16:42 vmcoreinfo-2.6.28-13-generic
-rw-r--r-- 1 root root 3501776 2009-04-24 15:56 vmlinuz-2.6.28-11-generic
-rw-r--r-- 1 root root 3487792 2009-05-02 04:34 vmlinuz-2.6.28-12-generic
-rw-r--r-- 1 root root 3487792 2009-06-02 16:41 vmlinuz-2.6.28-13-generic

Any ideas on how to solve this problem?

--
package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to install/upgrade: subprocess post-installation script returned error exit status 10
https://bugs.launchpad.net/bugs/388923
You received this bug notification because you are a direct subscriber
of the bug.

Status in �linux� package in Ubuntu: Incomplete

Bug description:
Ubuntu 9.04, Release 9.04

linux-image-2.6.28-13-generic:
  Installed: 2.6.28-13.44
  Candidate: 2.6.28-13.44
  Version table:
 *** 2.6.28-13.44 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status

On running update manager, the following files are downloaded but do not install:

E: linux-image-2.6.28-13-generic: subprocess post-installation script returned error exit status 10
E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-2.6.28-1...

[Matt Park (matthew-james-park)]

@Charlie, You are missing the initrd.img-2.6.28-13-generic. Do not just delete all the other kernels as suggested by ops0603 above or else you will be left without a working kernel.

So, in your case you need to reinstall the newer one like this.

su - #become the root user

apt-cache search kernel-image #this tells apt to find all the new kernels

apt-get install kernel-image-2.6.28-13 #installs the new kernel

That should be it unless you get additional errors. You will be able to edit your menu.lst with the new kernel info, if it doesn't happen automatically (it should)

[Vish (vish)]

Thank you for bringing this bug to our attention. Unfortunately a paper cut should be a small usability issue that affects many people and is quick and easy to fix. I'm afraid this bug can't be addressed as part of this project.

A paper cut is a minor usability annoyance that an average user would encounter on his/her first day of using a new installation of Ubuntu 9.10.

For further info about papercuts criteria , pls read > https://wiki.ubuntu.com/PaperCut

Don't worry though, This bug has been marked as "invalid" ONLY in the papercuts project.

[ops0603 (mike-perkins)]

Well @Matt, that's an interesting "hypothesis"...however it has *NO* effect whatsoever, as I don't have the initrd.img-2.6.28-13-generic installed at all on my image, and I have absolutely no problems, no errors, and the O/S is perfectly fine. Once I removed the other kernels as I originally posted, the "problem" went away, so I don't know what to tell you other than this...removing it does no harm.

I'll be happy to post an image capture of anything you would like to see as evidence to support my statement.

I'm not trying to be argumentative, just factual.

Just thought I would share this with you in case you as a point of interest.

Cheers,
M.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Matt Park
Sent: June-30-09 01:01 PM
To: <email address hidden>
Subject: [Bug 388923] Re: package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to install/upgrade: subprocess post-installation script returned error exit status 10

@Charlie, You are missing the initrd.img-2.6.28-13-generic. Do not just
delete all the other kernels as suggested by ops0603 above or else you
will be left without a working kernel.

So, in your case you need to reinstall the newer one like this.

su - #become the root user

apt-cache search kernel-image #this tells apt to find all the new
kernels

apt-get install kernel-image-2.6.28-13 #installs the new kernel

That should be it unless you get additional errors. You will be able to
edit your menu.lst with the new kernel info, if it doesn't happen
automatically (it should)

--
package linux-image-2.6.28-13-generic 2.6.28-13.44 failed to install/upgrade: subprocess post-installation script returned error exit status 10
https://bugs.launchpad.net/bugs/388923
You received this bug notification because you are a direct subscriber
of the bug.

Status in �linux� package in Ubuntu: Incomplete

Bug description:
Ubuntu 9.04, Release 9.04

linux-image-2.6.28-13-generic:
  Installed: 2.6.28-13.44
  Candidate: 2.6.28-13.44
  Version table:
 *** 2.6.28-13.44 0
        500 http://us.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status

On running update manager, the following files are downloaded but do not install:

E: linux-image-2.6.28-13-generic: subprocess post-installation script returned error exit status 10
E: linux-backports-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty-generic: dependency problems - leaving unconfigured
E: linux-backports-modules-jaunty: dependency problems - leaving unconfigured
E: linux-image-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-generic: dependency problems - leaving unconfigured
E: linux-generic: dependency problems - leaving unconfigured

ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 10
HibernationDevice: RESUME=UUID=a90270a2-355e-4237-9924-fd0aa77cdb9b
MachineType: Lenovo INVALID
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28...

[BerniePallek (bmatthiasp)]

FWIW, on my first reboot (after the failed update), kernel 2.6.28-13 was selected by GRUB, but during (and after) boot, my video drivers (fglrx) were obviously messed; my display was a conglomeration of uninitialized/scattered coloured pixels on a black background, including the mouse pointer, which was movable as a square "blob" if mostly black and white "static" (video white noise) pixels. I was able to see text-mode consoles okay (e.g. press CTRL-ALT-F1).

I rebooted, and selected my previous working kernel (2.6.28-11) from the runtime GRUB menu, which booted just fine (video okay), and I then edited menu.lst to select that kernel by default. I will leave it as such until an *explanation of the problem* appears (or I figure it out myself).

My menu.lst is fine; I understand how it works (including the automagical section, etc), and I confirmed that the changes made by the update process were okay (I compared them to a previous version; I keep old versions of important files like menu.lst and xorg.conf because I still don't trust machines to modify them competently).

Keep in mind that although my original bug report got folded into this one as a duplicate, it probably does differ at least a bit, insofar as my exit status code from the failures was different, and I'm running restricted video drivers (they were implicated in my report, but are not referenced in this one).

[Charlie (baka-animaster)]

@Matt
Thanks for your suggestion, but unfortunately it doesn't work.
When I tried the command "apt-cache search kernel-image", the output is: "comedi-source - Comedi kernel module source".
When I tried the command "apt-get install kernel-image-2.6.28-13", the output is: "E: Couldn't find package kernel-image-2.6.28-13".

Anyway when I tried "sudo apt-get dist-upgrade", I get the following error messages:

E: linux-image-2.6.28-13-generic: subprocess post-installation script returned error exit status 2
E: linux-restricted-modules-2.6.28-13-generic: dependency problems - leaving unconfigured
E: linux-image-generic: dependency problems - leaving unconfigured
E: linux-restricted-modules-generic: dependency problems - leaving unconfigured
E: linux-generic: dependency problems - leaving unconfigured

Any suggestion?

@ops0603
Thanks for your suggestion. I haven't tried to remove all the other kernels, but when I had tried to boot to the "2.6.28-13" kernel previously by modifying the menu.lst, and I got "kernel panic" error. I'm afraid if I remove the other kernels, I can no longet boot to Ubuntu. Any ideas?

Thank you.

[cosa (cosa78)]

Here's my menu.lst im still having problems with that

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=820ffbcb-2eab-4e7e-b6c2-a71cd02b1cb8 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=820ffbcb-2eab-4e7e-b6c2-a71cd02b1cb8

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should...

[®om (rom1v)]

Same problem for me, on Ubuntu Jaunty, only default repositories, fresh install, problem with the first upgrade (but I can still upgrade or install other programs) :

# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
7 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]? Y
Setting up linux-image-2.6.28-13-generic (2.6.28-13.45) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.28-13-generic
Running postinst hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.28-13-generic
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/nvidia-common
run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.28-13-generic.postinst line 1002.
dpkg: error processing linux-image-2.6.28-13-generic (--configure):
 subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-restricted-modules-2.6.28-13-generic:
 linux-restricted-modules-2.6.28-13-generic depends on linux-image-2.6.28-13-generic; however:
  Package linux-image-2.6.28-13-generic is not configured yet.
dpkg: error processing linux-restricted-modules-2.6.28-13-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-2.6.28-13-generic; however:
  Package linux-image-2.6.28-13-generic is not configured yet.
dpkg: error processing linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-restricted-modules-generic:
 linux-restricted-modules-generic depends on linux-restricted-modules-2.6.28-13-generic; however:
  Package linux-restricted-modules-2.6.28-13-generic is not configured yet.
dpkg: error processing linux-restricted-modules-generic (--configNo apport report written because the error message indicates its a followup error from a previous failure.
                          No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                                                    No apport report written because MaxReports is reached already
                                                 No apport report written because MaxReports is reached already
                                                                                                               ure):
 dependency problems - lea...

[®om (rom1v)]

(Maybe it's not the same problem, I opened a new bug 396230)

[David Rando (david-rando)]

this was resolved long ago, seems bad package at the moment only

[Matt Zimmerman (mdz)]

TRIAGERS: PLEASE READ https://wiki.ubuntu.com/KernelTeam/DebuggingUpdateErrors

There are many bugs marked as duplicates of this one, but there are several different problems underlying them.

Failures which involve errors from update-grub should be filed against the grub package.

dpkg --fsys-tarfile failing indicates a problem unpacking the .deb, e.g. full disk or I/O error

comment 27 shows the nvidia driver failing to compile:
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/nvidia-common
run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 10
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.28-13-generic.postinst line 1002.
dpkg: error processin

Refer to the document above for more tips on distinguishing different types of upgrade failures in the kernel package.

[Giorgio B. (spudhead85)]

This seems to be the same problem in these bugs:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/303795
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/292606 (Fix Released for Lucid)

On a fully-updated Karmic I had the same problem while installing a custom kernel compiled with make-kpkg.
Installing this package solved the problem:

http://linux.dell.com/dkms/permalink/dkms_2.1.1.2-0ubuntu1_all.deb

Hope this will help those who cannot upgrade to (still unstable) Lucid that uses the updated package.

[Doug Morse (dm-dougmorse)]

Hi,

I can't be completely sure, but I'm fairly certain this relates to a bug I reported, for which I have a SIMPLY, TEMPORARY WORKAROUND that MIGHT help folks effected by this bug. Note that I do NOT have a CUSTOM KERNEL and my workaround is for the stock Ubuntu 9.10 kernel.

Also, for those trying to fix the problem permanently, I have noted some findings that might be helpful.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/533970

Basically, the workaround is simply to temporarily remove all instances of nvidia-common from the /etc/kernel directory hierarchy to allow apt-get to finish the kernel update. It worked for me, and may work for others, but please proceed with caution and if others say that what I've done is a bad idea, then they probably know much better than I.

Hope this helps.

Cheers,
Doug

[Alberto Milone (albertomilone)]

Can you still reproduce the problem on Lucid after my last upload of nvidia-common?

[Jean-Baptiste Lallement (jibel)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
Thanks again!