I would like to install Xojo on CentOS 7, because my application doesn’t work properly anymore.
I embed containers on a webpage in the open event.
One container shrinks considerably and a group of containers disappear.
Is there somebody who had the same experience?
The app works properly in debug mode or on CentOS 6 32-bit
Therefor I’m installing Xojo on CentOS 7 to debug the app.
I have tested it on 3 CenTOS 7 servers. Two of them are updated. Same problem
The version of Xojo is 2018r3
On the server CentOS 6 32-bit the test was done with xojo 2017r1 which was okay.
Remember, you can use VirtualBox and create VMs of different distros to test this stuff. Also, I recommend mirrors.kernel.org for the most complete and up to date ISO downloads.
I have a server with esxi on it and several servers but all CentOS.
I have a mac mini on which I want to install ubuntu.
I will install 2018r4 tomorrow on CentOS 7 and maybe this will show a little bit more.
Can we pick this up tomorrow, because I like to go to sleep, almost midnight. Last night little bit short 5 hours of sleep.
You can build testing VMs in as little as 20GB of disk and 2GB of RAM for these tests. I’d still recommend that you try the VM route rather than dealing with Apple’s real hardware for this stuff.
I use a VM server with esxi, which has two CentOS 7, one CentOS 6 and one CentOS 5.
I’m investigating the problems with my application. I detected one error which I can correct, but for which I don’t have an explanation.
I will explain this later, because I have an appointment this evening.
I almost finished the installation of Xojo 2018r4 on my server CentOS 7. I installed group GNOME Desktop and I’m installing vncserver.
But the installation is totally different from CentOS 6. It isn’t working
systemctl enable vncserver@:1.service gives an error
systemctl start vncserver@:1
Feb 28 11:26:08 web.cat systemd[1]: Starting Remote desktop service (VNC)…
Feb 28 11:26:08 web.cat runuser[16209]: runuser: user does not exist
Feb 28 11:26:08 web.cat systemd[1]: vncserver@:1.service: control process exited, code=exited status=1
Feb 28 11:26:08 web.cat systemd[1]: Failed to start Remote desktop service (VNC).
Feb 28 11:26:08 web.cat systemd[1]: Unit vncserver@:1.service entered failed state.
Feb 28 11:26:08 web.cat systemd[1]: vncserver@:1.service failed.
[/code]
As long as there is no vncserver there will no Xojo
I’m continuing searching but to day I only have one half hour left.
Sorry to seem to be beating a dead horse, but a VM on your primary hardware is the best answer for what you are doing if you don’t have lots of hardware to test on (including monitors, keyboards, and mice. Or, have you considered a low cost KVM from someone like IOGear? We use lots of these in our lab and they work great: IOGear HDMI KVM Switch
I install servers at my clients. But my primary business is software development. So I install HP ML350 servers hoping for a minimum of problems with hardware.
Sorry man, but I can’t believe that you said that - if you write applications, they must run on hardware and operating systems. If you don’t have the platforms to test against, how can you ever know if your products work under a given situation?
Low-end PCs are cheap - you can get refurbished Dell desktop system that run Windows and Linux perfectly. Combine that will low cost KVMs and you don’t have to deal with a 1:1 monitor/keyboard situation.
Unless you are limiting your potential client base to a very specific OS version on a very specific hardware configuration, you’re bound to run into many more failures of this type.
All my clients have almost the same hardware and the same OS = CentOS. Normally I don’t have any problems. It is now that I switched to CentOS 7 64-bit that I have software issues. I almost never have hardware problems. I’m not interested anymore in PCs. Mostly my clients want to run on there PCs MsWindows, which I don’t like. So this is done by others.