SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Happens randomly and stops randomly while using Plasma 6 2. May be related to using Chrome which I use often, but I haven't found any triggers. OBSERVED RESULT Pointer doesnt change but still clicks on links, buttons, or text EXPECTED RESULT Pointer always changes correctly SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.7.8-2 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION
Does the issue happen only over link or text in Chrome? Or in other apps too? If so, which other apps? How about Firefox?
(In reply to Nate Graham from comment #1) > Does the issue happen only over link or text in Chrome? Or in other apps > too? If so, which other apps? How about Firefox? When it happens, it affects the cursor everywhere. I genuinely haven’t seen any specific triggers for causing or stopping it. I may be seeing it in Chrome first simply because it’s my most used app, though I don’t remember seeing it *without * Chrome running.. I usually have Discord and Steam running as well. All native. Breeze dark theme and breeze cursor. I know this isn’t much to go on. I will report back if I narrow it down any further.
(In reply to Nate Graham from comment #1) > Does the issue happen only over link or text in Chrome? Or in other apps > too? If so, which other apps? How about Firefox? I have to retract my last statement. It DOES only happen in Chrome. When I place my cursor in Discord (and I assume other apps but will report back) and starts working again and remains that way when I return it to Chrome.
Just to get this in quickly, I can confirm it only happens in Chrome and moving the cursor to any other app fixes the issue. I'm on google-chrome-stable with Wayland enabled.
Ok, great. Seems like it's definitely an issue in the app. Can you submit a bug report at https://issues.chromium.org/issues, and then link it here bu putting it in the "URL" field of this bug report? Thanks a lot!
(In reply to Nate Graham from comment #5) > Ok, great. Seems like it's definitely an issue in the app. Can you submit a > bug report at https://issues.chromium.org/issues, and then link it here bu > putting it in the "URL" field of this bug report? Thanks a lot! I can only confirm that this issue happens in Google Chrome and not Chromium since I don't use it regularly, so not sure if I should post a bug report there. I did send a report from Chrome but they don't provide a link to it or anything like that.