Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WT fails to start after Windows login #1954

Closed
angelog0 opened this issue Jul 13, 2019 · 16 comments
Closed

WT fails to start after Windows login #1954

angelog0 opened this issue Jul 13, 2019 · 16 comments
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.

Comments

@angelog0
Copy link

Even with this preview (v0.2.1831.0) I see the following.

Install WT from the Store.
Start it: all is OK. Close it.
Shutdown the PC (switch it off)
Start the PC (switch it on)
Log in to Windows
Start WT: an empty, transparent window shows up for a while then in closes: WT fails to start. Tried to start, to start, ... but does not work...

Now to start WT I have to start first MinTTY (MSYS2 terminal) or my MSYS2/MINGW64 build of Emacs from master. (Tried with Chromium, M. Store, T.Bird etc. but did not work, maybe there are other apps with wich this would work...)

Are there registry keys it writes? which?

Thanks.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 13, 2019
@DHowett-MSFT
Copy link
Contributor

Interesting. Do you happen to have a Windows Error Reporting event in your event log from when it fails to launch? We'd love to look for related crashes.

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jul 30, 2019
@miniksa miniksa added Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Product-Cmd.exe The issue is related to the legacy command interpreter, CMD.exe. Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Product-Cmd.exe The issue is related to the legacy command interpreter, CMD.exe. labels Aug 1, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 1, 2019
@angelog0
Copy link
Author

angelog0 commented Aug 4, 2019

@DHowett-MSFT, sorry for the late replay but waited for 0.3 release... I had uninstalled 0.2..

I installed 0.3 from the Store but not started it after installation. I rebooted, logged in in Windows and than started WT. It started. So closed it and rebooted another time repeating these steps: but now, it didn't start, just the empty (transparent) window (better: its contour rectangle).

With right mouse on Start I selected Event Viewer and searched under Windows registers (Windows logs could be another translation) and under Application but not found errors. Notice that I started WT at 15:14 but the logs where for 15:13 and 15:15, nothing for 15:14

May you suggest where to search? eventually from command line..

Thanks,
Angelo.

...obviously, after closing Event Viewer, retrying, WT started.

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Aug 4, 2019
@dgweller
Copy link

Similar, but not same. Under no scenario does wt successfully run on my machine.

Are there any command line params I can apply when manually launching wt.exe?

@DHowett-MSFT
Copy link
Contributor

DHowett-MSFT commented Aug 26, 2019

Would both of you mind following these feedback instructions?

@DHowett-MSFT DHowett-MSFT added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Feedback-Hub labels Aug 26, 2019
@ghost
Copy link

ghost commented Aug 26, 2019

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost ghost removed the Needs-Feedback-Hub label Aug 26, 2019
@dgweller
Copy link

Would both of you mind following these feedback instructions?

I just did that for #2535 . Thanks for reminding me!

@DHowett-MSFT
Copy link
Contributor

@dgweller no problem; I do still need that feedback link though... otherwise we can't investigate ;P

@dgweller
Copy link

Doh! I submitted once and failed to save the link. Here's a resubmitted Feedback link for my issue (I've linked to it on #2535 too)
https://aka.ms/AA5wtl6

@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 31, 2019
@ghost
Copy link

ghost commented Aug 31, 2019

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@angelog0
Copy link
Author

The only feedbak I have is that also 0.4 fails in the same manner. I don't find any core dumpor similar or messages of the failure. Maybe you have to design your application so that some log of the failure is released. Don't ask to use Feedback Hub because I don't like it and it is between bloat applications I remove after Windows installation... let me know if there is a way to start WT from command line, sometimes one can catch some output there... or simply close this: I see other users have similar failure.

BTW, some user commented the the issue could be related to powershell, but here PS works and WT starts if I start it after some other applications. Just re-read the topics.

@ghost ghost removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels Aug 31, 2019
@angelog0
Copy link
Author

May be I am wrong but in the last release (0.5+) the issue has gone.. Thanks.

Some comments/observations.

  1. Opacity/transparency. When useAcrylic is enable (for example for CMD profile) the behavior is : when the window has focus it is transparent otherwise it is opaque. I think it would be better the contrary: opaque when it has focus, transparent in the other case. Or, at least, it should have the appropriate setting.

  2. When in Ubuntu one uses less to read a text file, the mouse wheel does not work to scroll it: only up/down arrow keys work. Many terminals have that.

  3. Usually I use MinTTY from MSYS2 on Windows so I have the habit to copy/paste with the mouse double clicking and pasting with the mouse wheel. Doing that wrongly in WT did not work, obviously, but after a while I tried it caused the crash of WT (no messages etc., just disappeared... may be I had enabled copyOnSelect). Many terminal work that way.. Why not WT?

  4. Sometimes the tab width it is too short. Consider the CMD tab. It contains the icon, the string cmd and the x to close it but often just selecting this tab results in closing it because one click too near the x... May be the tabs should have a larger width even if the text it contains is short.

  5. Last but not least, why you do not introduce an option to set the position of its top-left corner so that when one launch it, the window is always in the same position (something like the initial Cols, Rows...)

@DHowett-MSFT
Copy link
Contributor

I'm surprised it started working for you. Unrelatedly, we identified an issue where it looks like on some machines the console driver just isn't automatically loaded, which speaks to a potential issue in our pseudoconsole init path.

@zadjii-msft
Copy link
Member

Hey @angelog0, a couple things:

  • First, please try and keep each issue thread specific to the issue being discussed in that issue. This particular thread is dealing with the bug of the Terminal displaying an empty window on launch.
  • Second, please search before filing new issues. As Dustin pointed out, there are issues already for each of those bullet points.
  • If you do come across an issue that's not already being tracked, please try and keep each issue to a singular problem. A big grab-bag of feedback is much harder to deal with than 5 individual issues for separate pieces of feedback.

@angelog0
Copy link
Author

angelog0 commented Sep 27, 2019

@DHowett-MSFT, I installed this new version from the store, then rebooted. Login and launch WT first time. OK. rebooted. Then many times: Login and launch WT. It started. Add MSYS2, MSYS2 MinGW32/64; change the font (first DejaVU Sans Mono installed ad hoc then Cascadia Code from WT), change the cursor to fillBox and its color for Ubuntu, MSYS2 & C., change the Ubuntu icon to ubuntu.png... It always starts in the procedure described above!

Since the last time I had installed WT there was a new W10 monthly update and I decided to uninstall LibreOffice installed from the msi and to install only the portable version (unpacking with 7z the paf.exe, more or less a manual installation)

The only issue I have now with WT: it crashes copy/pasting, too often but, at the moment, I have not a recipe to reproduce it systematically.

@zadjii-msft, sorry for the noise.

@zadjii-msft
Copy link
Member

Hey @angelog0 I'm just scrolling through our backlog of old issues, looks like this one got a little lost. Since this specific issue does seem like it was resolved a while ago for you, I'm gonna close this thread out. Thanks!

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Jun 1, 2020
@zadjii-msft zadjii-msft added Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely. and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-TerminalControl Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.
Projects
None yet
Development

No branches or pull requests

5 participants