Bug 327017

At least attach /etc/X11/xorg.conf and /var/log/Xorg.0.log.

Created attachment 173885 [details]
xorg.conf

Created attachment 173887 [details]
Xorg.0.log

someone mentioned they had a problem with their "fn" key.  i have an "f lock" key and i've tried it in both the on and off positions.  i'm not sure what's going on.

clearing needinfo; the requested logfiles were provided in comment #2 and comment #3

Obviously you created xorg.conf with nvidia-xconfig. This is not supported.

Created attachment 173904 [details]
xorg.conf.backup

it didn't work before the nvidia installation either.

So you attached the same config file two times. What use is this?

Created attachment 174001 [details]
xorg.conf.saxsave

sorry, pointed to the wrong conf file.

i used "showkey -k" in runlevel 3, as suggested by someone in another report.  when i press and release the keys ctrl alt and f1, showkey does report correctly...  i think it was 29, 56 and 59 respectively, pressed, then it shows them released.  so they keys are working, but i can't switch tty/vt at all.

print screen isn't working either.

hmm, this also might be related...  the mouse works fine most of the time, but if the computer starts crunching, like when the software cache is being read by yast, i can hardly move the mouse at all.  i mean, i slide it 6" and it moves on screen about 1/2".  the mouse (logitech g5) never performed this badly in alphas 1 thru 7 or betas 1 thru 3.  is this or the keyboard related to the evdev problem?  

Created attachment 174002 [details]
saved as plain text

This is the X11 configuration used during installation, which is used as fallback, if sax2 fails at the end of the installation. So you are still using "fbdev" video (slow!) and "mouse" (no "evdev"!) driver.

I think you should create a real configuration with SaX2 first.

i compared my new xorg.conf to one from a previous install and noticed one line
that looked suspicious in InputDevice section:

Option "XkbVariant" "nodeadkeys"

so i commented this line out and restarted x.

vt switching (ctrl+alt+fkey) and print screen all work now.

the mouse is still dreadfully slow whenever the system really gets to
crunching, like when using the software manager.  i can barely move the mouse
at all.

i'm going to look for other bugs with mice now.

i need to reopen this bug.

the vt switching problem is definitely caused by sax2 when it saves the xorg.conf during installation.

i did a clean install of rc1 onto a different drive (sata).

default xorg.conf (xorg.conf.install / xorg.conf.saxsave):

Section "InputDevice"
  Driver		"kbd"
  Identifier	"Keyboard[0]"
  Option		"Protocol"		"Standard"
  Option		"XkbRules"		"xfree86"
  Option		"XkbKeycodes"	"xfree86"
  Option		"XkbModel"		"pc104"
  Option		"XkbLayout"		"us"
EndSection

after sax2 saves the xorg.conf

Section "InputDevice"
  Driver       "kbd"
  Identifier   "Keyboard[0]"
  Option       "Protocol" "Standard"
  Option       "XkbLayout" "us"
  Option       "XkbModel" "microsoft"
  Option       "XkbRules" "xfree86"
  Option       "XkbVariant" "nodeadkeys"
EndSection

the "Option "XkbVariant" "nodeadkeys"" line is the direct cause of my problem.

with that line, i cannot switch vt's using ctrl+alt+fkey, and print screen also fails.  if i comment that line and restart x, all keys work normally.

this problem may have existed prior to rc1, but my sax2 in all previous versions failed due to a known problem with the logitech g5 mouse, so sax2 never saved an xorg.conf.

Created attachment 174099 [details]
xorg.conf, before and after sax2

Indeed there's no nodeadkeys variant for us keyboard layout. Therefore keyboard layout loading fails - although this cannot be seen in the logfile.
Looks like a bug in SaX2 to me.

@stefan bug 327517 seems related

nodeadkeys variant was never set and is not needed for us keyboards
and worked in the past

Marcus, if I understand Darren correctly, SaX2 now sets nodeadkeys for us keyboard layouts by default. This is wrong needs to be adressed.

I didn't change anything in us keyboard mapping:

# /.../
# Mapping table for console -> X11 mapping
#==================================================================================
# CONSOLE       | MODEL | LAYOUT       | VARIANT    | KEYCODE | LA| RA| SL| RC| OPT
#---------------|-------|--------------|------------|---------|---|---|---|---|----
us              : microsoftpro : us           : x            : xfree86 : x : x : x : x : x


x -> no variant

I checked that and it works for me with us.map.gz set in /etc/sysconfig/keyboard
(KEYTABLE variable)

This would mean that Darren enabled it manually.

not the case, this is a vanilla install, i didn't do anything silly and at no point did i ever manually select a keyboard layout or a mouse for that matter.

i installed rc1 two times with identical results.  i installed the previous 10 versions, some of them twice, and never saw this before, not one time.

i use print screen heavily, and i switch vt's constantly so i can play with multiple wm's at the same time which is the only reason i noticed the problem immediately.

reopening for now.

installation process is not sax, the installer uses libsax and can setup
the keyboard in its own way. if you can't reproduce the issue with the
following commands it's definitely not a sax2 bug

   init 3
   sax2 -a

   ==> check the /etc/X11/xorg.conf
       If you are using the us.map.gz console map in /etc/sysconfig/keyboard
       (KEYTABLE) variable _no_ variant must be set

Thanks

Created attachment 174320 [details]
sax2 -a test...

marcus...

i moved my xorg.conf out of the way, switched to init 3 and ran sax2 -a as you requested.

i am still getting:  Option "XkbVariant" "nodeadkeys"

> If you are using the us.map.gz console map in /etc/sysconfig/keyboard

i have no idea if i am or not, i don't even know where to change that, but i didn't change it myself.

> > If you are using the us.map.gz console map in /etc/sysconfig/keyboard
>
> i have no idea if i am or not, i don't even know where to change that, but i
> didn't change it myself.
Check for KEYTABLE in /etc/sysconfig/keyboard. Shouldn't be that hard.

If you don't mind call:

cat /etc/sysconfig/keyboard | grep KEYTABLE 

Thanks

sgt-d@meh-u8i9:~> cat /etc/sysconfig/keyboard | grep KEYTABLE
# e.g. KEYTABLE="de-latin1-nodeadkeys", "us" or empty for US settings
KEYTABLE="us.map.gz"
#  or KEYTABLE will be used then -- most keyboard maps don't have a
sgt-d@meh-u8i9:~>

yast sysconfig editor shows hardware -> keyboard -> keymap = us.map.gz

er..  keytable*

?? can you tell me the information from

   sysp -q keyboard

thanks

meh-u8i9:/home/sgt-d # sysp -q keyboard
Keyboard0 =>  XkbModel   : microsoftpro
Keyboard0 =>  XkbLayout  : us
Keyboard0 =>  Name       : Microsoft Natural® Ergonomic Keyboard 4000
Keyboard0 =>  VendorID   : 0x045e
Keyboard0 =>  DeviceID   : 0x00db
Keyboard0 =>  Profile    : microsoft-natural
Keyboard0 =>  RealDevice : /dev/input/event4

*Aha* the microsoft-natural profile is hitting us... there is the variant
set for only this keyboard *grr* :)

fixed

KICK ASS!

*whew* i was almost convinced i was doing something wrong ;)

;-) you were fine... I was wrong