Summary: | Konsole 18.12.2 regression: cursor lingers where typing has already occurred | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | A. Wilcox (awilfox) <awilfox> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | m.j.everitt, nate, wbauer1 |
Priority: | NOR | ||
Version: | 18.12.2 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
A. Wilcox (awilfox)
2019-03-02 00:02:35 UTC
I don't see this on my Konsole 18.12.2 with mostly stock appearance settings. Do you have any custom fonts, font sizes, color schemes, or widget themes active that might help explain this? And is it reproducible when compositing *is* enabled? (In reply to Nate Graham from comment #1) > I don't see this on my Konsole 18.12.2 with mostly stock appearance > settings. I can reproduce it here. But this is about the "Underline" cursor, you need to switch to that in the profile settings (Advanced tab->Cursor Shape). The cursor seems to be rendered slightly wrong since anti-aliasing was introduced, and that likely causes the "lingering" artifact. The standard block cursor had a similar problem but that was fixed in 18.12.1 with https://cgit.kde.org/konsole.git/commit/?h=Applications/18.12&id=b48ecb5712037027e6385515c9eced7fabfc3dc3 And the "I-Beam" cursor is also still rendered wrong, although that doesn't seem to cause any artifacts here. > And is it reproducible when > compositing *is* enabled? Yes, it does happen with compositing on here. Btw, this is probably a duplicate of bug#402589 I think. Can reproduce now, if I use the underline cursor. :( Looks like a duplicate, indeed. *** This bug has been marked as a duplicate of bug 402589 *** |