-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Import-Clixml Error when opening Terminal #126
Comments
We would want to see the output from the below after the error. get-error -last 2 Additionally, does the same error happen when you load PowerShell Core with no profile? You launch with Lastly, it is possibly related to #121. |
If you don't mind 1 second delay below profile works for me with a 2x2 split terminal startup with pwsh 7.4.5
|
Similar error for me: import-module terminal-icons
Import-Clixml: Value for dictionary entry is not specified. Line 603, position 40. Full error: PSMessageDetails :
Exception : System.Xml.XmlException: Value for dictionary entry is not specified. Line 603, position 40.
at System.Management.Automation.InternalDeserializer.ReadDictionary(ContainerType ct, ConsolidatedString
InternalTypeNames)
at System.Management.Automation.InternalDeserializer.ReadPSObject()
at System.Management.Automation.InternalDeserializer.ReadOneDeserializedObject(String& streamName, Boolean&
isKnownPrimitiveType)
at System.Management.Automation.InternalDeserializer.ReadOneObject(String& streamName)
at System.Management.Automation.InternalDeserializer.ReadDictionary(ContainerType ct, ConsolidatedString
InternalTypeNames)
at System.Management.Automation.InternalDeserializer.ReadPSObject()
at System.Management.Automation.InternalDeserializer.ReadOneDeserializedObject(String& streamName, Boolean&
isKnownPrimitiveType)
at System.Management.Automation.InternalDeserializer.ReadOneObject(String& streamName)
at System.Management.Automation.InternalDeserializer.ReadDictionary(ContainerType ct, ConsolidatedString
InternalTypeNames)
at System.Management.Automation.InternalDeserializer.ReadPSObject()
at System.Management.Automation.InternalDeserializer.ReadOneDeserializedObject(String& streamName, Boolean&
isKnownPrimitiveType)
at System.Management.Automation.InternalDeserializer.ReadOneObject(String& streamName)
at System.Management.Automation.Deserializer.Deserialize(String& streamName)
at System.Management.Automation.Deserializer.Deserialize()
at Microsoft.PowerShell.Commands.ImportXmlHelper.Import()
at Microsoft.PowerShell.Commands.ImportClixmlCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
TargetObject :
CategoryInfo : NotSpecified: (:) [Import-Clixml], XmlException
FullyQualifiedErrorId : System.Xml.XmlException,Microsoft.PowerShell.Commands.ImportClixmlCommand
ErrorDetails :
InvocationInfo : System.Management.Automation.InvocationInfo
ScriptStackTrace : at <ScriptBlock>, C:\Users\jakew\OneDrive\Documents\PowerShell\Modules\terminal-icons\0.11.0\Terminal-Icons.psm1: line
3419
at <ScriptBlock>, C:\Users\jakew\OneDrive\Documents\PowerShell\Modules\terminal-icons\0.11.0\Terminal-Icons.psm1: line
3418
at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {} When exploring these lines in (Get-ChildItem $userThemePath -Filter '*_icon.xml').ForEach({
$userIconTheme = Import-CliXml -Path $_.FullName
$userThemeData.Themes.Icon[$userIconTheme.Name] = $userIconTheme
}) I found that This location did not contain the expected xml files, thus why this error was occuring. My workaround to address this for me was:
The above steps caused the module to create a: |
Current Behavior
I get an error randomly when i open the terminal, it only gives an error at launch.
Error Message:
(yesterday, when i checked i received this error message)
(this error i just received)
Steps to Reproduce (for bugs)
Opening the terminal randomly gives the error, sometimes i see the error, othertimes i don't.
The error doesn't seem to be causing any issues with the terminal, most probably just a visual error.
Your Environment
OS Version: Windows 10(22H2)
Terminal: Powershell 7.4.1
I'm using ohmyposh and Terminal-Icons powershell modules
The text was updated successfully, but these errors were encountered: