[17:11] <m4t> not 100% sure what's happening - has anyone seen oddness in 24.04 with mate-terminal and extra newlines being sent?
[17:12] <m4t> could be my keyboard, i also updated firmware on that at the same time
[17:12] <m4t> i think once running 'reset' fixed it. haven't noticed happening in an older ubuntu vm.
[19:57] <superkuh> Perhaps you have braketed paste on?
[19:58] <superkuh> https://www.linuxquestions.org/questions/slackware-14/pasting-stuff-in-a-terminal-is-now-highlighted-but-by-what-4175686705/ Create a ~/.inputrc with the line, "set enable-bracketed-paste Off"
[19:59] <superkuh> I do this in all new deb/ubuntu based distros now. Started being required about 4 years ago.
[20:05] <m4t> it just happened in a vm as well actually
[20:05] <m4t> going to downgrade kb firmware
[20:12] <m4t> Bathroom Epiphanies:Frosty Flake:1: BUILD:  (Feb 16 2024)
[20:12] <m4t> kept trying to rebuild when i just wanted to flash, wound up figuring out the command 'make' was calling and flashing the old .hex
[20:14] <m4t> superkuh: i don't think it's that, if i do ctrl-shift-t to open a new terminal then do 'sudo -i<enter>', it'll send 2 newlines and try to auth with a blank pass immediately
[20:14] <m4t> happens in other console apps as well. but it just happened in a VM running older mate (20.04) so i think it's the kb. could be x11 as well i guess.
[20:14] <m4t> it does it about 5-10% of the time
[20:29] <m4t> if this fixes it i may try to bisect and/or compile the latest git with the avr-libc toolchain from 23.10 (used for libc on the keyboard microcontroller)
[20:33] <superkuh> Your keyboard runs on an avr and you can change the firmware? That's rad.
[20:38] <m4t> yeah, it's a coolermaster quickfire rapid. it actually has a socketed controller board, so i found a third party (now discontinued) plug in replacement based on avr
[20:38] <m4t> the newer versions have a soldered on controller so can't be swapped
[20:39] <superkuh> I am using a 21 year old Microsoft Internet Keyboard 3.0a (PS/2).
[20:39] <m4t> lol
[20:39] <m4t> been using it for 21 years?! or it's just old
[20:40] <superkuh> I've used it constantly since I bought it new when I built my "going to university" computer in 2023.
[20:40] <superkuh> I've had to re-solder on a new PS/2 connector twice. Otherwise it's held up perfectly. And I type *a lot*.
[20:40] <superkuh> Keycaps are just as bright as new.
[20:40] <superkuh> ER, in 2003.
[20:41] <m4t> i think i understand what that bracketed paste thing you're talking about does now
[20:41] <superkuh> Not 2023. :|
[20:41] <m4t> paste multiple lines to bash, and it doesn't execute it
[20:41] <superkuh> Yes.
[20:41] <m4t> have to hit enter again
[20:41] <superkuh> I guess that's kind of the opposite of your problem.
[20:41] <m4t> heh
[20:42] <m4t> it might be something with the debounce handling in the fw (or some timing change introduced with newer toolchain). i don't see it on other keys though.
[20:42] <m4t> maybe there is some cheeto dust in the switch
[20:42] <superkuh> Does xev say anything special?
[20:43] <m4t> i didn't test with that, if it keeps happening i will try to repro there
[20:43] <m4t> another possibility is that my fingers are just suddenly fatter
[21:27] <m4t> yeah i don't think it's the keyboard; i can kinda repro it now
[21:27] <m4t> if i hit the key firmly and press it all the way down, it's registering 2 presses
[21:28] <m4t> maybe the repeat keys setting
[21:31] <m4t> trying to find the keyboard settings in 'dconf dump /'. i see the accessibility ones, but not repeat keys / cursor blinking from the first page
[21:34] <m4t> may mess with this: https://github.com/qmk/qmk_firmware/blob/master/docs/feature_debounce_type.md
[21:34] <m4t> when it happens, the 2 presses are in very rapid succession; like, milliseconds apart, so i think it's too quick to be done by the OS actually
[21:36] <m4t> worse comes to worse i could replace the switch. already did it for one years ago, i think it was misbehaving as well
[21:41] <m4t> time 674546179, time 674546180 from xev when it happens
[21:49] <m4t> perl -Mstrict -Mwarnings -e 'use Time::HiRes qw(tv_interval gettimeofday); my $last = [gettimeofday]; while(<>) { my $now = [gettimeofday]; print(tv_interval($last, $now), "\n"); $last = $now; }'
[21:49] <m4t> shows when it repeats they're ~20ms apart
[21:51] <m4t> holding the key, repeat is 32ms apart
[22:48] <m4t> i ordered some replacement switches, gonna be annoyed if that's not it heh
[23:08] <superkuh> What was the result of testing with a different keyboard?