@David i see you touched it last
i also see alexl have packaged it before

CC: (none) => luigiwalser

This is Alex's package.  I just touched it because I updated quazip once.

CC: luigiwalser => (none)
Assignee: bugsquad => loginov_alex

ping @Alex:
This is a leaf package so if you have the time...  :)

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

fritzing-0.8.7-0.beta20140124.4.mga5

http://www.zimagez.com/zimage/capturadetela2016-10-1622-23-55.php

Linux michael-pc 4.4.16-desktop-1.mga5 #1 SMP Tue Jul 26 09:23:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
task-xfce-minimal-4.12-1.mga5

CC: (none) => michaelfm21

Assigning to all packagers collectively, since there is currently no registered maintainer for this package.

Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Same bug on MAGEIA6 and fritzing 0.9.2 mga x64:

Errors are : 
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlDatabasePrivate::removeDatabase: connection 'qt_sql_default_connection' is still in use, all queries will cease to work.
QSqlDatabasePrivate::addDatabase: duplicate connection name 'qt_sql_default_connection', old connection removed.
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: 
QSqlDatabasePrivate::removeDatabase: connection 'qt_sql_default_connection' is still in use, all queries will cease to work.
QSqlDatabasePrivate::addDatabase: duplicate connection name 'qt_sql_default_connection', old connection removed.

In use :
- you can't add wire
- two components on the same line crashes with : Segment Fault (core dumped)

0.9.3 tar.bz2 run fine 

If nobody does it, I will look if I can modify src.rpm (not sure : my last packaging was twelve years ago)

CC: (none) => vincent

It would be nice to have this fixed for mga6 and maybe mga7.

This may be the last version of this program:
http://forum.fritzing.org/t/is-fritzing-dead-no-updates-since-june-2016/6095
- but it is really useful for beginners, hobbyists and schools many more years even if it do not get more updates than 0.9.3b.

Whiteboard: (none) => MGA6TOO

I will try to package this 0.9.3b version. But it needs a lot of build patches...

Assignee: pkg-bugs => lists.jjorge
Status: NEW => ASSIGNED
CC: (none) => lists.jjorge

Pushed to Cauldron, it needs a few hours to be built as we have a big todo list.

Whiteboard: MGA6TOO => (none)
Version: Cauldron => 6

Ready to test in MGA6.

RPMS:
fritzing-0.9.3b-0.git624187517fc89062a4e83d6c08d306863c0d4ec7.mga6.src.rpm

fritzing-0.9.3b-0.git624187517fc89062a4e83d6c08d306863c0d4ec7.mga6.x86_64.rpm

Suggested advisory :

The version is fritzing in MGA6 crashed often and was outdated. As the latest release is from 2016, we have updated both code and parts to Git status as of Oct 17 2018.

Assignee: lists.jjorge => qa-bugs

Release was too long, it is now :

fritzing-0.9.3b-1.git20181017*rpm

Thank you for working on this :)

Testing on mga6 x86_64

There seem to be a problem of location of the part bins:

On initial launch it display a dialog "Cannot read file /home/morgan/bins/core.fzb: No such file or directory."

And that is true, I dont have ~/bins/


After clicking OK in that dialog, there is a new dialog:

  "Fritzing cannot load the parts bin"
                                [ OK ]

Then it loads OK.
I noticed the parts bin seem to work: when i click a bin group the content is loaded.

Then i closed the program and started again.
Again the dialog about ~/bin

Then a dialog listing 24 parts it could not find.

OK that and main window shows up. but now clicking a parts bin there are errors "unable to find" the items.

(In reply to Morgan Leijström from comment #12)
> On initial launch it display a dialog "Cannot read file
> /home/morgan/bins/core.fzb: No such file or directory."

I could launch it once without any problem. Now when I try again, I can get this strange message. So I think it is because personal config files are created. Maybe upstream may explain?

MGA6-32 on IBM Thinkpad R50e MATE
No installation issues.
Launching it gives me the same dialogue as in Comment 12.
At the CLI I get:
$ fritzing 
QIODevice::read (QFile, "/home/tester6/bins/core.fzb"): device not open
QIODevice::read (QFile, "/home/tester6/bins/contribParts.fzb"): device not open
QIODevice::read (QFile, "/home/tester6/bins/core.fzb"): device not open
QIODevice::read (QFile, "/home/tester6/bins/contribParts.fzb"): device not open
 
and the parts list in fritzing is empty, and of course there is no bins directory.

CC: (none) => herman.viaene

The binary from upstream website do not have this issue.
It displays itself as 0.9.3 (b04.19)
Is this compiled from same sources?

... and addition the upstream version downloads updated components, which are used next start.

Found that the files not found as in Comment 14, are actually created in the pwd where fritzling happens to be opened.
In my case, the pwd was /home/tester6/Documenten and I find the files in /home/tester6/Documenten/Fritzing/bins and /home/tester6/Documenten/Fritzin/parts.

Seems odd to me that it looks in the wrong place for the files it created.

@ zezinho: From the sidelines. it looks as if this is not yet good. Both Morgan's and Herman's, + your own tests, point up problems.

From comment 0:
> the new version 0.9.3b ... Works great :)
Confirmed by Vincent in comment 6:
> 0.9.3 tar.bz2 run fine
and he may be able to help package this:
> If nobody does it, I will look if I can modify src.rpm
> (not sure : my last packaging was twelve years ago).
Morgan's comment 7 makes the effort seem worthwhile:
> This may be the last version of this program:
> but it is really useful for beginners, hobbyists and schools many more years
> even if it do not get more updates than 0.9.3b.
which suggests that we should include the updated package (once working) in Mageia 7.

CC: (none) => lewyssmith

Assigning back to packagers as the package needs to be fixed still.

Assignee: qa-bugs => lists.jjorge
CC: (none) => pkg-bugs, qa-bugs

Project have come alive again - at least it is moving forward!

Bugfix release 0.9.4 december 2019:
https://fritzing.org/download/history-changes/

Issue tracker is running, with dev replies:
https://github.com/fritzing/fritzing-app/issues 

New forum: https://forum.fritzing.org/

I happily paid the suggested fee and will use it for an official DIY design :)

The Fedora 30 download seem to run nicely on mga7, and downloads components libraries OK.  No problem for a half hour playing.  The bugs in comments above seem fixed.

Keywords: feedback => (none)
Version: 6 => 7

How development got going again :)
https://github.com/fritzing/fritzing-app/issues/3435#issuecomment-487213019
https://github.com/fritzing/fritzing-app/issues/3443

@José : Ping.

It is now over a year since this was shelved for various reasons, but comment 20 gives reason to re-launch it.
> Bugfix release 0.9.4 december 2019:
> The Fedora 30 download seem to run nicely on mga7, and downloads components
> libraries OK.  No problem for a half hour playing.  The bugs in comments
> above seem fixed.

This bug was reported initially for mga6, the mga7 release was updated and I think is workable as it should.

Also Cauldron is up-to-date with the latest 0.9.4 release.

CC: (none) => geiger.david68210

It is a huge difference in stability. I have been using 0.9.4 now for 20-30 hrs, not a single crash, plus some other bugs fixed, like problems described above :)

I can test an update on mga7, if made.

0.9.5 is 73% complete according to github, so probably as far away as mga8.

Still no new release but there is commit now and then
https://github.com/fritzing/fritzing-app/commits/develop

0.9.6 was released 2021-02-22
https://fritzing.org/releases/0-9-6

mga7 is still at 0.9.3b-6 (no update)
mga8 have fritzing-0.9.4-4.git20191201.mga8.x86_64.rpm
More history: upstream had 0.9.5d around, but not officially released.

-------

Source code is GNU GPL v3  (ref https://fritzing.org/faq/)

-------

Quick test on Mageia 7 of downloaded 0.9.6 Ubuntu 20.04 tar.gz from https://fritzing.org/download/

Just downloaded it, unzipped it, cd into it and $ ./Fritzing

It seems i had all needed dependencies installed, because it just works:

I put parts on schema, connected on breadboard, found that shema and PCB hade updated automatically, autorouted, exported to pdf, all OK.

Whiteboard: (none) => MGA7TOO
Version: 7 => 8

Cauldron, mga8 and mga7 now updated to latest 0.9.6 upstream release, please test them, thanks in advance!

Assigning to QA now,


Advisory:
========================

This updates fritzing to the latest version which is supported upstream. It adds several bugfixes.
And also it fixes this initial bug report which is "Fritzing crashes sometimes".

========================

Packages in 7/core/updates_testing:
========================
fritzing-0.9.6-1.mga7.i586.rpm
fritzing-0.9.6-1.mga7.x86_64.rpm

Packages in 8/core/updates_testing:
========================
fritzing-0.9.6-1.mga8.i586.rpm
fritzing-0.9.6-1.mga8.x86_64.rpm


Source RPM: 
========================
fritzing-0.9.6-1.mga7.src.rpm
fritzing-0.9.6-1.mga8.src.rpm

Assignee: pkg-bugs => qa-bugs

Thanks, that was agile.
Quick test: There is something wrong with it not finding things: At launch there are three consecutive message popups:

§ Unable to find parts git repository

§ Cannot read file screw_terminal_2_3.5mm.fzp:
No such file or directory.

§ Unable to find the following 159 part(s):
<and a list of them here>

Similar problems if trying to open examples.



In my test in comment 27 using the tar.gz it found everything.  And also my earlier projects i have in a custom location, defined from earlier when i used 0.9.3b from another tar.gz. it found, but the rpm packaged verison do not.
So two isssues:
1) dont find data files that is supposed to be packaged.
2) dont find user config file

Also see comment 17, may be similar now, but i have to quit for today.
Also in future it maybe will want to download updated content like earlier version see comment 16, i dont know how to check that... but at least it seems it need to check upstream git part repo if i understand first error message correctly.

Note: I never tested the previous fritzing Mageia rpm on mga7.
(only used tar.gz from upstream.)

Assignee: qa-bugs => pkg-bugs

So after some research i found what is going wrong with parts path! We have to generate the parts database (parts.db in /usr/share/fritzing/parts/) but for an unknown reason I don't know why we can't build this database like fedora or archlinux does :(

I tried the fedora method during build adding :

# Generate the parts database
./Fritzing -platform minimal -f ./parts -db ./parts/parts.db

But fails on BS with:

+ ./Fritzing -platform minimal -f ./parts -db ./parts/parts.db
/home/iurt/rpmbuild/tmp/rpm-tmp.FO9JLJ: line 43: 23315 Aborted                 (core dumped) ./Fritzing -platform offscreen -f ./parts -db ./parts/parts.db
error: Bad exit status from /home/iurt/rpmbuild/tmp/rpm-tmp.FO9JLJ (%build)

And on my own system fails with:

+ ./Fritzing -platform minimal -f ./parts -db ./parts/parts.db
This plugin does not support propagateSizeHints()


If you download the fedora package and take their "parts.db" file and copy it in  "/usr/share/fritzing/parts/" it works fine w/o any warnings.

Thanks for working on it :)

Unfortunately neither Flatpak nor Appimage exist, and the 0.9.6 Ubuntu tar.gz working on mga7 is more like pure luck...

We have to founf how to create this missing parts.db files :(

Can you open a new bug report upstream please? at https://github.com/fritzing/fritzing-app/issues/

https://github.com/fritzing/fritzing-app/issues/3796

Nothing new upstream, sent a ping.
Mga7 is EOS

Whiteboard: MGA7TOO => (none)

Still no response to our request for help.

Meanwhile, upstream released 0.9.8, and have an Appimage.
"Funnily" that Appimage have problem creating the database.

There exist an (unofficial?) flatpak of 0.9.6, that seem to work nicely.

Details at https://forum.fritzing.org/t/is-fritzing-still-free/13649/5

Stumbled on this build instruction
https://github.com/fritzing/fritzing-app/wiki/4.-Publishing-a-Release

Version 9.9 got released september
https://blog.fritzing.org/2021/09/24/fritzing-0-9-9

Source code
https://github.com/fritzing/fritzing-app

Flatpak are only available unofficiallly and as old 9.6

I did not want to pay to try 9.9 Appimage, I paid for 9.8 which Appimage did not work, see above...

Wonder if both their appimage and the package we tried to build our own stumble on the same thing...  But they say they tested on Fedora 34.

hello,
Launching the command:
Fritzing -f ./parts -db ./parts/parts.db
I get a message dialogue box:
"Unable to find parts git repository"

CC: (none) => yves.brungard_mageia

@papoteur: which version, and type of install?

Revisiting

§ Version 0.9.10 was released in may.

§ No response in our upstream help request.

§ No new inofficial Flatpak version since 0.9.6 (and non at all official)

Appimage are released at a (moderate) cost.
The 0.9.8 I tried before seem to work if I manually download the parts:

 cd /usr/share/fritzing/
 sudo git clone https://github.com/fritzing/fritzing-parts.git

It was a hint from searching internet. It also said to 
  sudo mv fritzing-parts/ parts
But i have not checked the implications.

* Interesting *

With this, our Fritzing 0.9.6 seem to work!
But by now it is old...
I am loosing interest in this myself
But I could make a quick test if new version is packaged.
Anyhow it seems user need to know to fetch the parts lib.
And the program fritzing will probably not update the parts lib when updated upstream.  Guessing.  Should ask on fritzing forum.  Too tired.

URL: (none) => https://github.com/fritzing

Still no response to our upstream bug

So drop from Cauldron/mga9!

Check: the Appimage from upstream do work. (64 bit, on mga8)

Bit the bullet and bought 0.9.10
I could use it to open old sketch made with 0.9.4, 
And also create and save fresh stuff.
And printed.

Still no official flatpak.

We have alternative packages in Mageia so this is maybe worth a Errata entry if we don't drop fritzing befor MGA9 release.
Fritzings seems inactive/dead again as the last release is from March 2021 and there are over 500! open issues!

Alternative packages in Mageia:
geda
kicad
ngspice
pcb
logisim

and some digital circuit simulator packages...

Hey! hey! stop!

Why drop it??

we have latest release on Mageia Cauldron fritzing-0.9.10-1.mga9 and it work as it should.

That sounds great David!

OK so the problem is this bug until now have not gotten that info!
I will test it today on mga9.

Regarding Fritzing itself it is a bit special hobbyist thing.
Integration between schema and breadboard is common, but this have breadboard mode too, all three in parallel.
Nice to play with as electronics starter, but have quirks.
Project seem dead sometimes, but there is activity still on dev and user forum.

Nice!

I confirm fritzing-0.9.10-1.mga9 works good on mga9 :)

Can we have it in mga8?

Please test upcoming fritzing-0.9.6-1.1.mga8


Packages in 8/core/updates_testing:
========================
fritzing-0.9.6-1.1.mga8.i586.rpm
fritzing-0.9.6-1.1.mga8.x86_64.rpm


Source RPM: 
========================
fritzing-0.9.6-1.1.mga8.src.rpm

OK it launches and seem to working in a quick test
So useable

But a rather big problem though: During launch it pops up a message:

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

So like in comment 4 from 2016...

In terminal where i launched it there are hundreds of lines of:
QSqlQuery::prepare: database not open

And of course 0.9.6 is a few versions behind what users expect anyway.

Is there a problem packaging fritzing-0.9.10 in mga8?

We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Resolution: (none) => OLD
Status: ASSIGNED => RESOLVED