xpra icon
Bug tracker and wiki

Opened 5 weeks ago

Last modified 9 hours ago

#2301 new defect

xpra shadow: cannot type "|" "<" keys, all write ">"

Reported by: stdedos Owned by: stdedos
Priority: major Milestone: 3.0
Component: server Version: 2.5.x
Keywords: Cc:

Description

Using xpra shadow :0, I cannot type the "|" and "<" characters.
Using en-us as active kb layout (on both sides) all write ">".

I tried following the https://xpra.org/trac/wiki/Keyboard template, ...:

  • active keyboard layout(s): en-us*, el-gr (both)


  • gtk_view_keyboard.py (named GTK_Keyboard_Test.exe on MS Windows)

... but the steps seem too much:

  • client and server log output with the -d keyboard debugging switch
  • running both the server and the client with the debug option -d keyboard, or for very verbose debugging: -d keyboard,verbose

... I don't know how to work them:

  • input methods
  • keyboard related configuration setup/files
  • keyboard type
  • if the problem is affecting specific keys, you may want to use the environment variable XPRA_DEBUG_KEYSYMS=keyname1,keyname2 on the server to log the keyboard mapping process for those keys
  • xev output of the misbehaving key events

... they sound irrelevant:

  • whether the bug is also present with/without --no-keyboard-sync

... these could be automated in one script saving them:

  • setxkbmap -print and setxkbmap -query (both directly in the client if it supports those commands and in the xpra session)
  • Keymap_info.exe on MS Windows, or xpra/gtk_common/keymap.py everywhere else
  • xmodmap -pke and xmodmap -pm (again on both)
  • xkbprint -label name $DISPLAY

(#2299 was found during this ticket)

xpra start gnome-terminal sends the keys just right, it's probably a shadow-server-thing

Attachments (4)

Xpra_cmd-gtk_view_kb_2019-05-17_11-51-15.png (59.1 KB) - added by stdedos 5 weeks ago.
kb-bug-report.zip (72.7 KB) - added by stdedos 5 weeks ago.
xpra-2301-client.txt (10.0 KB) - added by stdedos 11 hours ago.
xpra-2301-server-2019-06-18_13-20-44.txt (9.4 KB) - added by stdedos 11 hours ago.

Download all attachments as: .zip

Change History (15)

Changed 5 weeks ago by stdedos

Changed 5 weeks ago by stdedos

Attachment: kb-bug-report.zip added

comment:1 Changed 3 weeks ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos

From the bug report zip file, this system seems to be running Ubuntu 16.04 and xpra GTK3 client version 3.0 r22449.
Is the client MS Windows? What version?

Please capture the -d keyboard output of just when you press the keys that are not mapped properly.

comment:2 in reply to:  1 Changed 3 weeks ago by stdedos

Replying to Antoine Martin:

From the bug report zip file, this system seems to be running Ubuntu 16.04 and xpra GTK3 client version 3.0 r22449.
Is the client MS Windows? What version?

Win10 r22633

Please capture the -d keyboard output of just when you press the keys that are not mapped properly.

Is it possible to do that?

It would help a lot with the server bug reports, since, -d keyboard means my lockscreen password is coming up on the logs

comment:3 Changed 3 weeks ago by Antoine Martin

Is it possible to do that?

tail -f on the logfile and copy only the portion corresponding to the event.

comment:4 Changed 12 hours ago by Antoine Martin

I've added a greek layout to my ms windows 7 system, connected to an ubuntu 16.04 shadow server.

All the keys worked just fine.

Unless you can provide easily reproducible steps, I will have to close this ticket as 'needinfo'.

comment:5 Changed 11 hours ago by stdedos

Owner: changed from stdedos to Antoine Martin

I believe xpra shadow :0 -d keyboard mixes mouse events :/

[36m2019-06-18 13:18:13,945 update_mouse(3, 5386, 620, 906, 620) current=(1016, 776), client=1, show=True[0m
[36m2019-06-18 13:18:13,947 filtered_modifiers_set([])=set([])[0m
[36m2019-06-18 13:18:13,947 filtered_modifiers_set([])=set([])[0m

Changed 11 hours ago by stdedos

Attachment: xpra-2301-client.txt added

Changed 11 hours ago by stdedos

comment:6 Changed 11 hours ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos

I believe xpra shadow :0 -d keyboard mixes mouse events :/

I don't understand what that means, in any case this doesn't provide any steps to reproduce the problem.

comment:7 Changed 11 hours ago by stdedos

I am not sure what do you mean you don't understand.

I started a shadow server with -d keyboard, and I see mouse events (mixed with the keyboard events)

Additionally, I added debug run from both ends as an attachment - and I believe that it is complete debug information according to your request.

comment:8 Changed 11 hours ago by Antoine Martin

I started a shadow server with -d keyboard, and I see mouse events (mixed with the keyboard events)

Pointer events include the modifiers state. So you will see things like filtered_modifiers_set.. and some adjustments made on occasion.
That's because if you change shift or alt state whilst moving over another window, we need to synchronize that state when moving back over xpra's window, as some applications use this state.

Additionally, I added debug run from both ends as an attachment - and I believe that it is complete debug information according to your request.

As per comment:4, I asked for exact steps to reproduce the problem.
How to configure my test systems to trigger this issue.

comment:9 Changed 10 hours ago by stdedos

I don't have any special configuration in-place. Except the /etc/xpra/80_lock.conf, I simply provide any configuration straight to the command line for reproducibility

On both stations I have US layout active (but GR installed also), I start xpra-shadow remotely, I am just pressing <>?| keys in a sublime window (see that it "gives" >>?>), and close the session.

comment:10 Changed 10 hours ago by Antoine Martin

Like I said, I cannot reproduce the problem at all using a default configuration.
So please provide the details required so that I can configure my test systems exactly like yours. (as per keyboard / bug reporting wiki pages: setxkbmap -query from the server session, etc)

comment:11 Changed 9 hours ago by stdedos

Have you opened https://xpra.org/trac/attachment/ticket/2301/kb-bug-report.zip ?

It contains setxkbmap -query

rules:      evdev
model:      pc105
layout:     us

and a couple of other things too

Configuration on the server is "pretty clean too":

log-file              (used)   = 'display-$DISPLAY.log'            <type 'str'>
log-file             (default) = '$DISPLAY.log'                    <type 'str'>
microphone            (used)   = 'disabled'                        <type 'str'>
microphone           (default) = 'off'                             <type 'str'>
min-quality           (used)   = 20                                <type 'int'>
min-quality          (default) = 30                                <type 'int'>
min-speed             (used)   = 50                                <type 'int'>
min-speed            (default) = 30                                <type 'int'>
pings                 (used)   = 1                                 <type 'int'>
pings                (default) = 5                                 <type 'int'>
speaker               (used)   = 'disabled'                        <type 'str'>
speaker              (default) = 'on'                              <type 'str'>
start-on-last-client-exit  (used)   = 'bash -c 'echo now I will touch ; touch /run/user/1000/xpra-test-`date +%s`'', 'bash -c 'echo now I will fail! ; `date`'', 'bash -c 'echo now I will lock ; . /run/user/1000/dbus-session; gnome-screensaver-command -l''  <type 'list'>
start-on-last-client-exit (default) = []                                <type 'list'>
webcam                (used)   = 'no'                              <type 'str'>
webcam               (default) = 'auto'                            <type 'str'>

Last edited 9 hours ago by stdedos (previous) (diff)
Note: See TracTickets for help on using tickets.