Description of problem: after upgrading a Mandriva Linux 2010.x to a Mageia alpha1 by network upgrade, on reboot, gfxmenu is still the MDV one: entries, background, ...) Version-Release number of selected component (if applicable): - mageia-gfxboot-theme-4.1.19.26-2.mga1.src.rpm - kernel-desktop-2.6.37.1-1.mga-1-1.mga1 How reproducible: Every time Steps to Reproduce: 1. Start from a Mandriva 2010.x 2. urpmi.removemedia -a 3. urpmi.addmedia --distrib http://you_mageia_mirror 4. urpmi --auto-update 5. reboot and see the gfxmenu Tip: 1. rpm -q --scripts mageia-gfxboot-theme 2. grub-gfxmenu --update-gfxmenu Now your gfxmenu is up to date Reproducible: Steps to Reproduce:
Priority: Normal => release_blockerComponent: Installation => RPM Packages
Weird... mageia-gfxboot-theme-4.1.19.26-2.mga1 does obsolete mandriva-gfxboot-theme (mageia-gfxboot-theme-4.1.19.26-*1*.mga1 didn't obsolete the mdv package, but 2mga definitely does...).
CC: (none) => dmorganec, tmbAssignee: bugsquad => ennael1
Can this be tested so that we can close bug ? At least next isos will have updated package
Still present with an network update from mdv 2010.2 to mageia [manu@localhost ~]$rpm -qa | grep gfxboot mageia-gfxboot-theme-4.1.19.26-2.mga1
CC: (none) => manuel
I think the problem of gfxboot post scriptlet not getting run comes from: %post if [ "$1" -gt 1 ]; then %_sbindir/grub-gfxmenu --update-gfxmenu fi $1 isn't greater than 1 , this is the first time the package is being installed. Now this exists in the mdv spec too, so the question is, what creates /boot/gfxmenu during a clean install? (I don't know much about the installer).
CC: (none) => stormi
This is fixed by adding a trigger the should run %_sbindir/grub-gfxmenu --update-gfxmenu when mandriva-gfxboot-theme is uninstalled, this is to workaround the package name change.
i tried an update mdv -> mga and now all is OK
Status: NEW => RESOLVEDResolution: (none) => FIXED
*** Bug 669 has been marked as a duplicate of this bug. ***
CC: (none) => mordbe0