You are not logged in.
Starting sometime over the past week after i upgraded chromium, i see flickering every time the mouse pointer goes over the tabs, it flickers and it often switches to the wrong tab. I searched this forum, it seems no one else reported this issue. I did a google search and only found this issue [1] in the Debian bug tracker. I am currently using chromium version 141.0.7390.76-1 but it happened with a previous version too. I use xfce on openbox with the proprietary nvidia driver. I tried to turn off hardware acceleration in the chromium settings but it made no difference.
Does anybody have this issue?
[1] https://bugs.debian.org/cgi-bin/bugrepo … ug=1117646
Last edited by archdub (2025-11-06 21:37:07)
Offline
I stumbled over new information about this issue. It turns out that there is a bug in recent versions of chromium that manifests with my trackball, model Kensington Slimblade. I have another trackball of the exact same model that I use with my work computer running Windows. I tested the same version of chromium that I have in Arch and there was no issue. I also tested two chromium based browsers from the AUR. The issue manifests in thorium, which is based on a recent version of chromium and does not manifest with cromite which is based on a old version of chromium.
I checked the chromium issue tracker yesterday and this issue was not there. I am not inclined to file an issue there as the chances it will be fixed are small since it affects a specific model of trackball on Linux.
If I need a workaround I can use a cheap Dell mouse that I normally don't use. Using xev I did a basic comparison of events generated by this cheap mouse and my trackball, and could not spot any abnormality in the events. So it is a rather odd chromium bug. All the other apps work fine with the trackball. I have been using chromium for years with this trackball and it worked well until a few weeks ago.
Offline
The issue was fixed in yesterday's Arch release, Version 142.0.7444.134 .
This happens many times, if I wait the issue often gets fixed days or weeks later, in this case it took around 5 weeks.
I just had to endure the annoyance caused by this bug, and use a mouse a few times instead of my trackball.
Offline