error while compile [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3. 8.0:compile (default-compile) on project RemoteSupportTool-Core: Fatal error com

I am not sure how to debug this. I have some experience with C#, but none with TCL. The window location is off the screen on my multi monitor setup when I launch the application. I am not sure where to even begin making those modifications since for the most part the TCL seems to be a bundling script as opposed to a full programing language

Unfortunately our current PyInstaller based build system has some downsides. After spending a lot of time and frustration we were still not able to produce application binaries anymore on certain systems. Due to our limited time and lack of knowledge about the internals of PyInstaller we were not able to track down the cause of the problem.

Therefore we've decided to migrate the application from Python to Tcl/Tk. This allows us to implement an easier and more flexible build system. Based on precompiled tclkit binaries it is possible to cross compile the application for all supported target systems on a single machine without any hassle.

Besides the application itself all build scripts were ported from Bash & Batch to Tcl/Tk. This means, that we don't need to provide separate build scripts for Windows anymore. The build scripts can be used on every operating system with an installed Tcl environment. If that is not possible, one might also use one of the provided tclkit binaries in order to execute the build scripts.

Unfortunately there is no comparable alternative to Paramiko available for Tcl. Therefore we're using OpenSSH for SSH tunneling. Linux and Mac OS X are providing OpenSSH out of the box. For Windows systems we've integrated the binaries provided by mls-software.com.

The mouse pointer of staff and customer are at a different positions.

It is only correct a the top left corner. I guess this is caused by the highdpi screen at customer side (windows 10 with scaling > 200%). RemoteSupportTool uses a low res screenshot, but it doesn't scale the mouse position of staff from low res to high res. To fix use native res screenhot or scale the mouse position.

OpenSSH doesn't start when I try to connect from a Windows 10 Machine via the GUI, but it is working if I start it from CMD without the -f parameter (and without sleep 15). Does somebody know what to do, to make it working? From Linux its just working fine.

As described here pyi-build is deprecate since versione 3 of pyinstaller: https://github.com/pyinstaller/pyinstaller/commit/a5cd4b748d5bd831ff1869bcf55133b125f156eb https://github.com/pyinstaller/pyinstaller/issues/1490

The position of the mouse cursor send by the staff is not properly shown on the customer's machine, if the customer uses multiple monitors.

We were able to reproduce this problem for Linux customers with a multi monitor setup provided by the Nvidia graphics driver. It's currently not clear, if the same problem occurs in other scenarios (Xinerama on Linux or generally on other operating systems). Further investigation is required.

The urls to AdoptOpenJDK in the openjdk init scripts did not work. Please find the working ones in the diff. A nice enhancement would be if the init scripts would check the exit value of curl for easy and obvious detection of changing urls in the future.

diff --git a/release/share/openjdk/init-linux64.sh b/release/share/openjdk/init-linux64.sh index ea7ca59..c06bbdb 100755 --- a/release/share/openjdk/init-linux64.sh +++ b/release/share/openjdk/init-linux64.sh @@ -25,7 +25,8 @@

-----------------------------------------------------------------------

TARGET="linux64" -TARGET_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Linux_jdk-10.0.2.13.tar.gz" +TARGET_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Linux_jdk-10.0.2+13.tar.gz"

DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" DOWNLOADS_DIR="$DIR/downloads" diff --git a/release/share/openjdk/init-windows64.sh b/release/share/openjdk/init-windows64.sh index 95bc9fb..89dd620 100755 --- a/release/share/openjdk/init-windows64.sh +++ b/release/share/openjdk/init-windows64.sh @@ -25,7 +25,8 @@

-----------------------------------------------------------------------

TARGET="windows64" -TARGET_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Windows_jdk-10.0.2.13.zip" +TARGET_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Win_jdk-10.0.2+13.zip"

DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" DOWNLOADS_DIR="$DIR/downloads" diff --git a/release/share/openjdk/init.sh b/release/share/openjdk/init.sh index f3a8c75..c1a47e1 100755 --- a/release/share/openjdk/init.sh +++ b/release/share/openjdk/init.sh @@ -39,7 +39,7 @@ case "$SYSTEM" in case "$SYSTEM_ARCH" in x86_64) echo "Initializing Linux 64bit environment..."

•      SYSTEM_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Linux_jdk-10.0.2.13.tar.gz"
  

•      SYSTEM_JDK="https://github.com/AdoptOpenJDK/openjdk10-releases/releases/download/jdk-10.0.2%2B13/OpenJDK10_x64_Linux_jdk-10.0.2+13.tar.gz"
       ;;
     i686)
  

Hi, I am Korean and My English is not good. Recently I take this program and compile with Ubuntu by myself with downloading master.zip file. Compile is fine, but when I click 32bit-exe file in the launch4j folder, it has an error [ This application requires a Java Runtime ENvironment 10(32bit)] With [https://github.com/OpenIndex/RemoteSupportTool/releases] 's StaffSupportTool-1.0.0-win32.exe & CustomerSupportTool-1.0.0-win32.exe, it is working with my Win 10 64 bit PC. When i search Java 10 32bit , it is not exist. How can i solve it? Thank have good day.

With the migration to Java (see #9) we're going to change the license from MIT to Apache 2.0. This should not make a huge difference for the users. But because all of our Java based projects are licensed with Apache 2.0, we like to have some sort of consistency here.

Up to now we only provide a graphical interface for the user, that likes to share his desktop. Reworking the application with Java 10 (see #9) also allows us to create a graphical interface for the support staff. This makes it a lot easier for the support side to open a support session. No external requirements (separate VNC viewer, manual SSH tunneling, etc.) are needed.

Sometimes the costumers screen resolution is bigger than that of the staff. In this case the screen is resized to fit the staff resolution at the moment. It would be nice if there would be an on/off 1:1 option in the staff window during a remote session to switch to costumer resolution and to add scroll bars in the staff window to enable navigation.

How can I send CTRL-ALT-DEL from the staff Application to the client application without the client OS intercepting it? The client screen locked and I did not find a way to send the unlock keys. I tried this [1], but it did not work.

[1] https://www.pointdev.com/en/faq/faq-ideal-administration-send-ctrl-alt-del-tightvnc-vnc-logon-sas-computer-machine-id-227.html

It would be great to have an optional reconnect feature. I have customers who starts the connections once and leave the window open for me to work for a longer period alone. If the connection is dropped because of some network glitch, the customer has to manually reconnect at the moment. This takes time and causes work interruptions. It would be great to have on option "Automatic reconnect" in the client GUI. The client watches if the connection is down, and it reconnects automatically to the Staff Tool when the checkbox is checked and of course the client GUI is still running.

It seems that the customer application is not properly working on Linux with Wayland. If the customer application is running on Fedora 29 (latest version), the staff only receives a black screenshot.

It might be an issue with OpenJDK. Or maybe there might be a way to explicitly allow an application to take screenshots. Fortunately Wayland is currently not widely used. But sooner or later we need to find a solution.

Certain settings for performance / quality might be editable during a support session:

• level of JPEG compression (currently 60% by default)
• screenshot interval (currently 250 ms by default)
• width / height of transferred screenshot tiles (currently 100 px by default)