starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

.bash_history truncated after Terminal update #15756

New Issue
Closed
opened 2026-01-31 04:47:28 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:47:28 +00:00
Owner
Copy Link

Originally created by @GPHemsley-RELX on GitHub (Nov 1, 2021).

Windows Terminal version (or Windows build number)

1.11.2921.0

Other Software

Ubuntu 20.04 (WSL1)

Steps to reproduce

I can't say for sure if Windows Terminal is to blame here (as opposed to some overzealous enterprise sanitizing, for example), but I figured I'd file this just in case.

If it is, then I suspect this is vaguely what happened:

  • Install Windows Terminal via the store.
  • Have multiple instances of the same Ubuntu running.
  • Upgrade versions, which forcibly closes Terminal and its running sessions. (#6726)

All I really know is that .bash_history is now empty and a new version of Terminal was recently released.

Expected Behavior

Some copy of .bash_history (from some instance) is present. In other words, whatever it was doing before.

Actual Behavior

.bash_history is truncated and no history from any instance is available.

Originally created by @GPHemsley-RELX on GitHub (Nov 1, 2021). ### Windows Terminal version (or Windows build number) 1.11.2921.0 ### Other Software Ubuntu 20.04 (WSL1) ### Steps to reproduce I can't say for sure if Windows Terminal is to blame here (as opposed to some overzealous enterprise sanitizing, for example), but I figured I'd file this just in case. If it is, then I suspect this is vaguely what happened: * Install Windows Terminal via the store. * Have multiple instances of the same Ubuntu running. * Upgrade versions, which forcibly closes Terminal and its running sessions. (#6726) All I really know is that .bash_history is now empty and a new version of Terminal was recently released. ### Expected Behavior Some copy of .bash_history (from some instance) is present. In other words, whatever it was doing before. ### Actual Behavior .bash_history is truncated and no history from any instance is available.
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-ReproNeeds-Attention labels 2026-01-31 04:47:28 +00:00
claunia commented 2026-01-31 04:47:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 2, 2021):

Weird! I don't really know how bash goes about persisting the history. This might be a side effect of the "WSL processes get orphaned when the Terminal is force-updated by the store" issue, #9914.

@therealkenc IIRC you're the WSL triage wizard, any ideas here?

@zadjii-msft commented on GitHub (Nov 2, 2021): Weird! I don't really know how `bash` goes about persisting the history. This might be a side effect of the "WSL processes get orphaned when the Terminal is force-updated by the store" issue, #9914. @therealkenc IIRC you're the WSL triage wizard, any ideas here?
claunia commented 2026-01-31 04:47:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 29, 2022):

I'm guessing that this is somehow related to #9914. I don't know when bash writes out .bash_history, and I don't know why it would be empty. That would almost imply that the bash process totally cleared it out, which doesn't make any sense. I'm under the impression that bash just appends to it, always. That's real weird.

There might be something else going on here in ubuntu land. (impossible to say right now because stack exchange is down at the time of writing):

There's enough posts here for me to think this isn't solely a Terminal problem. You still seeing this/?

@zadjii-msft commented on GitHub (Jul 29, 2022): I'm guessing that this is somehow related to #9914. I don't know when `bash` writes out `.bash_history`, and I don't know why it would be _empty_. That would almost imply that the `bash` process totally cleared it out, which doesn't make any sense. I'm under the impression that bash just appends to it, always. That's real weird. There might be something else going on here in ubuntu land. (impossible to say right now because stack exchange is down at the time of writing): * https://askubuntu.com/questions/257249/bash-history-not-being-preserved * https://askubuntu.com/questions/372755/bash-history-not-containing-all-history-and-blank-after-reboot-how-to-resolve * https://superuser.com/questions/1239456/why-is-my-command-history-empty There's enough posts here for me to think this isn't _solely_ a Terminal problem. You still seeing this/?
claunia commented 2026-01-31 04:47:30 +00:00
Author
Owner
Copy Link

@GPHemsley-RELX commented on GitHub (Aug 1, 2022):

I only encountered it that one time, so it's hard to say. At a glance, all of those Stack Exchange posts suggest that it has something to do with permissions, so I wonder if there was some sort of race condition where the WSL drive wasn't properly set up? I don't know if that would be a thing caused by Windows or by all the security management things on my computer, though.

@GPHemsley-RELX commented on GitHub (Aug 1, 2022): I only encountered it that one time, so it's hard to say. At a glance, all of those Stack Exchange posts suggest that it has something to do with permissions, so I wonder if there was some sort of race condition where the WSL drive wasn't properly set up? I don't know if that would be a thing caused by Windows or by all the security management things on my computer, though.
claunia commented 2026-01-31 04:47:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 1, 2022):

Huh. Well, if it hasn't happened again, let's just close this out for bookkeeping's sake. If it starts happening again, or someone else starts seeing this, we can reopen and revaluate. Thanks!

@zadjii-msft commented on GitHub (Aug 1, 2022): Huh. Well, if it hasn't happened again, let's just close this out for bookkeeping's sake. If it starts happening again, or someone else starts seeing this, we can reopen and revaluate. Thanks!
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 Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#15756
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?