Can only run Repetier-Host under sudo?

deleted_user_15009

I am running Repetier-Host V2.2.4 and Server V1.4.2 on Linux Mint 20.3 Una.

If I launch Repetier-Host using sudo repetierHost it opens and runs correctly, connects to the server, prints, etc.. However, if I attempt to run it under my user it doesn't start and gives me the following errors:

$repetierHost

$ libpng warning: iCCP: known incorrect sRGB profile

Unhandled Exception:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at RepetierHost.view.FormPrinterSettings.comboScripts_SelectedIndexChanged (System.Object sender, System.EventArgs e) [0x0004a] in <63c553364181423faf81fbf20d6b440d>:0
at RepetierHost.view.FormPrinterSettings.formToCon () [0x0001f] in <63c553364181423faf81fbf20d6b440d>:0
at (wrapper remoting-invoke-with-check) RepetierHost.view.FormPrinterSettings.formToCon()
at RepetierHost.view.FormPrinterSettings.LoadDefaultPrinter () [0x00066] in <63c553364181423faf81fbf20d6b440d>:0
at RepetierHost.Main..ctor () [0x002ac] in <63c553364181423faf81fbf20d6b440d>:0
at (wrapper remoting-invoke-with-check) RepetierHost.Main..ctor()
at RepetierHost.Program.Main (System.String[] args) [0x00015] in <63c553364181423faf81fbf20d6b440d>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.IndexOutOfRangeException: Index was outside the bounds of the array.
at RepetierHost.view.FormPrinterSettings.comboScripts_SelectedIndexChanged (System.Object sender, System.EventArgs e) [0x0004a] in <63c553364181423faf81fbf20d6b440d>:0
at RepetierHost.view.FormPrinterSettings.formToCon () [0x0001f] in <63c553364181423faf81fbf20d6b440d>:0
at (wrapper remoting-invoke-with-check) RepetierHost.view.FormPrinterSettings.formToCon()
at RepetierHost.view.FormPrinterSettings.LoadDefaultPrinter () [0x00066] in <63c553364181423faf81fbf20d6b440d>:0
at RepetierHost.Main..ctor () [0x002ac] in <63c553364181423faf81fbf20d6b440d>:0
at (wrapper remoting-invoke-with-check) RepetierHost.Main..ctor()
at RepetierHost.Program.Main (System.String[] args) [0x00015] in <63c553364181423faf81fbf20d6b440d>:0

My username is a member of the tty dialout group so that doesn't appear to be the problem.

The major issue is that I am trying to get access to the slicer g-code files, but they are being saved under root which is complicating access.

Repetier

Sounds like there is some bad setting in your users registry while root is using own registry with different settings. They are atore in home/.mono/ Not sure if Software/repetier or directly but somewhere there. Rename the repetier folder so it thinks it's a new installation and it should start. Then configure again or try finding the offending setting in repetier folder.

deleted_user_15009

Do you mean rename~/.mono/registry/CurrentUser/software/repetier? Do I just rename it repetier?

deleted_user_15009

I just did this in ~/.mono/registry/CurrentUser/software

$mv repetier repetier2

$mv repetier2 repetier

I then tried to run $repetierHost without sudo, got the same errors.

Repetier

> Do you mean rename~/.mono/registry/CurrentUser/software/repetier? Do I just rename it repetier?

yes that folder,

$mv repetier repetier2

$mv repetier2 repetier

second command undoes first so you get error back. So just rename it to repetier2 and starting host should create a new repetier folder.

deleted_user_15009

OK, I see. I renamed it to repetier2 and started using repetierHost, starts and runs configuration queries for language, but a lot of the text shown is gibberish. Setting language and hitting OK starts RepetierHost, but the screen freezes and I can't do anything with it. It seems to be messing with screen graphics as it shows bits of my desktop too. The window title is Repetier-Host V2.2.4-tablet amf if that matters. I seem to get a hanging mono process that I have to kill from the command line, the window won't respond to clicking close.

I get the following error in the console, but I got that when I was running under sudo:

libpng warning: iCCP: known incorrect sRGB profile

EDIT: Restarting with repetierHost in console seems to work on the second attempt. I am not sure why the initial setup launch was all screwed up, but it seems OK now.