Replies: 5 comments 6 replies
-
There have been a number of these issues in the past but I am unsure what causes it. However, the vast majority of servers don't have this issue. So it is something specific to your distro or install of LinuxGSM. Could you provide the output of ./vhserver post-details. It might provide more info that could be useful |
Beta Was this translation helpful? Give feedback.
-
Same thing is happening to me. No special characters anywhere. Discord suggested it may be tmux related so I tried 3 different version (2.8, 3.0b, 3.2) without any changes to outcome. |
Beta Was this translation helpful? Give feedback.
-
Looks like it is an issue with the call to tmux in command_start.sh. Something is not-quite-right with the quoting. If I remove all double quotes from the line it works fine. It was attempting to run |
Beta Was this translation helpful? Give feedback.
-
I was stumped on this one for a few hours. This is what worked for me, in the end, I removed the double quotes from the command on command_start.sh#L75 tmux new-session -d -x ${sessionwidth} -y ${sessionheight} -s ${sessionname} ${preexecutable} ${executable} ${startparameters} 2> "${lgsmlogdir}/.${selfname}-tmux-error.tmp" Borrowed the idea from @nickmayer above. Running Valheim, on |
Beta Was this translation helpful? Give feedback.
-
I opened a new issue for this: #3397 |
Beta Was this translation helpful? Give feedback.
-
The server only starts in debug mode and seems works fine therein. But when I try to run
./vhserver start
I get this:I'm running Ubuntu 20.04.2 on a ACEPC mini PC that's a couple years old.
I googled a bit and thought it might be an issue with tmux, but I'm able to start and exit a tmux session without issue.
Beta Was this translation helpful? Give feedback.
All reactions