Kicad-nightly-9.0.0.rc1 problem with

I can’t open normally project from version 8.xx in Kicad 9.0:
error 2 and 5.
It is first time i got this.
Windows 11, Kicad 8.0.7 work normally, 9.0 not.

Application: KiCad x64 on x64

Version: 9.0.0-rc1-165-g19c748048c, release build

Libraries:
wxWidgets 3.2.6
FreeType 2.13.3
HarfBuzz 10.0.1
FontConfig 2.15.0
libcurl/8.10.1-DEV Schannel zlib/1.3.1

Platform: Windows 11 (budowa 26100), wydanie 64-bitowe, 64 bit, Little endian, wxMSW

Build Info:
Date: Dec 30 2024 06:17:19
wxWidgets: 3.2.6 (wchar_t,wx containers)
Boost: 1.86.0
OCC: 7.8.1
Curl: 8.10.1-DEV
ngspice: 43
Compiler: Visual C++ 1942 without C++ ABI
KICAD_IPC_API=ON

Locale:
Lang: pl_PL
Enc: UTF-8
Num: 1 234,5
Encoded кΩ丈: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)


Any help will be appreciated

do you have it also open in v8?
its complaining about getting exclusive lock to a file

Yes, I can open in v.8.
and I can’t found any lck file to delete.
I think this compilation is garbage. I don’t time to install and uninstall next version.
It’s a pity, everyone writes that it has so many better things but I have no way to check it.

Other people can open their projects from v8, but you can’t. That not necessary means that the 9.0.0rc1 compilation is “garbage”.

The screenshot shows a bunch of errors creating paths that should be possible to create. This points to something strange about your Windows setup, probably.

Is it possible you used “Run as Administrator” on KiCad in the past?

I mean, do you have v8 open/running with the same project while trying to open with v9-rc?
could there be a kicad process still running ? check task manager or do a reboot

This is not an issue of another KiCad process locking the design – that warning can be skipped. Something is wrong with the KiCad path inside the OP’s Documents folder. The most likely thing is that the permissions are wrong, which could have been caused by launching KiCad 8 as an administrator and then trying to run KiCad 9 as a regular user. But there could be some other issue going on, I’m not sure.

In general, KiCad is working fine, it just doesn’t have permissions to create paths inside Documents\KiCad, which it should definitely have in a normal installation.

No is not working fine:

look for padstack colour in V9 and V8 - do you think the lack of visual distinction between paths and padstack is ok?

For many years it was like in v8, i.e. time for a revolution - let the board image be more illegible, new users will be delighted, old ones will be forced to the new - without giving them a choice - is this the power of open source?

I install version 8 like my not administrator - its my computer with only one owner.
And v9.0 instal in this same way - but v8.0 work, v9.0 not.

…old ones will be forced to the new - without giving them a choice - is this the power of open source?

…well you can stick to v8 if bothers you. Sometimes with commercial SW you are not even given that choice. so yes, this is the power of foss.

Can someone explain why there is so much useless background noise about irrelevant details like pad colors?

3 Likes

Not any old pad colors. Just THT pad colors. No change to SMD pad colors.

Ah, ok! that’s why i didn’t notice. I got rid of tht in the 1999->2000 passage. :innocent:

1 Like

Its not how you install but how you run. As @craftyjon mentioned, something is stopping you writing to your directory and a common reason is the process doesn’t have access (ie another user owns that c:\user\tbarw\Documents\KiCad directory…) and this usually occurs if admin is used to run the application and makes that directory.
You can check who owns that directory via the properties option in windows explorer (under permissions). Likewise make a test file in c:\user\tbarw\Documents\KiCad (readme.txt for instance) and if you can write there then its not a permissions issue.

Now if your user does OWN it and you can write there its either a disk full issue or time for a fsck

1 Like

Well said and Thank You ! If you find this noise source let me know !! have a Wonderful new year !
:mouse:

I don’t know what happens, but I can’t use normalkly kicad v9. Only v8 work well.
Mayby final version v9 will be usable for me.
Permission folders is fine, check disk ok, disk is not full - just v9 has problem with error 2 and error 5.
I don’t time for this.

Tomasz, most people in Poland right now are happily celebrating the New Year and you’re busy complaining about KiCad. Can’t it wait until, say, 2nd of January? For now, grab a bottle of something and celebrate with friends!

Happy 2025 from another Tomasz

4 Likes

You may get some clues by running the following command in the Windows command prompt (CMD.EXE).

echo %USERNAME%
dir /q %USERPROFILE%\Documents\KiCad
dir /q %USERPROFILE%\Documents\KiCad\9.0
cacls %USERPROFILE%\Documents\KiCad*
cacls %USERPROFILE%\Documents\KiCad\9.0*
tasklist /v /fi “IMAGENAME eq kicad.exe”

Revised version of the confirmation command

echo %USERNAME%
dir /q C:\Users\tbarw\Documents\kicad9_pliki\estat-przednia-poprawiona-4\
cacls  C:\Users\tbarw\Documents\kicad9_pliki\estat-przednia-poprawiona-4
cacls  C:\Users\tbarw\Documents\kicad9_pliki\estat-przednia-poprawiona-4\*
dir /q %USERPROFILE%\Documents\KiCad\
dir /q %USERPROFILE%\Documents\KiCad\9.0\
cacls %USERPROFILE%\Documents\KiCad
cacls %USERPROFILE%\Documents\KiCad\*
cacls %USERPROFILE%\Documents\KiCad\9.0\*
tasklist /v /fi "IMAGENAME eq kicad.exe"

Reference materials such as a table of file system error codes for Windows OS

2 (0x2) ERROR_FILE_NOT_FOUND The system cannot find the file specified.
5 (0x5) ERROR_ACCESS_DENIED Access is denied.

Huh? Does this screenshot you posted mean that you can open data created with 8.0.7 with 9.0.0-rc1-165-g19c748048c?

Yes, I can open but not save, so v9 is useless for now.