Josh Minzner

Can you provide a code example that demonstrates the problem? Also, what does calling wrapper.debug() output?

One thing that immediately jumps out to me is your use of async/await. The enzyme setState method does not return a Promise, so your use of await is effectively a...

If somebody was able to open up a PR with a failing testcase for this issue, that’d be amazing.

I somehow managed to get the touchscreen working! I ssh'd in, `cd`'d into the `/lib/modules/5.18.14-arch1-1/kernel/drivers/input/touchscreen` directory, ran `sudo rmmod goodix_ts`, and then `sudo insmod goodix_ts.ko.zst`. ~What's surprising to me is...

Okay I spoke too soon. The fix continues to work if I _restart_ my NEXT, but if I shut it down and then power it back on the touchscreen ceases...

Turns out the _only_ thing I need to run after startup to get the touchscreen working is `sudo modprobe goodix_ts`

Here's how I'm hacking around the issue: 1. Prevented the goodix_ts module from loading automatically by adding `blacklist goodix_ts` to `/etc/modprobe.d/system-tweaks.conf` (not sure if this is actually necessary) 2. Created...

Your suggestion is what I tried first with no success. ☹️ What's weird is that when I ran `lsmod` after trying the `modules-load.d` approach, I _did_ see `goodix_ts` listed! But...

Okay here's something more telling! journalctl when I run `sudo modprobe goodix_ts` _the very first time on a fresh start_ **with my fix disabled**: ``` Sep 05 16:46:52 chimeraos sudo[8826]:...

So it looks like the enable + disable + enable part of my fix is important. For whatever reason, the driver fails to load the first time, but succeeds the...