unit not found (StdCtrls)

[VisualLab]

Had this problem for a LONG time with Lazarus 2.... and now 3.0 on Linux Mint Cinnamon with Lazarus installed from the Linux Mint software manager.
Eventually took ownership of /usr/lib/lazarus using sudo chown -R username:username /usr/lib/lazarus.
The problem stopped completely.
Will still play with ownership / group settings to see if there is better way to address the access rights

There is nothing better than being a brazen "godless of the Church of Saint Penguin"

And this is done by:

• unlocking the root account in the GUI (only once),
• logging into the GUI as root (all the time).

It works great. No need to do any "crazy sudo-f..g on the keyboard" every 2 minutes

Of course, on a computer intended for experimentation (not on a server, nor a computer at work).

Lazarus served from the official Debian repositories is quite old. It's better to install DEB packages from the Lazarus creators, e.g. from Lazarus Files. I installed them 2 weeks ago in Kubuntu 24.04 (version: Lazarus 4.0 RC1 for AMD64). It works without problems.


P.S. Where have the former times of freedom of action in Linux gone? Back then I was mainly using various Red Hats and derivatives. You could change everything as you wanted (yes, the system was more clumsy on a desktop back then). But no nosy gendarme, oprichnik, hunweibin or other chekist tried to block various things in the system with idiotic scripts, as it is now (especially in Deb(il)ian and derivatives). They accuse MS of imposing various artificial restrictions, and they themselves do it in Linux, hypocrites.

[munair]

I have not run into this issue since I use Lazarus 3.2 on Debian 12.

[JD]

P.S. Where have the former times of freedom of action in Linux gone? Back then I was mainly using various Red Hats and derivatives. You could change everything as you wanted (yes, the system was more clumsy on a desktop back then). But no nosy gendarme, oprichnik, hunweibin or other chekist tried to block various things in the system with idiotic scripts, as it is now (especially in Deb(il)ian and derivatives). They accuse MS of imposing various artificial restrictions, and they themselves do it in Linux, hypocrites.

  I'm curious to know what you think of immutable distros like VanillaOS and others like it.

https://www.ubuntupit.com/immutable-linux-distributions/

[TRon]

Had this problem for a LONG time with Lazarus 2.... and now 3.0 on Linux Mint Cinnamon with Lazarus installed from the Linux Mint software manager.
Eventually took ownership of /usr/lib/lazarus using sudo chown -R username:username /usr/lib/lazarus.
The problem stopped completely.
Will still play with ownership / group settings to see if there is better way to address the access rights

There is nothing better than being a brazen "godless of the Church of Saint Penguin"

And this is done by:

• unlocking the root account in the GUI (only once),
• logging into the GUI as root (all the time).

It works great. No need to do any "crazy sudo-f..g on the keyboard" every 2 minutes

Of course, on a computer intended for experimentation (not on a server, nor a computer at work).

also not on any machine for experiments. Even stronger, especially not on a machine for experiments exactly because ... experimental (meaning more chance to mess up) 

One of the more correct ways of doing it is creating a separate group that allow r/w access to lazarus folder (and yes, taking ownership does the same thing but does not so for all users) and making "developers that are allowed to use lazarus" a member of that group.

Running as root is a no-go, not on any platform that supports using different access rights.

P.S. Where have the former times of freedom of action in Linux gone?

It always was this way if you setup Linux as intended. As comparison the days that you can run windows with admin account in order to circumvent all issues is also long gone (and for the ones that believe it works perfect, please keep on doing so as you are not the target of this remark so, please keep sharing).

There is no good reason whatsoever to advertise the "take all access rights behaviour" because it makes life easier. That is how the world of (not) computing got into all this mess in the first place. On the other hand people don't seem to care at all any more these days, so why bother with linux at all: just install chromeOS and/or android and be gone with any privacy at all (hello and goodbye m$)

But I understand that access rights and how to deal with them properly is not a happy place topic so the other workaround is to install in user-space and not bother at all with any ownership/access rights whatsoever.

2 cents,

PS: the correct solution would ofc be for this issue to be fixed but it seem to be a difficult one to reproduce with a simple and consistent example.

[Thaddy]

PS: the correct solution would ofc be for this issue to be fixed but it seem to be a difficult one to reproduce with a simple and consistent example.

Which in 99% of the cases means the questioner screwed up and possibly in 1% of the cases it is a real issue.
You have to be firm with children. You think the same. Be blunt.
A bodged install caused by a bodged uninstall from a previous version.