Bug 19262

Summary: konsole hangs while typing text on last line
Product: Mageia Reporter: Giuseppe Ghibò <ghibomgx>
Component: RPM PackagesAssignee: KDE maintainers <kde>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
URL: h
Whiteboard:
Source RPM: konsole-16.04.3-1.mga6.src.rpm CVE:
Status comment:

Description Giuseppe Ghibò 2016-08-29 13:51:30 CEST
Well, it's hard to this report as it's difficult to reproduce but it happens at least once or twice a day (according to whether you are typing a lot or not), but I observed it since a few months, and is still there.

Sometimes happens that konsole hangs (like when you were pressing a scroll-lock key) while you are typing text and you are on the *last line* of the konsole. At this point you can't type anything further. Only thing which sound to do some activity is the "clear scrollback and reset" from the View menu, but it will just clear the current konsole and no further typing or activity is allowed anyway. Also on the File menu adding a "new tab" would fork a new working konsole tab.

There are no other strange behaviour in logs, or crazy processes that eats 100%. Very hard to debug. This reminds me a similar bug that was happening on the AmigaOS on its console, in the same circumstances, i.e. when you were typing on the last line of text.

Suggestions?
Comment 1 Rémi Verschelde 2016-08-29 13:54:25 CEST
I'm using yakuake (which uses konsole as backend) and don't experience this issue - but that doesn't mean it wouldn't be reproducible in konsole itself.

Assignee: bugsquad => kde

Comment 2 Giuseppe Ghibò 2016-08-29 14:00:37 CEST
Note that I was experiencing this on at least two different machines with different video card (one using nvidia driver the other intel driver).
Comment 3 Nicolas Lécureuil 2017-03-18 01:46:23 CET
is it still valid with current cauldron ?

CC: (none) => mageia

Comment 4 Aurelien Oudelet 2021-05-17 01:15:33 CEST
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED