Gambas3 IDE startup fails after updates
Posted
#1
(In Topic #1167)
Trainee
Any suggestions please on how to get it running under my own username, and how to avoid problems in future?
Framework 13th gen Intel, Fedora 39. Doesn't start from the GUI menus, or from CLI :-
Code
[roopid@fedora ~]$ gambas3
[gb.jit].CCompilation.Run.83: #68: Cannot run child process: cannot run executable: No such file or directory
[gb.jit].CCompilation.Run.83 [gb.jit].Jit._Compile.143 ?
I just tried sudo and the IDE starts OK and seems to be running correctly :-
Code
[roopid@fedora ~]$ sudo gambas3 &
[6] 10096
[5] Done sudo gambas3
[roopid@fedora ~]$
but I don't see sudo as a long term solution
Roops
Posted
Guru

try
which gambas3
is it
/usr/bin/gambas3
ls -l /usr/bin/gambas3
is it..
lrwxrwxrwx 1 root root 14 Dec 23 00:12 /usr/bin/gambas3 -> gambas3.gambas
does it load okay if you type
gambas3.gambas
It certainly a problem your end and not something common we are familiar with.
Posted
Trainee
Code
[roopid@fedora ~]$ which gambas3
/usr/bin/gambas3
[roopid@fedora ~]$ ls -l /usr/bin/gambas3
lrwxrwxrwx. 1 root root 14 Aug 7 01:00 /usr/bin/gambas3 -> gambas3.gambas
[roopid@fedora ~]$ ls -l /usr/bin/gambas3.gambas
-rwxr-xr-x. 1 root root 6432588 Aug 7 01:00 /usr/bin/gambas3.gambas
[roopid@fedora ~]$
Posted
Trainee
dnf info shows Source : gambas3-3.18.3-2.fc39.src.rpm and I can't see anything out of the ordinary.
Hmm…
Roops
Code
[roopid@fedora ~]$ dnf info gambas3-ide.x86_64
Last metadata expiration check: 0:18:40 ago on Tue 02 Jan 2024 16:07:33 GMT.
Installed Packages
Name : gambas3-ide
Version : 3.18.3
Release : 2.fc39
Architecture : x86_64
Size : 6.1 M
Source : gambas3-3.18.3-2.fc39.src.rpm
Repository : @System
From repo : fedora
Summary : The complete Gambas3 Development Environment
URL : http://gambas.sourceforge.net/
License : GPL+
Description : This package includes the complete Gambas3 Development Environment.
: It pulls in the Gambas3 components necessary for the IDE to function.
[roopid@fedora ~]$
Posted
Guru

you could try the env setting GB_NO_JIT = true
env GB_NO_JIT=true gambas3
if it works you could set an alias in /etc/profile.
alias gambas3='env GB_NO_JIT=true gambas3'
I had a similar issue when i changed my /tmp folder to be a tmpfs ramdisk. It broke gambas JIT so i stopped making /tmp a ramdisk.
Not sure why your gambas JIT is broken but at least it can be bypassed.
Posted
Guru

is gambas3-gb-jit installed?
Posted
Trainee
I still don't know what broke it, but as long as it work…
Thanks for the suggestions :-)
Roops
1 guest and 0 members have just viewed this.



