19:33 <adamcstephens> Is there any way to shut up this error? Every key I press in multiple terminals triggers it, and it's just noise in my logs. river[1955237]: error(text_input): inactive text input tried to commit an update, client bug?

20:03 <leon-p> what terminal are you using? May be worth reporting this potential client bug to them

20:23 <ifreund> we could also downgrade the log to a warning if it's really so common and noisy

20:58 <soulseeder> I've got the same thing, is it due to terminal?

21:11 <soulseeder> I could not trace it to pressing keys though

21:34 <adamcstephens> I've seen it in kitty and ghostty

21:35 <adamcstephens> I'm not confident enough in my understanding to report an issue to Kovid, and I've stopped using ghostty because dealing with issues on a closed source terminal is not worth my time

21:35 <adamcstephens> a warning would probably make more sense from my perspective, since it's not actually breaking anything as a user :)

21:37 <adamcstephens> ❯ journalctl --user --grep "error\(text_input\)" | wc -l

21:37 <adamcstephens> 322831

21:37 <adamcstephens> so it must be from more than just key presses, but that's only a few hours of logs

21:42 <soulseeder> I am using kitty and can confirm it's there

21:43 <soulseeder> leon-p: you suggest we report it but I am not sure how to provide more useful info to e.g. kitty maintainers

21:44 <soulseeder> or is this error actionable enough from your perspective?