Lazarus Release Candidate 3 of 4.0

[dbannon]

As spotted by Robert in https://forum.lazarus.freepascal.org/index.php/topic,70833.msg553538.html#msg553538

The current Lazarus 4.0RC3 debian packages, when installed, do not seem to allow the Lazarus IDE  "cleanup and rebuild" command to run. It fails when deleting the existing *.o and *.ppu files.  If its attempted after a fresh install, all the relevant files are still only in read only space so, obviously they cannot be deleted. But even after lazarus rebuilds itself, only the gtk2 widget set files seem to appear in ~/.lazarus under units/x86_64-linux/gtk2. And, of course, the new lazarus binary.

Similarly, with Lazarus 2.2.0 packaged with Ubuntu 2.2.0 and Lazarus 3.0 packaged in Ubuntu 24.04 (which, incidentally, also does not rebuild itself, instead crashes).

I have posted, separately, a suggested (but quite radical) solution https://forum.lazarus.freepascal.org/index.php/topic,71009.msg553637.html

Davo

Edit : the b*..y files are in read only space Davo, not user. Pay attention!

[n7800]

when switching from some application (looks like from any application) back to Lazarus RC3 using the mouse, i.e, click back and forth between some app and Lazarus, when clicking on Lazarus a console window flashes very quickly.

From your signature, does this happen on Windows?

Perhaps some package does this. Which ones do you have installed?

The console window appears and disappears too quickly to discern anything it may be displaying or doing.

You can try recording a video of the screen so that when viewing the video frame by frame you can see the console output and the window title.

[440bx]

@n7800,

Yes, it was a package that was causing the problem, not a Lazarus problem.

Thank you for your interest in the problem.

[n7800]

So I guessed right, but it's too late ))

Right now I accidentally saw it on the bug tracker. Next time please add a link to the created issue.

[440bx]

Right now I accidentally saw it on the bug tracker. Next time please add a link to the created issue.

I created the issue several days after I posted the question here because I wasn't sure it should be considered a bug.  I should have edited the post after creating the issue in the bug tracker.  mea culpa.