No worries, my posts aren't the easiest to follow to begin with

Moderators: Klaus, FourthWorld, heatherlaine, robinmiller, kevinmiller
Peter TB Brett 2016-04-13 13:04:01 BST wrote: The command needed here is to run :> strace -fe trace=process /path/to/installer
It looks like the issue is as follows:
- The Community installer is trying to launch "LiveCode Community.x86_64", which doesn't exist (the binary is named "livecodecommunity.x86_64" for backwards-compatibility reasons)
- The Business installer is trying to launch "LiveCode Business.x86_64", which does exist
And despite what you said in another thread about companies, bugs, and software, while I agree that all software has bugs, maybe fixing known ones with in a year or two isn't such a bad goal.Maybe someone with access to the source who knows what they are doing could submit a pull and fix the spelling issue, before it becomes a teenager?
That's weird. It's the least interesting part of the product from a technology standpoint. ::scratching head::
Not really. The github repository allows you to build the community project. The installer has to handle all the different editions, check the licensing details, package all the myriad parts and unpack them into the appropriate places with proper permissions, etc. There are good reasons for keeping some proprietary parts private.That's weird.
Try your distro x with the MATE desktop, I think you'll be surprised. The launch after install works on Linux Mint Debian Edition 2 (which uses the MATE desktop by default). Go figure, I think it must have been designed to work on Gnome2 and was just never updated.ClipArtGuy wrote: ↑Sun Aug 26, 2018 4:44 pmedit: also the "launch livecode" option at the end of the installation process doesn't work, but LC is installed and can be launched after that fails.richmond62 wrote: ↑Sun Aug 26, 2018 5:21 pmThat has NEVER worked for me on any Linux installation in the last 13 years.