Skip to content
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

Chocolatey GUI does not start if the config folder is missing from C:\ProgramData\Chocolatey GUI #996

Closed
4 tasks done
imm0rtalsupp0rt opened this issue Apr 20, 2023 · 1 comment
Assignees
Labels
5 - Released The issue has been resolved, and released to the public for consumption Bug Issues where something has happened which was not expected or intended
Milestone

Comments

@imm0rtalsupp0rt
Copy link

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my problem.
  • I have verified this is not an issue for a specific package.
  • I have verified this issue is not security related.

What You Are Seeing?

While troubleshooting another issue, we noticed that after deleting the Config folder from C:\ProgramData\Chocolatey GUI and the data.db file from C:\Users\<USER>\AppData\Local\Chocolatey GUI that the data.db file was recreated in the Users directory, but the Config folder was not recreated in the ProgramData directory upon trying to start Chocolatey GUI.

Without the Config folder present, Chocolatey GUI will not start.

What is Expected?

If the Config folder is not present, Chocolatey GUI should recreate it upon startup.

How Did You Get This To Happen?

  1. Deleted the Config folder from C:\ProgramData\Chocolatey GUI and the data.db file from C:\Users\<USER>\AppData\Local\Chocolatey GUI.
  2. Tried to launch Chocolatey GUI from the Start menu and from the CLI and it would not start.
  3. Witnessed the data.db file being recreated in the User directory, and noticed that the Config folder was not recreated in the ProgramData directory.

System Details

  • Operating System: Windows Server 2019
  • Windows PowerShell version: 5
  • Chocolatey CLI Version: 1.3.1
  • Chocolatey Licensed Extension version: 5.0.2
  • Chocolatey License type: Business

Installed Packages

Chocolatey GUI 1.1.2
Chocolatey GUI Extension 1.0.2

Output Log

N/A

Additional Context

Found while troubleshooting for chocolatey/chocolatey-licensed-issues#395

@imm0rtalsupp0rt imm0rtalsupp0rt added Bug Issues where something has happened which was not expected or intended 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue labels Apr 20, 2023
@pauby pauby added this to the 2.2.0 milestone Jun 28, 2023
@gep13 gep13 modified the milestones: 2.2.0, 2.1.1 Apr 22, 2024
@gep13 gep13 added 2 - Working A user or team member has started working on the issue and removed 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue labels Apr 22, 2024
corbob added a commit to corbob/ChocolateyGUI that referenced this issue Apr 22, 2024
If the directory for a LiteDatabase doesn't exist, LiteDatabase will not
attempt to create it, and will throw an exception because it can't
create the file without the parent directory. This ensures that the
folder exists before trying to create the database.
corbob added a commit to corbob/ChocolateyGUI that referenced this issue Apr 24, 2024
If the directory for a LiteDatabase doesn't exist, LiteDatabase will not
attempt to create it, and will throw an exception because it can't
create the file without the parent directory. This ensures that the
folder exists before trying to create the database.
@corbob corbob added 3 - Review Code has been added, and is available for review as a pull request and removed 2 - Working A user or team member has started working on the issue labels Apr 25, 2024
gep13 added a commit that referenced this issue Apr 26, 2024
(#996) Create config directory if it doesn't exist
@corbob corbob added 4 - Done Code has been added to the repository, and has been reviewed by a team member and removed 3 - Review Code has been added, and is available for review as a pull request labels Apr 29, 2024
@corbob corbob closed this as completed Apr 29, 2024
@corbob corbob changed the title Chocolatey GUI does not start if the Config folder is missing from C:\ProgramData\Chocolatey GUI. Chocolatey GUI Does Not Start if the Config Folder is Missing From C:\ProgramData\Chocolatey GUI. Apr 29, 2024
corbob added a commit that referenced this issue Apr 29, 2024
* hotfix/2.1.1:
  (build) Switch to a PowerShell step
  (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/'
  (build) Bump Recipe package to latest version
  (maint) Remove unnecessary whitespace
  (#996) Create config directory if it doesn't exist
  (maint) Remove unused pragmas
  (#967) Parse Info for Error, Warn, and Fatal
@corbob corbob changed the title Chocolatey GUI Does Not Start if the Config Folder is Missing From C:\ProgramData\Chocolatey GUI. Chocolatey GUI does not Start if the config folder is missing from C:\ProgramData\Chocolatey GUI Apr 29, 2024
@corbob corbob changed the title Chocolatey GUI does not Start if the config folder is missing from C:\ProgramData\Chocolatey GUI Chocolatey GUI does not start if the config folder is missing from C:\ProgramData\Chocolatey GUI Apr 29, 2024
@corbob corbob added 5 - Released The issue has been resolved, and released to the public for consumption and removed 4 - Done Code has been added to the repository, and has been reviewed by a team member labels Apr 29, 2024
@corbob
Copy link
Member

corbob commented Apr 29, 2024

🎉 This issue has been resolved in version 2.1.1 🎉

The release is available on:

Your GitReleaseManager bot 📦 🚀

corbob added a commit that referenced this issue Apr 29, 2024
* master:
  (build) Switch to a PowerShell step
  (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/'
  (build) Bump Recipe package to latest version
  (maint) Remove unnecessary whitespace
  (#996) Create config directory if it doesn't exist
  (maint) Remove unused pragmas
  (#967) Parse Info for Error, Warn, and Fatal
  (maint) Remove mention of services no longer used
  (tests) Update Pester tests to be consistent
  (tests) Move the Pester tests to be consistent
  (maint) synced local '.templates/' with remote '.github/GitReleaseManager/.templates/'
  (maint) Update GRM configuration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Released The issue has been resolved, and released to the public for consumption Bug Issues where something has happened which was not expected or intended
Projects
None yet
Development

No branches or pull requests

4 participants