Bug#295242:

[Braden]

Harald,

Wow, I wish I could help you, but I haven't solved my own problem yet.  If I 
do find out what it is I will let you know ASAP, but it doesn't look like the 
solution will be in my grasp soon.  I've talked to several people about the 
keyboard setup, and they all say that my settings are correct, so I am going 
to assume that yours is as well.  The only way I have been able to work 
around the problem is to connect remotely via XDMCP.  Its not the best 
solution (or a good solution), but it has given me X access to the box.

Regards,
Braden


On Wednesday 23 February 2005 01:32 pm, you wrote:
> Hi!
>
> I ran into this while setting up a friends machine. Unfortunately there
> is no internet there, so I couldn't look into the BTS there and now
> I don't have the PC available. Sorry for the incomplete information!
>
> Ad Braden: Can you confirm, whether the same problem shows up when
> starting X with startx?
>
> I believe that this bug is an instance of the problems described in
> #169427, but here are the details:
>
> I set up the machine with sarge-installer RC2, Kernel 2.4
> The keyboard is ordinary pc105 on a PS2-Port.
> The mouse is on USB.
>
> After a few tries we got gpm running. (Sorry don't remember the
> details, didn't expect any real trouble then.)
>
> Issuing xstart as an ordinary user brougth up X without trouble.
> I don't know, whether the keyboard worked at that time. My friend
> pressed some key-combinations he doesn't remember. (They had some
> effect at least.) At some point the keyboard went away. Neither
> of Ctrl-Alt-Fn nor anything else showed any effect.
>
> After terminating the running Gnome-Session using the mouse, we
> got the ttys back, but the keyboard was in trouble there too:
> To me it seems like the Ctrl-key was pressed the whole time
> (d leading to eof (logout), s leading to Scroll_Lock - I don't
> know a possibility to recover from that, ans Scroll_Lock itself
> leading to "Show_State")
>
> As we believed the keyboard configuration to be wrong, we tried a lot
> of different things. But all in subsequent tries the keyboard was
> broken under X from the very beginning (even after cold booting).
> In some cases ttys worked well after the x server had terminated
> and sometimes the above Ctrl-key problem showed up again. We can't
> reproduce this reliably yet.
>
> After reading #169427 I believe that the mouse setting is causing
> that and IIRC we had the very same setting of "Configured Mouse"
> and "Generic Mouse" as Braden has. I don't have access to the PC
> ATM, so I can't investigate this further.
>
> Hopefully this is helpful to somebody. I'll send a follow up as
> soon as I have access to the affected computer again.
>
> Harald