Bugzilla – Bug 445402
Default boot entry uses failsafe boot settings
Last modified: 2008-11-16 17:03:06 UTC
I have installed openSUSE-11.1-Beta5-DVD-i586.iso on my Toshiba A300-12H. During the yast2 setup I selected the german keyboard layout. But after the installation and the first start of kde3 the system used the us keyboard layout. The yast2 setuptool for the keyboard layout displayed the german keyboard layout in use for the system. But with some keypress to to input test field it was clear the us keyboard layout was actual active. I had to reapply the settings to change the keyboard layout to german.
Created attachment 252454 [details] y2logs
Where did you reapply settings? Do you have also wrong keyboard setting on console/in other window manager?
If I switch to a virtual console with key CTRL-ALT-1 I have the right german keyboard setting. If a window manager is activ (gnome, KDE3 or KDE4) and I open a terminal console or start a gnome/kde program the us keyboard setting is activ. There is a yast tool 'Keyboard Layout' in the hardware section to directly set up the keyboard setting. After start of this tool it displays the following keyboard properties: Type: Microsoft Natural Keyboard Pro / Microsoft Interne... Layout: Germany Variant: nodeadkeys If I make keyboard entries to the test input field the us keyboard settings are still activ. If I repick the layout option Germany the german keyboard setting is activ. After restart of window manager or computer there is the wrong keyboard setting back again.
Doesn't sound kde-specific.
Please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log.
Created attachment 252495 [details] /etc/X11/xorg.conf
Created attachment 252496 [details] /var/log/Xorg.0.log
xorg.conf: [...] Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "de" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" Option "XkbVariant" "nodeadkeys" EndSection [...] Everything fine here. > (==) Using config file: "/etc/X11/xorg.conf.install" You're using the failsafe boot option, which means you'll get the X.Org configuration from installation (since it is considered safe, otherwise a graphical installation would not have been possible). For some reason you did the installation with us keyboard layout. If you need to boot into failsafe remove "x11failsafe" option ==> INVALID
Created attachment 252499 [details] /boot/grub/menu.lst
I selected the german keyboard layout on the boot menu after the start of the installation DVD. Yast2 reported the german language and keyboard layout are in use. Also the german keyboard layout was available during the yast2 installation process. But the tip on the failsafe boot option gave me the idea to take a look on the grub settings in /boot/grub/menu.lst. For some reason the failsafe boot options have been setup for the standard and the failsafe openSUSE menu entries. This seems to be the real reason for the wrong keyboard layout. ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.1 Beta 5 - 2.6.27.5-2 root (hd1,2) kernel /boot/vmlinuz-2.6.27.5-2-pae root=/dev/disk/by-id/ata-Hitachi_HTS542516K9SA00_080226BB0C00WGKTE30A-part3 ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe showopts vga=0x317 initrd /boot/initrd-2.6.27.5-2-pae ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.1 Beta 5 - 2.6.27.5-2 root (hd1,2) kernel /boot/vmlinuz-2.6.27.5-2-pae root=/dev/disk/by-id/ata-Hitachi_HTS542516K9SA00_080226BB0C00WGKTE30A-part3 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317 initrd /boot/initrd-2.6.27.5-2-pae
This is really bad! Please reassign to the right person. We have so many bootloader packages on the distribution. No idea which one is currently used and needs to be fixed. Last time I tried to fix one, I patched dead code and even the maintainer didn't notice that this code is no longer in use. :-(
Yast Team, looks like a bootloader problem.
Probably for Pepa.
this is duplicate, it si caused by yast-bootloader bug in filling default append *** This bug has been marked as a duplicate of bug 440125 ***