Chocolatey GUI Not Displaying Error Output When Running as Non-Admin Through Background Service #327
Labels
0 - Backlog
Where tickets start after being triaged. This means the ticket has targeted milestone/labels.
Bug
Tickets that represent defects/bugs.
LicensedExtension
Issues affecting the Chocolatey Licensed Extension (chocolatey.extension)
Is Your Feature Request Related To A Problem? Please describe.
When installing a package through Chocolatey GUI. With the background service enabled and logged into the PC as a non-admin user. Chocolatey GUI says their is an error but does not give you the full content of the error message.
Describe The Solution. Why is it needed?
This would help in easier troubleshooting if the full error was emitted within Chocolatey GUI instead of having to dig into the chocolatey log to ascertain the contents of the actual error that occurred.
Steps to Reproduce Behavior
choco new throw-message --version 1.0.0
choco pack
against the .nuspec file to generate the throw-message.1.0.0.nupkgchoco source add -n Local -s C:\temp --allow-self-service
the self-service will be needed for non-admin testing of the package.choco feature enable -n useBackgroundService
, the chocolatey-agent package installed, and the useBackgroundServiceWithNonAdministratorsOnly feature enabled.choco install throw-message -y
. You should get the following output:choco install throw-message -y
now being logged in to the PC as a non-admin user. The output from this:As you can see the GUI output from the 2 users is different. One shows the complete error where as the non-admin does not. Also if you look into the CLI output more you can notice the admin user's is highlighted red to indicate an error. Where the non-admin's same output is in white text, usually indicating standard/info output.
Reproduction Enviornment
OS Version: Windows 10 V 10.0.19045.0 Powershell Version: 5.1.19041.1682 Chocolatey Version: 1.1.0
Choco list -lo output from system:
Additional Context.
Related Issues
┆Issue is synchronized with this Gitlab issue by Unito
The text was updated successfully, but these errors were encountered: