Bug 363821 - Cursor position two characters to the right of where it should be as root.
Summary: Cursor position two characters to the right of where it should be as root.
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: kpart (show other bugs)
Version: 3.0.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2016-06-01 23:49 UTC by Rick Stanley
Modified: 2018-10-30 14:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Stanley 2016-06-01 23:49:50 UTC
After the latest update the cursor appears to have two spaces before the visible cursor, only after su to root.  This does not occur as regular user, in the [Ctrl]-[Alt]-[F1] console as root, or the XTerm terminal, as root.

Reproducible: Always

Steps to Reproduce:
1. Press [F12] to invoke Yakuake
2. su to login as root
3.

Actual Results:  
Visible Block cursor two characters to the right of where it should be.

Expected Results:  
Cursor appears as it should be immediately after the last character entered.

It becomes VERY annoying when you attempt to edit the command line.  I "Purged" Yakuake using aptitude, then reinstalled, without success.  I have not altered the default prompt for root or regular user.  I can provide images if that would help.
Comment 1 Eike Hein 2016-06-02 03:00:33 UTC
Most likely a font issue. Try a different font.
Comment 2 Rick Stanley 2016-06-02 23:27:13 UTC
That corrected the problem, but why did a daily update alter the behavior of the application?  I did not change anything myself to cause this to happen.  My end of this is now closed.
Comment 3 Marco Richetta 2018-10-30 14:19:39 UTC
Hi, I'm from the Bugsquad team and we are triaging bugs on Konsole today.
Thanks for reporting the bug.

Application Version: 17.12.3
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

Does the bug still exist on your system?