Ticket #157 (closed usability: fixed)

Opened 5 years ago

Last modified 3 years ago

Space key must be pressed twice in Xephyr with -kb

Reported by: lmklassen@… Owned by: jeremyhu@…
Priority: Nice to Have Milestone: 2.3.3
Component: xserver Version: 2.3.0 (xserver-1.4.2-apple5)
Keywords: Xephyr Cc: brian@…

Description

Xeyphr requires space to be pressed twice in order to register once. This behaviour occurs when launching with

$ startx /usr/X11/bin/twm -- /usr/X11/bin/Xephyr :20 -kb

This behaviour is also observed when I try using Xephyr to connect via XDMCP to a RH 4u3 machine running GNOME desktop with the command

$ Xephyr :20 -kb -once -query remotehost

Omitting the -kb option in either case causes the keyboard to produce incoherent input.

System: Mac OS X 10.5.4 with Xquartz 2.3 installed

Change History

comment:1 Changed 5 years ago by jeremyhu@…

  • Priority changed from major to minor
  • Milestone set to 2.3.2
  • Summary changed from Space key must be pressed twice in Xephyr to Space key must be pressed twice in Xephyr with -kb

Don't use -kb as a command line argument and you should be fine.

comment:2 follow-up: ↓ 5 Changed 5 years ago by jeremyhu@…

Oh, I just saw your note about incoherent input. Install 2.3.1_rc2 and use '-kb' ... I'm guessing you were using 2.3.0.

comment:3 Changed 5 years ago by brian@…

I am seeing this issue as well, even after installing RC2. Without -kb it works fine now. I am trying to use Xephyr for XDMCP (like the original submitter) and with or without -kb, I get garbled text in the XDMCP GNOME session.

comment:4 Changed 5 years ago by brian@…

  • Cc brian@… added

comment:5 in reply to: ↑ 2 Changed 5 years ago by lmklassen@…

Installing 2.3.1_rc3 appears to have solved the issue with requiring -kb option to get coherent keyboard input. However using -kb option still requires space key to be pressed twice.

comment:6 Changed 5 years ago by jeremyhu@…

  • Milestone changed from 2.3.2 to 2.3.3

comment:7 Changed 4 years ago by jeremyhu@…

  • Milestone changed from 2.3.3 to 2.4.0

comment:8 follow-up: ↓ 9 Changed 4 years ago by jeremyhu@…

  • Milestone changed from 2.4.0 to 2.4.1

Is this still happening with 2.4.0_rc1?

comment:9 in reply to: ↑ 8 Changed 4 years ago by lmklassen@…

I only have the 2.3.3.2 installed on my system. The issue no longer occurs in that release. The keyboard also produces correct results with or without the -kb option.

comment:10 Changed 4 years ago by jeremyhu@…

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from 2.4.1 to 2.3.3
Note: See TracTickets for help on using tickets.