-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having trouble running Fritzing on Linux Mint 19.2. #3575
Comments
Can you try to install additional qt libraries: Also, can you check the content of $HOME/.config/Fritzing/Fritzing.conf . |
Apparantly these packages were already installed.
The "7 not upgraded" are samba packages which have nothing to do with Fritzing. Below the contents of ~/.config/Fritzing/Fritzing.conf:
Erik |
This looks all good so far. Another thing to try The file should have +rw permission for the user, and be about 11MB. If the file has zero size Fritzing will detect this and recreate it from the parts. But if the file is broken, lets say only 1MB, Fritzing might not be able to recover. It is save to remove the file. Fritzing will automatically regenerate it on the next start. |
The libqt5sql5-sqlite library was not there. Installing it with So for now on the following packages should be present on linux mint 19.2 before using Fritzing:
The file /home/erik/bin/fritzing-0.94/fritzing-parts/parts.db has the right permissions and size:
Below the terminal output from running Fritzing. Don't know if I should be worried about that. Will do further testing tomorrow.
Erik |
The above looks pretty normal for console output on Linux, it seems to work fine anyway. It would be nice to eliminate the error messages, but bugs that break things are a much higher priority for limited developer time. @KjellMorgenstern should we need to add those libraries? I thought on 0.9.3b all the Qt libraries needed were in the tarball (although I may be wrong there.) Are the Qt libraries a standard part of the Linux distros these days? Peter |
On my fresh linux installation in Virtualbox. The QT5 libraries are installed. However QT itself is, I think, not installed:
As far as I can see the QT5 libraries are in In stead of including the necessary libraries in the tarball maybe it is worthwhile to create a PPA and handle dependencies there? Will continue to test and if you want I can continue to look in to the installation in Linux Mint by taking a look at the install_fritzing.sh script to find out which lines are necessary to install the mime types and to get Fritzing in the menu. Let me know. Erik |
If the user did not install any other app that depends on qt5, they will run into this error. |
@KjellMorgenstern On my fresh VM install of linux mint 19.2 I also had to install libqt5printsupport5 and libqt5sql5-sqlite. To be on the safe side maybe it is better to use the command Erik |
I'll add this and also instructions for fedora. By the way, removing the scripts doesn't mean I want to dump them, but currently I just don't have time to verify and improve them. |
I think that the release script for 0.9.3b copies all the Qt libraries in to the tar ball as this from https://github.com/fritzing/fritzing-app/wiki/4.-Publishing-a-Release says "... Official Qt documentation: http://doc.qt.io/qt-5/linux-deployment.html There is a good set of instructions for setting up virtual machines and building the linux releases here, so I will just add a bit of context. First, we do our builds under Ubuntu 16.04 LTS. Basically, to do the build, you use the script release.sh, and it can be found in Fritzing source in tools/linux_release_script/. Once your vm is set up correctly, you merely have to run the script with the current release string as the parameter (e.g.: ./release.sh 0.8.6b). The process will create a standalone tar.bz2 file containing the Fritzing executable plus all the necessary auxiliary files (including the qt libraries). These bz2 files are download-ready." I know this because if you don't run this script (or make a sym link for libgit2, which is what I used to do) when building from source for 0.9.3b, it won't link libgit2 properly. Running the release script fixed that. Here is an ls from the 0.9.3b tarball on Linux (Ubuntu 18.04 lts): fritzing-0.9.3b.linux.AMD64/lib: fritzing-0.9.3b.linux.AMD64/lib/imageformats: fritzing-0.9.3b.linux.AMD64/lib/platforms: fritzing-0.9.3b.linux.AMD64/lib/sqldrivers: On .9.3b the only times I've seen install problems on Linux over the years is when the user used one of the package managers to install Fritzing (some of them omitted the parts repository which caused problems), in all cases I know of uninstalling that version and installing the distribution tarball instead just worked (I think because all the required parts are in lib although I could be wrong.) I expect we would have had more complaints if it was depending on Qt being installed already because of systems that didn't have Qt installed. |
Updated instructions on qt5 dependencies in INSTALL.txt |
Current Behaviour
Having trouble running Fritzing on Linux Mint 19.2.
See: https://forum.fritzing.org/t/trouble-installing-fritzing-on-linux-mint-19-2/7881
Screenshots: http://users.skynet.be/fa403916/Screenshots-Errors.pdf
Build:
0.9.4
Operating System:
Linux laptop-erik 5.3.0-24-generic #26~18.04.2-Ubuntu SMP Tue Nov 26 12:34:22 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce:
Unzip Fritzing tar ball
Run ~/bin/fritzing-0.94/Fritzing
Click OK on error messages until the app appears
Click "Breadboard"
Click "Part --> Regenerate part database"
Click "Regenerate"
Click "Ok" on the error
Click "File --> Quit"
Terminal output:
Expected Behaviour
App should start normally without errors :-)
The text was updated successfully, but these errors were encountered: