When will Kicad 5 be available?

It’s possible, but how to do it depends on the system.

Getting closer!
https://lists.launchpad.net/kicad-developers/msg36729.html

Very… couldn’t wait anymore.

3 Likes

:fireworks: YAY! :sparkler: :tada:

Seems the mac package will take a few days: https://lists.launchpad.net/kicad-developers/msg36730.html

I guess this might be to blame: https://lists.launchpad.net/kicad-developers/msg36713.html

A big congratulation to the team of developers and librarians!!!

1 Like

5.0.0 reliably crashes for me on Windows 10

1 Like

https://forum.kicad.info/t/20jul18-v5-0-0-crash-in-3d-viewer/11617/10

The Error Window gets moved behind the KiCad Window. Minimize the KiCad Window and click “Cancel” on the Error Window; only needs to be done once per session from what I have observed.

ON EDIT: @davidsrsb ONLY the “Cancel” button ‘works’ on Windoze 7. You might want to alter your bug report with this information.

The Yes button works on Windows 10.
Can you add to my bug report for the Windows 7 case?

@davidsrsb Try clicking the Cancel button.

Clicking cancel seems to work. I am not sure what the error is going to do though.
Still, expecting new users to minimise pcbnew and find the hiding error dialog, which has grabbed focus, is a bit much.

1 Like

Its an unexpected bug, possibly due to the packager building KiCad incorrectly :confused:

I’ve seen no negative effects on the saved files; at this point in time. If I had, I would have also posted on the forum.

It does seem to affect what GUI buttons can be clicked with the mouse.

Well, I did post about it here first to discuss the issue. Apparently no one else had the issue and I had no way of knowing it was not a quirk on my machine.

The packagers have noticed some problems with compilation which lead to “assert” dialogs. All of you who have downloaded and installed 5.0.0: stay tuned for possible updates. At least Windows and OSX may have been affected. Problematic packages will be replaced in the download section of kicad.org.

I have the dubious honour of causing the first commit against the 5.0 release to fix this assert bug:

You have never linked to a bug report.

I have not yet needed to.
It is not my intent to waste developers time. My current machine/Windoze instal is anything but stable on it’s own. As such is the case, I always ask here if others are having the same problem and discuss whether or not the issue is KiCad related.
Majority of the time it is an already reported bug.

What then does the line “add your info to the bug report” mean? (Reporting anything only here makes no sense at all. You really need to report it on the bugtracker. Otherwise the devs will not be aware of any of the listed problems!)