*finds out the windows X2GO client uses NoMachine under the hood*
@dammkewl if you dig deep enough you'll probably keep uncovering new geological layers, i think it's really VNC over XPRA over NoMachine over remote desktop over a remote X connection
@orionwl At this point I wouldn't be surprised.
With everything I try, I end up in an error situation that seemingly does not conform to what most stumble into. And I cannot for the life of me figure out whether it's having picked Fedora, picking worng package versions, configuring them incorrectly, or something else.
Right now trying the X2GO client established some kind of connection, but the client shows an error dialog "drkonqi closed unexpectedly" because of some segmentation fault.
@dammkewl ah yes the old IT yak-shaving fun, once you fix one error message, you'll move to the next one, and you can spend all day like that :(
or you could simply switch to all terminal applications, then good ol' putty will do ! :)
@orionwl I'd really like that to be an option for my case, but alas: I work a full time job as a java developer.
I need a graphical IDE that allows me to have visual overviews of class hierarchies, automated refactoring, debugging multiple threads simultaneously, etc. And our product is accessed by web browser so yeah, no choice there.
Also, I refuse to use VIM, but that's mostly a personal dispute I started with someone from the IT ops dept. that I can't back out of becuase office lulz. #nano
@dammkewl we… create our own hell
though in this case, instead of running the editor remotely, would it be possible to use a remote filesystem and run the editor locally and edit over that?
@orionwl It would be a practical solution, but that would also make me more liable in the case of IP theft due to having accessed our codebase from my personal home machine directly.
Aside from legalities, I don't just need this to work for me, but as a general solution for the department I work in so that colleagues who also eventually switch to Linux can go through a predetermined process to setup the working environment quickly and reliably.
But so far, "reliably" has yet to come in sight.
@orionwl Well, I found the root cause of all problems really: SELinux.
Should've seen that coming a mile away...
@dammkewl SELinux, arghhh *that* NSA conspiracy got to you again 🤦♀️
@orionwl There was also the case of "yeah xrdp by default starts xterm even though xterm is not a dependency" so installing xrdp really doesn't do anything from the get-go.
After finding out "startkde" was the startup command I needed for my specific case (which does a lot of setting stuff ready apparently), and found the spot where xterm was usually started (a libexec script called startwm.sh) I replaced one with the other et voilà: windows remote desktop connection works!
@orionwl Wait, am I anticipating this correctly: if I ever update packages like xrdp in my case, will my libexec scripts be overridden?
@dammkewl depends on the distribution; on debian, for example it depends on whether the file is classified as configuration file
configuration files will be preserved on package upgrades, except if they have been changed in the package, in which case you'll get a prompt whether you want to keep your version, or overwrite it
for non-configuration files I honestly don't know, they might just be blasted away
@orionwl Thanks for the help!