WT fails to start after Windows login #2742

@DHowett-MSFT commented on GitHub (Jul 25, 2019):

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.

@DHowett-MSFT commented on GitHub (Jul 25, 2019): 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.

claunia commented

@angelog0 commented on GitHub (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.

@angelog0 commented on GitHub (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.

claunia commented

@dgweller commented on GitHub (Aug 26, 2019):

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?

@dgweller commented on GitHub (Aug 26, 2019): 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?

claunia commented

@DHowett-MSFT commented on GitHub (Aug 26, 2019):

Would both of you mind following these feedback instructions?

@DHowett-MSFT commented on GitHub (Aug 26, 2019): Would both of you mind following these feedback instructions?

claunia commented

@ghost commented on GitHub (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!

@ghost commented on GitHub (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](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)

claunia commented

@dgweller commented on GitHub (Aug 26, 2019):

Would both of you mind following these feedback instructions?

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

@dgweller commented on GitHub (Aug 26, 2019): > Would both of you mind following these feedback instructions? I just did that for #2535 . Thanks for reminding me!

claunia commented

@DHowett-MSFT commented on GitHub (Aug 27, 2019):

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

@DHowett-MSFT commented on GitHub (Aug 27, 2019): @dgweller no problem; I do still need that feedback link though... otherwise we can't investigate ;P

claunia commented

@dgweller commented on GitHub (Aug 27, 2019):

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

@dgweller commented on GitHub (Aug 27, 2019): 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

claunia commented

@ghost commented on GitHub (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.

@ghost commented on GitHub (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**.

claunia commented

@angelog0 commented on GitHub (Aug 31, 2019):

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.

@angelog0 commented on GitHub (Aug 31, 2019): The only feedbak I have is that also 0.4 fails in the same manner. I don't find any `core dump`or 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.

claunia commented

@angelog0 commented on GitHub (Sep 27, 2019):

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

Some comments/observations.

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.
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.
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?
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.
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...)

@angelog0 commented on GitHub (Sep 27, 2019): 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`...)

claunia commented

@DHowett-MSFT commented on GitHub (Sep 27, 2019):

#1375 acrylic is "flipped" by system policy, there's a heated debate on it going on right now
#376 Garbled output from pipenv in a WSL window (#545)
#2807 Feature Request: name on tabs (#2927)
#597 and you can set the tab title with the tabTitle profile option
Set the social media image for the project ... (#1043)

@DHowett-MSFT commented on GitHub (Sep 27, 2019): 1. #1375 acrylic is "flipped" by system policy, there's a heated debate on it going on right now 2. #376 #545 3. #2807 #2927 3. #597 and you can set the tab title with the `tabTitle` profile option 5. #1043

claunia commented

@DHowett-MSFT commented on GitHub (Sep 27, 2019):

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.

@DHowett-MSFT commented on GitHub (Sep 27, 2019): 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.

claunia commented

@zadjii-msft commented on GitHub (Sep 27, 2019):

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.

@zadjii-msft commented on GitHub (Sep 27, 2019): 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.

claunia commented