Summary: | Cursor shape for text may not change, and stay as arrow | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Igor Mironchik <igor.mironchik> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | nate, xaver.hugl |
Priority: | NOR | Keywords: | qt6 |
Version First Reported In: | 5.93.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Igor Mironchik
2024-02-29 15:55:01 UTC
Do you have an NVIDIA GPU, by any chance? No, I'm on Intel integrated GPU. Intel Core i5 7th Gen. Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: HP Product Name: HP ProBook 640 G3 Thanks. > Graphics Platform: X11
Is this correct?
(In reply to Vlad Zahorodnii from comment #4) > > Graphics Platform: X11 > > Is this correct? No, guess, no. I caught a lot of these issues on Wayland. And due to other blocking issues on Wayland, I switched to X11. Info was copied from X11 session, but problem most occurred on Wayland. on X11, if I remember everything right, I didn't see this issue. While you're on X11, can you stop kwin_x11 (systemctl --user stop plasma-kwin_x11) and check if the issue is still reproducible? After you've finished, run systemctl --user start plasma-kwin_x11 to start back kwin (In reply to Vlad Zahorodnii from comment #6) > While you're on X11, can you stop kwin_x11 (systemctl --user stop > plasma-kwin_x11) and check if the issue is still reproducible? > > After you've finished, run systemctl --user start plasma-kwin_x11 to start > back kwin I didn't understand where should I check, on Wayland with stopped kwin_x11, or on X11 with stopped kwin_x11? In anyway, I guess, that with recent updates this issue is gone. I'm unable to reproduce anymore either on X11 nor on Wayland. FWIW I've seen this issue happen before with KDevelop and Kate, and can also no longer reproduce it. I think it's been fixed in Qt. |