KDE neon Surface Go Pen latching/getting stuck in the pressed state

Hello, recently I decided to install KDE Neon onto my Surface Go, since that’s the OS I use on my desktop and the pretty old hardware in the surface was getting bogged down by windows. Everything went smoothly and works pretty well, except for the touch/pen inputs.

They work separately, touch and pen. But when using the pen and resting a palm on the screen after some time the pen gets stuck in some sort of semi pressed state. When I lift the pen and then place it somewhere else - it will register as a continuous streak.

This state also propagates onto the touchscreen and the touchpad behaviors system wide. For example if I try moving the mouse cursor using the touchpad over the task bar after getting this stuck state, it will register as if I’m trying to drag the icons around, even though I am not pressing anything on the touchpad.

Here is a video demonstrating the above: video (the issue starts at roughly 1:26)

Here is the output of xinput list:

~$ xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ Microsoft Surface Type Cover Consumer Control     id=9    [slave  pointer  (2)]
⎜   ↳ ELAN9038:00 04F3:261A Stylus stylus       id=13   [slave  pointer  (2)]
⎜   ↳ ELAN9038:00 04F3:261A Stylus eraser       id=18   [slave  pointer  (2)]
⎜   ↳ Microsoft Surface Type Cover Mouse        id=10   [slave  pointer  (2)]
⎜   ↳ ELAN9038:00 04F3:261A touch               id=12   [slave  pointer  (2)]
⎜   ↳ Microsoft Surface Type Cover Touchpad     id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Video Bus                                 id=6    [slave  keyboard (3)]
    ↳ Power Button                              id=7    [slave  keyboard (3)]
    ↳ Microsoft Surface Type Cover              id=8    [slave  keyboard (3)]
    ↳ Intel HID events                          id=14   [slave  keyboard (3)]
    ↳ Intel HID 5 button array                  id=15   [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=16   [slave  keyboard (3)]
    ↳ Microsoft Surface Type Cover Consumer Control     id=17   [slave  keyboard (3)]

I would like some guidance on where I should even begin to troubleshoot this as I am not very experienced with xinput and how it ties all the different inputs together.

Thank you.