having problem installing Repetier Host 2.16 on Linux Mint

Dear Team,
I've been using Repetier Host for five years and know by experience that this is is the most practical and user-friendly 3D printing host of all. Very recently I switched my desktop computer Lenovo ThinkCentre from Windows 7 to Linux Mint. Linux Mint was a dream made true until I tried to install my downloaded files of Repetier Host 2.16. It was always easy to do it on Windows XP, 7 or 10.
To be honest, I don't have a clue about how to do it. My Linux Mint is already upgraded. 
Any help or suggestion will be greatly appreciated.
Sincerely,
Victor

Comments

  • Normally you should install the appimage version as that contains all required software. It might still fail to work due to some missing package. To see if something is missing start it from a shell you see the output. Then you easily see if some library is missing and all you need to do is installing the library mentioned. If you find one is missing pleas elet me know and I might be able to add it in next version by default. 
  • Belated thanks for your kind answer. Could you please tell me which shell should I use to find out which library or package I'm missing in order to make Repetier applmage version on Linux Mint 20.
  • Just open a terminal windows - shell is not relevant which, but guess you get bash. Then just start the app from the terminal window and you see all output.
  • This is what i got. Definetely something is missing here.
    -bash: Repetier-Host-x86_64-2.1.6.AppImage.tar.gz: command not found
    victor@victor-ThinkCentre-M58p:~/Downloads$ Repetier-Host-x86_64-2.1.6.AppImage.tar.gz
    -bash: Repetier-Host-x86_64-2.1.6.AppImage.tar.gz: command not found
    victor@victor-ThinkCentre-M58p:~/Downloads$





  • The downloaded file should have name Repetier-Host-x86_64-2.1.6.AppImage  without tar.gz. Only the non app image version has that extension.
  • I made sure that it is in downloads. something continues missing. Should I download it and extract again?

    victor@victor-ThinkCentre-M58p:~/Downloads$ Repetier-Host-x86_64-2.1.6.AppImage
    -bash: Repetier-Host-x86_64-2.1.6.AppImage: command not found
    victor@victor-ThinkCentre-M58p:~/Downloads$



  • When you are in Downloads check file
    ls -l

    it could be that you did not add execute permissions to the file:
    chmod a+x Repetier-Host-x86_64-2.1.6.AppImage

    Without that it is not an executeable and would not run.
  • Hi. I am facing the same problem.

    I downloaded the Repetier-Host-x86_64-2.1.6.AppImage  file, changed it to executable and I am able to run it. I configured the connection (IP) of my printer and as soon as I click connect, Repetier host hangs.

    I tried to run it from a terminal and here it is what I have after click connect button

    dell@dell-inspiron1525:~/Repetier$ ./Repetier-Host-x86_64-2.1.6.AppImage 

    LD_LIBRARY_PATH = /tmp/.mount_Repetiz5ewtC/usr/lib:/tmp/.mount_Repetiz5ewtC/usr/lib/mono/4.5:
    MONO_PATH = /tmp/.mount_Repetiz5ewtC/usr/lib/mono/4.5

    Unhandled Exception:
    System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
      at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.ConsoleDriver..cctor () [0x0004d] in <a07d6bf484a54da2861691df910339b1>:0 
       --- End of inner exception stack trace ---
      at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Console..cctor () [0x0008e] in <a07d6bf484a54da2861691df910339b1>:0 
       --- End of inner exception stack trace ---
      at RepetierHost.connector.SocketConnector.WriteLoop () [0x00030] in <374e76794d164d76af696b6b7ca9e871>:0 
      at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <a07d6bf484a54da2861691df910339b1>:0 
    [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
      at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.ConsoleDriver..cctor () [0x0004d] in <a07d6bf484a54da2861691df910339b1>:0 
       --- End of inner exception stack trace ---
      at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Console..cctor () [0x0008e] in <a07d6bf484a54da2861691df910339b1>:0 
       --- End of inner exception stack trace ---
      at RepetierHost.connector.SocketConnector.WriteLoop () [0x00030] in <374e76794d164d76af696b6b7ca9e871>:0 
      at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <a07d6bf484a54da2861691df910339b1>:0 
      at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <a07d6bf484a54da2861691df910339b1>:0 
    dell@dell-inspiron1525:~/Repetier$ 

  • Are you sure the printer supports telnet ip connection? If not that can cause also hangs until a timeout. While some printers have some web interface that is not the port you need to enter in host to get a working connection. You need the port that communicates the same way it would using usb connection.
  • Strange. The printer is a Gtmax3d ProCore H5. It uses a repetier server embedded but customized for the gtmax. So it does not seems to be the case you are talking about the telnet IP to be the problem.

  • When you connect to server you need use the server connector and port is normally 3344. Do not confuse it with the regular TCP/IP connector which will not work.

    As a test call http://serverip:3344 on your browser. If you see server gui the server connector should work.
Sign In or Register to comment.