[Fwd: Re: Since chvt works, the problem must be the keymap]

[Florian Kulzer-3]

On Fri, May 04, 2007 at 00:26:29 -0400, Amy Templeton wrote:

> Andrew Sackville-West wrote:
> > On Thu, May 03, 2007 at 10:09:42PM +0200, Florian Kulzer wrote:
> > > On Thu, May 03, 2007 at 00:41:32 +0100, David Claughton wrote:
> > > > Florian Kulzer wrote:
> > > >  > I am afraid it is time to start grasping at straws now:
> > > >> - try "gb" instead of "uk" for XkbLayout
> > > >
> > > > Well, would you believe it - that fixed the problem!
> > > >
> > > > I still can't quite believe it was as simple as that.
> > > >
> > > > Thanks a lot for your help :-)
> > >
> > > Well, in retrospect it is obvious that we should have had a good look at
> > > your xorg.conf and your logfile first. You joined this thread when we
> > > were already completely fixated on solving the ultimate mystery of the
> > > keysyms and therefore we could not see the forest for the tress anymore,
> > > I guess.
> >
> > is Amy still lurking on this thread??? is there something
> > missing in your xorg.conf?
>
> I'm still around. I guess you missed my quick workaround the
> other day (thanks to the magics of xbindkeys, sudo, and
> chvt). However, if there is an alternative to "us" that you
> think might fix the problem if given as an argument to
> "XkbLayout," I'd certainly be glad to try it. GB settings
> are somewhat useless to me, I'm afraid, since I'm from the
> US. Thanks, though.

What do you see if you disable your workaround, run

tail -fn0 /var/log/Xorg.0.log

and press CTRL+ALT+F1? If you get some errors or warnings related to
switching graphics modes then we know that the key combination does work
after all and that there is a problem with the graphics driver. If there
is no output at all then we know that your keysyms are still not set up
correctly.

(My apologies if we went over this already. I have now totally lost
 track of the various branches of this thread.)

It might also be illuminating to try if the switching works with the
"gb" layout even if this layout is not an acceptable permanent solution.
This might at least provide an opportunity to revive the "color vs.
colour" thread that we had a while back...

--
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Amy Templeton]

Florian Kulzer <florian.kulzer+debian@...> wrote:
> (My apologies if we went over this already. I have now totally lost
>  track of the various branches of this thread.)

It's okay. Also, appreciated.

> On Fri, May 04, 2007 at 00:26:29 -0400, Amy Templeton wrote:
> > Andrew Sackville-West wrote:
> > > On Thu, May 03, 2007 at 10:09:42PM +0200, Florian Kulzer wrote:
> > > > On Thu, May 03, 2007 at 00:41:32 +0100, David Claughton wrote:
> > > > > Florian Kulzer wrote:
> > > > >  > I am afraid it is time to start grasping at straws now:
> > > > >> - try "gb" instead of "uk" for XkbLayout
> > > > >
> > > > > Well, would you believe it - that fixed the problem!
> > > > >
> > > > > I still can't quite believe it was as simple as that.
> > > > >
> > > > > Thanks a lot for your help :-)
> > > >
> > > > Well, in retrospect it is obvious that we should have had a good look at
> > > > your xorg.conf and your logfile first. You joined this thread when we
> > > > were already completely fixated on solving the ultimate mystery of the
> > > > keysyms and therefore we could not see the forest for the tress anymore,
> > > > I guess.
> > >
> > > is Amy still lurking on this thread??? is there something
> > > missing in your xorg.conf?
> >
> > I'm still around. I guess you missed my quick workaround the
> > other day (thanks to the magics of xbindkeys, sudo, and
> > chvt). However, if there is an alternative to "us" that you
> > think might fix the problem if given as an argument to
> > "XkbLayout," I'd certainly be glad to try it. GB settings
> > are somewhat useless to me, I'm afraid, since I'm from the
> > US. Thanks, though.

> What do you see if you disable your workaround, run

> tail -fn0 /var/log/Xorg.0.log

> and press CTRL+ALT+F1?

Well...if I do that while I'm still in the XTerm, I see...

^[[1;7P

...but I think that's just XTerm freaking out. When another frame
is focused and I press the buttons, there is no output.

> If you get some errors or warnings related to switching graphics
> modes then we know that the key combination does work after all
> and that there is a problem with the graphics driver. If there is
> no output at all then we know that your keysyms are still not set
> up correctly.

It appears, then, to be the latter.

> It might also be illuminating to try if the switching works with
> the "gb" layout even if this layout is not an acceptable
> permanent solution.

Well, that's interesting. It did work properly using the "gb"
layout (though it took me a while to figure that out, since I
thought the keyboard wasn't working at all, but it turns out there
were just some problems until I disabled my xmodmap). That's very
weird.

One thing that I saw in the startx output using the "gb" layout
that I definitely do *not* see under the "us" layout was the
following...

CODE:
___________________________

SetGrabKeysState - disabled
___________________________

...upon switching to the console, and...

CODE:
__________________________

SetGrabKeysState - enabled
__________________________

...upon switching back to X. Is this inspiring at all?

> This might at least provide an opportunity to revive the "color
> vs. colour" thread that we had a while back...

Oh dear...and that of course brings up "gray vs. grey," "center vs.
centre," "boot vs. trunk," and all those other bizarre little
spelling differences that don't actually make a difference in
pronunciation ("boot" is *totally* still pronounced "trunk" in GB,
I swear).

Anyway...

Thanks,
Amy

--
Measure twice, cut once.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andrew Sackville-West]

On Tue, May 08, 2007 at 11:40:02PM -0400, Amy Templeton wrote:

> Florian Kulzer <florian.kulzer+debian@...> wrote:
>
> > What do you see if you disable your workaround, run
>
> > tail -fn0 /var/log/Xorg.0.log
>
> > and press CTRL+ALT+F1?
>
> Well...if I do that while I'm still in the XTerm, I see...
>
> ^[[1;7P

that's not good. THat means X is ignoring those keystrokes and passing
them through to Xterm.

>
> ...but I think that's just XTerm freaking out. When another frame
> is focused and I press the buttons, there is no output.

the other frames provide no output because thety are ignoring
key-presses they don't know how to deal with, I assume.

>
> > If you get some errors or warnings related to switching graphics
> > modes then we know that the key combination does work after all
> > and that there is a problem with the graphics driver. If there is
> > no output at all then we know that your keysyms are still not set
> > up correctly.
>
> It appears, then, to be the latter.
>
> > It might also be illuminating to try if the switching works with
> > the "gb" layout even if this layout is not an acceptable
> > permanent solution.
>
> Well, that's interesting. It did work properly using the "gb"
> layout (though it took me a while to figure that out, since I
> thought the keyboard wasn't working at all, but it turns out there
> were just some problems until I disabled my xmodmap). That's very
> weird.

what happens when you disable your xmodmap with a "us" layout?

>
> One thing that I saw in the startx output using the "gb" layout
> that I definitely do *not* see under the "us" layout was the
> following...

are you seeing this on the VT you launched X from or is it in the
logs?

>
> CODE:
> ___________________________
>
> SetGrabKeysState - disabled
> ___________________________
>
> ...upon switching to the console, and...
>
> CODE:
> __________________________
>
> SetGrabKeysState - enabled
> __________________________
>
> ...upon switching back to X. Is this inspiring at all?
>
> > This might at least provide an opportunity to revive the "color
> > vs. colour" thread that we had a while back...
>
> Oh dear...and that of course brings up "gray vs. grey," "center vs.
> centre," "boot vs. trunk," and all those other bizarre little
> spelling differences that don't actually make a difference in
> pronunciation ("boot" is *totally* still pronounced "trunk" in GB,
> I swear).

I love how the spell "kitchen sheers" in the uk:
"kitchen-cester-sheers"

A

[Amy Templeton]

Andrew Sackville-West <andrew@...> wrote:

> On Tue, May 08, 2007 at 11:40:02PM -0400, Amy Templeton wrote:
> > Florian Kulzer <florian.kulzer+debian@...> wrote:
> >
> > > What do you see if you disable your workaround, run
> >
> > > tail -fn0 /var/log/Xorg.0.log
> >
> > > and press CTRL+ALT+F1?
> >
> > Well...if I do that while I'm still in the XTerm, I see...
> >
> > ^[[1;7P

> that's not good. THat means X is ignoring those keystrokes and
> passing them through to Xterm.

> > ...but I think that's just XTerm freaking out. When another
> > frame is focused and I press the buttons, there is no output.

> the other frames provide no output because thety are ignoring
> key-presses they don't know how to deal with, I assume.

That seems about right, yeah.

> > One thing that I saw in the startx output using the "gb" layout
> > that I definitely do *not* see under the "us" layout was the
> > following...

> are you seeing this on the VT you launched X from or is it in the
> logs?

On the VT.

> > > If you get some errors or warnings related to switching
> > > graphics modes then we know that the key combination does
> > > work after all and that there is a problem with the graphics
> > > driver. If there is no output at all then we know that your
> > > keysyms are still not set up correctly.
> >
> > It appears, then, to be the latter.
> >
> > > It might also be illuminating to try if the switching works
> > > with the "gb" layout even if this layout is not an acceptable
> > > permanent solution.
> >
> > Well, that's interesting. It did work properly using the "gb"
> > layout (though it took me a while to figure that out, since I
> > thought the keyboard wasn't working at all, but it turns out
> > there were just some problems until I disabled my xmodmap).
> > That's very weird.

> what happens when you disable your xmodmap with a "us" layout?

Oh dear...this is disturbing...it works properly. But...but...I
need to have Control where Caps Lock used to be, and I don't even
touch left-Alt! If xmodmap is the culprit, I'm afraid I'm just
going to have to deal with the problem. But at least, thanks to
you, the source of the problem has been found. Maybe I'll go
through at some point and comment out small portions at a time so I
can isolate the nefarious line(s) in question. But for now, I am
going to finish up the paper I'm ostensibly working on (no more
distracting self with email) and go to bed.

Thanks to all who've replied,
Amy

--
I can resist everything except temptation. -Oscar Wilde


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Thomas Dickey]

Amy Templeton <amy.g.templeton@...> wrote:
>> and press CTRL+ALT+F1?

> Well...if I do that while I'm still in the XTerm, I see...

> ^[[1;7P

> ...but I think that's just XTerm freaking out. When another frame
> is focused and I press the buttons, there is no output.

It helps to read the documentation -

        http://invisible-island.net/xterm/ctlseqs/ctlseqs.html

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Thomas Dickey]

Andrew Sackville-West <andrew@...> wrote:

> that's not good. THat means X is ignoring those keystrokes and passing
> them through to Xterm.

Fortunately, "X" ignores keystrokes, so you're able to use your keyboard.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andrew Sackville-West]

On Wed, May 09, 2007 at 01:00:19AM -0400, Amy Templeton wrote:

> Andrew Sackville-West <andrew@...> wrote:
>
> > what happens when you disable your xmodmap with a "us" layout?
>
> Oh dear...this is disturbing...it works properly. But...but...I
> need to have Control where Caps Lock used to be, and I don't even
> touch left-Alt! If xmodmap is the culprit, I'm afraid I'm just
> going to have to deal with the problem. But at least, thanks to
> you, the source of the problem has been found. Maybe I'll go
> through at some point and comment out small portions at a time so I
> can isolate the nefarious line(s) in question. But for now, I am
> going to finish up the paper I'm ostensibly working on (no more
> distracting self with email) and go to bed.

Does this mean the problem is "solved"?

If so, then yes, its jsut a matter of figuring out what's not
compatible in your xmodmap and fixing it up.


A

[Andrew Sackville-West]

On Wed, May 09, 2007 at 10:34:46AM -0000, Thomas Dickey wrote:

> Amy Templeton <amy.g.templeton@...> wrote:
> >> and press CTRL+ALT+F1?
>
> > Well...if I do that while I'm still in the XTerm, I see...
>
> > ^[[1;7P
>
> > ...but I think that's just XTerm freaking out. When another frame
> > is focused and I press the buttons, there is no output.
>
> It helps to read the documentation -
>
> http://invisible-island.net/xterm/ctlseqs/ctlseqs.html

come on. Its not like this is slashdot or someth... oh. nm.

A

[Amy Templeton]

Andrew Sackville-West <andrew@...> wrote:

> On Wed, May 09, 2007 at 01:00:19AM -0400, Amy Templeton wrote:
> > Andrew Sackville-West <andrew@...> wrote:
> >
> > > what happens when you disable your xmodmap with a "us" layout?
> >
> > Oh dear...this is disturbing...it works properly. But...but...I
> > need to have Control where Caps Lock used to be, and I don't
> > even touch left-Alt! If xmodmap is the culprit, I'm afraid I'm
> > just going to have to deal with the problem. But at least,
> > thanks to you, the source of the problem has been found. Maybe
> > I'll go through at some point and comment out small portions at
> > a time so I can isolate the nefarious line(s) in question. But
> > for now, I am going to finish up the paper I'm ostensibly
> > working on (no more distracting self with email) and go to bed.

> Does this mean the problem is "solved"?

> If so, then yes, its jsut a matter of figuring out what's not
> compatible in your xmodmap and fixing it up.

Oh...the [Solved] is a holdover from the first time it got
"solved." It just never got removed. Sorry for the confusion. But
it's solved enough for me, for the moment.

Amy

--
... the flaw that makes perfection perfect.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andrew Sackville-West]

On Thu, May 10, 2007 at 08:01:45PM -0400, Amy Templeton wrote:

> Andrew Sackville-West <andrew@...> wrote:
> > On Wed, May 09, 2007 at 01:00:19AM -0400, Amy Templeton wrote:
> > > Andrew Sackville-West <andrew@...> wrote:
> > >
> > > > what happens when you disable your xmodmap with a "us" layout?
> > >
> > > Oh dear...this is disturbing...it works properly. But...but...I
> > > need to have Control where Caps Lock used to be, and I don't
> > > even touch left-Alt! If xmodmap is the culprit, I'm afraid I'm
> > > just going to have to deal with the problem. But at least,
> > > thanks to you, the source of the problem has been found. Maybe
> > > I'll go through at some point and comment out small portions at
> > > a time so I can isolate the nefarious line(s) in question. But
> > > for now, I am going to finish up the paper I'm ostensibly
> > > working on (no more distracting self with email) and go to bed.
>
> > Does this mean the problem is "solved"?
>
> > If so, then yes, its jsut a matter of figuring out what's not
> > compatible in your xmodmap and fixing it up.
>
> Oh...the [Solved] is a holdover from the first time it got
> "solved." It just never got removed. Sorry for the confusion. But
> it's solved enough for me, for the moment.

I meant that the xmodmap was the problem, and without it your vt
switching functioned properly, right? So now its a "how do I fix my
xmodmap" question...

A

[Amy Templeton]

Andrew Sackville-West <andrew@...> wrote:

> On Thu, May 10, 2007 at 08:01:45PM -0400, Amy Templeton wrote:
> > Andrew Sackville-West <andrew@...> wrote:
> > > On Wed, May 09, 2007 at 01:00:19AM -0400, Amy Templeton wrote:
> > > > Andrew Sackville-West <andrew@...> wrote:
> > > >
> > > > > what happens when you disable your xmodmap with a "us" layout?
> > > >
> > > > Oh dear...this is disturbing...it works properly. But...but...I
> > > > need to have Control where Caps Lock used to be, and I don't
> > > > even touch left-Alt! If xmodmap is the culprit, I'm afraid I'm
> > > > just going to have to deal with the problem. But at least,
> > > > thanks to you, the source of the problem has been found. Maybe
> > > > I'll go through at some point and comment out small portions at
> > > > a time so I can isolate the nefarious line(s) in question. But
> > > > for now, I am going to finish up the paper I'm ostensibly
> > > > working on (no more distracting self with email) and go to bed.
> >
> > > Does this mean the problem is "solved"?
> >
> > > If so, then yes, its jsut a matter of figuring out what's not
> > > compatible in your xmodmap and fixing it up.
> >
> > Oh...the [Solved] is a holdover from the first time it got
> > "solved." It just never got removed. Sorry for the confusion. But
> > it's solved enough for me, for the moment.

> I meant that the xmodmap was the problem, and without it your vt
> switching functioned properly, right? So now its a "how do I fix my
> xmodmap" question...

Oh. Well, in that case, yes. I figure that part shouldn't be too
hard; I'll just comment out everything, start X, switch to a VT,
kill X, uncomment something, start X, switch to a VT...etc. When I
have time, that is.

Anyway, thanks for your help in this!

Amy

--
Darth Vader! Only you would be so bold!
                -- Princess Leia Organa


--
To UNSUBSCRIBE, email to debian-user-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...