Quantcast
Channel: bugs - fritzing forum

French traduction

$
0
0

Hello.
I saw 2 french translations errors
Menu Edit → Preferences → Code View

plateforme supportées => Plateformes supportées
Emplaceement => Emplacement

image

I don’t know how to correct. So if some one know how to …

Regards

2 posts - 2 participants

Read full topic


Cannot change pin labels on my parts

$
0
0

I am creating parts for my own SDIP package.

In Version 0.9.10, I had a problem where the pin labels in my parts in the schematic view would disappear every time I opened a sketch, but I was able to get it back by re-editing the pin labels.

After updating to Version 1.0.0, the pin labels no longer change from the pin number when they are edited.

Since it is a DIP package, I tried overwriting the my parts data with the Generic IC schematic image, but it still showed the pin number even after editing the pin label.

6 posts - 2 participants

Read full topic

Version 1.0.1 crashes when doing anything

$
0
0

Hi,
I just recently (like 10 minutes ago) bought Fritzing for my Mac (running Venture 13.2) on an Intell processor. The Fritzing application starts, but if I try to do anything, like even move the window, it crashes immediately.
What can I do to help log the problem, and hopefully resolve it so I can use the application?
Thanks,
Doug

What I expected should have happened instead:

My version of Fritzing and my operating system:

Please also attach any files that help explaining this problem

3 posts - 3 participants

Read full topic

Parts of traces vanish after aligning connected objects

$
0
0

PCB View

Steps I took that resulted in the problem:

Two headers connected by traces. Ctrl+clicked both, chose Part → Align → Align Horizontal Center.

What I expected should have happened instead:

I would expect parts to align (which they do) without the portions of the traces vanishing.

NOTE: The traces are still there; grabbing any bend point and moving it will restore that trace’s visibility. I’ve also had it add additional bend points.

My version of Fritzing and my operating system:

Fritzing 1.0.1, fresh install
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-83-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Xeon® CPU E31225 @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NV167

Please also attach any files that help explaining this problem
BEFORE

AFTER

2 posts - 2 participants

Read full topic

Text padding affects horizontal alignment

$
0
0

PCB View

Put a text object onto the workspace, type in “PEPPERONI”. Put another text object onto the workspace below the first, type in “ONIONS”. Select both objects, then select Part → Align → Align Right.

The objects themselves align, but because the padding is affected by the character count, the text does not align.

I would have expected the text to be aligned.

Fritzing 1.0.1
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-83-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Xeon® CPU E31225 @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NV167

2 posts - 2 participants

Read full topic

Trace snapping behaves unpredictably when angled traces are involved

$
0
0

Fritzing 1.0.1
Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-83-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Xeon® CPU E31225 @ 3.10GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NV167

Create a trace with a segment angled to something other than a multiple of 90°. Hold the SHIFT key and drag a bendpoint. The bendpoint might vanish or appear somewhere else, the trace might move along on the angled axis.

I would expect the bendpoint to snap to some multiple of 90°, e.g. 0, 22.5, 45, 90, to make aligning traces easier.

Tried to link a small video, but MP4s aren’t allowed. Converted to GIF, but then it was too big. Here’s a link to a video that demonstrates the problem..

1 post - 1 participant

Read full topic

Part Edit crashes

$
0
0

1rst Time using Fritzing, 1st time using Part Editor
I need a new part, Shelly Uni.

just played a little with parts editor
started fritzing
click on breadboard
click on core part , generic resistor
click on Part Edit
click on Schematic
deleted X Connector Pins
click 3 times on a deleted connector Fritzing crashes

Tried with different parts

My version of Fritzing and my operating system:

Windows 11, Fritzing 1.0.1

2 posts - 2 participants

Read full topic

Fritzing Will Not Open - MacOS Ventura

$
0
0

Steps I took that resulted in the problem:

I recently downgraded from Mac OS Sonoma to Ventura. Now fritzing will not open. I bought another copy and downloaded it and installed fresh, but am still getting this error:


Translated Report (Full Report Below)

Incident Identifier: 97C17688-BE80-4773-976D-44202B4B4B8E
CrashReporter Key: 9A0825E9-DE47-6FA4-CAC0-198185AEBC25
Hardware Model: MacBookPro18,1
Process: Fritzing [1568]
Path: /Applications/Fritzing.app/Contents/MacOS/Fritzing
Identifier: org.fritzing.Fritzing
Version: 1.0.0 (353be4)
Code Type: X86-64 (Native)
Role: Background
Parent Process: launchd [1]
Coalition: org.fritzing.Fritzing [1318]

Date/Time: 2023-11-06 11:29:09.0748 -0800
Launch Time: 2023-11-06 11:29:05.9524 -0800
OS Version: macOS 13.6.1 (22G313)
Release Type: User
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: ROSETTA 0

Triggered by Thread: 0

Thread 0 Crashed:
0 runtime 0x7ff7fff16544 0x7ff7fff12000 + 17732

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000022 x1: 0x0000000000000000 x2: 0x00007ff7fff43311 x3: 0x0000000000000800
x4: 0x00007ff7fff3e40e x5: 0x0000000000000000 x6: 0x000000000000002c x7: 0x0000000000000000
x8: 0x00007ff7fff4d000 x9: 0x0000000000000000 x10: 0x00000000fffffed4 x11: 0x0000000000000010
x12: 0x0000000000000078 x13: 0x000000000000001e x14: 0x00007ff7fff35980 x15: 0x00007ff7fff4d8b4
x16: 0x0000000000000209 x17: 0x000000030a779ae7 x18: 0x000000030a77a0ab x19: 0x00007ff7fff43311
x20: 0x00007ff7fff43311 x21: 0x0000000000000063 x22: 0x00007ff7fff3dddf x23: 0x000000030a779c10
x24: 0x000000010c2d02e0 x25: 0x0000000000000248 x26: 0x0000000000000009 x27: 0x0000000203b14000
x28: 0x0000000000000001 fp: 0x000000030a779ba0 lr: 0x00007ff7fff2fc18
sp: 0x000000030a779b80 pc: 0x00007ff7fff16544 cpsr: 0x40001000
far: 0x0000000000000000 esr: 0x56000080 Address size fault

Binary Images:
0x203a6c000 - 0x203b07fff dyld () <3df96f32-b9c9-3566-a6b7-4daebc6d6563> /usr/lib/dyld
0x7ff7fff12000 - 0x7ff7fff41fff runtime (
) <15ccd9bf-9a15-3540-a1ff-3abea3e2ca9d> /usr/libexec/rosetta/runtime

Error Formulating Crash Report:
dyld_process_snapshot_get_shared_cache failed

EOF


Full Report

{“app_name”:“Fritzing”,“timestamp”:“2023-11-06 11:29:09.00 -0800”,“app_version”:“1.0.0”,“slice_uuid”:“78f648a4-85e7-3af1-bcdd-8d594c00d837”,“build_version”:“353be4”,“platform”:0,“bundleID”:“org.fritzing.Fritzing”,“share_with_app_devs”:0,“is_first_party”:0,“bug_type”:“309”,“os_version”:“macOS 13.6.1 (22G313)”,“roots_installed”:0,“name”:“Fritzing”,“incident_id”:“97C17688-BE80-4773-976D-44202B4B4B8E”}
{
“uptime” : 380,
“procRole” : “Background”,
“version” : 2,
“userID” : 504,
“deployVersion” : 210,
“modelCode” : “MacBookPro18,1”,
“coalitionID” : 1318,
“osVersion” : {
“train” : “macOS 13.6.1”,
“build” : “22G313”,
“releaseType” : “User”
},
“captureTime” : “2023-11-06 11:29:09.0748 -0800”,
“incident” : “97C17688-BE80-4773-976D-44202B4B4B8E”,
“pid” : 1568,
“translated” : true,
“cpuType” : “X86-64”,
“roots_installed” : 0,
“bug_type” : “309”,
“procLaunch” : “2023-11-06 11:29:05.9524 -0800”,
“procStartAbsTime” : 9067169948,
“procExitAbsTime” : 9142077506,
“procName” : “Fritzing”,
“procPath” : “/Applications/Fritzing.app/Contents/MacOS/Fritzing”,
“bundleInfo” : {“CFBundleShortVersionString”:“1.0.0”,“CFBundleVersion”:“353be4”,“CFBundleIdentifier”:“org.fritzing.Fritzing”},
“storeInfo” : {“deviceIdentifierForVendor”:“D2A8EA88-0EA7-5D4B-93C2-1B46D0CCD2E8”,“thirdParty”:true},
“parentProc” : “launchd”,
“parentPid” : 1,
“coalitionName” : “org.fritzing.Fritzing”,
“crashReporterKey” : “9A0825E9-DE47-6FA4-CAC0-198185AEBC25”,
“codeSigningID” : “org.fritzing.Fritzing”,
“codeSigningTeamID” : “YNHU8667XW”,
“codeSigningFlags” : 570503953,
“codeSigningValidationCategory” : 6,
“codeSigningTrustLevel” : 0,
“sip” : “enabled”,
“exception” : {“codes”:“0x0000000000000000, 0x0000000000000000”,“rawCodes”:[0,0],“type”:“EXC_CRASH”,“signal”:“SIGABRT”},
“termination” : {“namespace”:“ROSETTA”,“flags”:518,“code”:0},
“extMods” : {“caller”:{“thread_create”:0,“thread_set_state”:0,“task_for_pid”:0},“system”:{“thread_create”:0,“thread_set_state”:0,“task_for_pid”:0},“targeted”:{“thread_create”:0,“thread_set_state”:0,“task_for_pid”:0},“warnings”:0},
“faultingThread” : 0,
“threads” : [{“triggered”:true,“id”:18563,“threadState”:{“x”:[{“value”:34},{“value”:0},{“value”:140703127843601},{“value”:2048},{“value”:140703127823374},{“value”:0},{“value”:44},{“value”:0},{“value”:140703127883776},{“value”:0},{“value”:4294966996},{“value”:16},{“value”:120},{“value”:30},{“value”:140703127787904},{“value”:140703127886004,“symbolLocation”:12,“symbol”:“crashreporter_info”},{“value”:521},{“value”:13060512487},{“value”:13060513963},{“value”:140703127843601},{“value”:140703127843601},{“value”:99},{“value”:140703127821791},{“value”:13060512784},{“value”:4499243744},{“value”:584},{“value”:9},{“value”:8651882496,“symbolLocation”:0,“symbol”:“dyld_all_image_infos”},{“value”:1}],“flavor”:“ARM_THREAD_STATE64”,“lr”:{“value”:140703127763992},“cpsr”:{“value”:1073745920},“fp”:{“value”:13060512672},“sp”:{“value”:13060512640},“esr”:{“value”:1442840704,“description”:" Address size fault"},“pc”:{“value”:140703127659844,“matchesCrashFrame”:1},“far”:{“value”:0}},“frames”:[{“imageOffset”:17732,“imageIndex”:1}]}],
“usedImages” : [
{
“source” : “P”,
“arch” : “x86_64”,
“base” : 8651194368,
“size” : 638976,
“uuid” : “3df96f32-b9c9-3566-a6b7-4daebc6d6563”,
“path” : “/usr/lib/dyld”,
“name” : “dyld”
},
{
“source” : “P”,
“arch” : “arm64”,
“base” : 140703127642112,
“size” : 196608,
“uuid” : “15ccd9bf-9a15-3540-a1ff-3abea3e2ca9d”,
“path” : “/usr/libexec/rosetta/runtime”,
“name” : “runtime”
}
],
“vmSummary” : “ReadOnly portion of Libraries: Total=1168K resident=0K(0%) swapped_out_or_unallocated=1168K(100%)\nWritable regions: Total=136.2M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=136.2M(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nRosetta Generic 8K 2 \nRosetta IndirectBranch (reserved) 32K 1 reserved VM address space (unallocated)\nRosetta JIT 128.0M 1 \nSTACK GUARD 56.0M 1 \nStack 8176K 1 \nVM_ALLOCATE (reserved) 200K 4 reserved VM address space (unallocated)\n__DATA 80K 3 \n__DATA_CONST 32K 1 \n__DATA_DIRTY 16K 1 \n__LINKEDIT 368K 4 \n__TEXT 816K 2 \nmapped file 22.9M 10 \n=========== ======= ======= \nTOTAL 216.4M 31 \nTOTAL, minus reserved VM space 216.2M 31 \n”,
“legacyInfo” : {
“threadTriggered” : {

}
},
“logWritingSignature” : “688a19c16328f596b1e3e85910df1080cee36ebf”,
“trialInfo” : {
“rollouts” : [
{
“rolloutId” : “6297d96be2c9387df974efa4”,
“factorPackIds” : {

  },
  "deploymentId" : 240000014
},
{
  "rolloutId" : "5ffde50ce2aacd000d47a95f",
  "factorPackIds" : {

  },
  "deploymentId" : 240000348
}

],
“experiments” : [

]
},
“reportNotes” : [
“dyld_process_snapshot_get_shared_cache failed”
]
}

Model: MacBookPro18,1, BootROM 10151.1.1, proc 10:8:2 processors, 16 GB, SMC
Graphics: Apple M1 Pro, Apple M1 Pro, Built-In
Display: Color LCD, 3456 x 2234 Retina, Main, MirrorOff, Online
Display: S27E310, 1920 x 1080 (1080p FHD - Full High Definition), MirrorOff, Online
Memory Module: LPDDR5, Samsung
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x4387), wl0: May 27 2023 01:34:59 version 20.96.31.0.8.7.148 FWID 01-126f2c4c
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: USB2.0 Hub
USB Device: DeskJet 2700 series
USB Device: Gaming Mouse G400
USB Device: USB2.0 Hub
USB Device: USB31Bus
USB Device: ArmorATD
USB Device: USB31Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.

What I expected should have happened instead:

My version of Fritzing and my operating system:

Fritzing 1.1 (also tried 1.0) and Ventura 13.6.1

Please also attach any files that help explaining this problem

Thank you!
-Erin

3 posts - 2 participants

Read full topic


Fritzing Crashes on MacOS 14.1.2

$
0
0

Steps I took that resulted in the problem:

Loading any components or loading circuit examples crashes Fritzing.

My version of Fritzing and my operating system:

Fritzing Version 1.01 (also tried version 1.0.0)
Running on Macbook Pro 2019 Intel, running MacOS Sonoma 14.1.2

6 posts - 2 participants

Read full topic

Cannot import any part file

$
0
0

Steps I took that resulted in the problem:

During the import process of a part, the part does not import and produces an error message ‘The system cannot find the file specified’. I have tried to import several parts from several sources, all failed with the same error message. It does not matter where I download the parts to on my PC, they all fail to import.

What I expected should have happened instead:

Parts can be imported.

My version of Fritzing and my operating system:

1.0.2
Windows 11

Please also attach any files that help explaining this problem

2 posts - 2 participants

Read full topic

Exporting breadboard as SVG bugs

$
0
0

Posting this here as I guess I came off too strong on a GitHub post and got in trouble and in timeout for a month… Sorry, my frustration got the best of me. :sweat_smile:

Two issues when exporting as an image and selecting SVG as the format.

  1. The sizing is not correct and it causes the image (and in turn parts) to appear cutoff. If I manually edit the SVG file values, I can resolve this issue though but of course that shouldn’t be needed.
  2. Wires don’t align with the pins they are attached to as expected. This does not happen when I export as PNG/JPG/PDF.

Steps I took that resulted in the problem:

  1. Create breadboard diagram
  2. File > Explort > as Image > SVG
  3. View file

What I expected should have happened instead:

All parts viewable (not cutoff) and wires align where they are supposed to be as with other export methods.

My version of Fritzing and my operating system:

V1.02
macOS 14.2.1

I’ve attached the SVG which you can see has issues. I’ve also attached a PNG and PDF which do not. I’m wanting to export as SVG for two reasons:

  1. Where I plan to use the image.
  2. Only when exported as SVG do the pins not highlight.

Please let me know if you need anything further.
heltec v3 cardkb


7 posts - 3 participants

Read full topic

Is the ESP32 broken?

$
0
0

Steps I took that resulted in the problem:

Setting up a few sensors (BME280, BH1750 and AM312) together with an RGB LED (common anode) plus 3 resistors connected to an ESP32/30pin in breadboard view - switched over to circuit view and wondered about suggested wiring. Set up a new breadboard with LED / resistors only connected to the ESP32 - same weird wiring suggested.

What I expected should have happened instead:

R, G and B should connect to Pins RX2, TX2 and D18, anode should connect to 3V3.

My version of Fritzing and my operating system:

0.9.4 and Win10
(Actually I can’t find my paid download and don’t want to pay again right now.)

Please also attach any files that help explaining this problem



8 posts - 2 participants

Read full topic

Ground Fill taking a lot of space

$
0
0

Hey there,

I wanted to design a pcb to manufacture it via PCB-milling.
When I add the ground fill as the last step the file size grows from ~4kB to ~500kB. Unfortunately the processing software to generate the g-code can’t handle the file with the ground fill.

Maybe it is possible to have the interrupted soldering pad without the ground fill algorithm manually?

I also asked the developer of CopperCAM if he has an idea. This is what he wrote:

The bases (GroundFill) consist of thin hatch lines. CopperCAM calculates the outlines for each, then the collisions with everything else, then the connections. This takes a lot of time.

The Gerber RS274X format allows direct generation of surface polygons with G36/G37 codes. You must use these polygons. There must be an option for this in the Gerber output.
(Translated with DeepL)

Should I file a bug report on github to export the ground fill as polygons?

Thanks for your help!
Sammy

I’m on Linux with fritzing 1.0.2

6 posts - 3 participants

Read full topic

New Ground fill bug

$
0
0

Hello all.

I was preparing a PCB for manufacturing and I noticed that the new ground fill is not generating a proper file. More specifically, I saw that the part’s trace pads are connected to the copper fill when they shouldn’t be connected.

I tried the old ground fill and I didn’t get this problem. The part I’m using is the JDY-23 which you can find here: JDY-23 / JDY-23A BLE module. I never had an issue using ground fill in the past using older versions of Fritzing with this part.

You can see what the new ground fill generated and how the part’s pad are connecting to the copper fill:

and what the old ground fill generated where the pads are not connecting:

Thanks,
steliosm

2 posts - 2 participants

Read full topic

I can't open any sketches files

$
0
0

Hello, I just downloaded Fritiz yesterday and I was working on a sketch, today I was trying to open it but it gives me this error

Unable to open ‘C:/Users/ana-a/OneDrive/desktop/
Untitled Sketch 2.fzz’: zip.open(): %d

I tried to create a new sketch and save it to see if there was a problem on the previous file but still the same, even the new sketch is not opening.

12 posts - 2 participants

Read full topic


Schematic Frame

$
0
0

Steps I took that resulted in the problem:

Updated from 0.9.6 to 1.0.2

What I expected should have happened instead:

Schematic frame showed ok in 0.9.6 and not data box shows huge in 1.0.2

My version of Fritzing and my operating system:

0.9.6 → 1.0.2
Windows 10

V0.9.6

V1.0.2

4 posts - 2 participants

Read full topic

Fritzing will not install on Win 11 Home

$
0
0

Steps I took that resulted in the problem:

…Opened the installer file and got an error that windows installer service could not be accessed.Win 11 missing the msi server

What I expected should have happened instead:

…It would have installed if msiserver was installed

My version of Fritzing and my operating system:

…1.0.2 Windows 11 Home

Please also attach any files that help explaining this problem

2 posts - 2 participants

Read full topic

Silkscreen image wrong size?

$
0
0

Hi,
I’m having an issue with the silkscreen image being the wrong size when exported to Gerber file.
Here you can see the difference between Fritzing and Gerbv.

Even if I put the image much smaller (or larger) it always appear that size in the Gerber.

(using Fritzing 1.0.3)
Thanks!

13 posts - 3 participants

Read full topic

Fritzing 1.0.1 unable to retrieve update info

$
0
0

Steps I took that resulted in the problem:

Tested 2 machines

What I expected should have happened instead:

Download en update parts

My version of Fritzing and my operating system:

Linux Mint 22 / Fritzing 1.0.1

Please also attach any files that help explaining this problem

16 posts - 4 participants

Read full topic

Installation errors

$
0
0

Installing Fritzing - Error Messages: Can somebody assist me with the following error message when attempting installation with Microsoft Windows 10 Pro on Desktop HP ZBook 15 G2:

  1. Called RunScript when not marked in progress.
  2. Called InstallFinalize when no install in progress.
  3. Fritzing setup ended prematurely because of an error. Your system has not been modified. To install this program at a later time, please run the installation again.

Tried a few times with no luck.

2 posts - 2 participants

Read full topic

Silkscreen not appearing in JLCPCB

$
0
0

Hi Folks ! I’m facing kind of weirdness with my pcb. I made a two layer drawing with Inkscape. I made proper XML editing for the ID of the two objects : the shape of the pcb and the silkscreen. I tried two methods : Importing the shape and next importing the silkscreen with the icon. I then also tryed to import in Fritzing both board shape and silkscreen at the same time. While doing this everything worked fine, but : When I upload the gerber file in JLCPCB the silkscreen is no more here. What happened ? I don’t know… Why could it be ? I don’t know. What could be the problem ? Does anyone know what is that issue ? it’s the first time it happens to me … Thanks for your answers !!
JTPCB

5 posts - 2 participants

Read full topic

Missing components after exporting as SVG

$
0
0

My OS & Fritzing version

macOS Sonoma 14.4.1
Fritzing 1.0.3

So I was exporting the breadboard view of a college work to svg, but some parts I´m using are not showing in the final svg.

Here is the file I’m working with:
ESP32_Greenhouse.fzz (89.4 KB)

I’ve read there is some isue with the parts id, but I couldn’t figure it out how to resolve them.

2 posts - 2 participants

Read full topic


Updated design is not sent to PCBWAY

$
0
0

Steps I took that resulted in the problem:

  1. Make design e.g. v1.1 and press Fabricate > PCBWAY > Open browser. v1.1 is seen in the PCBWAY website.
  2. Update design to v1.2, save, press Fabricate > PCBWAY > Open browser. v1.1 one is still shown in the PCBWAY website and not the updated design.

What I expected should have happened instead:

Expected the updated design to be sent to PCBWAY. In the processing window it seems like the zipping process goes very fast/skipped, so I am thinking it does not zip the updated design and just sends the old design to PCBWAY.

My version of Fritzing and my operating system:

Fritzing 1.0.4
MacOS Sonoma 14.7.1

9 posts - 2 participants

Read full topic

Using 555 timer chip doesn't work

$
0
0

Steps I took that resulted in the problem:

Created a simple timer circuit with a 555 timer chip. Started the simulation, LED does not flash, just stays steady on. In the console, i get an error over and over again:

SendCharFunc (libId:0): stderr Error: vector time not found!

What I expected should have happened instead:

LED light should flash on and off and no error should occur in the console

My version of Fritzing and my operating system:

version 1.0.4 of Fritzing on Ubuntu 24.10

Please also attach any files that help explaining this problem

5 posts - 2 participants

Read full topic

Fritzing crashes when try to simulate

$
0
0

Hi everybody. I am very keen of working with “fritzing” and I cannot wait to start with it but, this morning, with a very simple circuit only for testing (resistor+led+arduino UNO as power 5v) when I pushed the “Simulate” button, I have got an error. (In Spanhis):

Fritzing capturó una excepción de simulationButton en el evento 3: bad_function_call

After that, I click on the window error button and Frintzing close.
As I said, I would like to download it and start working but, I cannot do it that, in advance, I know it does not work.

I have it installed in Linux Mint 22 totally updated (Fritzing 1.0.1) working into VMWare WorkStation 17.6.2 for Windows (Windows 11 updated). I have got glibc installed. I have checked it with “lld --version” utility. My versión is GLIBC 2.39-0ubuntu8.3

Captura de pantalla 2025-01-03 090509

By the way, I would like to have it installed both on Windows 11 and Linux. When this issue is fixed, may I download the tool for both OS in one payment? Thanks.

2 posts - 2 participants

Read full topic



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>