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

[Feature] Perhaps automatic restart should not be performed after the update is completed #132

Open
2 tasks done
YCZ01111 opened this issue Oct 12, 2024 · 3 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@YCZ01111
Copy link

Before Requesting

  • I found no existing issue matching my feature request
  • This request is related to Millennium, and not a request for a specific theme/addon

Describe the feature you'd like!

In China, due to ISP settings, checking for updates and downloading Millennium can be very slow, which can result in early loading of SteamUI. During playing games, if Millennium detects an update or the latest version has been downloaded, it may cause Steam to automatically restart. Perhaps tasks related to Millennium updates should not be performed during SteamUI's work period, or automatic restarts should not be performed after the update is completed.
Of course, I know how to set check_for-updates to no, but doing so may cause errors on port 8080 for a few people. Until now, we still don't know why port 8080 is related to check_for-updates.

Anything else?

No response

@YCZ01111 YCZ01111 added the enhancement New feature or request label Oct 12, 2024
@shdwmtr
Copy link
Collaborator

shdwmtr commented Oct 12, 2024

The issue with port 8080 should have been fixed last update. I'll see what do-able with the updates issue though.

@shdwmtr shdwmtr changed the title [Feature]Perhaps automatic restart should not be performed after the update is completed [Feature] Perhaps automatic restart should not be performed after the update is completed Oct 12, 2024
@YCZ01111
Copy link
Author

The Millennium version I am currently sharing with my audience is 2.12.3, but a few people still encounter the issue with port 8080 due to set check_for-updates to no. I haven't noticed anyone else reporting this issue, but it doesn't seem like it's caused by a Chinese ISP either.

@shdwmtr
Copy link
Collaborator

shdwmtr commented Oct 12, 2024

there is a 2.12.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants