Managed libraries keep disappearing -- Eagle 9 on Mac

[traykoff]

EAGLE 9.0.0 on a Mac...

Open app, open Library Manager, add a few managed libraries.  They download and show up in "Managed Libraries".

I then go to add parts from these libraries to a schematic, and then save the work.

Close app.  Restart.

All my Managed Libraries are gone in the control panel, and I have to re-import them to be able to search and/or use parts in them.

The libraries are still in my home directory under  ~/Library/Application Support/Eagle/lbr, however they are all put into folders adsk.eagle_library_NNN where NNN is some sort of serial number.

This isn't correct behavior of the app, is it?  I have seen this happen on two different Eagle on Mac installs...

Thanks,.

T

[david.mellis]

You're right, that's not the correct behavior. The record of the managed libraries is kept in the EAGLE RC file (~/.eaglerc on Mac). Is it possible that file is being lost or overwritten somehow? Can you share a copy of your EAGLE RC file?

When the libraries disappear, are you able to re-download them from the library manager (available tab)?

[traykoff]

Hi.  I have deleted .eaglerc, and everything in ~/Library/Application Support/Eagle, so that it should be a fresh start.  I started up Eagle 9, logged in, and the problem persists.

After restarting Eagle, all my managed libraries are gone.  So that didn't fix it.

A workaround that I am using is to:

cp /Applications/EAGLE-9.0.0/cache/lbr/*lbr /Applications/EAGLE-9.0.0/lbr/

This basically disables the Managed Library feature.

Thanks,
Taavo

[david.mellis]

When you quit EAGLE after creating / installing managed libraries, do you see entries like the following in your EAGLE RC?

Lbr.Managed.1.author = "EAGLE PCB"
Lbr.Managed.1.has_urns = "1"
Lbr.Managed.1.modified = "0"
Lbr.Managed.1.name = "19inch"
Lbr.Managed.1.path = "/Users/mellisd/Library/Application Support/Eagle/lbr/adsk.eagle_library_79/19inch.lbr"
Lbr.Managed.1.urn = "urn:adsk.eagle:library:79"
Lbr.Managed.1.version = "1"

Do they remain when you restart EAGLE and then quit again?

[traykoff]

No such lines in .eaglerc after adding a few managed libraries and then quitting the app.

In fact:

$ grep -i managed .eaglerc

Lbr.ManagedCacheInstalled.9.0.0 = "1"

[[ Just that one line exists ]] 

[david.mellis]

Strange. Is it possible something has changed the value of your $HOME environment variable (used to locate the EAGLE RC file)? Do you know what it's set to? 

Are you running EAGLE from the command line and passing it any command-line arguments?

[traykoff]

Strange indeed.

I deleted .eaglerc, and Eagle created it again so I think it is going to the right location for this file.  No, I am running in from the Mac Search.  Not a command line...

[david.mellis]

Any chance you can record a screen capture of the process? I'm not sure what might be happening and seeing the process might provide some clues.

[david.mellis]

Also, do you have the same problem with a previous version of EAGLE (e.g. 8.7)? That should help isolate what's causing the problem.

[traykoff]

Thank you for checking into this.

I have this problem on 8.6 also.  I also have this with installs on two separate machines; both of which are running Mac OS High Sierra.

I have installed 9.0 on a Windows machine.  It works very differently, to say the least.

I can send some screenshots later if helpful.

[david.mellis]

Screenshots would be helpful. If you don't mind posting it, it would be helpful to see the contents of your EAGLE RC as well. I'm baffled as to what's going on here, so the more information, the better. 

[traykoff]

I found a Mac that this works on, and what I think is a big hint to the problem.  The Mac that this "works" on has a case-insensitive file system, while the ones that it does not have case-sensisitive file systems.

I can send my .eaglerc, but can't figure out how to do it on this forum.  Do you want to send your email so we can transfer files, etc. related to this issue?

[david.mellis]

Thanks for tracking that down! I'm assuming the problem is indeed the case-sensitive filesystem; I don't believe I've tested that case on Mac. No need to send the EAGLE RC file. I'll get this fixed ASAP.

[traykoff]

Thanks!!

[traykoff]

I did a dtruss on this, and sure enough it appears that this is the problem:

819/0x65ba:  stat64("/Users/taavoraykoff/Library/Application Support/Eagle/lbr/adsk.eagle_library_169009/Nordic_nRF.lbr\0", 0x7FFEEFBFA528, 0x0) = 0 0

  819/0x65ba:  stat64("/users/taavoraykoff/library/application support/eagle/lbr/adsk.eagle_library_169009/nordic_nrf.lbr\0", 0x7FFEEFBFA598, 0x0) = -1 Err#2

What's the chance of getting this fixed soon?  

Thanks!