Bug 24114

Summary: fritzing looks for parts in $PWD/bins instead of actual install location
Product: Mageia Reporter: Christian Lohmaier <lohmaier+mageia>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: fri, geiger.david68210, lists.jjorge, loginov_alex, marja11
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: fritzing-0.9.3b-1.git20181017.mga7.src.rpm CVE:
Status comment:

Description Christian Lohmaier 2019-01-02 18:36:39 CET
Description of problem:

Try to launch fritzing →  complains about not being able to load parts, and in GUI you don't have any parts to pick from.

How reproducible:
100%

Steps to Reproduce:
1. open terminal, start fritzing →  see about attempts to access $HOME/bins/core.fbz and the other default part sets
2. close again and cd /tmp first → now looks for /tmp/bins/core.fbz
3. workaround: cd /usr/share/fritzing/parts/ , then start fritzing, then it can load the files (as they are in /usr/share/fritzing/parts/bins)

to fix the package:
Likely some configure flag missing that defines partsdir or similar, if such a switch doesn't exist:
replace fritzing by a shell wrapper that cd's to the expected directory first, then launches Fritzing (and also change the .desktop file to launch the wrapper, and not the uppercase Fritzing directly or add working dir to the desktop file)
Comment 1 Marja Van Waes 2019-01-02 21:27:26 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC'ing some committers.

Assignee: bugsquad => pkg-bugs
CC: (none) => geiger.david68210, lists.jjorge, loginov_alex, marja11

Comment 2 David GEIGER 2019-01-02 22:23:16 CET
Should be fixed with fritzing-0.9.3b-3.git20181017.mga7!
Morgan Leijström 2019-01-03 00:25:47 CET

CC: (none) => fri

Comment 3 Christian Lohmaier 2019-01-03 12:15:00 CET
thanks for the quick fix, verified with fritzing-0.9.3b-3.git20181017.mga7
Comment 4 Morgan Leijström 2019-01-03 12:16:26 CET
Thank you both :)
Comment 5 David GEIGER 2019-01-04 08:23:30 CET
Fixed? or not? if yes please close this bug!
Comment 6 David GEIGER 2019-01-06 13:31:41 CET
Closing of this bug!
Comment 7 David GEIGER 2019-01-06 13:32:33 CET
Really close this bug!

Status: NEW => RESOLVED
Resolution: (none) => FIXED