Wobbly pic here: https://dl.dropboxusercontent.com/u/4147101/mga3final/2013-05-16_21-39-16.jpg Noticed on first reboot and also subsequent reboot. I'll attach some logs Reproducible: Steps to Reproduce:
Created attachment 3984 [details] journal.xz
Created attachment 3985 [details] syslog.xz
report.bug.gz https://dl.dropboxusercontent.com/u/4147101/mga3final/report.bug.gz
Created attachment 3986 [details] boot.log
Less wobbly pic: https://dl.dropboxusercontent.com/u/4147101/mga3final/2013-05-16_22-10-30.jpg
CC: (none) => ennael1
Confirmed after uprgrade of an x86_64 system. dkms shows ... [ 18.186968] <3>[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize fail. [ 18.188784] <3>[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize fail
CC: (none) => davidwhodgins
Fixed by running "dracut -f", so it's another case of dracut last being run before things it uses are updated.
*sigh*. Yeah, this is why I think we really cannot support doing this kind of thing long term. I guess we could add a hack to mgaapplet-upgrade helper to offer to regenerate initrds at the end, but this only helps mgaonline users. I still maintain that we want some kind of infrastructure in urpmi, but, to be honest, this probably wouldn't play nicely with packagekit in the future anyway. So hack in mgaaplet-upgrade-helper and it should just be "general advice" for people doing urpmi is the only suggestion I can make here. I won't be able to look at this until Sunday tho'.
Very simple to fix. Like for other low level stuff (lvm2 ...), just make the kernel either requires a new enough version or conflicts with too old plymouth in order to ensure it got updated first. Here we want a conflict tags
CC: (none) => thierry.vignaud, tmbHardware: i586 => AllSummary: After mgaonline upgrade plymouth fails during boot => After mgaonline upgrade plymouth fails during boot (add conflicts on too old plymouth)Source RPM: plymouth? => kernel
CC: (none) => dglent
This is still valid with an upgrade mga2 to 3 today.
(In reply to claire robinson from comment #10) > This is still valid with an upgrade mga2 to 3 today. That was almost 1½ yrs ago, assuming ti got fixed for later releases. Please reopen if that's not the case
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => FIXED