Bug 1251390 - Clear scrollback and reset leaves the terminal screen blank.
Clear scrollback and reset leaves the terminal screen blank.
Product: Fedora
Classification: Fedora
Component: konsole (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-07 04:23 EDT by 3ndymion
Modified: 2016-07-19 13:24 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Fedora 22 KDE 5
Last Closed: 2016-07-19 13:24:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description 3ndymion 2015-08-07 04:23:02 EDT
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:

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 13:24:16 EDT
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

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

Note You need to log in before you can comment on or make changes to this bug.