Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X
Hello,
during start of Codebeamer on Oracle Linux 8 we receive following warnings:
# /codebeamer/cb2210_sp7/bin/startup
/codebeamer/cb2210_sp7/bin/startup: line 80: test: too many arguments
/codebeamer/cb2210_sp7/bin/startup: line 86: warning: setlocale: LC_CTYPE: cannot change locale (en_US.utf8
en_US.utf8@ampm): No such file or directory
/codebeamer/cb2210_sp7/bin/startup: line 87: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8
en_US.utf8@ampm)
/codebeamer/cb2210_sp7/bin/startup: line 89: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8
en_US.utf8@ampm)
Running Codebeamer in background mode...
Command resut of # locale -a | grep -i 'en_US.UTF.*8'
en_US.utf8
en_US.utf8@ampm
Command locale shows:
# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
environment setting shows:
# cat /etc/environment
LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8
Seems en_US.UTF-8 is applied so wondering why get this warning.
Is this a problem or we should ignore?
thank you
Solved! Go to Solution.
Hi @MM_10991077 , after a quick research based on the errors I could see that this is likely a bug fixed on version 2.1.0.0 or any major:
Hope it helps
Hi @MM_10991077,
Thank you for your question!
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.
Best regards,
Hi @MM_10991077 , after a quick research based on the errors I could see that this is likely a bug fixed on version 2.1.0.0 or any major:
Hope it helps
Hello Alfonso,
thank you for your feedback.
Michal.