I just upgraded from 5.?? to 7.0.2. When I open Kicad, then create new project, then click on schematic, or preferences/manage symbol libraries, or preferences/preferences, the schematic never opens and the project viewer hangs. When I try to open an existing schematic (from 5.1 version) it also gives me the data collection opt in dialog then nothing.
I am using the same version at work with no problem, but it has different custom libraries, etc, and maybe different computer settings.
Is there a log file I can see or any debugging hints. I have never this kind of issue before so not sure how to debug.
Also, assuming it is something wrong with my setup, where do I remove any custom libraries in case that is the problem.
Some people have experienced issues where the old personal config files from v5 are present. They are located in ~/.config/kicad on Linux and the equivalent directory (don’t know it off the top of my head) on Windows. Move those out of the way, then run KiCad v7 again and it will give you a fresh start.
Deleted c:\Users\Username\AppData\Local\KiCad, c:\Users\Username\AppData\Roaming\KiCad, uninstalled KiCad, rebooted, installed KiCad and it worked. Your comments sent me in the right direction, and I see that others also had these problems which stem from choosing to import the library file table from previous version rather than choosing default libraries. Importing the linbrary list seems like the right thing to do, but is a definite no-no. Thanks again.
In case this helps some one nail down the issue, just a reboot fixes it for me. Its weird this didn’t happen on 7.0.1 or 7.0.0 but is on 7.0.2. I am on a fresh windows 10 install.(because of mb/cpu upgrade) So for me its not an old profile issue. The only thing that may be odd is that I have an older amd R9 290 video card and an on board ryzen5 on board GPU.
Been trying to nail down the issue to file a bug report but I cant find a repeatable way to make it happen. The only thing i can somewhat say is opening a file after windows goes into sleep or off a mapped drive seams to make it happen more often, but not consistently. And if it happens once until you reboot it will happen on every file.
Another thing that helps is opening the PCB file before the schematic file, makes it more likely to work.
Yeah I agree but not 100% shure if its different, i am mostly curious if another person have issues as well to compare notes (this is the first google result) but its weird, and there no disk io at the time just eschma stuck on a locked up state(not responding).
OK so my unrelated issues was related to the on board GPU Disabling it in windows device manger
has fixed it. There may be some gpu issues with ryzen5 on board gpus with windows/kicad.
