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

Crash on About dialog when running Terminal unpackaged #2910

New Issue
Closed
opened 2026-01-30 23:08:35 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:08:35 +00:00
Owner
Copy Link

Originally created by @driver1998 on GitHub (Jul 24, 2019).

Originally assigned to: @zadjii-msft on GitHub.

Environment

Windows build number: [run "ver" at a command prompt] 10.0.18941.1001
Windows Terminal version (if applicable): commit 9d36b08b82c67c6965263c63bb83b024c15f3474

Any other software?

I know it is not a supported scenario, but with https://github.com/microsoft/terminal/pull/2043 we can now run Terminal unpackaged.
And some people might prefer it this way.

Steps to reproduce

Run WindowsTerminal.exe directly, outside of app package.
Click about in the drop down menu.

Expected behavior

The about dialog show up as normal.

Actual behavior

The app crashes.

Originally created by @driver1998 on GitHub (Jul 24, 2019). Originally assigned to: @zadjii-msft on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [run "ver" at a command prompt] 10.0.18941.1001 Windows Terminal version (if applicable): commit 9d36b08b82c67c6965263c63bb83b024c15f3474 Any other software? ``` I know it is not a supported scenario, but with https://github.com/microsoft/terminal/pull/2043 we can now run Terminal unpackaged. And some people might prefer it this way. # Steps to reproduce Run WindowsTerminal.exe directly, outside of app package. Click about in the drop down menu. <!-- A description of how to trigger this bug. --> # Expected behavior The about dialog show up as normal. # Actual behavior The app crashes.
claunia commented 2026-01-30 23:08:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 24, 2019):

I'm going to chime in and say if #2043 made this work a little, I kinda want to make sure it keeps working. Before we went open-source, there was a time you could build and run the terminal from the commandline, using unpackaged activation like this. At some point it broke, and we just never had the time to investigate. If #2043 fixes launching, then I'm inclined to leave this open to track fixing this entirely.

@zadjii-msft commented on GitHub (Jul 24, 2019): I'm going to chime in and say if #2043 made this work a little, I kinda want to make sure it keeps working. Before we went open-source, there was a time you could build and run the terminal from the commandline, using unpackaged activation like this. At some point it broke, and we just never had the time to investigate. If #2043 fixes launching, then I'm inclined to leave this open to track fixing this entirely.
claunia commented 2026-01-30 23:08:37 +00:00
Author
Owner
Copy Link

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

This actually also fails in the packaged version. 😄

@DHowett-MSFT commented on GitHub (Jul 24, 2019): This actually also fails in the packaged version. :smile:
claunia commented 2026-01-30 23:08:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2019):

I'm leaving a note to myself here: When the trying to run the terminal unpackaged, the resources.pri from CascadiaPackage is what you need. You can double-click WindowsTerminal.exe when you copy that file out of CascadiaPackage's output into bin\%ARCH%\%CONFIGURATION%, and launch the WindowsTerminal.exe in that folder. Running the WindowsTerminal.exe in the CascadiaPackage directory shockingly doesn't work.

However, I think we only build the resources.pri file if we build CascadiaPackage, so trying to only build WindowsTerminal then running it won't work. Hmmmm.

@zadjii-msft commented on GitHub (Jul 25, 2019): I'm leaving a note to myself here: When the trying to run the terminal unpackaged, the `resources.pri` from `CascadiaPackage` is what you need. You can double-click WindowsTerminal.exe when you copy that file out of CascadiaPackage's output into `bin\%ARCH%\%CONFIGURATION%`, and launch the WindowsTerminal.exe in that folder. Running the WindowsTerminal.exe in the CascadiaPackage directory shockingly doesn't work. However, I think we only build the resources.pri file if we build CascadiaPackage, so trying to _only_ build WindowsTerminal then running it won't work. Hmmmm.
claunia commented 2026-01-30 23:08:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2019):

This should maybe block v0.3. You can't open the about dialog at all, so we're going to get 100 dupes for this, and bug reports are going to become impossible to track.

  🌛
💪 💪
  👖
@zadjii-msft commented on GitHub (Jul 25, 2019): This should maybe block v0.3. You can't open the about dialog at all, so we're going to get 100 dupes for this, and bug reports are going to become impossible to track. ``` 🌛 💪 💪 👖 ```
claunia commented 2026-01-30 23:08:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2019):

So this seems to be related to the NavigateUri property on the Hyperlinks in the about dialog. If you remove those NavigateUri's, then it'll display just fine (but obviously not work).

Maybe we hack a workaround for now?

@zadjii-msft commented on GitHub (Jul 25, 2019): So this seems to be related to the `NavigateUri` property on the Hyperlinks in the about dialog. If you remove those `NavigateUri`'s, then it'll display just fine (but obviously not work). Maybe we hack a workaround for now?
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-UserInterface Issue-Bug Needs-Triage Product-Terminal Resolution-Fix-Committed Severity-Crash
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#2910
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?