About the crash when no label is specified: it seems actually that gfxboot core never runs menuconfig.init (the menu parsing function).
Running under Bochs, it appears that gfxboot core does its initialization (gfx_init_51 is run since the hello msg is displayed) and the VGA initialization too (the console get redrawn). But shortly thereafter, bochs reboots (maybe around gfx_init_59 when it looks at the stack?). In the logs: 00258214795i[BIOS ] Booting from 0000:7c00 Maybe gfxboot core returns somewhere when it realizes that label count (passed by gfxboot.com) is zero. About the gfxboot-theme-ubuntu patch: attached to this comment and test case description below. Testing Done: Installed pristine gfxboot-theme-ubuntu-0.8.1 bootlogo to Karmic alternate CD (isolinux/bootlogo). Patched isolinux.cfg: --- isolinux.cfg.orig 2009-08-10 00:05:48.000000000 +0000 +++ isolinux.cfg 2009-08-10 00:04:11.000000000 +0000 @@ -2,4 +2,4 @@ default vesamenu.c32 prompt 0 timeout 0 -gfxboot bootlogo +ui gfxboot.com bootlogo Copied usr/lib/syslinux/isolinux.bin and usr/lib/syslinux/gfxboot.com from https://launchpad.net/~pam-mouraf/+archive/ppa/+build/1132652/+files /syslinux-common_3.82+dfsg-1ubuntu1_all.deb to the CD isolinux directory. Packed the ISO with mkisofs -r -V 'Ubuntu 9.10 i386' -o karmic-alternate-i386-hacked.iso -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no- emul-boot -boot-load-size 4 -boot-info-table new_iso Booting karmic-alternate-i386-hacked.iso under Qemu makes it reboot. Adding 'label foo' in isolinux.cfg makes the UI appear but only one label (foo) is displayed. Patching menuconfig.inc with the attached patch makes the other labels appear. The keyboard is broken though (stack corruption due to either the confusion between the added labels and the stack presented by gfxboot.com or a bug that I introduced). ** Attachment added: "Add missing labels" http://launchpadlibrarian.net/30094070/menuconfig.inc.diff -- please upgrade syslinux from debian to 3.82 https://bugs.launchpad.net/bugs/270822 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
