13:32 <the_eye> I have (as of a few minutes ago) a weird symptom and would need pointers as to where to start looking. The symptom: both installed Webbrowsers (librewolf and chromium) show erratic scroll movements (without me touching the laptop) upon first opening some websites. While that is going on, focusing a terminal and trying to type in it eats keypresses, i.e. only every second or third key

13:32 <the_eye> is registered.

13:33 <the_eye> As soon as the browser has calmed down (after a minute or so?) the terminal windows are also back to normal

13:33 <the_eye> Where might I start looking for what is wrong?

13:34 <jbe> are these "some websites" the same ones in both browsers?

13:36 <the_eye> as far as I can tell, yes

13:36 <the_eye> (one, e.g., is some ancient probably phpBB powered forum)

13:37 <the_eye> potentially relevant: I _think_ I have a very similiar set of extensions active in both browsers

13:37 <the_eye> (ublock0, vimium, darkreader)

13:38 <the_eye> bitwarden, too

14:25 <the_eye> hmm. disabling all extensions, quitting and restarting the browser doesn't stop it from happening

14:54 <the_eye> for example I open https://kde.org/announcements/changelogs/plasma/6/6.3.5-6.4.0/ and it immediately starts scrolling down. But due to the length of the page this takes more than 2 minutes. During this time, I can't type worth shit in my yakuake terminal window. AFAICT the "not all keypresses are registered" doesn't apply to the space-bar nor backspace but at least to all the letters.

14:54 <the_eye> Pasting works, though. This is quite vexing...

14:55 <fl0_id> maybe try another browser?

14:55 <the_eye> happens in librewolf as well as chromium

14:55 <the_eye> so I don't think the browser itself is the problem

14:55 <the_eye> also the fact that it is able to affect what I type in another window?

14:55 <the_eye> like .. wtf?

14:55 <j`ey> can you check dmesg/journalctl?

14:55 <fl0_id> yeah I got that. that's why maybe yet another one. just to be sure

14:56 <fl0_id> I assume just focus is not passed to other window, right?

14:57 <the_eye> fl0_id: no, the terminal window is focused. I can type in it but at least every second letter typed doesn't register. As soon as the website (currently in a not focused window in the background) has scrolled to the very bottom, typing becomes normal again

14:58 <fl0_id> mmh weird. does it happen with a different window manager? (just trying to think of things)

14:58 <the_eye> j`ey: I am currently _not_ having a website open that does the scrolling. journalctl is completely spammed with messages of the form "qt.accessibility.atspi: ValueChanged event and no ValueInterface or ComboBox: QAccessibleInterface(0xaaaafc3b6c90 name="" role=Client childc=2 obj=LegendDelegate_QMLTYPE_497_QML_499(0xaaaafac52f80)"invisible")"

14:58 <the_eye> (one every second)

14:58 <the_eye> this wasn't the case yesterday .. (before the plasma update to 6.4)

14:59 <the_eye> ah no two every second

14:59 <the_eye> lemme check if it changes when a website does its thing

15:01 <fl0_id> you could also check if there are some plasma / qt issues about it

15:03 <the_eye> same look to journal. Also for a second, while I wasn't touching the Laptop, it started showing a long chain of "1"s, as if I was holding that key down. Was able to make that stop with ctrl-c

15:04 <the_eye> At this point I'm suspecting poltergeist activity or something

15:05 <j`ey> you reported this same thing a few months ago

15:06 <the_eye> yep

15:07 <the_eye> after a while it went away and I have no idea why

15:07 <the_eye> but I _think_ I just found it

15:07 <j`ey> oh?

15:08 <the_eye> https://bugs.kde.org/show_bug.cgi?id=499004 - this is a problem with screenreader, which apparently can be started with meta+alt+s. and I _think_ that earlier, when I wanted to make a screenshot of something, for which I have configured meta+SHIFT

15:08 <the_eye> +s (because windows), I may have misfingered...

15:11 <the_eye> Because the screenshot utility only came up on the second try.

15:12 <the_eye> That the Screenreader (from what I understand how it would work) would need to scroll browser Windows all the way to the bottom kinda seems to make sense? So I just need to figure out how to stop the Screenreader and how to not accidentally start it again..

15:16 <fl0_id> yeah or unbind the key combo...

15:16 <fl0_id> if possible

15:21 <the_eye> w00t, it has stopped! and journal is quiet again! also, I've removed the keycombo for starting orca

15:22 <j`ey> poltergiest defeated

15:25 <the_eye> weirdly joins in with threads I had been reading on mastodon about how accessiblity is kinda shit these days on linux desktops

15:30 <fl0_id> whoop