Older Schematics doesn't show any Sympols at all anymore all of a sudden!

[lasmahei]

Its now for years, that KiCad has majure issues with its Schmatics symbol library remapping. Today, I opend a schematics in KiCAD 5.1.6 under Manjaro Linux which I just had open yesterday, and not a single library symbol is showing again. No matter what I do. This is frustrating and very annoying. Reading throw other comments in KiCad blogs and forums, similar issues had been reported for years! Why is it still such a problem to make this just work? It can’t be that difficult! KiCad is such a wonderful EDA, if just that damn librariy thing would’t be such a crap! Terrible!

[linuxman]

Have you installed the library or modules files?
what do you see if you look in /usr/share/kicad/library for example?

[paulvdh]

So what does it look like?
Do you get nothing at all, or do you see the square symbols with question marks?

Are all your symbols “missing”, are the symbols from the default libraries missing? or are symbols from a custom library missing?

Maybe this helps:
https://forum.kicad.info/search?q=library%20management%20category%3A19

In KiCad V6 there are going to be big changes in the schematic part. A whole new file format, and copies of the schematic symbols are going to be embedded in the schematic itself, just as is already the case with Footprints in Pcbnew at the moment.

[lasmahei]

The entire Schematics has the square symbols with question marks. All Symbols.
If I open the Schematics, I get a Notification window, which says: "The schematics currently uses the project symbol library list look up method for loading library symbols. KiCAD will attempt to map the existing symbols… etc…

Then, when I click “Remap Symbols”, I get an error Message saying:
Failed to backup file /… sym-lib-table
Failed to back up file …sch
Failed to back up file …pro
etc…

I also get this annoying error message: "Impossible to set permission for the file … rescue-2020-10…lib. error 95: Operation.
(Which is as what I read a bug in the wxWidges when opening a KiCAD file from a NAS drive, which I do.)
So I ignore rescue and hit “close” in the first window. The Schematics looks just fine. Everything is how its supposed to be.
Now, I change one value of a component an try to save the schematics.
I get the Error message: "Error occurred creating symbol library /run/user/1000/gvfs/smb-share:server=… -cache.lib
And:
Symbol GND-RESCUE-f1 not found in any library or cache
Symbol TC1014 not found in any library or cache Symbol
Symbol LM324 not found in any library or cache Symbol
Symbol …
Symbol …
…

So I close the Schematics and reopen: Then I get a page with Squares and Question-marks only.
The Schematics is not recoverable (At least I couldn’t recover it). Gladly, I had an old Backup on another drive.

So my guess is, it has something to do either with that wxWidgets bug, or its in the KiCAD Library Management, or both.

However, if I save a kicad_pcb file, I am also getting “Failed to set temporary file permissions (error 95: Operation not supported)”, but if I reopen it, everything looks fine and it saved the change perfectly.
So there must be some bug withing Schematics or the Library Management, regarding this wxWidgets error 95 when accessing a samba network drive.

(I reported this error in August 2017 already and others 2016 already. Unfortunately its still there and nothing changed)

[linux mint17] Failed to set temporary file permissions-Error 95

This error appears after I have installed Kicad, started a schematic project and tried to set a relative path to libraries via Preferences==>Component libraries. …/user/share/kicad/library This is the latest version and installed on Mint 17, everything fully up to date. Can someone provide a simple solution? An absolute path does not work either. Thanks.

[pedro]

You want to read this FAQ entry

I had KiCad 4 installed previosly. Now i updated to v5. Now i have some problems with the library setup

Recommended reading: Library management in KiCad version 5 KiCad does not automatically discover libs. Nor does it update the list of libraries on update. If you had KiCad 4.0.x installed previously then i would bet you still have parts of its configuration surviving. Most importantly the fp-lib-table. This file controls which footprint libs you use. If this is the case then you probably still run the on demand online footprint libs originally “distributed” with KiCad 4.0.x installations. The …

[Rene_Poschl]

I am not sure this is the correct FAQ article. My guess is that this one is better suited Converting KiCad version 4 projects to version 5 (Remap a project)

[davidsrsb]

Check the owner and permissions of those files, this looks a bit like “root” ownership errors

[paulvdh]

At this moment some trouble with file ownership also seems to be more logical then problems with the libraries itself.

Is there anything special you did or maintenance on you PC between the day it “worked” and the day it “stopped working” ?

Do you have other projects that still work?
What happens if you start a new project? Can it read the libraries?

[lasmahei]

While I was just working on a new project, I did the “assign PCB footprints to schematic symbols”. When I hit “Apply, Save Schematic & Continue” I got an error popup window, showing:

Failed to set temporary file permission (error 95: Operation not supported).

But everything was saved correctly!
Then I changed a footprint and saved it again: No error popup message.

Here I found a post which describes the same problem:

Failed to set temporary file permission

Hi community! When I create a new project on my NAS I get the error message “Failed to set temporary file permissions” for the .pro file. I don’t get this error when I create a new project on my local hard disk, so I’m 99% sure this has to do with how my CIFS/Samba connecton on/to the NAS is configured. I.e. not a bug in KiCad. Here is a screenshot of the error window: [Screenshot%20from%202018-04-10%2019-50-51%20(copy)] Oddly, this error message does not seem to affect anything, as I can h…

My guess is, that this is the root cause of the messup with the library conversions I had in the first place.