Red Hat Bugzilla – Bug 424811
liveinst stops with: No module named firstboot_module_window
Last modified: 2009-01-07 13:17:17 EST
Description of problem:
When starting liveinst on a livecd it stops after you accept that this is a
The graphical error:
An error occurred when attempting to load an installer interface component
className = KeyboardWindow
The output in a terminal:
FATAL: Module md not found.
/usr/sbin/liveinst: line 40: /usr/sbin/swapoff: No such file or
No volume groups found
Probing for video card: nVidia Corporation NV17 [GeForce4 MX 440]
11:01:55 Starting graphical installation...
No module named firstboot_module_window
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a livecd from current rawhide
2. boot the cd
3. start "liveinst" in a terminal
It seems that after the initial start of liveinst my keyboard layout was set
to german. The locale in the kickstart for the livecd was en_US.UTF-8. I
haven't manually set this.
I've grabbed anaconda-18.104.22.168-1 from koji and updated it on a running livecd.
This is due to the changes in system-config-keyboard. Chris -- I thought you
had a fix for this.
The used version of system-config-keyboard is 1.2.11-3.fc8
Created attachment 289803 [details]
Rework to support new firstboot module system
Attached is a new version of keyboard_gui.py which should work with the new
firstboot in rawhide. I've tested this briefly as a firstboot module and as a
stand-alone program, but I have not yet gotten a chance to test it with
anaconda due to no images today. More testing would be appreciated.
I've copied the file into a running livecd into the normal place and started
liveinst. The graphical error is the same, but in the terminal a new error is
cannot import name KeyboardWindow
If I start anaconda directly with "anaconda --method=livecd" I'm seeing the
keyboard selection. But when I select one and hit "next" the same error
svahl -- you also need a newer anaconda (.12)
But even with that, things don't quite work. Unfortunately both firstboot and
anaconda have a module named 'constants' and both are just (ab)using the python
path to get their modules available. Thus, you only get the anaconda constants
module and not the firstboot one.
Given that firstboot is providing an API, it probably makes sense to have it
available as the 'firstboot' module and then it'd be firstboot.constants and
things would be happy.
firstboot has been updated and rebuilt in order to provide a real python module.
This will require changing my new keyboard module above to not append
/usr/share/firstboot and also to import firstboot.whatever instead.
This should be fixed in today's rawhide.
(In reply to comment #8)
> This should be fixed in today's rawhide.
Fixed with system-config-keyboard-1.2.11-4.fc9 and anaconda-22.214.171.124-1.