just for some more info, I asked for clarification from cjwatson.
$ rmadison gfx-boot-theme-ubuntu
gfxboot-theme-ubuntu | 0.13.2 | precise | source, amd64, i386
gfxboot-theme-ubuntu | 0.13.3 | precise-updates | source, amd64, i386
gfxboot-theme-ubuntu | 0.16.1 | trusty | source, amd64, i386
gfxboot-theme-ubuntu | 0.18.0 | vivid | source, amd64, i386
gfxboot-theme-ubuntu | 0.18.0 | wily | source, amd64, i386
gfxboot-theme-ubuntu | 0.20.0 | xenial | source, amd64, i386
Even though gfx-boot-theme-ubuntu did nto change from vivid to wily where the regression occurred, cjwatson suggests that it still may be the cause of the issue as gfxboot-theme-ubuntu and syslinux are very tightly related.
just for some more info, I asked for clarification from cjwatson. theme-ubuntu theme-ubuntu | 0.13.2 | precise | source, amd64, i386 theme-ubuntu | 0.13.3 | precise-updates | source, amd64, i386 theme-ubuntu | 0.16.1 | trusty | source, amd64, i386 theme-ubuntu | 0.18.0 | vivid | source, amd64, i386 theme-ubuntu | 0.18.0 | wily | source, amd64, i386 theme-ubuntu | 0.20.0 | xenial | source, amd64, i386
$ rmadison gfx-boot-
gfxboot-
gfxboot-
gfxboot-
gfxboot-
gfxboot-
gfxboot-
Even though gfx-boot- theme-ubuntu did nto change from vivid to wily where the regression occurred, cjwatson suggests that it still may be the cause of the issue as gfxboot- theme-ubuntu and syslinux are very tightly related.