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

"One or more resources (such as icon or backgroundImage) specified in your settings could not be found." error with valid icon URL #24025

New Issue
Closed
opened 2026-01-31 08:59:18 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:59:18 +00:00
Owner
Copy Link

Originally created by @sba923 on GitHub (Jan 29, 2026).

Windows Terminal version

1.24.10212.0

Windows build number

10.0.19045.6809.amd64fre.vb_release.191206-1406

Other Software

No response

Steps to reproduce

Use the following icon URL in a profile:

            {
                "guid": "{51855cb2-8cce-5362-8f54-464b92b32386}",
                "hidden": false,
                "icon": "https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png",
                "name": "Ubuntu",
                "source": "CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc"
            }

The https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png is valid, but this generates an error:

Image

Removing the "icon": "https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png", line makes the error disappear.

Expected Behavior

The profile should use the icon at https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png

Image

Actual Behavior

Windows Terminal emits the following error:

Image
Originally created by @sba923 on GitHub (Jan 29, 2026). ### Windows Terminal version 1.24.10212.0 ### Windows build number 10.0.19045.6809.amd64fre.vb_release.191206-1406 ### Other Software _No response_ ### Steps to reproduce Use the following icon URL in a profile: ``` { "guid": "{51855cb2-8cce-5362-8f54-464b92b32386}", "hidden": false, "icon": "https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png", "name": "Ubuntu", "source": "CanonicalGroupLimited.Ubuntu_79rhkp1fndgsc" } ``` The `https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png` is valid, but this generates an error: <img width="1244" height="642" alt="Image" src="https://github.com/user-attachments/assets/09ea0403-51d5-4aab-ad8f-dfb4c49dce8c" /> Removing the `"icon": "https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png",` line makes the error disappear. ### Expected Behavior The profile should use the icon at `https://assets.ubuntu.com/v1/49a1a858-favicon-32x32.png` <img width="64" height="64" alt="Image" src="https://github.com/user-attachments/assets/5f8f57c0-c4df-44c6-a048-0cb6695b1b1c" /> ### Actual Behavior Windows Terminal emits the following error: <img width="1244" height="642" alt="Image" src="https://github.com/user-attachments/assets/b27264bc-3ad0-4f73-b7e5-b8502b32ea2f" />
claunia added the Resolution-By-DesignNeeds-TriageIssue-Bug labels 2026-01-31 08:59:18 +00:00
claunia commented 2026-01-31 08:59:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 29, 2026):

Hey. I know this sucks. For both security and reliability reasons, we had to disable icons (images, shaders, sounds) being downloaded directly from the web.

We got a couple sporadic reports that Terminal would try to make outgoing connections during startup.

It turns out that XAML's Image element automatically downloads web images. We never opted in for this, so it was somewhat of an accidental misfeature.

We realized pretty quickly that these could be used as tracking pixels (sending a ping to a server every time settings reloads, or every time Terminal launches). It also led to delays on launch while XAML ran downloads (mind you, it used the Internet Explorer engine to do so).

We could have added some aggressive caching, but honestly... the juice wasn't worth the squeeze. It would still be a risk and a danger, and it would still mess up our reliability stats.

Not LLM-written, I'm just long-winded.

@DHowett commented on GitHub (Jan 29, 2026): Hey. I know this sucks. For both security and reliability reasons, we had to disable icons (images, shaders, sounds) being downloaded directly from the web. We got a couple sporadic reports that Terminal would try to make outgoing connections during startup. It turns out that _XAML's `Image` element_ automatically downloads web images. We never opted in for this, so it was somewhat of an accidental misfeature. We realized pretty quickly that these could be used as tracking pixels (sending a ping to a server every time settings reloads, or every time Terminal launches). It also led to delays on launch while XAML ran downloads (mind you, it used the Internet Explorer engine to do so). We could have added some aggressive caching, but honestly... the juice wasn't worth the squeeze. It would still be a risk and a danger, and it would still mess up our reliability stats. Not LLM-written, I'm just long-winded.
claunia commented 2026-01-31 08:59:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 29, 2026):

(For that profile specifically, you may also be able to inherit the icon field and have it perhaps maybe just work.)

@DHowett commented on GitHub (Jan 29, 2026): (For that profile specifically, you may also be able to `inherit` the icon field and have it perhaps maybe just work.)
claunia commented 2026-01-31 08:59:19 +00:00
Author
Owner
Copy Link

@sba923 commented on GitHub (Jan 30, 2026):

@DHowett I also love to take the long and winding road.

I had intuited that some security-driven blocking had been put in place, your answer has just confirmed that.

But I didn't add that URL to my config file, this was probably inherited from restoring data from an old file that had been auto-populated by an earlier version of Windows Terminal.

Because of that, I would have expected a different behavior.

The new versions that don't support that anymore should emit a clear message along the "this is no longer supported" lines. With a clear reference to the unsupported entry. Stating that the resource cannot be found is... plain wrong if you ask me. Would creating an issue for that make sense?

@sba923 commented on GitHub (Jan 30, 2026): @DHowett I also love to take the long and winding road. I had intuited that some security-driven blocking had been put in place, your answer has just confirmed that. But I didn't add that URL to my config file, this was probably inherited from restoring data from an old file that had been auto-populated by an earlier version of Windows Terminal. Because of that, I would have expected a different behavior. The new versions that don't support that anymore should emit a clear message along the "this is no longer supported" lines. With a clear reference to the unsupported entry. Stating that the resource cannot be found is... plain wrong if you ask me. Would creating an issue for that make sense?
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 Issue-Bug Needs-Triage Resolution-By-Design
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#24025
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?