<h1 dir="auto">Environment</h1>
<p dir="auto">Introduced by <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="480323636" data-permission-text="Title is private" data-url="https://github.com/microsoft/terminal/issues/2422" data-hovercard-type="pull_request" data-hovercard-url="/microsoft/terminal/pull/2422/hovercard" href="https://github.com/microsoft/terminal/pull/2422">#2422</a></p>
<p dir="auto">Since we'll be defaulting to the Windows Terminal default settings, this means that the user may be working with profiles that don't exist AFTER the proper settings are imported. Below is an example of such a case, but several other places may cause the same issue to arise.</p>
<p dir="auto">I'd bet that this is because we usually use "FindProfile()" (or something like that) and we just don't handle that properly.</p>
<h1 dir="auto">Steps to reproduce</h1>
<ul dir="auto">
<li>create a tab from the WT default settings</li>
<li>import your custom settings</li>
<li>duplicate the created tab</li>
</ul>
<h1 dir="auto">Expected behavior</h1>
<p dir="auto">Not sure. Maybe a dialogue box saying "This operation could not be completed"?</p>
<h1 dir="auto">Actual behavior</h1>
<p dir="auto">CRASH!</p>
<h1 dir="auto">Environment</h1>
<p dir="auto">Windows Terminal version: Version: 0.6.2951.0<br>
Microsoft Windows [Version 10.0.18362.418]</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<ol dir="auto">
<li>Install Ubuntu 18.04 (on WSL 1.0), install minicom inside Ubuntu.</li>
<li>Open Windows Terminal and run Ubuntu 18.04</li>
<li>Open minicom from Windows Terminal and try to capture serial console message from any embedded dev. board (say Raspberry PI)</li>
<li>You will see messages scrolling above the view port. If you scroll up you won't see the messages from the minicom.</li>
</ol>

<h1 dir="auto">Expected behavior</h1>
<p dir="auto">If I scroll up, I should be able to see the serial console messages from my embedded target.</p>

<h1 dir="auto">Actual behavior</h1>
<p dir="auto">Scroll up shows my command that I typed long ago. The serial console message is lost. If I run Ubuntu terminal directly (instead of doing the same from Windows Terminal), I could scroll up and see right messages.</p>

<p dir="auto">Not sure, may be ncurses behavior is not compatible with Windows Terminal's expectations?</p>