@Rachel_Sandler I had the SAME. EXACT. ISSUE.
And I accidentally “solved” it.
(before you get exited, I have no Idea if this will fix the issue for anyone else)
(sorry for how dramatic this is gonna be, I’ve been staring intensely at the screen for an hour and i have a headache now.)
After an hour of running terminal commands such as evtest with no interpreted input from the buttons, I gave up, and started drawing in Krita without the nice buttons.
A few minutes in, I accidentally pressed one of the buttons–LO AND BEHOLD, IT DID SOMETHING. I tested both buttons, they BOTH WORKED.
My guess as to how this has occured is that the stylus needed a bit to connect? I actually have no clue.
After this, I have gone to the gui tablet thingy in settings to see if it would detect the stylus, but no luck there (there are already ongoing remapping issues (look here if you’re curious) with styluses and Linux, so I’m not going to bother anyway)
I also went back to the terminal, and ran evtest | grep 'BTN' (I’m piping to grep because otherwise the output is extremely messy) AND FOR WHATEVER REASON, IT’S NOW MAGICALLY BEING DETECTED NOW, AS THOUGH THE ISSUE NEVER EXISTED.
oh also early on in my attempts to fix the issue, I booted into BIOS to change the protocol from MPP to USI, which I say in case that is relevant to this for some reason, but switching protocols didn’t fix it at first so i KINDA doubt MPP is a factor.
Goodness, this stylus might as well be a magic wand with whatever wizardry allowed this to happen.
Moral of the story: Tech gets to choose when it works, not you.