starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Clear-screen bug after updating to Ubuntu 19.04 #1013

New Issue
Closed
opened 2026-01-30 22:13:57 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 22:13:57 +00:00
Owner
Copy Link

Originally created by @radium-v on GitHub (May 13, 2019).

  • Your Windows build number: 10.0.17763.475

  • What you're doing and what's happening:

  1. Open Ubuntu 19.04 with a terminal window:
    2019-05-12 (0)

  2. Type clear and hit enter
    2019-05-12 (1)
    2019-05-12 (2)

  3. The screen scrolls too far and the prompt is too far up
    2019-05-12 (3)

  4. Typing in the prompt even after scrolling up resets to the borked scroll positon:
    2019-05-12 (4)

  5. Resizing the window fixes the re-jumping but only if you scroll the prompt back into view first:
    2019-05-12 (5)

This started happening after upgrading to Ubuntu 19.04 and wasn't an issue before. I'm noticing some other weird stuff too:

  • As described in Microsoft/WSL#4015, the amount of lines the scrolling is off by is equal to the amount of lines that were present when the clear was called.
  • Manually scrolling the window to the top with the mouse brings the prompt back into view, though typing in the prompt resets the scroll position offscreen (by the entire incorrect offset).
  • If I scroll to the top, then resize the window, the scroll position is fixed. This only works if I haven't already started typing a new command
  • This is happening in both Windows Terminal as well as Visual Studio Code (1.33.1 system setup).
  • This happens when I run wsl.exe, ubuntu.exe, open the Ubuntu app shortcut, or open a terminal in Visual Studio Code.
  • The cls command in cmd works as expected.
  • Using clear -x does scroll into position as expected, but doesn't remove previous lines.
Originally created by @radium-v on GitHub (May 13, 2019). * Your Windows build number: 10.0.17763.475 * What you're doing and what's happening: 1. Open Ubuntu 19.04 with a terminal window: ![2019-05-12 (0)](https://user-images.githubusercontent.com/863023/57591182-20a96b80-74fe-11e9-8858-a9253cffdc14.png) 2. Type `clear` and hit enter ![2019-05-12 (1)](https://user-images.githubusercontent.com/863023/57591187-2901a680-74fe-11e9-8761-cc183d566933.png) ![2019-05-12 (2)](https://user-images.githubusercontent.com/863023/57591189-2bfc9700-74fe-11e9-9229-21fc9f4cf8b9.png) 3. The screen scrolls too far and the prompt is too far up ![2019-05-12 (3)](https://user-images.githubusercontent.com/863023/57591198-3454d200-74fe-11e9-94da-af3e0efcefdc.png) 4. Typing in the prompt even after scrolling up resets to the borked scroll positon: ![2019-05-12 (4)](https://user-images.githubusercontent.com/863023/57591210-4fbfdd00-74fe-11e9-8208-2f53cab47b3b.png) 5. Resizing the window fixes the re-jumping but *only* if you scroll the prompt back into view first: ![2019-05-12 (5)](https://user-images.githubusercontent.com/863023/57591245-69f9bb00-74fe-11e9-924d-79b3c6e50c00.png) This started happening after upgrading to Ubuntu 19.04 and wasn't an issue before. I'm noticing some other weird stuff too: * As described in Microsoft/WSL#4015, the amount of lines the scrolling is off by is equal to the amount of lines that were present when the `clear` was called. * Manually scrolling the window to the top with the mouse brings the prompt back into view, though typing in the prompt resets the scroll position offscreen (by the entire incorrect offset). * If I scroll to the top, then *resize the window*, the scroll position is fixed. This *only* works if I haven't already started typing a new command * This is happening in both Windows Terminal as well as Visual Studio Code (1.33.1 system setup). * This happens when I run `wsl.exe`, `ubuntu.exe`, open the Ubuntu app shortcut, or open a terminal in Visual Studio Code. * The `cls` command in `cmd` works as expected. * Using `clear -x` does scroll into position as expected, but doesn't remove previous lines.
claunia added the Product-ConhostArea-VTResolution-Duplicate labels 2026-01-30 22:13:57 +00:00
claunia commented 2026-01-30 22:13:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 13, 2019):

Since this is 17763, I'm inclined to believe this is a dupe of #270

@zadjii-msft commented on GitHub (May 13, 2019): Since this is 17763, I'm inclined to believe this is a dupe of #270
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-VT Product-Conhost Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1013
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?