Your message dated Thu, 9 Feb 2017 19:02:50 +0100
with message-id <20170209180250.3i2vzxt3bbctq6gb@localhost>
and subject line The last version provides the bugfix
has caused the Debian Bug report #854430,
regarding fritzing: Fritzing fails to find core parts
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
854430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fritzing
Version: 0.9.3b+dfsg-4
Severity: grave
Similar to 847655, while displaying a screen that says, "loading bin
'Core Parts'", Fritzing displays another screen that says, "Cannot read
file screw_terminal_2_3.5mm.fzp: No such file or directory.". That file
exists in /usr/share/fritzing/parts/core/. After clicking OK on that
screen, Fritzing displays a screen titled "Unable to find the following
143 parts:". I randomly selected several and all were in
/usr/share/fritzing/parts/core. After continuing from there, almost no
parts are displayed.
Directly calling /usr/bin/fritzing instead of the wrapper
/usr/bin/Fritzing generates an error that it cannot find the file
/usr/share/fritzing/parts/core/bins/core.fzb. That file is actually in
/usr/share/fritzing/parts/bins/core.fzb. Again, continuing results in
almost no parts displayed.
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fritzing depends on:
ii fritzing-data 0.9.3b+dfsg-4
ii libc6 2.24-9
ii libgcc1 1:6.3.0-6
ii libgit2-24 0.24.5-1
ii libgl1-mesa-glx [libgl1] 13.0.4-1
ii libqt5concurrent5 5.7.1+dfsg-3+b1
ii libqt5core5a 5.7.1+dfsg-3+b1
ii libqt5gui5 5.7.1+dfsg-3+b1
ii libqt5network5 5.7.1+dfsg-3+b1
ii libqt5printsupport5 5.7.1+dfsg-3+b1
ii libqt5serialport5 5.7.1~20161021-2
ii libqt5sql5 5.7.1+dfsg-3+b1
ii libqt5sql5-sqlite 5.7.1+dfsg-3+b1
ii libqt5svg5 5.7.1~20161021-2
ii libqt5widgets5 5.7.1+dfsg-3+b1
ii libqt5xml5 5.7.1+dfsg-3+b1
ii libstdc++6 6.3.0-6
ii zlib1g 1:1.2.8.dfsg-5
fritzing recommends no packages.
Versions of packages fritzing suggests:
ii fritzing-parts 0.9.3b-1
-- no debconf information
--
Neil Roeth
--- End Message ---
--- Begin Message ---
Fritzing version 0.9.3b+dfsg-4 provides a workaround for this bug: it
invokes the command 'fritzing' after a working directory change.
Please be sure to call the command 'Fritzing' in order to launch it
safely (this command name did not change, and the .desktop file taken in
account in the applications menu behaves as expected).
signature.asc
Description: PGP signature
--- End Message ---
