mythbuntu-bugs team mailing list archive

["Timothy R. Chavez" <timothy.chavez@xxxxxxxxxxxxx>]

The bug task for the somerville project has been removed by an automated
script.  This bug has been cloned on that project and is available here:
https://bugs.launchpad.net/bugs/1306062

** No longer affects: somerville

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/188287

Title:
  dependencies installs -386 kernel which hangs on boot

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Fix Released
Status in “linux-restricted-modules-2.6.24” package in Ubuntu:
  Fix Released

Bug description:
  I'm not sure if this is the right place to "complain", but I upgraded
  my desktop to alpha4 and it installed the -386 flavor of the kernel
  for some reason. Since grub lists -386 as the first entry, it was
  booted by default and the computer hung while usplash was still
  visible.

  Anyway, I was wondering why I got the kernel in the first place?
  Jockey-common depends on restricted-modules, but AFAICT the order is
  correct (generic | 386). I have nvidia-glx-new installed which depends
  on nvidia-kernel-169.09, and searching for pacakges that provide it
  lists l-r-m-ver-386 as first, don't know if it matters or not.

  hope this report makes any sense.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/188287/+subscriptions