Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.
As of Local v9.2.5 (Releases - Local) we should have this addressed for Ubuntu and Fedora:
Improved Ubuntu 24 and Fedora compatibility by bundling missing dependencies that are no longer included in latest Linux releases. Previously, this was causing issues installing Local and starting nginx on these operating systems.
That said it might still be an issue with Linux Mint 22. I’ll check with our devs regarding that!
As far as Ubuntu, are you still getting the errors with new sites or is this happening on previously created sites? Could you share your full Local Log?
Thanks for looking into this. I had only tried with a new site since moving to Mint 22.2 from 21.3. I was unable to create a site from a zip, and when I tried to create a blank site and then add the SQL dump, I received the error message, “Failed to get current SQL modes. Reason: mysql: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory.” With a bit of effort, I installed libncurse5 and was then able to import the ZIP file normally, but that is obviously not a good long term solution due to potential conflicts with libncurses6.
Improved Ubuntu 24 and Fedora compatibility by bundling missing dependencies that are no longer included in latest Linux releases. Previously, this was causing issues installing Local and starting nginx on these operating systems.
More specifically, there were two rough issues that were addressed in the above release:
The Local installer used to require libncurses.so.5 and when an OS couldn’t satisfy that dependency, it refused to install. Technically, Local core (ie, the actual app that you click around) doesn’t require libncurses – it’s MySQL that does. Because of this, we remove that hard requirement on the Local installer
Because the actual dependency comes from MySQL, we updated the Lightning Service (roughly the MySQL environment, plus some wrappers so Local Core can manage those processes) to include libncurses.so.5. This was necessary so that when you created a new site using Local, it was able to finish creating a site and importing SQL files.
You didn’t say explicitly, but I think you probably ran into the issue within a site shell – correct?
If that’s true, you’re probably wondering why it’s still broken in the terminal and why it’s preventing you from importing a sql file.
I was able to work around it by updating the LD_LIBRARY_PATH environment variable to point to the lib folder of the MySQL lightning service. This is roughly the fix that we implemented in those other situations.
The specific command was this one, though if new versions of MySQL are released, the path might change:
While QA’ing, I did notice that some wpcli db commands are broken, but that’s a known issue with wpcli in our environment: Unable to run some wp-cli DB commands
I’ve added a ticket to our backlog to implement this fix. Anyway, the wp db import command should work again with this workaround and our eventual fix.
Thanks again for finding this issue and letting us know about it!
