package linux-generic 2.6.24.23.25 failed to install/upgrade: dependency problems - leaving unconfigured

Bug #311363 reported by JimBurton
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

$ uname -a
Linux daisy 2.6.22-15-generic #1 SMP Tue Jun 10 09:21:34 UTC 2008 i686 GNU/Linux
$ cat /proc/version_signature
Ubuntu 2.6.22-15.54-generic

ProblemType: Package
Architecture: i386
Date: Wed Dec 17 12:55:12 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: dependency problems - leaving unconfigured
Package: linux-generic 2.6.24.23.25
PackageArchitecture: i386
SourcePackage: linux-meta
Title: package linux-generic 2.6.24.23.25 failed to install/upgrade: dependency problems - leaving unconfigured
Uname: Linux 2.6.22-15-generic i686

Revision history for this message
JimBurton (jim-sdf-eu) wrote :
Revision history for this message
JimBurton (jim-sdf-eu) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

This is not a bug in the linux-meta package, moving to the linux package.

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Jim,

Can you comment if this is still an issue for you? I notice the following in your DpkgTerminalLog.gz file:

debconf: whiptail output the above errors, giving up!

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

dpkg: error processing linux-image-2.6.24-23-generic (--configure):

 subprocess post-installation script returned error exit status 255

dpkg: dependency problems prevent configuration of linux-ubuntu-modules-2.6.24-23-generic:

 linux-ubuntu-modules-2.6.24-23-generic depends on linux-image-2.6.24-23-generic; however:

  Package linux-image-2.6.24-23-generic is not configured yet.

dpkg: error processing linux-ubuntu-modules-2.6.24-23-generic (--configure):

 dependency problems - leaving unconfigured

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

 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!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.