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

[Bug] 1.31.2 Locks up (not responding) on Windows 11 on clicks #3709

Closed
btgoodwin opened this issue Nov 17, 2022 · 3 comments
Closed

[Bug] 1.31.2 Locks up (not responding) on Windows 11 on clicks #3709

btgoodwin opened this issue Nov 17, 2022 · 3 comments
Labels
Duplicate Duplicate of another issue

Comments

@btgoodwin
Copy link

Background

  • Operating System: Windows 11 22h2
  • CKAN Version: 1.31.2
  • KSP Version: 1.12.4.3187

I have installed Parallax 2.0.4 and stock scatter textures by hand since the published ones are broken (or at least they have been since 2.0.0 was released).

Problem

CKAN automatically updated itself, then asked to upgrade (reinstall) all mods because metadata changed. I permitted it to do both the update and upgrade. I then noticed it reported the installed version of Parallax as 2.0.0 despite the latest being 2.0.4, so I clicked Refresh and CKAN became non-responsive. I had to forcefully quit the app.

I then re-opened CKAN and tried clicking Apply Changes. Again, it locked up and I had to forcefully close the program.

Re-opening CKAN, I clicked the checkbox next to Parallax for the Update column. Again, it locked up, force close.

I then tried reinstalling CKAN straight from the EXE published on GitHub (here) and had the same result in all situations.

Finally, I tried running CKAN as admin and achieved the same result in all situations.

Expected behavior

I would expect the program not to lock up.

CKAN error code (if applicable):

No error codes were present.

@HebaruSan HebaruSan added the Duplicate Duplicate of another issue label Nov 17, 2022
@HebaruSan
Copy link
Member

Thanks, we just finished fixing this, you can try the latest dev build if you'd like to test:

@HebaruSan
Copy link
Member

Duplicate of #3707

@HebaruSan HebaruSan marked this as a duplicate of #3707 Nov 17, 2022
@btgoodwin
Copy link
Author

That did it for me. Sorry for the duplicate ticket; I didn't realize these were related, but that new version fixed it for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate Duplicate of another issue
Projects
None yet
Development

No branches or pull requests

2 participants