Commits

• fixed a circle/ellipse trimming issue (Dongxu Li)

What's Changed

• Exiting print preview displays wrong drawing #1207 by @israelmsnts in #1696
• fix compilation with clang and llvm's libcxx by @dpronin in #1798

New Contributors

• @israelmsnts made their first contribution in #1696
• @dpronin made their first contribution in #1798

Full Changelog: 2.2.0.2...2.2.0-latest

Bugfix release 2.2.0.2

This is a bugfix release for official stable release 2.2.0.

It fixes 3 minor issue:

• An undetected vulnerability, opening malformed LFF font files caused a crash
• Format issues in bundled fonts
• A regression, finding nearest points on ellipses caused a crash

MD5 sums:

747e2e9986801d87b94e67d76a5807e9  LibreCAD-2.2.0.2-x86_64.appimage
39f31210941ae2f94f757ff3d677e889  LibreCAD-2.2.0.2.dmg
f73213a4c8036f46ef0a397efd5d7b16  LibreCAD-Installer-2.2.0.2.exe

SHA256 hashes:

e5f32dce953b856f357bb3ccaaffa30cad99459bbd0d474ab07b16065249c7fb  LibreCAD-2.2.0.2-x86_64.appimage
552e2ac63fca297c617511c3983be7477bc050e8f774841abb7db5ce81ce935b  LibreCAD-2.2.0.2.dmg
996014cc38e0e98d274fbbb89e4f6ff92455e487e3a06ba46a38feb7c575a9d2  LibreCAD-Installer-2.2.0.2.exe

Bugfix release 2.2.0.1

This is a bugfix release for official stable release 2.2.0.

It fixes a minor vulnerability (CVE-2023-30259) with a mature shapelib contained in our codebase.
The vulnerability addresses only the plugin Importshp, which is used to import shape files (SHP/SHX/DBF).
Shape files are used in surveying and so do not affect the most users.
As this is probably not a widely used plugin, the fix was just to remove the plugin.

If you are a surveyor and need the shape file support, it is safe to stay with 2.2.0 version, as long as you know the origin of the used shape files.
The vulnerability is an out-of-bounds read, what means, if a malformed shape file is imported, the application can crash.
With some efforts an attacker possibly can create a shape file, which can lead to unintended code execution and seize your computer.
But this is a worst case scenario, which I would rate as extremely low to occur.

MD5 sums:

059e5fff8d19b4ff729ea8d07656209c  LibreCAD-2.2.0.1-x86_64.AppImage
33b0675ea52c77f2f1f6c8861677414d  LibreCAD-2.2.0.1.dmg
5aaa9f6b237fdfd42a4095058584dbcb  LibreCAD-Installer-2.2.0.1.exe

SHA256 hashes:

278967ae89398e07321ff4bd430e9cfbff4b9d17b887113d08fb51c8f2def2e7  LibreCAD-2.2.0.1-x86_64.AppImage
23b47914440c99d6d0371e67d31f5bb328ad8f6966d7ed564820cb7a71a3b350  LibreCAD-2.2.0.1.dmg
f1520db7a6ef13928780d42cb2dc6dd74c88f7f6c39a7774efc83b79d52abd5d  LibreCAD-Installer-2.2.0.1.exe

Finally, here it is!

It took far too long to present this new stable LibreCAD version.
Already announced several times, new obstacles kept appearing. But the main cause, however, is the loss of manpower in recent years.
We no longer have the resources to maintain a stable and a development branch side by side.
In addition, there were many problems in our parallel project libdxfrw, which we also take care of.
And there are also many invisible tasks to be dealt with, such as moving to a new cloud server, a new homepage, looking for financing our expenses, to name just a few.

About 4800 commits have been made since the last stable version 2.1.3. Too much to go into detail.
So here are a few notable changes in the new version 2.2.0:

• many causes of crashes have been eliminated
• eliminated DWG issues in libdxfrw, which caused several crashes
• the performance of panning and zooming in large files has been significantly improved
• the undo/redo engine has been completely revised due to several problems
• adjustments for new compiler and Qt versions were required
• extension of the command line, multi-line commands, paste and open command files
• improvement of the print preview, with tiled printing and line widths adjustment
• multiple selection and bulk actions in block and layer lists

By expanding our CI, we can now easily provide up-to-date binary packages that allow many users to easily test and bug hunt on Windows, MacOS and Linux.

The new release also has an online manual which is hosted at Read the Docs.

This new stable version 2.2.0 finally replaces the previous stable 2.1.3.

Unfortunately, we have to disappoint people who are hoping for a soon release of LibreCAD 3. It is still a long way from productive use.
Also there are still many contributions available for version 2.2 we wont waste. These can now be integrated into an unstable development branch. That means there will probably be one or two more feature release 2.2.x.
There may be LibreCAD 3 releases in parallel in future, but for the time being, not with the features that LibreCAD 2.2 currently offers.

At last, let me mention, that we recently resumed to accept financial contributions again. These are basically used to pay our expenses for hosting and domain services.
This has become possible through OpenCollective and by GitHub Sponsors.

MD5 sums:

f6c6d3aeb9586c3db16e3af0f60905ce  LibreCAD-2.2.0-x86_64.AppImage
36a5be5acd623a13cdaf7ae8efb4279e  LibreCAD-2.2.0.dmg
3fe516a5f9c4efe4ae4fb186cd008857  LibreCAD-Installer-2.2.0.exe

SHA256 hashes:

5b1cd348fa0ee8c1dc47fe56aef761b980582e58eafc6683207c40aadf30b74b  LibreCAD-2.2.0-x86_64.AppImage
e17d81be0d943f99613d4c12e9a552e3257a41229a99933b7189ea3e896f5011  LibreCAD-2.2.0.dmg
233809d3c7ebf2b9c32601354b29f16f1eb269fe529415828174b3068bce3fa4  LibreCAD-Installer-2.2.0.exe

This pre-release is presumably the last one.
When no issues arise, this will be the new release 2.2.0 soon.

For latest changes see CHANGELOG.md

A build for Apple M1 hardware failed, but you can use the x86 DMG package too, it runs on M1 hardware via Rosetta 2 translation layer.
See #1548

This pre-release is mainly for our Linux users.
It provides our first AppImage for Linux, which will be built now automatically with each push to master.
The latest build for Linux will be available at Continuous Build from now.

There were also some notable improvements from libdxfrw, which should make DWG reading more stable. This is attractive for all user.

macOS users please take care, that there are 2 packages, one for Big Sur and one for older ones.
Probably the Big Sur package runs on Monterey too, if not, please report in the forum or open an issue here.

More than 280 commits since 2.2.0-rc1 and too much delay, but here it is, the next big step to final 2.2.0 release.
We fixed some really serious bugs with DWG reading, what hopefully leads to much less issues and crashes when opening DWG files.
There may be still some issues with DWG we want to address and fix for the final 2.2.0 release.

Please find here the binary packages for Windows and macOS.
And hopefully soon also an AppImage for Linux, any help to achieve this is welcome.

As the work continues, have a look at our SourceForge site too.
There you can find nightly builds for Windows and macOS, which should be tested and may have issues fixed from this release candidate.
For Windows XP: https://sourceforge.net/projects/librecad/files/Windows/NightlyBuilds/master.xp/
For Windows 7-10: https://sourceforge.net/projects/librecad/files/Windows/NightlyBuilds/master/
For macOS: https://sourceforge.net/projects/librecad/files/OSX/2.2/preRelease/

Our online manual at https://librecad.readthedocs.io/ is almost up to date with this release candidate.

new Mac hardware with M1-Chip / macOS Big Sur 11.1

It is reported, that the MacOS package doesn't work on new Mac hardware with M1-Chip and Big Sur 11.1.
If you have one of these, M1-Chip hardware or Big Sur 11.1, you're welcome to test the package and share you're results here:
https://forum.librecad.org/2-2-0-rc2-fails-to-install-on-BigSur-11-1-td5719978.html

We have a new DMG package which was build by a community member on Big Sur, but not on a M1 system. Many thanks!
Please test LibreCAD-2.2.0-rc2-BigSur.dmg and report success or failure to the above forum thread.

Unfold Assets below to find the appropriate file for your OS

There were more than 250 commits since 2.2.0-alpha, thus it was overdue to get rid of the alpha in the tag now.
With some more improvements in the last couple weeks, we switch directly to Release Candidate as the response from community is, that the master branch is stable.
There are only some minor changes in the line before the final 2.2.0 release.