Skip to content

Attempting to run a second instance of Chocolatey GUI quitely errors and doesn't show the user anything #1099

@gep13

Description

@gep13

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

When Chocolatey GUI is already running on a machine, if you attempt to run a second instance of it, say while you are logged in as another user, the application silently fails, with no clear indication of what happened, and why Chocolatey GUI isn't running.

You can see this happening as well when trying to run chocolateyguicli when Chocolatey GUI is already running. You can see the following (i.e. nothing is being output from the command):

Image

when you should see the following being output from Chocolatey GUI CLI:

Image

Describe The Solution. Why is it needed?

Currently, Chocolatey GUI estabishes an exclusive lock on the configuration database that is used to store the Chocolatey GUI configuration. As a result, another instance of Chocolatey GUI can't get access to it, and can't start. This happens quietly, so it is not immediately clear what is going on.

Chocolatey GUI should notify the end-user that there is already another instance of Chocolatey GUI running, and throw an error.

Additional Context

If/when this issue is addressed, the documentation that was added in this PR on the docs repository should be updated to explain what now happens.

Related Issues

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions