Honestly, TCH, running lazarus as root ?
Honestly. And not just Lazarus, but everything.
I'll make few suggestions but your underlying problem is clear but it sounds like you won't accept that.
Accept what? That you think this happened because i use my systems as root? I accept that you think that. But if this is a dpkg/apt problem, what difference it would have made if i would install the package as
sudo dpkg -i lazarus-project_x.y.z_i386-deb as a normal user instead of
dpkg -i lazarus-project_x.y.z_i386-deb as root, since the former is technically identical to the latter...?
- Because you have a failed install of lazarus-project, (obtained from sourceforge) that should be registered in your apt data base now, so the --reinstall option should (?) work with it. It just needs to configure most likely. But I am not sure. Using "apt-get" instead of apt might be a good idea too, Stretch is pretty old.
Apt cannot reinstall the package, it is not in the repository. I installed all the packages via dpkg. But i tried to reinstall the 2.2.6 via deb package and it did the same as if i would install 3.0.0
- Otherwise, you have little choice other than removing everything that looks or sounds a bit like lazarus and starting again. Definitely all the lazarus config, where ever it is. Make sure dpkg -l does not list anything to do with Lazarus. (leave your fpc install alone.)
I did it. I purged lazarus-project and then did
find / -iname "*lazarus*" and deleted the files. The only result was that
/var/log/dpkg.log now does not says that there is a half-installed 2.2.6; now it says it for 3.0.0 (note: this is a VBox machine and i restored the disk image after each try):
2023-12-31 11:09:17 startup packages purge
2023-12-31 11:09:17 status installed lazarus-project:i386 2.2.6
2023-12-31 11:09:23 remove lazarus-project:i386 2.2.6 <none>
2023-12-31 11:09:23 status half-configured lazarus-project:i386 2.2.6
2023-12-31 11:09:23 status half-installed lazarus-project:i386 2.2.6
2023-12-31 11:09:24 status triggers-pending mime-support:all 3.60
2023-12-31 11:09:26 status triggers-pending man-db:i386 2.7.6.1-2
2023-12-31 11:09:27 status triggers-pending shared-mime-info:i386 1.8-1+deb9u1
2023-12-31 11:09:27 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:28 purge lazarus-project:i386 2.2.6 <none>
2023-12-31 11:09:28 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:28 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:28 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:28 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:29 status config-files lazarus-project:i386 2.2.6
2023-12-31 11:09:29 status not-installed lazarus-project:i386 <none>
2023-12-31 11:09:29 trigproc mime-support:all 3.60 <none>
2023-12-31 11:09:29 status half-configured mime-support:all 3.60
2023-12-31 11:09:30 status installed mime-support:all 3.60
2023-12-31 11:09:30 trigproc man-db:i386 2.7.6.1-2 <none>
2023-12-31 11:09:30 status half-configured man-db:i386 2.7.6.1-2
2023-12-31 11:09:32 status installed man-db:i386 2.7.6.1-2
2023-12-31 11:09:32 trigproc shared-mime-info:i386 1.8-1+deb9u1 <none>
2023-12-31 11:09:32 status half-configured shared-mime-info:i386 1.8-1+deb9u1
2023-12-31 11:11:07 status installed shared-mime-info:i386 1.8-1+deb9u1
2023-12-31 11:11:08 startup packages configure
2023-12-31 11:17:48 startup archives install
2023-12-31 11:17:54 install lazarus-project:i386 <none> 3.0.0
2023-12-31 11:17:54 status half-installed lazarus-project:i386 3.0.0
2023-12-31 11:17:55 status triggers-pending shared-mime-info:i386 1.8-1+deb9u1
2023-12-31 11:17:55 status triggers-pending man-db:i386 2.7.6.1-2But it hangs at the same pont. So the problem was not 2.2.6 being "half-installed".
- Given what you said earlier, and the fact that Stretch is no longer supported, maybe its time for a clean install from scratch ? Bookwork worm has fpc322 in its repo, and a not too distant Lazarus (but a source build of 3.0 would be better).
You might be right about it, but this will be the last resort.
Finally, please do a bit of reading about the underlying principles of Unix, make a user account and use it for everything except the few operations that really need root. Its a tried and tested model and it works.
What makes you think i did not read anything? I know what i am doing when i go as root. I always used my unix(-like) systems as root since i first tried Linux two decades ago and never got hacked, never lost any data with them. The only problems were programs which tried to prevent me using them as root,
but i got around that too.
This problem has nothing to do with the root account at all. This is either a package problem and it does not make any difference if you do package handling via
sudo, rather than simply do it as root, or something is not enough, or something is missing.
Update: I left dpkg where it hanged when i started to write this post and when i was done and looked back, the installation was complete. Apparently there was no problem at all, it was just this slow... So yeah, something was not enough: the CPU. O_O
I do not recall installing 2.2.6 would be this slow.