On Wed, 2007-02-14 at 20:39 -0800, Kenward Vaughan wrote: > On Wed, 2007-02-14 at 16:24 +0100, Florian Kulzer wrote: > > On Tue, Feb 13, 2007 at 18:37:04 -0800, Kenward Vaughan wrote: ... > > > > > > 06:32:58 > > > daddy:~# xmodmap -pk | grep Switch_VT > > > > > > 06:33:19 > > > daddy:~# > > > > > > Something's missing here, yes? > > > > Yes, I think we may have found the problem. If I run > > > > xmodmap -e "keycode 67 =" > > > > to remove the keycode for XF86_Switch_VT_1 then I can no longer use > > CTRL-ALT-F1 to switch to tty1. I can restore switching with: > > > > xmodmap -e "keycode 67 = F1 XF86_Switch_VT_1" > > > > I therefore hope that you can fix your problem by assigning these keycodes > > again. Try to run > > > > for ((i=1;i<=10;i++)); do xmodmap -e "keycode $((66+i)) = F$i > > XF86_Switch_VT_$i"; done > > > > to set them all at once (to the values that work for me here). > > > > This could be a bug of a package other than xlibs-* and xkb-*, which > > would explain why your purging/reinstalling did not have any effect. > > Something might screw around with the keycodes, for example the startup > > scripts of fluxbox. You can try to find out where it happens and file a > > bug report. If all else fails then it will hopefully be enough to > > include the above "for ..." command into your own startup scripts to set > > the keycodes at the beginning of each new X session. > > > Ah well. Ran the script (both as user and root), checked that things > were in place, but no good, no change. :( > > That included an X-window shutdown/restart, and a reboot following just > to see if some process I don't recognize kept the changes from becoming > effective. All no go. > > Where is XF86_Switch_VT_x defined/interpreted? If it's in the system but > not being recognized, where does that happen? While I see fluxbox as a > possible culprit, I'll point out again that the problem seems to run > across the board with any WM/DE used.
I started up gdm to give myself choices on sessions (to test fully whether this was a problem across the board with WM's) and found things working properly across the board. [EMAIL PROTECTED]&! Go figure. Using gdm enables the keys. Without gdm, no go. Several oddities: I notice as I write this note is that the keyboard is no longer inputting as UTF-8 encoding (i.e. I don't have to hit a space to have a quote mark print on its own instead of generating an umlaut, etc). Also, trying to start a gnome session failed--iceWM came up instead of Metacity, and the gnome session part froze. Lastly, VT 7 is not being used by gdm--8 is being used. ???? But now I can switch VT's as desired as long as gdm is running. So am I correct in assuming that gdm has somehow caused this problem? I was using it for a while but decided to stop it, opting for a leaner approach to things. I don't recall when that was relative to noticing the switching terminal problem. I'll file a bug, but don't know what to complain about regarding evidence... Kenward -- In a completely rational society, the best of us would aspire to be _teachers_ and the rest of us would have to settle for something less, because passing civilization along from one generation to the next ought to be the highest honor and the highest responsibility anyone could have. - Lee Iacocca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
