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

Komga not checking if it's already running #1336

Closed
5 tasks done
Chirishman opened this issue Dec 8, 2023 · 2 comments
Closed
5 tasks done

Komga not checking if it's already running #1336

Chirishman opened this issue Dec 8, 2023 · 2 comments
Labels
consider Not sure yet if this makes sense or not released

Comments

@Chirishman
Copy link

Steps to reproduce

Start Komga server twice on Windows

Expected behavior

Some kind of message/warning about the fact that it is already running and a clean exit of the second instance.

Actual behavior

image

Logs

No response

Komga version

1.8.4

Operating system

Windows 11

Installation method

from download.komga.org

Other details

I ran the installer and didn't immediately see the icon in the system tray, so I went to the start menu and started Komga, unaware that the installer automatically kicks it off. I was then presented with the above error message and thought I had a bad/corrupt install.

Acknowledgements

  • I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I have checked the FAQ.
  • I have updated the app to the latest version.
  • I will fill out all of the requested information in this form.
@Chirishman
Copy link
Author

Looks like I'm not the only one who has been caught/confused by this: #1298

Usually installers have a little check box at the last step asking if you want to run it right away which I don't remember seeing when installing this. Some kind of cue like that as well as gracefully handling this might be a good improvement here.

@gotson gotson added consider Not sure yet if this makes sense or not and removed triage labels Dec 8, 2023
@gotson gotson closed this as completed in 0fdcb2a Dec 11, 2023
gotson added a commit that referenced this issue Dec 12, 2023
Copy link
Contributor

🎉 This issue has been resolved in 1.9.0 (Release Notes)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
consider Not sure yet if this makes sense or not released
Projects
None yet
Development

No branches or pull requests

2 participants