Lazarus Release Candidate 1 of 1.4

[mai]

I've installed lazarus_1.4RC1-0_i386.deb then went to recompile

I cannot reproduce this error on x86_64-linux. Recompile works fine here with lazReports pack added

But I had to login as a different user from the user who installed Laz via fpcUP to keep Laz 1.4RC1 (and other .deb installed versions) from not finding those bloody units. I believe, the fcp.cfg settings get mixed up, which might show in the view/IDE internals window for the effective paths asf..

Using a freshly created user account to run  .deb installed Lazarusses can help a lot, especially with those common "source stuff not found" errors 

[Martin_fr]

Code: [Select]

"/usr/share/lazarus/1.4RC1/ide/cmdlinedebugger.pp"

This file is not supposed to exist (not in that path anyway)

But there was a previous report (linux too) about the same issue.

Can you post more of the messages output (copy all shown and hidden)?

The error will probably go away if you "clean all"

[JuhaManninen]

Using a freshly created user account to run  .deb installed Lazarusses can help a lot, especially with those common "source stuff not found" errors 

No need for a new user account. Just remove all .ppu and .o files from your local Lazarus config dir.
It has nothing to do with fcp.cfg.

[goodname]

Going on hints from mai I renamed ~/.lazarus to ~/.lazarusBACKUP and tried to compile again. This time it worked. There is something in the upgrade of .lazarus settings. I will try to reproduce the error.

I'll try removing the .ppu and .o files in the original .lazarus and see if that changes anything.

EDIT: Lines in Message Window when error happens.

Code: [Select]

Build IDE: Exit code 2, Errors: 1, Warnings: 1
Verbose: /usr/bin/make -C ide idepkg
Verbose: make[1]: Entering directory `/usr/share/lazarus/1.4RC1/ide'
Verbose: /usr/bin/make --assume-new=lazarus.pp lazarus OPT=' @/home/goodname/.lazarus/idemake.cfg -vbq -FU/home/goodname/.lazarus/units/i386-linux/gtk2 -FE/home/goodname/.lazarus/bin'
Verbose: make[2]: Entering directory `/usr/share/lazarus/1.4RC1/ide'
Verbose: /usr/bin/fpc -gl -Sci -dlclgtk2 -Fu../designer -Fu../debugger -Fu../debugger/frames -Fu../converter -Fu../packager -Fu../packager/frames -Fu../components/custom -Fuframes -Fu. -Fu/usr/lib/fpc/2.6.5/units/i386-linux/rtl -Fu/usr/lib/fpc/2.6.5/units/i386-linux/paszlib -Fu/usr/lib/fpc/2.6.5/units/i386-linux/fcl-process -Fu/usr/lib/fpc/2.6.5/units/i386-linux/hash -Fu/usr/lib/fpc/2.6.5/units/i386-linux/fpmkunit -Fu/usr/lib/fpc/2.6.5/units/i386-linux/regexpr -Fiinclude -Fiinclude/linux -Fi../images -FE.. -FU../units/i386-linux/gtk2 -Fl/usr/lib/gcc/i486-linux-gnu/4.7 -Flinclude -Fl/etc/ld.so.conf.d/*.conf @/home/goodname/.lazarus/idemake.cfg -vbq -FU/home/goodname/.lazarus/units/i386-linux/gtk2 -FE/home/goodname/.lazarus/bin -di386 lazarus.pp
Verbose: Free Pascal Compiler version 2.6.5 [2015/01/21] for i386
Verbose: Copyright (c) 1993-2012 by Florian Klaempfl and others
Verbose: Target OS: Linux for i386
Verbose: Compiling lazarus.pp
Verbose: Compiling main.pp
Verbose: PPU Loading /home/goodname/.lazarus/units/i386-linux/gtk2/cmdlinedebugger.ppu
Verbose: PPU Source: cmdlinedebugger.pp not found
Warning: Recompiling CmdLineDebugger, checksum changed for FileUtil
cmdlinedebugger.pp(160,31) Fatal: Can't find unit CmdLineDebugger used by LazDebuggerGdbmi
Verbose: Compilation aborted
Verbose: /usr/bin/ppc386 returned an error exitcode (normal if you did not specify a source file to be compiled)
Verbose: make[2]: Leaving directory `/usr/share/lazarus/1.4RC1/ide'
Verbose: make[1]: Leaving directory `/usr/share/lazarus/1.4RC1/ide'
Verbose: [lazarus] Error 1
Verbose: [idepkg] Error 2

Edit1: Deleting *.ppu and *.o files seams to remove the problem.

[mai]

Martin_fr, I reedited http://forum.lazarus.freepascal.org/index.php/topic,27412.msg169662.html#msg169662
hoping the patch can be found to make everyone happy in 1.4RC 2 with XTRA mouse buttons. If need be, I post-factum submit a buggy report. 

[balazsszekely]

http://forum.lazarus.freepascal.org/index.php/topic,27455.msg169683/topicseen.html#new

[Hudsonkem]

awesome job lazarus team, I can feel the new features, very good. if i've had a bug, i will report thx.

[avra]

Some people would like to switch on or off this feature. I would like having it switched on only if pastel background colors were used instead of current colors which are too strong and too much distracting by default settings.

It is all configurable!

Funny how the coolest, most profound improvement of the whole 1.4 release is considered a bad thing by many people.

Maybe those people just do not like such strong distractions? I am in business of PLC/SCADA/HMI design for almost 20 years, and I have learned well how much color affects operator attention. Softening current non-harmonic strong default colors and making them more pastel would help making most of the people happy. Everyone finding default colors too distracting will soften them manually, but can you imagine maintaining colors in several Lazarus incarnations some of us have, multiplied by several computers or virtual machines? I do not find that funny. 

Here is a pastel palette example, and hex color values can be seen on mouse hovering over color:
http://www.colorschemer.com/schemes/viewscheme.php?id=5128

More pastel combinations to choose from:
http://media.mediatemple.netdna-cdn.com/wp-content/uploads/2010/01/tetradic-pastel.jpg
http://katersacres.com/wp-content/uploads/2014/03/Spring-Pastels-Polymer-Clay-Color-Palette.jpg
http://interiordesignable.com/wp-content/uploads/2013/12/house-of-laiqa-light-pastel-color-scheme.jpg
http://www.curioushomes.co.uk/wp-content/uploads/2010/08/shabby-chic-palette.gif

May we have messages window default colors more pastel, pretty please? 

[CM630]

Here is what happened:
I was logged in WinXP (fat 32) and I have run the internet browser as another user. So I downloaded Lazarus and installed it (as secondary installation) from the account of the user running the browser.
Then I started Lazarus from the account of the first user. It run, compiled an app, containing only a messagebox, but upon executing it a sigsegv occured.
Then I run Lazarus as the second user (shift->right click-> run as...) and everything went well.
I do not know if this is a bug or that is how the it should behave.

[JuhaManninen]

May we have messages window default colors more pastel, pretty please? 

Yes, the default colors may not be perfect. If somebody wants to change them with a patch, it will be accepted and merged to 1.4.
This is a typical "geek GUI" phenomenon. The author concentrated on the technical feature (which was challenging in this case), the GUI colors are low priority then.

[Basile B.]

May we have messages window default colors more pastel, pretty please? 

Yes, the default colors may not be perfect. If somebody wants to change them with a patch, it will be accepted and merged to 1.4.
This is a typical "geek GUI" phenomenon. The author concentrated on the technical feature (which was challenging in this case), the GUI colors are low priority then.

I agree, plz, less saturated by default.
And, even more important, if someone makes a patch; please remove the dashed black lines, they're awfull !

Otherwise did someone else notived that when Anchordocking is installed docked pages are now saved.
This was an awaited feaure, for me at least. Thx !

[Eugene Loza]

If it is a bug, fill a report. Otherwise feel free to comment here.

Sorry, could not find lazarus 1.4 RC1 version in bug report system (1.2.7 SVN being the latest)...

BUG:
Category: compiler;
Reproducibility: always;
Platform/system/version: Windows 7 64 bit SP1
Lazarus version: 1.4 RC1 64 bit

Summary:
Project exe file cannot be overwritten.

Description:
When I create a project & compile it, the compiled exe file cannot be overwritten and the second compile fails, requiring me to delete each compiled exe before re-compiling.
When exiting lazarus and loading the project again compilation works normally and exe is overwritten.
Sometimes this bug appears for saved projects with the same result but this is not 'always' reproducible. Seems that reboot after saving the project removes the bug permanently from the given project.
Project1.exe does not appear in taskmanager and may be deleted in a regular way. The next compiled project exe also cannot be overwritten.

Steps to reproduce:
1. Create an empty project (application).
2. Save all to a known place.
3. Compile.
4. Change the project (any change for recompilation, e.g. add an additional variable in var section).
5. Compilation fails.

Hint: (11030) Start of reading config file E:\lazarus\fpc\2.6.4\bin\x86_64-win64\fpc.cfg
Hint: (11031) End of reading config file E:\lazarus\fpc\2.6.4\bin\x86_64-win64\fpc.cfg
Free Pascal Compiler version 2.6.4 [2015/02/14] for x86_64
Copyright (c) 1993-2014 by Florian Klaempfl and others
(1002) Target OS: Win64 for x64
(3104) Compiling project1.lpr
(9022) Compiling resource V:\Temp\2\lib\x86_64-win64\project1.obj
(9015) Linking project1.exe
V:\Temp\2\project1.lpr(20,1) Error: (9003) Can't create object file: project1.exe
V:\Temp\2\project1.lpr(20,1) Fatal: Can't create executable project1.exe
Fatal: (1018) Compilation aborted
Error: E:\lazarus\fpc\2.6.4\bin\x86_64-win64\ppcx64.exe returned an error exitcode (normal if you did not specify a source file to be compiled)

[Syndrome]

I agree with Eugene Loza. This is the most annoying bug ever. And it is present in all versions of Lazarus. Sometimes I have to remove executable before compilation despite the fact that Lazarus folder is excluded from Windows Defender list.

[Eugene Loza]

And it is present in all versions of Lazarus.

Actually I don't remember if I experienced this bug before (namely 1.1.6, 1.2.4, 1.2.6 were clear). Maybe in some very early versions, like 0.24 or 0.30... My report corresponds to 1.4 RC1.

[Zoran]

Steps to reproduce:
1. Create an empty project (application).
2. Save all to a known place.
3. Compile.
4. Change the project (any change for recompilation, e.g. add an additional variable in var section).
5. Compilation fails.

I cannot reproduce this bug (windows 7, 64-bit, lazarus 32-bit). The project compiles fine.