David Niklas <[email protected]> writes: >> I rebooted the system after renaming .Xmodmap. >> >> I have found the same problem with twm. >> >> I changed the default window manager to twm, the default display manager >> to xdm, rebooted the system, created a new user, copied the .twmrc >> file, but still F1 didn't work. >> >> xev shows it is sending key 67 F1. >> >> It's all very odd. I am sure it used to work on that computer. There is >> a twmrc from 2014 with F1 set to call emacs. But it is so long ago I >> cannot remember what I was doing. I had some mapping done to change the >> prefix key for stumpwm but that's about all I can recall. >> >> It is probably easier to re-install linux than try to find out what is >> going on. >> > > --READ ALERT-- > Borg wimp off the port bow. > Shields to full. Arm photon torpedoes. > > Aside from Xmodmap, some computers have "Action Keys". These evil key > bindings were shackled to us by Windowz. You can turn them off in the > bios or work around the problem via typing Fn F1 .
I can't see anything in the Bios about it. Pressing Fn F1 does nothing. > On the other hand, if that it not your problem then reinstalling will > probably not help. > You see, when you reinstall you backup your home directory (you do do > that right?). When you restore your home dir you also restore whatever > oddity that you had when you had not reinstalled your Linux system > (unless there is some really odd thing, like a mis-auto-configured grub > boot loader that was installed when updating another Linux system on the > same computer, but you'd just need to boot a live CD/DVD and then chroot > to the correctly configured system and tell grub to install from there. > > Personally if "Action Keys" are not the problem, I'd try creating a new > user and then logging in with that users account and starting twm or > something not ctwm and seeing what happens. > I already tried that, as I said above.
