Is there some secret way to reset rocky 9 back to “just installed”
Did a idiot thing by running Install_burn_headless but I forgot that it has adisplay dongle and now burn wont render anymore and nomachine is freaking out and everything is broken.
It comes with a warning that i skipped over so now reinstall time (boo)
sudo /usr/local/bin/rmsoft
(let me look for the headless option)
the headless option is -g
so:
sudo /usr/local/bin/rmsoft -g
then reinstall the DKU
then reinstall flame
then reinstall your remote control software.
this is about 12 - 20 minutes.
you could even try:
sudo /usr/local/bin/rmsoft -fag
or
sudo /usr/local/bin/rmsoft -fagcv
Usage: rmsoft [option]
Options:
-h, --help show this help message and exit
-a, --all Remove all Autodesk software
-r RESUMES, --resumes=RESUMES
Remove Autodesk software associated with either the
resume file or the regexp string specified
-k KEEP, --keep=KEEP Remove All Autodesk software except the one associated
with either the resume file or the regexp string
specified
-f, --delete-folders Remove all autodesk FOLDER
-c, --no-confirm No confirmation
-g, --no-gui trigger interactive shell mode
-v, --verbose verbose mode
yea… tried that, down the rabbit hole, i uninstalled it all, recreated a new xorg, nomachine now just shows me “oh no! something something” broke, i did a bunch of random stuff now with xorg, reinstalling nvidia drivers, restarting gdm, but its just not working at all… i think install_headless really does some crazy damage
yea there was more weird configs with virtualGL, removing it using the nomachine app actually worked!
i am so close now the only thing I still get is
Users reported that: When launching Burn jobs to a Burn node that has no desktop session started, the render fails, showing the error:
Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
so its not technically headless, as it does have a display connected (dummy hdmi dongle) if I login to nomachine i get echo $DISPLAY = 1 and my flame config also has that, so that works… just BURN wants to not start
I think I am giving up and reinstalling the system tomorrow, man this is so weird, everything else runs, houdini e.t.c
i really dont know how this is supposed to work with a non headless workstation thats used for both burn as well as regular remote sessions. I dont even want to run flame interactive but other things.
i can get it to launch a session as display:0 but that doesnt seem to solve burns issue either, I guess burn runs as root? should I just auto-login root as tty2 on display0?
I don’t know about NoMachine, but when in Teradici mode, Burn does not run. But when using NiceDCV, yes, Burn works. So I suggest you test that, and make sure to use the latest 2024 version of DCV. I tested a pre-release fix this morning, not sure when it will make it to the general public.