Bug 1251390

Summary: Clear scrollback and reset leaves the terminal screen blank.
Product: [Fedora] Fedora Reporter: 3ndymion <3ndymion.1>
Component: konsoleAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Fedora 22 KDE 5
Last Closed: 2016-07-19 17:24:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description 3ndymion 2015-08-07 08:23:02 UTC
Description of problem:
In the Konsole terminal emulator, whenever you do "clear scrollback and reset", either through the menu option or by pressing Control Shift K, the screen will remain blank.  The prompt is not there.  It will reappear whenever you press another key.

Version-Release number of selected component (if applicable):
Konsole Version 15.04.0

How reproducible:
Always

Steps to Reproduce:
1. Go to "View".
2. Choose "Clear Scrollback and Reset".
3. Or press Control+Shift+K

Actual results:
Screen remains blank.

Expected results:
The prompt should be showing.

Additional info:

Comment 1 Fedora End Of Life 2016-07-19 17:24:16 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.