Created attachment 472880 [details] /tmp/anaconda.log Description of problem: Version-Release number of selected component (if applicable): anaconda-15.14 How reproducible: every time Steps to Reproduce: 1. Compose install DVD for x86_64 from Fedora 15 rawhide of 2011-01-11, using pungi+lorax. 2. Boot DVD for Install. 3. Accept defaults (Basic storage devices), try to Next from timezone dialog. Actual results: installation aborts with message on VT1: ERROR:lib/modules.c:214:lu_modules_load:assertion failed: (module != NULL) Expected results: successful install Additional info:
Created attachment 472881 [details] /tmp/syslog
Created attachment 472883 [details] output from /sbin/lsmod
Created attachment 473130 [details] strace.out.gz (about 1MB) strace output from attaching to anaconda process as soon as VT2 is available at appearance of first graphical dialog: strace -p 714 -f -o "|gzip -c >/tmp/strace.out.gz" & Looking at all the ENOENT errors might be interesting: are some files missing inadvertently?
Haven't looked into this much, but seems to be an Anaconda bug. Why is it assigned to me, out of interest? Jon.
Because at first glance, it sounded module related to me. Anyway, looks like lorax simply isn't including some file that the buildinstall procedure was.
If it turns out that lorax forgot something, then that should be fixed. After that, send this bug _back_ to anaconda because it's a Usability error. If a file is missing then the message should say "Missing file" and give the name of the file, or at least its *specific* characterization. Error messages should give enough info to fix the underlying condition, not just say, "Bang! You're dead."
Created attachment 473383 [details] strace.out.gz (about 1MB) Same error occurs when DVD is built by pungi+buildinstall. Here's the strace of anaconda.
Changing Component back to anaconda.
There's no way we can possibly raise a "missing file" dialog - this is some module (who knows what) attempting to be loaded by some program (again, who knows what) that is being used by anaconda very indirectly. In short, we don't know what file's missing and we aren't even responsible for loading it. It's not just a simple matter of slapping some dialogs around like you seem to think it is.
So, I tried installing a compose made with buildinstall and this happens there too. So something must have changed a while ago, because it was working just fine before, and our buildinstall/lorax scripts were not updated to that change.
Ok, so I tried narrowing down, when this happened. The compose from Jan 11th works, and the compose from Jan 12th doesn't. I also found out that the lu_modules_load function is a libuser function. So Miroslav, could you help me identify what that libuser wants from us?
One note, this happens, when we're trying to show the Set root password page, so that points to libuser too.
If we don't have the libuser.mo in locales, can this cause this assertion fail?
Hitting this too with both buildinstall and lorax. This sucks.
From a first look, this is likely to be a bug in libuser. A possible temporary workaround is to create /mnt/sysimage/etc/shadow before initializing libuser (.i.e. switching to the "change password" page): this should fix this particular problem, but if anaconda assumes that libuser doesn't manage etc shadow, it can also cause other problems.
Should be fixed in libuser-0.57.1-1.fc15 .