Fritzing noch finding any parts

Bug #1740846 reported by Hadmut Danisch
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
fritzing (Ubuntu)
Fix Released
Undecided
Georges Khaznadar

Bug Description

Under 16.04 fritzing 0.9.2b+dfsg-3 worked just well, but under 17.10 0.9.3b+dfsg-4 is just broken.

First, there are two executables, /usr/bin/fritzing as an executable and /usr/bin/Fritzing (the former name of the binary) as a shell script, starting the binary. Unclear, which to use (actually doesn't matter, both not working)

Starting fritzing (the binary) runs into several error messages:

"Sorry, we have a problem with the swapping mechanism. Fritzing still works, but you won't be able to change parts properties."

"Cannot read file /home/danisch/bins/core.fzb: No such file or directory."

"Fritzing cannot load the parts bin"

and then does not find any parts to use.

Starting Fritzing (the script) does not issue any error message, but changes the working path and does not offer any parts to install, i.e. it just does not work without any complaints.

Means: Fritzing not working at all under 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: fritzing 0.9.3b+dfsg-4
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jan 2 11:14:20 2018
InstallationDate: Installed on 2017-10-24 (69 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
SourcePackage: fritzing
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Hadmut Danisch (hadmut) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fritzing (Ubuntu):
status: New → Confirmed
Revision history for this message
Jonah (jonah) wrote :

I'm also having this problem with a fresh install on Artful.

Revision history for this message
sattellite (sattellite) wrote :

In Debian bug tracker maintainer said that version 0.9.3b+dfsg-5 is fixed this problem. Can anyone of maintainers copy this fix to Ubuntu version?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891842

Revision history for this message
sattellite (sattellite) wrote :

As temporary fix of problem is install fritzing-parts and edit .desktop file.

Copy /usr/share/applications/fritzing.desktop to $HOME/.local/share/applications and add row "Path=/usr/share/fritzing/parts" to it end.

Revision history for this message
karah-IEEE (karah) wrote :

Thanks @sattellite, that fixed it!

Revision history for this message
Jan van den Hurk (janvdhurk3) wrote :

The problem as I see it, is in dir fritzing/fritzing-parts is a file parts.db which should have at least read authority.
Is only set so for the userid that installed it, Had to give the authority for any user that is allowed to use fritzing.
This should at least give an idea where the problem arises.

Revision history for this message
Georges Khaznadar (georgesk) wrote :

This problem is fixed in the last release, 0.9.3b+dfsg-9

Changed in fritzing (Ubuntu):
assignee: nobody → Georges Khaznadar (georgesk)
status: Confirmed → Fix Released
Revision history for this message
Андрей Сюткин (siutkinan) wrote :

Thanks @janvdhurk3, I add 'rm /usr/share/fritzing/parts/parts.db' before launch fritzing.real in script '/usr/bin/fritzing'.

Revision history for this message
Kyler Laird (kylerlaird) wrote :

Apparently no one else starts fritzing from the command line. This problem of not finding parts remains an issue if you run /usr/bin/fritzing from a directory other than /usr/share/fritzing/parts/. (I created a simple wrapper to change the directory before starting fritzing.) I'm using 0.9.3b+dfsg-4.1ubuntu1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.