Kubuntu 22.04

[tetsuo29]

Just tried to install LC 9.6.9 (64 bit) on Kubuntu 22.04. Made the download executable and in the terminal typed:

Code: Select all

sudo ~/Downloads/LiveCodeInstaller-9_6_9-Linux.x64

Nothing appears to happen.

Any ideas on how to troubleshoot? Is there a log file that can be looked at? Are there required libraries that I need to make sure are present?

Thanks.

[FourthWorld]

Downloading usually clears the executable bit. chmod 755 to make it runnable.

[tetsuo29]

Downloading usually clears the executable bit. chmod 755 to make it runnable.

I guess you missed the part of my post where I said that I made it executable. I wish it was that simple.

I also ran LDD against it and got the following:

linux-vdso.so.1 (0x00007ffefe197000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa8976b1000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa8976ac000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fa89767b000)
libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007fa8975b3000)
libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007fa897569000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa897200000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa897480000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa897460000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa896e00000)
libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007fa8971c5000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fa897444000)
libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007fa897436000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fa89742b000)
/lib64/ld-linux-x86-64.so.2 (0x00007fa8976cc000)
libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007fa8971a2000)


I'm not really familiar with LDD but, I from the little I've read, it's good that there aren't any "not found" messages in that output?

I wish it would spit out some text complaining about why it can't run.

[FourthWorld]

Downloading usually clears the executable bit. chmod 755 to make it runnable.

I guess you missed the part of my post where I said that I made it executable.

You guessed correctly. I help with support across four forums. I may miss a detail now and then. I appreciate your patience.

I wish it would spit out some text complaining about why it can't run.

I your Kubuntu is stock, does double-clicking the exe not launch it?

I'm limited with what I can offer here; I respect the KDE project but have been using Gnome, and when I see an exe that can't run on Ubuntu I usually see some feedback in Terminal. A few here use KDE and hopefully someone will chime in shortly.

If you don't find a satisfying answer here, you might try the Kubuntu forums to at least get good diagnostic assistance. You could also try posting in the "Desktop Environments" section of the Ubuntu forums - I'm rg4w there and will see it if you do; would be interesting to see how that goes.
https://ubuntuforums.org/forumdisplay.php?f=329

[wsamples]

tetsuo, try adding the -ui flag to your command. I can't use the installer the "GUI" way any more but it runs and installs properly using the -ui flag. The installers launch for me but get stuck, so we don't have exactly the same behavior, but even if it doesn't result in a successful installation, you might get a little more useful information since output will hopefully be displayed in the terminal. You should create a log but if the installer aborts this early it won't write anything to the log. Your command will look something like this:

Code: Select all

 sudo ~/Downloads/LiveCodeInstaller-9_6_9-Linux.x64 -ui -log /PATH_TO_LOG/installer_log 

Good luck!

[FourthWorld]

Good info, Warren. Thanks.

Which distro are you on? And is it just the LC installer that doesn't run, or are you using the engine without an IDE, command-line only?

[wsamples]

Hi, Richard. It's an Arch spin (EndeavourOS) with Openbox. This has been happening for some months now and even installers which previously had worked now get stuck after selecting the installation location and starting the actual installation process. It shows a dialog complaining about conflicting apps. Strace shows an endless string of "resource temporarily unavailable" messages. Someone else reported this same issue some time ago although I can't find the post. Once installed, the IDE seems unaffected by whatever causes the problem for the installer and seems to work just fine.

[richmond62]

On Xubuntu, after setting the executable bit I double click on the installer and then choose the 'you only' type of install.

No need to go near the command line at all.

[tetsuo29]

tetsuo, try adding the -ui flag to your command. I can't use the installer the "GUI" way any more but it runs and installs properly using the -ui flag. The installers launch for me but get stuck, so we don't have exactly the same behavior, but even if it doesn't result in a successful installation, you might get a little more useful information since output will hopefully be displayed in the terminal. You should create a log but if the installer aborts this early it won't write anything to the log. Your command will look something like this:

Code: Select all

 sudo ~/Downloads/LiveCodeInstaller-9_6_9-Linux.x64 -ui -log /PATH_TO_LOG/installer_log 

Good luck!

Thank you! Your advice helped me hit pay dirt on this.

Here's what happened...

I got curious about just using the -log option and so I did:

Code: Select all

russ@REM-UX31E:~/Downloads$ sudo ./LiveCodeInstaller-9_6_9-Linux.x64 -log ~/livecodeinstall.log
[sudo] password for russ: 

(LiveCodeInstaller-9_6_9-Linux.x64:22742): Gtk-WARNING **: 10:51:40.763: Unable to locate theme engine in module_path: "adwaita",

And no installer. I also went looking for the livecodeinstall.log file I specified after the -log option. Looked in my user's home directory and root's home directory (since the command was started with sudo). No such file seems to be anywhere on my system.

I thought, 'that's interesting. what happens if I run it with the -log option and don't specify a file?'

So I did:

Code: Select all

russ@REM-UX31E:~/Downloads$ sudo ./LiveCodeInstaller-9_6_9-Linux.x64 -log

(LiveCodeInstaller-9_6_9-Linux.x64:22816): Gtk-WARNING **: 10:54:02.400: Unable to locate theme engine in module_path: "adwaita",

And guess what popped up on my screen and then ran without problems? So, something about adding the -log option lets it complain about its troubles but then get on with the install.

I don't know if I would have ever figured that out, so thanks again!

[FourthWorld]

Hi, Richard. It's an Arch spin (EndeavourOS) with Openbox. This has been happening for some months now and even installers which previously had worked now get stuck after selecting the installation location and starting the actual installation process. It shows a dialog complaining about conflicting apps. Strace shows an endless string of "resource temporarily unavailable" messages. Someone else reported this same issue some time ago although I can't find the post. Once installed, the IDE seems unaffected by whatever causes the problem for the installer and seems to work just fine.

Thank you for that background, Warren. It sounds similar to some of the issues I was seeing on the RPi back in the day, where the installer was dying but the IDE (often) ran fine.

Have you submitted a bug report on this? Do you know if they accept bug reports on systems outside their officially-support spec?

I would hope they do. The few Linux systems listed as officially supported are so old they're not supported at all by the distro vendors themselves.

[wsamples]

Thank you! Your advice helped me hit pay dirt on this.

I'm happy to learn you resolved the issue of the failing installer! That's the most important thing.

It's interesting to note that our problems were not the same insomuch as your solution of adding the '-log' flag does not work for me. The installer gui window launches and aborts again with the message about conflicting apps. Adding the '-ui' flag and letting the installer bypass its own window and run in the terminal results in success, with or without the '-log' flag.

So, two different and not well understood installer problems and two different potential working solutions to recommend when people have issues with the installer failing to behave as expected under Linux.

[richmond62]

I have a feeling that I might go completely bonkers and install Kubuntu on a 'spare' computer
I have lying around just to see what I can see: but unlikely until Sunday at the soonest.

Watch this space.

Certainly ran LC 4.5 on Kubuntu without any obvious problems a few years ago.

[mwieder]

tetsuo29-

I stopped installing for "all users" a while back to make my life simpler, especially for uninstalling.

Of course, all this could be solved with a proper linux installer, but LC has never had one of those.

[richmond62]

Well . . . hey,ho, hairy doo-dahs: Richmond's naivety has no end:

I installed Kubuntu 23.0.4 on a partition of my ACEPC (other partition holds HAIKU), and LiveCode 9.6.3 community (both the 64 and the 32 bit versions) and did this sort of thing:
-

KUB1.png (86.85 KiB) Viewed 18469 times

-

-
'Cos that's what I would do on Xubuntu, and what allows me to install these things on Xubuntu.

HOWEVER: a double-click does 'nix'.

[richmond62]

Cripes: that 'one' kept me awake for about 4 hours in the night.

So, not knowing whether my midnight fantasies had any basis in reality or not:

1. Booted up my Kubuntu 23.04 install.

2. Installed XFCE.

3. Logged out.

4. Logged into the XFCE desktop [by-ther-way: when you install XFCE be careful to select the 'ldm' window thingy].

(Wow! Got a dead-sexy default desktop picture).

5. Installed LC Linux 64-bit. [ set executable bit, double-clicked on desktop, selected 'you only' . . .]
-

-
6. Checked that it was in the 'Development' menu on XFCE.

6.5. Stared LiveCode under XFCE:
-

-
7. Logged out of XFCE.

8. Logged into Kubuntu 23.04.

9. Saw LiveCode in 'Development' menu [KDE].

10. Clicked on LiveCode, and everything worked.

ALL a bit of a rigmarole: BUT possibly less so that endless fooling around with the command line.