Unable to find parts git repository

[deshipu]

Current Behaviour

Fritzing can't find the parts repository. No parts are loaded.

Build: Version 0.9.9

Operating System: Linux Mint

Steps to reproduce:

• Download the appimage
• Make it executable
• Start it

Expected Behaviour

Fritizng should load the parts definitions.

[KjellMorgenstern]

Hello @deshipu, thanks for the report. The AppImage includes the most recent part database, and there should be nothing to update. A simple guess would be that Fritzing gets confused by a previous installation. Did you manually trigger the db regeneration, or did it start by itself?

[deshipu]

The message appears when I start the appimage. When I try to manually trigger the database regeneration, I get a different error, "Database failure".

Could it matter that my "desktop" directory, with its "Fritzing" directory, is in a non-standard place?

[deshipu]

Is there some log file I could post?

[vanepp]

You could try Help->Enable debug log which will open a debug log window (if the particular error that is occurring has debug code enabled in it an error message should appear in the debug window.) Another thing to try is clearing your user directories like this:

There are two user directories (with your parts and the parts database) which don't get touched during an install (to not affect your sketches during upgrades). On Windows they are in

c:\users\username\AppData\Fritzing\roaming\Fritzing (which is a hidden directory so you need to enable hidden directories in explorer) and

c:\Users\username\My Documents\Fritzing (where username is your windows id)

If you don't have any parts or sketches you want to keep you can just delete those two directories and Fritzing will recreate them, or you can move them aside by renaming them if you want to keep something in them.

linux

~/Documents/Fritzing/parts ~/.config/Fritzing

Mac

/Users/username/Documents/Fritzing/parts ~/.config/Fritzing

[deshipu]

Thanks. I tried moving the config files away, and enabling debug log. This is what I get when I click on any of the part bins:

Application folder fritzing-parts not found
Application folder parts not found
Application folder fritzing-parts not found
Application folder parts not found
loading bin 'Core Parts'
module id ResistorModuleID not found in database
module id 100milCeramicCapacitorModuleID not found in database
module id 100milTantalumCapacitorModuleID not found in database
module id SmallElectrolyticCapacitorModuleID not found in database
module id 56bed03878064b8286b71d5240035138InductorModuleID not found in database
module id 3254CBFC44diode not found in database
module id 2244EBEC21e not found in database
module id NPN-to92-ebc not found in database
module id 1001ABDC27 not found in database
module id mystery_part_sip_3_100mil not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:mystery_part_sip_3_100mil
module id 3234DBDC00PotentiometerModuleID not found in database
module id alps-starter-pot9mm not found in database
module id 3b1a8578c21940dfe27253a7b57c81f5PotentiometerModuleID not found in database
module id c7acdd26c5e6355cb2e7e05c0aa975c0PotentiometerModuleID not found in database
module id trimmer_3_1_vVariableCapacitorModuleID not found in database
module id alps_stec12e07_fix not found in database
module id 20A9BBEE34_ST-2leadbutton-horizon not found in database
module id 20A9BBEE34_ST not found in database
module id 1238DBDC00-toggle-switch not found in database
module id d206ca0d70364191f0b3fd30d5e53c5d not found in database
module id 1000ABDD10011 not found in database
module id fa3e296736059e8c25d88ac262af999a not found in database
module id 2010BBCD20113 not found in database
module id beab33bd7feee277622ef76dd6e79e4d not found in database
module id ADXL335_v13 not found in database
module id SparkFun_LSM303C_6_DOF_IMU_Breakout not found in database
module id LM35_THT not found in database
module id ad901601e6d29266846fc9e4568504b6 not found in database
module id c0e65b2d0c9003507cf4a3222e995a45 not found in database
module id 6d07f5eae4523283f5da4171f9c54e25 not found in database
module id a975d1270bd55d6fc3916947793f1a57 not found in database
module id Humidity_and_Temperature_Sensor_RHT03_6 not found in database
module id 5mmColorLEDModuleID not found in database
module id d4d5af9700923b8a114f57961f29a8a0 not found in database
module id AnodeLEDSuperfluxModuleID not found in database
module id Prolight RGB 3 Watt Star not found in database
module id 7segment10an not found in database
module id LED_Matrix_Kingbright_TA07-11 not found in database
module id LCD-GDM1602K not found in database
module id GLCD128x64 not found in database
module id 8abf6496b5d466c7a1893c17a296a676 not found in database
module id 5c5090e231dbe30e6bd4b9e2e7949902 not found in database
module id 415c9d899a1e7de6c023ea0731bab117 not found in database
module id 1000FADF10011leg not found in database
module id EDGY_motor_control not found in database
module id 3234DBDC80leg not found in database
module id 7d0bc366bcac9395c747f3a92e2ff843leg not found in database
module id 9f2b90fcf9c65c9bc09d570e3442069e not found in database
module id 045cef49a96039c64e7363608e127209 not found in database
module id 1099ABDE24_ST_relay not found in database
module id 71d4db74a3a0ec43d9303ddffee7361b not found in database
module id 93d4585be720f3982141f4d032f44c8e not found in database
module id 4f6dc41d6d2f66341ea506cdaf0e797e_2 not found in database
module id ab15a34dfcf83e23a26e83fe8a5a4dac_2 not found in database
module id 4d1eb8f243c1aba7afe676122ea516cc_2 not found in database
module id fa46ea3312d60697b8e907a5c75db23d_2 not found in database
module id generic_ic_dip_8_300mil not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:generic_ic_dip_8_300mil
module id 8e4b4f3e54f56b3f712afc6a8e6a8a71 not found in database
module id a59353bd0db0225dc22770e292c622f3 not found in database
module id 1001AAAB555Timer not found in database
module id 1001AAACOptocoupler not found in database
module id a4f38a10-dd92-11dd-a3e2-001f5b3a17a4 not found in database
module id 1a7828b6466fac9fd042221e931124c4 not found in database
module id HEF4094 not found in database
module id RevEd_24LC01 not found in database
module id RevEd_DS1302 not found in database
module id RevEd_FRM010 not found in database
module id RevEd_FRM050 not found in database
module id RevEd_ULN2003A not found in database
module id RevEd_uM_FPUv2 not found in database
module id M5450_LED_Driver not found in database
module id CrystalModuleID not found in database
module id 37asdf3c843a2127a0e499f8a0b3ef6aCrystalModuleID not found in database
module id 1000AFDF10011leg not found in database
module id d8f570d723ea4d14f9b61b34575a9699 not found in database
module id 1238DBDC00-voltage-reg_7805 not found in database
module id fuse_with_handler_cff5 not found in database
module id arduino_Uno_Rev3(fix) not found in database
module id ti_launchpad-rev1.5 not found in database
module id SPARKCORE_v1_fix not found in database
module id Bean_revE not found in database
module id pinoccio_board not found in database
module id bareconductive_touchboard not found in database
module id teensy_3.1 not found in database
module id Adafruit_Atmega32u4_Breakout not found in database
module id Netduino_plus_2 not found in database
module id chipkit_WF32 not found in database
module id blueIOT_Rc1-final not found in database
module id dquidio not found in database
module id sodaq_mbili_rev4 (4) not found in database
module id RaspIO_Duino not found in database
module id 2c9d427b475ef8d07dc752a4362af0ae not found in database
module id 81591c6c31ccf12f0f3ccec5f150df2d not found in database
module id 346b613c666d64fc5ac622407ace7130 not found in database
module id 760832bc79fe1f34e99f420ad872a0b8 not found in database
module id d30f97b6fbe1asdad59ea7f0d636a7a not found in database
module id RevEd_PICAXE_08 not found in database
module id c4256c251d53ee723058f86aa6d016a2 not found in database
module id jlpcb-128 not found in database
module id SparkFun_Stepoko not found in database
module id raspberry_pi_3_rev-1.2 not found in database
module id raspberry_pi_zero_rev-1.1 not found in database
module id arduino_Yun(rev1)_v1 not found in database
module id intel-arduino_galileo_gen2-(simple) not found in database
module id intelEdison-HiroseDF40 not found in database
module id linino_one_rev1 not found in database
module id udoo_dual not found in database
module id generic_female_pin_header_2_100mil not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:generic_female_pin_header_2_100mil
module id generic_shrouded_pin_header_10_100mil not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:generic_shrouded_pin_header_10_100mil
module id Molex-Picoblade-53261-0219_smd-2p-h not found in database
module id Molex-Picoblade-53398-0271_smd-2p-v not found in database
module id hirose-df13-2p-125h not found in database
module id hirose-df13-2p-125v not found in database
module id screw_terminal_2_3.5mm not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:screw_terminal_2_3.5mm
module id DB25F not found in database
module id 5e3b9f7a14a1627168e700bfc9a03b3c not found in database
module id c04a5dd707ca537800655cb3aa4b2048 not found in database
module id stereo-jack-3_5mm not found in database
module id 15719464aa8d63048081b2444ea6d39c not found in database
module id 1a4bfb87a0f0fd2c59be43f3497d72e6 not found in database
module id Shield_Eth06-PoE not found in database
module id WIZ820io not found in database
module id proto_shield_v6MEGA not found in database
module id jlpcb-104 not found in database
module id jlpcb-089 not found in database
module id Breadboard-RSR03MB102-ModuleID not found in database
module id 30.20PerfboardModuleID not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:30.20PerfboardModuleID
module id 30.20Stripboard2ModuleID not found in database
Application folder fritzing-parts not found
Application folder parts not found
SQLITE: couldn't retrieve part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:
SQLITE: couldn't insert part

     ERROR DRIVER: Driver not loaded
     ERROR DB: Driver not loaded
     moduleid:30.20Stripboard2ModuleID
module id WireModuleID not found in database
module id BreadboardLogoTextModuleID not found in database
module id newBreadboardLogoImageModuleID not found in database
module id GroundModuleID not found in database
module id DC2PowerModuleID not found in database
module id PowerLabelModuleID not found in database
module id NetLabelModuleID not found in database
module id SchematicFrameModuleID not found in database
module id SchematicLogoTextModuleID not found in database
module id newSchematicLogoImageModuleID not found in database
module id RectanglePCBModuleID not found in database
module id JumperModuleID not found in database
module id LogoTextModuleID not found in database
module id newLogoImageModuleID not found in database
module id HoleModuleID not found in database
module id ViaModuleID not found in database
module id PadModuleID not found in database
module id Copper1BlockerModuleID not found in database
module id GroundPlaneModuleID not found in database
module id NoteModuleID not found in database
module id RulerModuleID not found in database
Application folder fritzing-parts not found
Application folder parts not found
missing renderer for icon mystery_part_sip_3_100mil
Application folder fritzing-parts not found
Application folder parts not found
missing renderer for icon generic_ic_dip_8_300mil
Application folder fritzing-parts not found
Application folder parts not found
missing renderer for icon generic_female_pin_header_2_100mil
Application folder fritzing-parts not found
Application folder parts not found
missing renderer for icon generic_shrouded_pin_header_10_100mil
Application folder fritzing-parts not found
Application folder parts not found
missing renderer for icon screw_terminal_2_3.5mm
Application folder fritzing-parts not found
Application folder parts not found
Application folder fritzing-parts not found
Application folder parts not found

[deshipu]

Could it be a problem with the sqlite library?

[deshipu]

I compiled Fritzing from the repository, and I noticed that I get the same error when I start it with the -f,-parts, and -db parameters, but if I skip the -db parameter everything works fine (the parts.db is created inside the parts directory then).

[vanepp]

"I compiled Fritzing from the repository, and I noticed that I get the same error when I start it with the -f,-parts, and -db parameters, but if I skip the -db parameter everything works fine (the parts.db is created inside the parts directory then)."

It has been a few versions since I did a source build, but I don't remember starting with a -db parameter. It looks like it isn't finding the parts database file (I expect you need to provide a path to the db file on the -db parameter since I expect it is to use an alternate db file, but I don't know for sure.) If it runs without the -db parameter I'd go with that as the parts database should be in the parts directory in a normal install (i.e. one of the production versions installed from the installer.)

[KjellMorgenstern]

We have tested the AppImage with many different configurations, and it is already in use by many. If the problem was directly in the AppImage (like, for example, with sqlite library), then it would have shown much earlier and much more often.

The location where you start the AppImage should not matter. What could matter, are remains of previous installations, especially if they are a bit non-standard. @deshipu I guess the log output is from your own compiled version, not from the AppImage?

[KjellMorgenstern]

@deshipu How did you change the "Desktop" directory? Fritzing follows the Operating Systems standard for determining the Documents and Configuration locations. Details are at https://doc.qt.io/qt-5/qstandardpaths.html

[deshipu]

I changed my user directories in ~/.config/user-dirs.dirs — I never had any problems with that before.

I renamed both the old .config/Fritzing and the Desktop/Fritzing to make sure they don't get in the way. The appimage still doesn't work, the version I compiled myself works both with the old directories present and without them.

The log is from the appimage version, after enabling the logging, and trying to access the CORE bin.

[deshipu]

I will try running it on a completely new user later today.

[deshipu]

It runs without problems on a new user, so it must indeed be some leftover configuration somewhere. I'm closing this.

[chris-hatton]

I'm not so sure this should be closed @deshipu - I faced the same issue, also on Linux Mint. The only thing that fixed it for me was doing sudo rm -rf /usr/share/fritzing after uninstalling the older 0.93b that I'd previously installed through package manager. Needing to clean up Fritzing's old files manually (and without instruction) is not really acceptable: Any new version should be smart enough to work in the presence of config left over from older versions; this is a common version upgrade issue which any software product should handle.

[KjellMorgenstern]

So you installed 0.9.3b from the ubuntu package on linux mint? Which version of mint? And did you also install the fritzing-parts package? Did you try to uninstall both fritzing packages (fritzing and fritzing-parts) through the package manager?

[mrprole]

I managed to solve the problem after this operations and all work well. Some strange behavior with autoremove. mrprole@mrprole-Swift-SFX14-41G:~ sudo apt remove fritzing-parts [sudo] password for mrprole: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: fritzing-data libqt5serialport5 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: fritzing fritzing-parts 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 150 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. mrprole@mrprole-Swift-SFX14-41G:~ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. mrprole@mrprole-Swift-SFX14-41G:~ sudo apt remove fritzing-parts Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: fritzing-data libqt5serialport5 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: fritzing fritzing-parts 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 150 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 572595 files and directories currently installed.) Removing fritzing (0.9.3b+dfsg-10build2) ... Removing fritzing-parts (0.9.3b-5) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for mailcap (3.69ubuntu1) ... Processing triggers for desktop-file-utils (0.26-1ubuntu2) ... mrprole@mrprole-Swift-SFX14-41G:~ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: fritzing-data libqt5serialport5 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 7 409 kB disk space will be freed. Do you want to continue? [Y/n] y

[benreu]

I also run Linux Mint (19 & 20). I have the same problem.

When I uninstall the fritzing-data package using apt or equivalent, Fritzing 0.9.9 starts working. When I reinstall fritzing-data, Fritzing 0.9.9 complains that it is unable to find parts git repository. The fritzing-parts package doesn't affect the Fritzing 0.9.9 parts repository, installed or uninstalled.

This problem irritated me the longest time, I didn't know the fix until today. Every time a new release of Fritzing came out, I would donate some more of my hard earned money, only to run into the same problem. I commented on a previous issue, only to have it closed with the explanation that the problem no longer is relevant. It was a pretty disappointing experience.

I like Fritzing and have used it commercially for 10+ years, but this was almost enough to make me look somewhere else. I will say, I'm glad the community opened this issue and found a workaround.

[benreu]

One more thing I found:

If I open Fritzing 0.9.9, wait until it shows the error unable to find parts git repository, then uninstall fritzing-data, and then click OK in Fritzing, Fritzing will try to load a new sketch and hang at 14%.

[KjellMorgenstern]

Uninstalling the fritzing-parts package does still leave a directory "/usr/share/fritzing". This directory needs to be manually removed, Fritzing is still confused by it.

[KjellMorgenstern]

@benreu The issue was not closed by Fritzing, but the original poster.

[benreu]

Uninstalling the fritzing-parts package does still leave a directory "/usr/share/fritzing". This directory needs to be manually removed, Fritzing is still confused by it.

If you use Synaptic and select "Mark for complete removal" on fritzing-parts and fritzing-data it will remove directory "/usr/share/fritzing".

[benreu]

@benreu The issue was not closed by Fritzing, but the original poster.

No, it was an older issue about parts directory not found. It doesn't matter any more, as the solution has now been found for Linux Mint. I'm assuming this issue is only Linux Mint related, as nobody else is complaining. The previous issue was affecting all Linux users, if I remember correctly.

[KjellMorgenstern]

Ah, yes, there were other issues, for example Windows defender would scan all files during the first start, Fritzing would therefore slow down and be "This apllication is not responding" for ten minutes or more. When the user then kills Fritzing, the part database would be invalid... those and similar issues are solved. Anyway, i reopened the issue, i agree manually researching and then removing the old configuration should not be needed.

If possible, Fritzing should ignore those files. If in doubt, Fritzing should show an error message that helps the user to decide.

[christianbaun]

Uninstalling the fritzing-parts package does still leave a directory "/usr/share/fritzing". This directory needs to be manually removed, Fritzing is still confused by it.

I had the same issue in Debian 11 these steps solved it:

sudo apt remove fritzing-parts
sudo rm -rf /usr/share/fritzing/

[benreu]

There must be a difference between Debian and Mint, since I uninstalled Fritzing on 2 different Mint computers, and I did not have to remove the /usr/share/fritzing/ directory manually.

[deshipu]

For me, on Mint, the culprit was actually in ~/.local/share/fritzing – I suppose some earlier install must have put stuff in there.

[GeniuScientist]

Windows user here! So, I'm having this error when I try to build Fritzing (with Qt Creator). I already checked My Documents and APPDATA, but, since this is my first time building it, there were no folders. I might be missing something obvious, I would appreciate if someone helps me.

[ead0601]

I had the same issue, and this is what I did to resolve it.

sudo apt remove --purge fritzing sudo apt remove --purge fritzing-parts sudo apt remove --purge fritzing-data

also

rm -rf ~/.config/Fritzing

only after purging --purge, it start to work with the user based install at ~/bin/fritzing....

[benreu]

@ead0601 Please list you OS / distro. This problem seems to affect certain distros more than others

[deshipu]

I wonder if it would make sense to remove all the external search paths for this when making the appimage.

[KjellMorgenstern]

All good, next release won't have the issue.

[ead0601]

@ead0601 Please list you OS / distro. This problem seems to affect certain distros more than others

Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal

[failiz]

Was this fixed in 0.9.10? or will it be fixed in the next version?

[KjellMorgenstern]

Summary of the discussion above: We have found that 3rd party installs of Fritzing 0.9.3 can cause the issue observed. A left over part library folder would confuse Fritzing, and it would try to load the parts from there. This has been fixed in 0.9.10, so the workaround with apt remove --purge is not needed anymore. I think we can close this issue.

[jiapei100]

Issue continues of today... Dec 22, 2023....

I built fritzing-app with Qt-6.6.1.

I'm thinking there MUST be a way from within Fritzing IDE to specify the root/directory of fritzing-parts ???