If I run it from terminal or set the shortcut settings to include run in terminal, it works. I'm using KDE/Plasma and if I click on its icon, KDE shows the cursor animation for the launch for a second then nothing happens. I updated my system and after reboot vmware-view won't run anymore unless I start it from the terminal.
I'd appreciate any tips, even on where to report this to :( This persists after shutting down Horizon and until I log out of my X11 session. I've replicated this bug with Control_L, Control_R and Shift_R.
#VMWARE HORIZON CLIENT 5.4 3 SERIES#
It's not that Control_L is not registered - it's that Horizon somehow messses turns the pressed down state into a series of events. If I try repeating it on the parent OS, I get a series of alternating KeyPress and KeyRelease events at incrementing (Press, ~40 time units delay, Release, KeyPress, repeat) time values. However, once I connect to a virtual desktop through Horizon and interact with the desktop in any way, I get this neat behavior only on the virtual desktop. State 0x14, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
#VMWARE HORIZON CLIENT 5.4 3 SERIAL#
State 0x10, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,Īnd then when you release it, you'll get a KeyRelease event: KeyRelease event, serial 35, synthetic NO, window 0x8200001, If you hold down Control_L, it should send a single KeyPress event: KeyPress event, serial 35, synthetic NO, window 0x8200001, Lrwxrwxrwx 1 root root 20 Jul 18 11:45 libavutil.so.56 -> /lib/libavutil.so.56Ī couple notes on the behavior of the sticky keys bug in 2203. Lrwxrwxrwx 1 root root 21 Jul 18 11:45 libavcodec.so.58 -> /lib/libavcodec.so.58 Lrwxrwxrwx 1 root root 20 Jul 18 11:44 libavutil.so.56 -> /lib/libavutil.so.56 Lrwxrwxrwx 1 root root 21 Jul 18 11:44 libavcodec.so.58 -> /lib/libavcodec.so.58
Lrwxrwxrwx 1 root root 20 Jul 18 11:35 libavutil.so.56 -> /lib/libavutil.so.56 Lrwxrwxrwx 1 root root 21 Jul 18 11:35 libavcodec.so.58 -> /lib/libavcodec.so.58 I installed ffmpeg4.4, removed all copies of those two libraries in /lib/vmware/view/, and replaced them with symlinks to /lib/libavcodec.so.58 and /lib/libavutil.so.56 respectively. I poked around in /lib/vmware/view/ and noticed that it has libraries libavcodec.so.58 and libavutil.so.56 in software/ vaapi/ and vaapi2/. Authentication is fine, but as soon as it tries to display my remote machine it just closes. If VAAPI is configured on my system, I cannot open my remote machine at all. There's probably a better way to fix this, but this helped to get me up and running. Putting this here in case it helps anyone.
0 kommentar(er)
