Description of problem: I was syncing the Lineage 15.1 version to my laptop and after that I ran reset to clear all the previous output. The result was that the output disappeared as if it's cleared, but the scrollbar still looks the same as when the output was there. I even ran clear and it didn't help. I've had this issue for many new installations of Mageia on this laptop. I even built the latest version from the Cauldron src.rpm, but the problem still persists. Version-Release number of selected component (if applicable): 17.12.2 How reproducible: All the time. Steps to Reproduce: 1. Open Konsole. 2. Choose a random device to build Lineage 15.1 for. 3. Do mkdir -p android/lineage && cd android/lineage/ 3. Do repo init -u https://github.com/LineageOS/android.git -b lineage-15.1. 4. Run repo sync -f --force-sync --no-clone-bundle (WARNING! 20 GB of storage is needed". 5. Now type reset and press Enter. 6. Voila! The previous output seems to be gone, but if you look at the scrollbar on the right it seems like it's only hidden instead of erased even thought it IS erased.
I have also installed Ubuntu 17.10 and I can't reproduce that issue in Plasma.
Assignee: bugsquad => kdeCC: (none) => marja11
I'd say this is normal. What you seem to want is the "View → Clear Scrollback and Reset" option from Konsole's menu. Default shortcut for that is Ctrl+Shift+K.
CC: (none) => jan-bugs
Regarding Konsole not properly reacting to the 'reset' and 'clear' commands, maybe Konsole doesn't fully implement some terminal emulation API which makes those calls not work properly. In any case, that's a question for the Konsole developers. From what I've seen, Konsole behaves like this in other distributions.
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
CC: (none) => ouaurelienStatus: NEW => RESOLVEDResolution: (none) => OLD