Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2011-03

Lazarus application invalid on ubuntu 64

4 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Andrea Mauri

Dear all,
I loaded a lazarus project on my new Ubuntu 10.10 intel64 (lazarus 0.9.31 r30096 FPC 2.4.2 x86_64-linux-gtk 2).
The application is compiled correctly but it won't run. Lazarus give me this message:

Caption: Lazarus application invalid
Text: The launching application ""path/exename""
does not exist or is not executable.
See Run -> Run parameters -> Local

If I create a new project and I put some components on the form it runs properly.
I checked "See Run -> Run parameters -> Local" for both project and everything looks the same.
What can I check in order to solve this issue? I got that message for all my projects.

Anyway the compilation seems to work well but if I try to launch the executable outside Lazarus I got this message

Could not display "path/exename".
There is no application installed for executable files

Andrea

Reply by email

Hans-Peter Diettrich
to Andrea Mauri
Show quoted text 16 lines
I loaded a lazarus project on my new Ubuntu 10.10 intel64 (lazarus 0.9.31 r30096 FPC 2.4.2 x86_64-linux-gtk 2). The application is compiled correctly but it won't run. Lazarus give me this message: Caption: Lazarus application invalid Text: The launching application ""path/exename"" does not exist or is not executable. See Run -> Run parameters -> Local If I create a new project and I put some components on the form it runs properly. I checked "See Run -> Run parameters -> Local" for both project and everything looks the same. What can I check in order to solve this issue? I got that message for all my projects.

Looks to me like you have checked "Use launching application" in the Run Parameters, but enterd no valid shell path/name below it.

Simple solution: Uncheck that option, AFAIK it's only required to run console applications on Linux, or other projects which are not self-contained (runnable) executables.

When a launching application really is required, enter a valid application in the edit box.

DoDi

Reply by email

Rüdiger Ranft
to Andrea Mauri: I loaded a lazarus project on my new Ubuntu 10.10 intel64 (lazarus 0.9.31 r30096 FPC…
Show quoted text 5 lines
Anyway the compilation seems to work well but if I try to launch the executable outside Lazarus I got this message Could not display "path/exename". There is no application installed for executable files

What does `file executable` and `ldd executable` say? example:

foo at bar in ~
? file /bin/bash
/bin/bash: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped

foo at bar in ~
? ldd /bin/bash
linux-vdso.so.1 => (0x00007fff0c0da000)
libtermcap.so.2 => /lib64/libtermcap.so.2 (0x0000003847400000) libdl.so.2 => /lib64/libdl.so.2 (0x0000003844800000) libc.so.6 => /lib64/libc.so.6 (0x0000003844400000) /lib64/ld-linux-x86-64.so.2 (0x0000003844000000)

HTH
Rudi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 898 bytes
Desc: OpenPGP digital signature
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20110401/8c4b98f9/attachment.bin>

Reply by email

Andrea Mauri
to Rüdiger Ranft
Show quoted text 5 lines
foo at bar in ~ ? file /bin/bash /bin/bash: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9, stripped

ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped

I have some problems with permissions.
I have my project on a portable HD where I am not able to change users permissions in order to execute applications, I copied my executable on my local HD and allowing execution it runs.
I found that the problem is related to the last version of udisks. ...
ok I solved, I downgraded udisks and now it works. Thanks,
Andrea

Reply by email