Lazarus Release Candidate 1 of 3.0

[Tomki]

I did install the Beta over an existing IDE 2.2.6 on MacOS
Now, every time I start the IDE I get a warning as on the attached pic.
Is it recommended to remove the old installation before installing the Beta?

[Martin_fr]

I don't know the Mac specifics, but in General.

If you want more than one IDE installed, then
- install them in different path
- specify --primary-config-path=  or --pcp=

You seem to have replaced the 2.2.6 install with a 3.0

But one caveat. While the installed executable "lazarus.app" is upgraded, there is a shadow executable that is still 2.2.6.

This happens when you add packages, which rebuilds the IDE. But the newly build IDE can (due to user permissions) not be written in the global install location.
So it ends up in your home folder in the config dir (somewhere in it) ~/.lazarus/


You probably use "StartLazarus" and that finds this old 2.2.6

You can keep the install as it is.

Option 1)
remove that old version, from the config path => then 3.0 should start (you need to rebuild it, to get your packages)

Option 2)
Just rebuild your IDE

The Warning is, because the new and the old ide have that file in a different location....
You can ignore the warning, it will resolve itself with the above steps

[alank]

I managed to catche an issue in anchordocking. At the first glance possible a double free.

https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/40373

If that does not crash in lcl code, and runs the gtk2 freeing of components a 2nd time, then it could probably give the trace you had earlier.

Looks like the fix has been merged into the fixes branch for 3.0, so I'll give it a try once we get RC2.

Thanks very much!

[alank]

Another issue I noticed today:

1. Go to Tools -> Desktops
2. Uncheck "Auto save active desktop"
3. Click on the "Close" button
4. Exit Lazarus
5. Restart Lazarus and go to Tools -> Desktops. Note that "Auto save active desktop" is checked again.

Linux / Qt5 build of 3.0RC1

Alan

[JuhaManninen]

1. Go to Tools -> Desktops
2. Uncheck "Auto save active desktop"
3. Click on the "Close" button
4. Exit Lazarus
5. Restart Lazarus and go to Tools -> Desktops. Note that "Auto save active desktop" is checked again.

Is this a regression? How did it behave earlier?

[TRon]

1. Go to Tools -> Desktops
2. Uncheck "Auto save active desktop"
3. Click on the "Close" button
4. Exit Lazarus
5. Restart Lazarus and go to Tools -> Desktops. Note that "Auto save active desktop" is checked again.

Is this a regression? How did it behave earlier?

I am able to confirm. Linux x86/64 gtk2

When performed the same sequence in 2.2.6 the checkbox is unchecked after the restart so that would unfortunately indicate a regression

[JuhaManninen]

When performed the same sequence in 2.2.6 the checkbox is unchecked after the restart so that would unfortunately indicate a regression

Yes, there was a big refactoring, splitting EnvironmentOptions into pieces.
AutoSaveActiveDesktop value was not loaded or saved any more. I fixed it in ed7945efe2. Will be merged to fixes_3_0.

[Tomki]

I don't know the Mac specifics, but in General.

If you want more than one IDE installed, then
- install them in different path
- specify --primary-config-path=  or --pcp=

You seem to have replaced the 2.2.6 install with a 3.0

But one caveat. While the installed executable "lazarus.app" is upgraded, there is a shadow executable that is still 2.2.6.

This happens when you add packages, which rebuilds the IDE. But the newly build IDE can (due to user permissions) not be written in the global install location.
So it ends up in your home folder in the config dir (somewhere in it) ~/.lazarus/


You probably use "StartLazarus" and that finds this old 2.2.6

You can keep the install as it is.

Option 1)
remove that old version, from the config path => then 3.0 should start (you need to rebuild it, to get your packages)

Option 2)
Just rebuild your IDE

The Warning is, because the new and the old ide have that file in a different location....
You can ignore the warning, it will resolve itself with the above steps

Hi Martin
I tried this and I didn't succeed. It's probably because my leck of experience. So I deleted then old install and installed everything from scratch.
This worked (as anticipated) as far as the IDE itself is concerned. Then I tried to install the ZEOS package. This package installed with no errors but then I had to rebuild the IDE. This ended up with some errors (see attached).  The online package manager it shows the ZEOS components installed but in the palette the components don't show up (probably due to the missing recompile of the IDE)
What can I do now? I need ZEOS! And the DateTimePicker belongs to some other palette which obviously worked at first install from scratch.
Sorry, but I'm not the expert in this ...
 

[JuhaManninen]

This worked (as anticipated) as far as the IDE itself is concerned. Then I tried to install the ZEOS package. This package installed with no errors but then I had to rebuild the IDE.

No, it didn't install yet. Lazarus only supports static packages and a successful recompilation is needed.

This ended up with some errors (see attached).  The online package manager it shows the ZEOS components installed but in the palette the components don't show up (probably due to the missing recompile of the IDE)

It is a bug in online package manager if it shows ZEOS installed while it is not.

"Warning: Recompiling DateTimePicker, checksum changed for ... /lclintf.ppu."
means you have old .ppu files left somewhere after all. Do a clean build of Lazarus first.

[Tomki]

OK - any hint how I can cleanup the previous install?
The installation of Beta 3 worked fine after I deleted everything I could find from the previous installation. So I don't know why a recompile of the IDE doesn't find the files.
I searched the file manually and found it on "/Users/thomas/.lazarus/lib/DateTimeCtrls/lib/x86_64-darwin/cocoa/datetimepicker.ppu". How can I tell Lazarus that it's there?

[JuhaManninen]

OK - any hint how I can cleanup the previous install?
The installation of Beta 3 worked fine after I deleted everything I could find from the previous installation. So I don't know why a recompile of the IDE doesn't find the files.
I searched the file manually and found it on "/Users/thomas/.lazarus/lib/DateTimeCtrls/lib/x86_64-darwin/cocoa/datetimepicker.ppu". How can I tell Lazarus that it's there?

That is from a recompilation because Lazarus was installed into a write protected directory.
You can do a clean build from Tools -> Configure "Build Lazarus" ... and check "Clean all" before building.

If you got the fixes_3_0 branch sources from Gitlab into a writable user directory, you could just "make clean bigide". It builds the release version clean, assuming you have FPC installed. Then just run from its location: "./lazarus &".
No need to worry about write protection.

[Tomki]

OK - any hint how I can cleanup the previous install?
The installation of Beta 3 worked fine after I deleted everything I could find from the previous installation. So I don't know why a recompile of the IDE doesn't find the files.
I searched the file manually and found it on "/Users/thomas/.lazarus/lib/DateTimeCtrls/lib/x86_64-darwin/cocoa/datetimepicker.ppu". How can I tell Lazarus that it's there?

That is from a recompilation because Lazarus was installed into a write protected directory.
You can do a clean build from Tools -> Configure "Build Lazarus" ... and check "Clean all" before building.

If you got the fixes_3_0 branch sources from Gitlab into a writable user directory, you could just "make clean bigide". It builds the release version clean, assuming you have FPC installed. Then just run from its location: "./lazarus &".
No need to worry about write protection.

Tried a "clean install", resulting in more errors...
How can this be? The install from the install package was alright - and it should more or less do the same thing? Or am I totally wrong?!
I'm sorry, but I am only a Lazarus user and I'm not into MacOS too deep  :'(

[allanregistos]

The Lazarus team is glad to announce the first release candidate of Lazarus 3.0.
Yes, it may be that you are the only person with a project, that will not work in the new IDE. So if you do not test, we can not fix it.

Please do not wait for the final release, in order to test. It may be too late. Once the release is out we will have to be more selective about which fixes can be merged for further 3.x releases. So it may be, that we can not merge the fix you require. And then you will miss out on all the new features.

I am on Debian 12 64-bit. A minor UI bug, where the top menu will move erratically when dragging it along the screen. You may see the shared OneDrive link for information. This is happening for both XORG and Wayland.
https://steniel-my.sharepoint.com/:v:/g/personal/allan_registos_steniel_com_ph/EQkGcYgAGjZMgmkYSsXb4nIBGoaG4ztN7oE3uUd-sb4j-g?e=9k80nv

[hukka]

What can I do now? I need ZEOS! And the DateTimePicker belongs to some other palette which obviously worked at first install from scratch.
Sorry, but I'm not the expert in this ...

This doesn't seem ZEOS/Mac specific as I'm having the exact same problem ("Can't find DateTimePicker" etc. as in the screenshot) trying to rebuild the IDE on a fresh install of Debian 12 x64 (FPC/Lazarus installed via the .debs). No earlier version of FPC/Lazarus installed. Was trying to install AnchorDocking. If I remove the DateTimePicker packages it will then fail with a similar "Can't find" error on the AnchorDocking unit.

[Tomki]

I tried a "very clean" install. First deleted everything and then a fresh install. The problem persists. If I install a package from the online package manager and thereafter try to recompile the IDE, the problem with the missing datetimepicker comes up again - although it's there (see previous post) but obviously can't be found.
Also what I would like to suggest: As myself, many Lazarus users are "users only" and no expert in installing / maintaining / developing the IDE (which I admire you guys for), so these users do install a png or dmg file (on Mac) probably over the old installation. A solution would be nice, that makes this happen without drawbacks. I think that's another purpose of trying out the BETA version.
Myself, I have to go back to 2.2.6 because I can't have to installations of Lazarus on my Mac (at least not that I know of) and I need to install additional packages.