Trouble installing Fritzing on Linux Mint 19.2

[vanepp]

@ehoitinga

Sorry for my harsh words in my first post. It was just an expression of frustration due to the fact that I thought it was still buggy as hell after all these years.

Unfortunately it is still buggy after all these years , but there is progress now. I’ve been trying to restart development for the last couple of years without much success, but the credit goes to the Ansler folks who run the Fritzing Fab. their CTO manged to get development restarted although as you see there are still problems.

@ehoitinga

When I report the install issues on the github site can I post a link to this thread in order to not retype the problem in Github?

Yes that should be fine. The development team sometimes reads the forums, but bug tracking occurs on github. For what it is worth (which is probably not much because I have a full Qt development install on my Ubuntu 18.04 box), I just downloaded the 9.4 tar ball unbziped it and ran it without problems on Ubuntu 18.04. The missing QT library is in the lib directory in 0.9.3b but doesn’t seem to be (at least in the same place) in the 0.9.4 tarball. I need to install a clean copy of Ubuntu 18.04 (without QT) and see if it installs properly there. The problem you are having may be version skew in QT libraries, the 0.9.4 release moved up a couple of QT versions, but not to the latest one and you sudo install may have gotten the latest copy of the library, In any case, loading the library is not supposed to be needed, everything required should be in the tar ball, so there may still be a bug somewhere.

@ehoitinga

BTW: The website fritzing.org is regularly not reachable. I get cloudflare “Error 522” and “Error 524” messages.

Yes, it took me half an hour of getting those messages to log in to post this. The web site has suffered from years of no maintenance too, and has no staging environment, so changes are done on the live web installation by someone entirely new to the installation. My sense (because I’m just an interested helper rather than part of the development team) is that things were much worse than expected when the current team took over and it was a lot more work that expected to restart development (as noted, an entirely new deployment environment, because the previous one was apparently gone.) The web site is thought to have been hit by spambots and thus its mail reputation is so bad that email notifications no longer work (they possibly work on the server end but are discarded as spam on the receiving end.) I see as I finish this that you have reported it on github. Good, that should help as they know more about the deployment than I do.

Peter