CuriousTommy
Contributor
Contributor
‎11-08-2023 10:26 AM

Anyone Else Experiencing Issue With VSCode's Terminal Panel on Fedora 39/38 ARM64 VM?

Hello Everyone,

I am running into this annoying issue when I try to use VSCode's terminal panel on my Fedora 39 ARM64 VM. When I type something on the terminal panel, it doesn't immediately show the text I type in. Sometimes it shows after I type a few more letters, other times it only shows after I press enter.

I attached a video showing the issue. I was wondering if anyone else is running into this issue

Player Version: 13.5.0 (22583790)

Linux Distro: Fedora 39 (updated as of 11/08/2023)

Labels (4)
Labels
Preview file
184 KB
Reply
0 Kudos
Technogeezer
Immortal
Immortal
‎11-08-2023 02:50 PM

One thought. is 3D acceleration enabled for the VM? If so, try turning it off and see if the symptoms change.

 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
Technogeezer
Immortal
Immortal
‎11-08-2023 07:55 PM

I've tried VSCode and I think I'm seeing the same things as you do. The console is definitely wonky and laggy. I've tried it with X11, Wayland, 3D on and 3D off. Nothing hits me over the top of the head to help me figure out if this is VSCode, Fedora, or Fusion related. 

I'm going to try this on.a physical Intel PC running Fedora 39 (good chance for me to upgrade) to see if things are any different.

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
Reply
0 Kudos
CuriousTommy
Contributor
Contributor
‎11-08-2023 09:57 PM

Sorry for the late reply, I did test with acceleration off, but I also run into the same issue as you did.

> I'm going to try this on.a physical Intel PC running Fedora 39 (good chance for me to upgrade) to see if things are any different.

I have a AMD Workstation that runs Linux natively and I haven't run into this issue on that machine.

I also installed and tested on VSCode on Asahi Linux (Fedora 38 remix), as a way to see if the issue might be due to the ARM64 Linux build of VSCode. However, I have not been able to reproduce the issue there either.

Reply
0 Kudos