Mattias Gaertner wrote:
On Wed, 18 Feb 2015 21:36:33 +0000
Mark Morgan Lloyd <[email protected]> wrote:
Using FPC 2.6.4 or late 2.7.1, compiling trunk on Wheezy is OK but
running gives me
The program 'lazarus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 428 error_code 188 request_code 155 minor_code 23)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
Appears to affect Athlon (32- and 64-bit) and Intel (32-bit, don't have
64). Does not affect Squeeze. Building with OPT='-O- -gl' still doesn't
allow me to get a bt.
I just tested Wheezy 32bit on VirtualBox/Intel: it runs.
Lazarus trunk, fpc 2.6.4.
Please open a terminal and start the IDE with --sync:
cd sources/of/lazarus
./lazarus --sync --g-fatal-warnings
What do you get?
Trunk (as of yesterday evening), 2.6.4, export OPT='-O- -gl', make all,
run with ./lazarus --sync --g-fatal-warnings.
The machines here are generally Debian with KDE as a desktop, but the
"Wheezy" systems are closely modelled on the older "Squeeze" ones. It
appears that if I run on the machine's own display it works, but if I
attempt to run Lazarus over SSH (a combination that works on all other
systems around here and with numerous programs on the test systems) it
fails with
$ ./lazarus --sync --g-fatal-warnings
Xlib: extension "RANDR" missing on display "localhost:10.0".
TMainIDE.ParseCmdLineOptions:
PrimaryConfigPath="/home/markMLl/.lazarus"
SecondaryConfigPath="/etc/lazarus"
The program 'lazarus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 1054 error_code 188 request_code 155 minor_code 23)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
Is OK over a remote X session (i.e. running in Xnest). An initial
successful run to set up ~/.lazarus doesn't improve the situation over
SSH but gets it to the point where lazbuild works.
However I also find that a program built using Lazarus (IDE or lazbuild)
fails on that system (i.e. Wheezy) in the same way as the IDE.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
