Up from today there is an annoying issue in chrome-browsers.
If I open some pages, thy are scroll down the screen at their own in a ghostly manner.
I’ve tried it in Brave and Vivaldi
See this video, what happend if I refresh a Page (e.g. this Forum-Page here).
BTW: Yesterday there was a bigger upgrade available. I’ve done this update.
First I thought, it might be a sticked key or broken mouse-hardware… so I’ve unplugged them.
But the issue remain.
As I use a laptop (keyboard and mouse are untouched in last days) I want to be sure that it’s not an hardware issue of the build-in keyboard and touchpad… so I’ve started “screenkey” where I also activate “mouse-monitoring”.
So no keypress or mouse-move are recognized.
BTW: It make no difference if I start the browser in general or incognito-mode
What might the error be?
As I don’t have this scroll-down behavior in other applications (I’ve tried kate, libre-writer, thunderbird, etc.) I think it might be an chrome-engine issue?!?
What do you think about this?
I’ve looked into journalctl -b -e -f
and found many many entries like this:
Nov 29 12:13:54 secondone krunner[106849]: 0550:fixme:winsock:server_ioctl_sock Unsupported ioctl 0x120348 (device=0x12 access=0 func=0xd2 method=0)
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106340]: 0688:fixme:dwmapi:DwmGetWindowAttribute (0000000000010020 9 00007F2426F4F5A8 16) stub
Nov 29 12:13:54 secondone krunner[106849]: 0550:fixme:winsock:WSAIoctl unimplemented ioctl _WSAIOW(IOC_VENDOR, 17)
Nov 29 12:13:54 secondone krunner[106849]: 0550:fixme:winsock:server_ioctl_sock Unsupported ioctl 0x120348 (device=0x12 access=0 func=0xd2 method=0)
Ah… ok, that is not in any dependency to the issue.
I’ve found that this was caused of my Screen-Recorder Application which runs in wine.
If I stop it, and refresh the browser… and ghostly stuff scrolling starts again, no logs are created in the Journal.
So question remains… what does happens here?
Hi @rethus,
Since you mentioned it works on correctly in some apps, and others not it looks like, to me at least, it is a GTK issue, since all/most apps you mentioned working is Qt. The reason I say most is because you mentioned Thunderbird and I don’t think it’s Qt.
So I’d recommend checking that. I do not know what the settings are or is named, but I think that’s where the answer lay, at least.
Possibly more:
https://www.reddit.com/r/gnome/comments/128iq0w/vertical_scroll_sensitivity_fix_for_gtk3/
Ok, your suggestion might point in the right direction. Checked it with firefox now, same result (ghostly scrolling).
What other GTK-Based application can I check for this bug?
And how to fix it?
Your linked page give me no Idea what the reason might be and how I may fix it. The posting is about a user who tells that his touchpad is to senstive. But I don’t touch any key or touchpad at all.
I also have no idea, sorry.
Thinking look into Gnome/GTK’s mouse/pointer settings/sensitivity. That’s all I can think of…
Got it.
It was ocra - the screen-reader implementation.
Lucky me, I found this redit-post.
Deactivating and restarting kde solved it.
2 Likes
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.