Hello there,
I'm terribly sorry to hear about the problems you are having with LoadUI-Agent-2.5.4. Unfortunately the reason that you haven't gotten a fast reply is due to the fact that support is situated in Sweden and Swedes celebrated Ascension day from the 8th of May until 9th of May so nobody has been in the office for since then.
If you are still interested then i would like to assist with this problem as you are most likely not the only one who will encounter them until Java8 is released. There is a workaround that is defined in the guide on
this site, thanks for mentioning the typo in the guide by the way about how to launch it, it has been fixed now.
As for that OpenJDK is appearantly needed for the installer that does sound odd and i will look into that one further to reproduce it and investigate how it can be avoided in the future.
From the looks of it, your problems implicates that you either have not exported the DISPLAY=:99 variable or that Xvfb hasn't been started properly, and also the first setup of the agent might take some time depending on the system so it can interpreted as not working.Unfortunately i have not been able to recreate all of the problems you had on my Ubuntu Server 12.04 VM, nor RHEL6 or CentOS.
The only problems i ran into were related to my own belief that i knew the steps, since i composed the guide, and evidently missed a few.
Hopefully you and anyone else encountering these issues can learn from my mistakes and i will adapt the guide accordingly if it works out.
My Workflow:
downloaded the agent
chmod +x to the install-script
installed Xvfb
installed the dependencies for Xvfb
Tried to launch LoadUI-Agent, got Cannot Connect to X11 Window-error.
Realized that i hadn't started Xvfb using xvfb -ac :99 &, so i started it.
noticed that some dependencies hadn't really kicked in when Xvfb started.
Realized that my entire apt-get install had failed miserably du to not having applied --fix-missing
install dependencies again using apt-get install BIG-LIST-OF-DEPENDENCIES --fixmissing
restarted Xvfb
Tried to launch LoadUI-Agent again, got Gtk-WARNING **: cannot open display.
exported virtual display properly using export DISPLAY=:99.0
Started using binary: ./LoadUI-Agent-2.5.4 and the alternate bash-script ./loadUI-agent.sh, and reached the FrameWork Started.
Collection of encountered errors: Can't connect to X11 window server using ':99' as the value of the DISPLAY variable-error: Received among other errors when i hadn't installed dependencies correctly for Xvfb and LoadUI.
Tried --fix-missing to apt-get install
RANDR-error: It is related to an extension that is not implemented by Xvfb, but it has not implications for LoadUI-Agent
Read more hereSplash.xml-error: It's not a fatal error and has been cleaned up during some code-housekeeping lately. It can be ignored.
Gtk-WARNING **: cannot open display: I hadn't set the environment variable DISPLAY using
export DISPLAY=:99.0
Note:
The environment variables are reset on restart of system,
so put it in a startup-script like /etc/rc.local for example. No errormessages but agent has not started yet so i had to press CTRL+C and abort it:LoadUI-Agent evidently takes some time to start, give it atleast a few minutes depending on your system.
My VM took 30s to get it right, my workstation 15s, a really slow machine could probably take more than a minute.
The last line to be showing that the framework is started for the binary, and that the agent is listening on port 8443 for the binary.
Locale not supported by C library: This one i have not encountered on my VM, i believe it has to do with your environment and found
a possible workaround online, and it would be most interesting to know if it worked for you.
loadui-splash.fxml (No such file or directory)Not fatal, the splash cannot be displayed and should not be displayed either. This does not break anything and has been cleaned by code-housekeeping recently, but has yet to be released.
Check these things out and do get back should they not work,
there are no holidays the upcoming weeks so answers should hopefully be more swift.
Best Regards
Mikael
SmartBear Sweden