On Thu, 2009-07-16 at 22:58 +0000, Mark Richardson wrote: > Probably - possibly - For me it was from when I did the Jaunty > alpha / beta upgrade process from Hardy when the kernel was updated. > Ah! You shouldn't do that. You should upgrade via Intrepid first ;-)
> i.e. the upgrade failed when applying the kernel upgrade. a new > apt-get update / upgrade would produce the same error. Would have to > choose the old kernel for x to work / or use the correct resolution > display. (Using a Sun Ultra 24 with Nvidia card so I use the nvidia > binary driver). > > Looking back I would assume it was an issue applying the nvidia biinary > driver into the new kernel (?) > Almost certainly. > This went on for several minor kernel revisions - eventually - it > came right and upgraded correctly. It was fine just using the older > kernel during that time. > > Any more info required let me know. > I think we've fixed this in a way that it can't happen again, obviously if it does, please do file a new report. Scott -- Scott James Remnant [email protected] -- modinfo crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/362208 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
