Broken Installation lazarus / 1-Linux ---------------------------------------------------------------------- the.weavster · 2014-02-06 07:04 Hi, I installed FPC and Lazarus on Ubuntu Studio using the deb files. At first the install went well and everything was working fine but then I tried to add lazreports and rebuild the IDE, The IDE vanished half way through the rebuild and I can't get it to launch again, I get the splash screen and then it just vanishes. I have tried uninstalling and reinstalling (including the FPC) using the deb files but the problem persists. I tried 'complete removal' from Synaptic and installing the version from Ubuntu's repositories but even then the problem persists. Please help, I'm stuck. Thanks. ---------------------------------------------------------------------- Rails · 2014-02-06 11:40 You probably have a bit of an old or improper installation corrupting things.  Try finding and removing every trace of Lazarus manually with something like "locate lazarus", then reinstall.  Run updatedb first to make sure locate is working with the most recent file data. If you want to be really thorough, do the same thing with FPC as well. Edit: You didn't mention error messages, but I am adding this just in case that is what it was. Rebuilding Lazarus normally requires root privileges in Linux. Rebuilding as a regular user usually produces an error message at some point and a failed rebuild. This wiki entry covers the problem. http://wiki.lazarus.freepascal.org/Lazarus_directory_permissions_on_Li nux_and_Unix Personally, I just assign ownership of the lazarus directory under /usr (somewhere, its exact location isn't consistent) to my regular user, which takes care of the problem. As I am the only user, it's Linux, and the machine is behind multiple firewalls and NATs, I don't consider this particularly risky. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 16:31 Quote from: Rails on February 06, 2014, 12:40:33 pmRebuilding Lazarus normally requires root privileges in Linux. Rebuilding as a regular user usually produces an error message at some point and a failed rebuild. This wiki entry covers the problem. http://wiki.lazarus.freepascal.org/Lazarus_directory_permissions_on_Li nux_and_Unix This should not be needed. There is "startlazarus" to solve this problem. It runs Lazarus from the original installation first. While Lazarus is rebuilt the new binary goes to ~/.lazarus directory. Next time you run startlazarus it is clever enough to start the new binary. Is this system not known by Linux users? The "Lazarus_directory_permissions..." page (written by Arny and Jwdietrich) should be fixed to explain the proper way. There is a page documenting startlazarus but another page for this specific issue is good (once it has the facts right).   http://wiki.lazarus.freepascal.org/startlazarus#Searching_the_right_ executable Or, is there a bug that prevents using startlazarus? If yes, it should be reported at once. Such a serious bug can even delay 1.2 release if needed. ---------------------------------------------------------------------- Rails · 2014-02-06 16:46 Rebuilding Lazarus requires root privileges on a standard Linux installation. That is the problem.  Startlazarus does not solve that one. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 16:59 Quote from: Rails on February 06, 2014, 05:46:35 pmRebuilding Lazarus requires root privileges on a standard Linux installation. That is the problem.  Startlazarus does not solve that one. Startlazarus is made to solve EXACTLY that problem. If it does not work, then there is a bug. ---------------------------------------------------------------------- zeljko · 2014-02-06 17:14 Quote from: Rails on February 06, 2014, 05:46:35 pmRebuilding Lazarus requires root privileges on a standard Linux installation. That is the problem.  Startlazarus does not solve that one. That should not be the case. When you rebuild lazarus it should rebuild itself into $HOME/.lazarus and it works so. Just tried to install 1.0.16 on Fedora 19 in virtual machine and it works as expected - I can rebuild lazarus but it does not change anything in /usr/lib/lazarus, but it saves lazarus binary in my $HOME/.lazarus Maybe you want to change something in lcl, in that case you do not have permission to do it (except if you're root). My advice in that case would be: http://wiki.lazarus.freepascal.org/Lazarus_directory_permissions_on_Li nux_and_Unix ---------------------------------------------------------------------- Rails · 2014-02-06 17:28 Installing under the user's home directory is but one of the options mentioned in the link. There are others. I don't install from svn, so don't know where it installs in that case. Installing from the rpm packages via alien puts it under /usr/libsomething/lazarus on my systems, per the Debian policy manual. For me, there is no problem now that I know how to deal with it. Edit: As far as I can tell (I'm far from an expert on the deb packaging system), the Laz packages from the Debian repository and the Laz debs on sourceforge (built with Ubuntu, AFAIK) both default to installing under /usr. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 18:55 Quote from: Rails on February 06, 2014, 06:28:42 pmInstalling under the user's home directory is but one of the options mentioned in the link. There are others. There was no mention that Lazarus' standard installation rebuilds itself there automatically and startlazarus starts the right executable for you. I added a note on the top of the page. Somebody (the authors maybe) should fix it properly. The information is very misleading. QuoteI don't install from svn, so don't know where it installs in that case. Then you don't need to actually install, but the sources go to wherever you want. The path is given as a parameter for "svn co" command. QuoteInstalling from the rpm packages via alien puts it under /usr/libsomething/lazarus on my systems, per the Debian policy manual. For me, there is no problem now that I know how to deal with it. I remember you wrote already some time ago that installation from Debian package does not work for you and you must use Alien. Do you still have the problem? Now before 1.2 would be a good time to dig out all installation problems. However, the Debian packages work well for many people. ---------------------------------------------------------------------- Rails · 2014-02-06 19:04 Quote from: zeljko on February 06, 2014, 06:14:20 pm That should not be the case. When you rebuild lazarus it should rebuild itself into $HOME/.lazarus and it works so. Just tried to install 1.0.16 on Fedora 19 in virtual machine and it works as expected - I can rebuild lazarus but it does not change anything in /usr/lib/lazarus, but it saves lazarus binary in my $HOME/.lazarus So, you are saying that Lazarus lives in /usr/lib/lazarus but gets rebuilt as a different executable under the user's home directory? What then, move it manually to /usr/lib/lazarus, which requires root permission? Or just use the version under the user's home directory from now on? That would leave two versions on the machine, would it not? ---------------------------------------------------------------------- Rails · 2014-02-06 19:14 Quote from: JuhaManninen on February 06, 2014, 07:55:11 pm I remember you wrote already some time ago that installation from Debian package does not work for you and you must use Alien. Do you still have the problem? Now before 1.2 would be a good time to dig out all installation problems. However, the Debian packages work well for many people. The debian built packages tend to be out of date for my puposes. I don't remember if I had any other specific problems with them. It is possible, but mainly I want something more up to date, but not from svn. The ubuntu built debs on sourceforge gave me problems, but that is not surprising. Canonical has been dragging ubuntu as far away from debian as they can. It used to be not a problem to install debian packages on ubuntu and vice versa. These days, quite often it doesn't work.  I have given up trying. When I want to install something that isn't in the debian repositories, I can almost always install it from an RPM without any issues. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 19:32 Quote from: Rails on February 06, 2014, 08:04:30 pmThat would leave two versions on the machine, would it not? Yes, you got it! I improved the explanation in   http://wiki.lazarus.freepascal.org/startlazarus#Searching_the_right_ executable Please check if it is better now. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 19:41 Quote from: Rails on February 06, 2014, 08:14:45 pmThe debian built packages tend to be out of date for my puposes. I don't remember if I had any other specific problems with them. It is possible, but mainly I want something more up to date, but not from svn. Yes, the packages from Ubuntu repo are old. Lazarus project provides new ones. Why not from SVN? I think the fixes branch would be a good match for you. Trunk maybe not. QuoteThe ubuntu built debs on sourceforge gave me problems, but that is not surprising. Canonical has been dragging ubuntu as far away from debian as they can. It used to be not a problem to install debian packages on ubuntu and vice versa. These days, quite often it doesn't work.  I have given up trying. When I want to install something that isn't in the debian repositories, I can almost always install it from an RPM without any issues. Our deb packages work for everybody else, including myself. Ubuntu + Unity created GUI related problems but installation should be OK. I honestly wonder how only you have the same problem for many years already. ---------------------------------------------------------------------- Rails · 2014-02-06 19:46 Yes, the explanation is much, much better thank you  , but we are still back to the original problem.  When Laz is installed from the debs, or the rpm via alien, it will be under /usr, and we are still dealing with an IDE that can't be rebuilt because of permission issues, at least for the first rebuild.   At least that was still the case for me when I moved to 1.2RC2 recently. ---------------------------------------------------------------------- Rails · 2014-02-06 19:53 Quote from: JuhaManninen on February 06, 2014, 08:41:02 pm Our deb packages work for everybody else, including myself. Ubuntu + Unity created GUI related problems but installation should be OK. I honestly wonder how only you have the same problem for many years already. But I'm not the only one. At least one other person, maybe more, added that he had problems with those debs. Is the "everybody else" you are referring to installing on debian, ubuntu, or something else that nominally uses the .deb packages? As to the many years, I haven't tried the sourceforge debs for a a long time. No point in it, as the rpms work well. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 20:11 Quote from: Rails on February 06, 2014, 08:46:42 pmWhen Laz is installed from the debs, or the rpm via alien, it will be under /usr, and we are still dealing with an IDE that can't be rebuilt because of permission issues, at least for the first rebuild. No. As the wiki for startlazarus says:   "the IDE builds its new executable into a sub folder of the primary config path, for example ~/.lazarus/bin/". See, the primary config path is ALWAYS a directory where you have write access. It is under your home dir. This system works because 2 programs, Lazarus and StartLazarus, both support it. Lazarus builds itself into the user's home dir. StartLazarus finds the new executable from there. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 20:18 Quote from: Rails on February 06, 2014, 08:53:41 pmBut I'm not the only one. At least one other person, maybe more, added that he had problems with those debs. Is the "everybody else" you are referring to installing on debian, ubuntu, or something else that nominally uses the .deb packages? As to the many years, I haven't tried the sourceforge debs for a a long time. No point in it, as the rpms work well. Ok, fair enough. I have not done any deep research of possible problems. I have tested with Mint Linux which is based on Ubuntu. FPC and Lazarus packages don't have many lib dependencies so they should be easier than average to install. ---------------------------------------------------------------------- Rails · 2014-02-06 20:28 Quote from: JuhaManninen on February 06, 2014, 09:11:13 pmQuote from: Rails on February 06, 2014, 08:46:42 pmWhen Laz is installed from the debs, or the rpm via alien, it will be under /usr, and we are still dealing with an IDE that can't be rebuilt because of permission issues, at least for the first rebuild. No. As the wiki for startlazarus says:   "the IDE builds its new executable into a sub folder of the primary config path, for example ~/.lazarus/bin/". See, the primary config path is ALWAYS a directory where you have write access. It is under your home dir. This system works because 2 programs, Lazarus and StartLazarus, both support it. Lazarus builds itself into the user's home dir. StartLazarus finds the new executable from there. You probably didn't see this. I added this not too long ago. " At least that was still the case for me when I moved to 1.2RC2 recently." As I recall, the rebuild IDE process chokes when it tries to delete one or more existing files under /usr. I guess when the 1.2 final comes out or the next RC, whichever is first, I will go through the process again and make note of what happens. If there are issues,  I will post them. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 21:06 Quote from: Rails on February 06, 2014, 09:28:29 pmAs I recall, the rebuild IDE process chokes when it tries to delete one or more existing files under /usr. It proves you have something wrong with your Lazarus configuration. Maybe it is related to your installation problems. It would be nice to find the fundamental reason and exact steps to reproduce it. QuoteI guess when the 1.2 final comes out or the next RC, whichever is first, I will go through the process again and make note of what happens. If there are issues,  I will post them. There are no open issues about installation targeted for 1.2. The release will not change anything for you. ---------------------------------------------------------------------- Rails · 2014-02-06 22:11 Quote from: JuhaManninen on February 06, 2014, 10:06:48 pm It proves you have something wrong with your Lazarus configuration. Maybe it is related to your installation problems. It would be nice to find the fundamental reason and exact steps to reproduce it. There are no open issues about installation targeted for 1.2. The release will not change anything for you. It may not, but I can at least provide more exact detail as to what is going on. Prior to your changing the wiki, I saw nothing about the need to change permissions as being abnormal. What I was experiencing exactly matched the write up in the wiki. Several installations ago, I did as I advised the OP and wiped everything Laz and FPC related off of my systems and reinstalled, which resulted in working systems (after I changed the permissions (ownership really) in /usr/libwhatever/lazarus . I have been running the default installation ever since. This particular machine was brand new a couple of months ago. It has only had the two 1.2 release candidates on it. Again, they were the default installations which required only the ownership/permissions change in order to rebuild the IDE. If my configuration really is bad, it wan't from anything I changed. As to installing rpms via alien, I checked both the debian repository and sourceforge debs. I'm not a deb package expert by any means, but both appeared to be designed to be installed under /usr.  I should add that I really don't see my situation as being a hindrance.  A simple chown command to chance ownership of the Lazarus directory isn't a big deal, but having a second nearly complete installation on the same machine just to get around the permissions issue is something that seems somehow strange. ---------------------------------------------------------------------- JuhaManninen · 2014-02-06 22:41 Quote from: Rails on February 06, 2014, 11:11:35 pm... but both appeared to be designed to be installed under /usr. Correct. That is the standard place for any program installation in most Linux systems. Quote... but having a second nearly complete installation on the same machine just to get around the permissions issue is something that seems somehow strange. Which second installation you mean? Lazarus rebuilds itself into your home dir but that is not a "nearly complete installation". It is one executable only. I have a feeling you still did not understand the idea behind startlazarus. From what I know the only difference in your installation is Alien (RPM -> DEB converter). You could also try the latest .deb packages on a clean system. If they don't work any better, I will be buzzled. One more thing: are you sure you always run "startlazarus" instead of "lazarus" directly? ---------------------------------------------------------------------- Rails · 2014-02-06 23:10 Yes, I use startlazarus, not lazarus directly. Not sure what is supposed to be normal, but my my file manager reports .lazarus as 1730 items, totalling 131.2 MB. Under .lazarus, bin contains only link.res at 90.3 kB, and lib contains 1507 items in 25 folders, totalling 128.3 MB. There is other stuff in .lazarus, but that is by far the majority of it. In /usr/lib64/lazarus, I have amongst other things, lazarus and lazarus.old, both at 99 MB and dating from the last time I rebuilt the IDE a few hours ago. Also in /usr/lib64/lazarus, I have lazbuild and startlazarus, both from Jan 10 of this year, which is about when I migrated from RC1 to RC2. I assumed from the discussion and zeljko's post "When you rebuild lazarus it should rebuild itself into $HOME/.lazarus" that .lazarus was supposed to contain nearly everything. I'm happy to learn that isn't the case. ---------------------------------------------------------------------- JuhaManninen · 2014-02-07 08:30 Ok, right, the generated .ppu and .o files must obviously go to a writable dir, too. However now your Lazarus seems to build itself under /usr/... because it is writable. It builds itself into the config dir only if the install dir is write-protected. Could you please try it in a clean system, maybe a virtual machine. Standard installation from .deb packages, no "chmod" or "chown". Does it work? ---------------------------------------------------------------------- the.weavster · 2014-02-07 08:43 Quote from: JuhaManninen on February 06, 2014, 05:31:48 pmThis should not be needed. There is "startlazarus" to solve this problem. It runs Lazarus from the original installation first. While Lazarus is rebuilt the new binary goes to ~/.lazarus directory. Next time you run startlazarus it is clever enough to start the new binary.... And I think this is why uninstalling and reinstalling didn't fix my broken installation. Having deleted ~/.lazarus I have now been able to reinstall (from the deb on Ubuntu Studio) and I'm back up and running. Quote from: Rails on February 06, 2014, 09:28:29 pmAs I recall, the rebuild IDE process chokes when it tries to delete one or more existing files under /usr.Ah, that might be why my rebuild failed. Being a twit it didn't occur to me I needed to do the rebuild as root. Doh. I'll have a go at installing lazreports and rebuilding as root and see how it goes. Thanks for your help guys ---------------------------------------------------------------------- JuhaManninen · 2014-02-07 11:44 Quote from: the.weavster on February 07, 2014, 09:43:53 amAh, that might be why my rebuild failed. Being a twit it didn't occur to me I needed to do the rebuild as root. Doh. I'll have a go at installing lazreports and rebuilding as root and see how it goes. No, please don't do that! Read carefully what was written about "startlazarus" program and act accordingly. Rail's configuration is screwed somehow, hence his advice is not valid now. ---------------------------------------------------------------------- Rails · 2014-02-07 11:56 Quote from: JuhaManninen on February 07, 2014, 09:30:45 amOk, right, the generated .ppu and .o files must obviously go to a writable dir, too. However now your Lazarus seems to build itself under /usr/... because it is writable. It builds itself into the config dir only if the install dir is write-protected. Could you please try it in a clean system, maybe a virtual machine. Standard installation from .deb packages, no "chmod" or "chown". Does it work? I'll see what I can do, Juha. It make take a few days before I can set something up. I will report back when I have it. I will install Laz from the sourceforge deb. I will install FPC from the debian repository. ---------------------------------------------------------------------- Rails · 2014-02-07 14:30 Quote from: Rails on February 07, 2014, 12:56:53 pm[ I'll see what I can do, Juha. It make take a few days before I can set something up. I will report back when I have it. I will install Laz from the sourceforge deb. I will install FPC from the debian repository. OK, I installed the 64 bit laz 1.2rc2 deb from sourceforge. It installed OK, but it wants to be able to write to /usr/share/lazarus/1.2rc/*/* which is owned by root on debian, as recommended per the Filesystem Hierarchy Standard. I was able to "rebuild' the IDE, but only immediately after a clean install. Once I changed the build settings, it choked on the clean all setting. The error message complained that /usr/share/lazarus/1.2rc wasn't writable. Then it suggested I consult the web site for other options on how to install Lazarus.  I also tried compiling some example projects directly after the install. Laz immediately tried to back them up to /usr/share/lazarus/1.2rc/examples/backup which failed, of course. On the other hand, the good new is the laz executable and its backup did appear in ./lazarus/bin. The bad news is the system is unusable as installed. ---------------------------------------------------------------------- the.weavster · 2014-02-07 16:13 Quote from: JuhaManninen on February 07, 2014, 12:44:23 pmNo, please don't do that! Read carefully what was written about "startlazarus" program and act accordingly. Rail's configuration is screwed somehow, hence his advice is not valid now. I was only going to sudo to rebuild the IDE, I was not going to change the permissions of the installation folders or run Lazarus as root whilst developing. I don't think the ~/.lazarus option is working right now and I really want lazreports and weblaz. ---------------------------------------------------------------------- Rails · 2014-02-07 16:57 Quote from: the.weavster on February 07, 2014, 05:13:00 pmQuote from: JuhaManninen on February 07, 2014, 12:44:23 pmNo, please don't do that! Read carefully what was written about "startlazarus" program and act accordingly. Rail's configuration is screwed somehow, hence his advice is not valid now. I was only going to sudo to rebuild the IDE, I was not going to change the permissions of the installation folders or run Lazarus as root whilst developing. I don't think the ~/.lazarus option is working right now and I really want lazreports and weblaz. I assume you read all the stuff I wrote earlier in response to Juha's concerns. FYI, I do not agree with his assertion that I have a "screwed" configuration. I think that the tests I have done prove that. My installation works fine. It just requires dealing with the write permissions issue for the lazarus folder that gets installed under /usr/. My choice was to change it and its contents ownership to my user account.  That way I don't have to worry about switching to root just to rebuild the IDE, which can happen frequently if you are loading external packages. It lets me install updates in the least painful manner. It simply is a matter of letting the package manager install the new package, then doing a chown on the lazarus directory to take care of the ownership changes that are imposed by the installation package. I have no problems with this process. ---------------------------------------------------------------------- JuhaManninen · 2014-02-08 10:52 Quote from: Rails on February 07, 2014, 03:30:46 pm... it choked on the clean all setting. Ok, finally I was able to reproduce the problem. It happens only with "Clean all" checked. Without "Clean all" the rebuilding of Lazarus always works like train's toilet (*). I tested with a clean Mint Linux 15 KDE edition under VirtualBox and tried many ways of installing packages and rebuilding Lazarus. Rails and the.weavster, does this mean that you never tried building Lazarus WITHOUT the "Clean all"? How is that even possible? When you install packages, there is no selection for "Clean all". It is available only in the Configure Build Lazarus dialog. The whole setting is a hack made by Mattias some years ago. It is needed only when developing Lazarus and its packages, and even then only after moving files or directories to a new place. It is not needed when using a released version of Lazarus installed in a standard write-protected location. Sure it is a bug and must be fixed. It is a good example that nothing should be assumed when designing a GUI. [Edit] Reported : http://bugs.freepascal.org/view.php?id=25695 Another known issue are the example projects. They cannot be compiled in-place in a write-protected directory. It must be solved somehow later, but it is not a show-stopper issue. It does not affect rebuilding Lazarus itself, and an example project can always be copied elsewhere if you want to run it. However, failing to install packages in a standard installation of Lazarus without sudo rights would be a show-stopper issue. Can you please confirm that the problem was ONLY about "Clean all". Juha (*) "works like train's toilet" is used at least here as a metaphor for reliable technology. It comes from time when toilets in trains had only a hole under the seat and you could see the ground running by. ---------------------------------------------------------------------- Rails · 2014-02-08 13:54 Quote from: JuhaManninen on February 08, 2014, 11:52:01 amQuote from: Rails on February 07, 2014, 03:30:46 pm... it choked on the clean all setting. Ok, finally I was able to reproduce the problem. It happens only with "Clean all" checked. Without "Clean all" the rebuilding of Lazarus always works like train's toilet (*). I tested with a clean Mint Linux 15 KDE edition under VirtualBox and tried many ways of installing packages and rebuilding Lazarus. Rails and the.weavster, does this mean that you never tried building Lazarus WITHOUT the "Clean all"? How is that even possible? When you install packages, there is no selection for "Clean all". It is available only in the Configure Build Lazarus dialog. The whole setting is a hack made by Mattias some years ago. Another known issue are the example projects. They cannot be compiled in-place in a write-protected directory. It must be solved somehow later, but it is not a show-stopper issue. It does not affect rebuilding Lazarus itself, and an example project can always be copied elsewhere if you want to run it. However, failing to install packages in a standard installation of Lazarus without sudo rights would be a show-stopper issue. Can you please confirm that the problem was ONLY about "Clean all". I'm responding in the order above. No, it doesn't mean that at all. I first ran into this stuff a long time ago when I installed the luicairo package. Before that, I had never tried rebuilding the IDE. The package installation process told me the IDE needed to be rebuilt and the dialog asked me if I wanted to do that. I clicked on Rebuild Now (or equivalent term) and that is when the problem came up. I did not change any of the rebuild settings until later. I did not even know what they were at that time. I started digging through the wiki and may have even posted here about it, but don't remember. When I found the wiki entry that I linked earlier regarding Linux permissions, I simply dealt with it that way. I have been doing so ever since. Unfortunately, I don't remember what version I was using at that time, other than it was 0.9 something and came from the Debian repository. From then on, I automatically changed the lazarus directory's owner to my local user every time I installed a newer version of Laz and never had a problem. I have never tried any of the example projects before doing the clean install test for you yesterday. I simply tried to build one to see if the installation worked. I understood why they won't work, but have no doubt that new users are going to run into problems, since there are no instructions anywhere saying they need to me moved to be used. Today I changed the lazarus directory's ownership back to root on my current installation and can confirm that the IDE can be rebuilt if Clean All is not selected. ---------------------------------------------------------------------- JuhaManninen · 2014-02-08 14:29 Quote from: Rails on February 08, 2014, 02:54:56 pmToday I changed the lazarus directory's ownership back to root on my current installation and can confirm that the IDE can be rebuilt if Clean All is not selected. Cool! Thanks for the info. Maybe there were more problems in older versions, I don't know. I will try to hide the " Clean all" option and get it into 1.2. Then it would have one trap less for new users, and the Configure Build Lazarus dialog would be less intimidating. The Example Project Manager (Tools -> Example Projects ...) could maybe help with compiling examples. It would offer to copy a project to a better place when a user wants to open it. ---------------------------------------------------------------------- Rails · 2014-02-08 14:44 Quote from: JuhaManninen on February 08, 2014, 03:29:50 pm Cool! Thanks for the info. Maybe there were more problems in older versions, I don't know. I will try to hide the " Clean all" option and get it into 1.2. Then it would have one trap less for new users, and the Configure Build Lazarus dialog would be less intimidating. The Example Project Manager (Tools -> Example Projects ...) could maybe help with compiling examples. It would offer to copy a project to a better place when a user wants to open it. Sounds good to me. ---------------------------------------------------------------------- Rails · 2014-02-08 16:23 Juha, I just found another problem with the lazarus directory being owned by root. Run/Clean up Build Files now produces a string of errors starting with Unable to delete file "/usr/lib64/lazarus/compone nts/lazutils/lib/x86_64-linux/LazUtils.compiled". While selecting Skip errors bypasses the errors, I assume this stuff needs a fix too. Edit: Just to be clear, the project I am working on has its own directory owned by the user. ---------------------------------------------------------------------- the.weavster · 2014-02-09 07:39 Quote from: JuhaManninen on February 08, 2014, 11:52:01 amRails and the.weavster, does this mean that you never tried building Lazarus WITHOUT the "Clean all"? How is that even possible? When you install packages, there is no selection for "Clean all". It is available only in the Configure Build Lazarus dialog. The whole setting is a hack made by Mattias some years ago.It was the very first thing I did with a completely virgin install. If the problem is to do with a 'clean all' setting then it is set by default because I didn't even know it existed. ---------------------------------------------------------------------- JuhaManninen · 2014-02-09 09:57 Quote from: the.weavster on February 09, 2014, 08:39:37 amIt was the very first thing I did with a completely virgin install. If the problem is to do with a 'clean all' setting then it is set by default because I didn't even know it existed. Very strange. Does it work for you now? The build is done with some big functions with lots of parameters. I must refactor them into a class before trying to fix problems. It means this will not go to 1.2 release. Building system is partly black magic anyway, this is risky and must be tested well. I will look at the "Run/Clean up Build Files" issue later. ---------------------------------------------------------------------- the.weavster · 2014-02-09 20:05 Quote from: JuhaManninen on February 09, 2014, 10:57:59 amVery strange. Does it work for you now?I opened a terminal and typed: $ sudo lazarus-ide I added lazreports and weblaz and then did the rebuild, now everything's working. AFAIC it's no big deal, in fact it's sensible that if I installed it with sudo I should have to rebuild it with sudo. I think a simple reminder note on the rebuild screen should suffice, just to stop melons like me tripping themselves up. Perhaps the examples should be installed somewhere under ~/ Thanks again both of you for your help. ---------------------------------------------------------------------- JuhaManninen · 2014-02-09 22:51 Quote from: the.weavster on February 09, 2014, 09:05:31 pmopened a terminal and typed: $ sudo lazarus-ide I added lazreports and weblaz and then did the rebuild, now everything's working. The idea was to do it without sudo. Can you please try again as a normal user. Just don't touch "Clean All". Maybe delete ~/.lazarus again before testing. It seems only you still have this problem. Rails confirmed that only "Clean All" causes problems for him. Maybe some old versions had more problems, I don't know, but now we test 1.2RC2. QuoteAFAIC it's no big deal, in fact it's sensible that if I installed it with sudo I should have to rebuild it with sudo. I think a simple reminder note on the rebuild screen should suffice, just to stop melons like me tripping themselves up. No, it is important that you can install packages without sudo rights. Lazarus does not support dynamic packages now, but installing static packages is almost as easy from Package -> Install/Uninstall packages ... You don't need to think of it, you just install by clicking a button. Things would be much worse if you had to quit Lazarus, run it as sudo, install a package, quit it again and then start it again as normal user.