Posted November 20, 2019
Since the update today, my Galaxy 2.0 installations on both of my machines display the "Importing - 99%" message for about 5 minutes. While it is displayed, a bunch of cover art is missing and slowly loads in as it goes.
Additionally, other cover art I've set for months now is missing. On top of that, I'm unable to change any of these incorrect cover arts, it just switches back to the old one after about 9 seconds, no matter how many times I try.
I did a complete fresh reinstall of Galaxy 2.0 on my desktop and let it re-import my data but I'm still having the exact same problems (takes a very long time to start the program, cannot fix incorrect cover art, etc).
Has anyone else run into this issue or is it just me? I'd think it was just some freak issue, but that it happens on two completely different machines, even after a fresh install leads me to believe there is something wrong with my account and the data it is pulling from, or there is some conflict with software I have installed on both computers, but no way to really nail down what it could be.
I already reported the bug via the cog wheel, but I was curious if anyone else has run into this, figured out what is causing it, or figured out a fix yet.
Additionally, other cover art I've set for months now is missing. On top of that, I'm unable to change any of these incorrect cover arts, it just switches back to the old one after about 9 seconds, no matter how many times I try.
I did a complete fresh reinstall of Galaxy 2.0 on my desktop and let it re-import my data but I'm still having the exact same problems (takes a very long time to start the program, cannot fix incorrect cover art, etc).
Has anyone else run into this issue or is it just me? I'd think it was just some freak issue, but that it happens on two completely different machines, even after a fresh install leads me to believe there is something wrong with my account and the data it is pulling from, or there is some conflict with software I have installed on both computers, but no way to really nail down what it could be.
I already reported the bug via the cog wheel, but I was curious if anyone else has run into this, figured out what is causing it, or figured out a fix yet.