ASCII Logo is broken when running with --server --terminal CLI option

[AFCMS]

Minetest version

Minetest 5.7.0-dev-1f0d042-dirty (Linux)
Using Irrlicht 1.9.0mt10
Using LuaJIT 2.1.0-beta3
BUILD_TYPE=Release
RUN_IN_PLACE=1
USE_CURL=1
USE_GETTEXT=0
USE_SOUND=1
STATIC_SHAREDIR="."

OS / Hardware

Operating system: Ubuntu 22.04
CPU: Intel Core i3

Summary

Steps to reproduce

Run minetest server from CLI with the --terminal option. Wait until the server is fully started. See that the logo is broken.

[hlqkj]

I can confirm this happens on Ubuntu 22.04 LTS.

[Zughy]

Cannot reproduce on Pop!_OS, i7, 5.8.0-dev

[AFCMS]

Could this be related to the terminal software used? I use the default GNOME one.

[Desour]

Can't reproduce either, using bash and gnome-terminal.
Edit: Oops, haven't read reproduction steps correctly.

You could try piping the stdout and stderr into a file and upload it here. And also try cat <file>.

[AFCMS]

Tested again with Fedora 38 and same problem.

2023-05-15.22-00-44.mp4

I also get the problem with the Kitty terminal emulator.

Tested with Bash, too.

[Zughy]

@AFCMS only with --server or in general?

[Desour]

@AFCMS only with --server or in general?

Run minetest server

=> With --server.

Can reproduce.

[AFCMS]

I was running with --server, but with minetestserver I get the same issue (just tested with latest master).

[AFCMS]

[Zughy]

What I meant was, does the ASCII art explode even if you run it as a normal client?

[AFCMS]

If I run the client the ASCII are is fine.

If I add just the --terminal flag there is no terminal (I think the option is just ignored for non-servers) and the ASCII art is also fine.

[mrGoodWolf]

it happens mac too with version
Minetest 5.7.0 (OSX)
Using Irrlicht 1.9.0mt10
Using LuaJIT 2.1.0-beta3
BUILD_TYPE=Release
RUN_IN_PLACE=0
USE_CURL=1
USE_GETTEXT=1
USE_SOUND=1
STATIC_SHAREDIR="minetest.app/Contents/Resources"
STATIC_LOCALEDIR="minetest.app/Contents/Resources/locale"

2023-09-24.09-02-25.mov

[srifqi]

I can not reproduce this issue with Minetest 5.7.0 (as well as the recent master branch) on Windows 10 (10.0.19045) both in Command Prompt and in Windows PowerShell.

I also can not reproduce it with the recent master branch on Ubuntu 22.04.3 LTS (running on VirtualBox).

         __.               __.                 __.
  _____ |__| ____   _____ /  |_  _____  _____ /  |_
 /     \|  |/    \ /  __ \    _\/  __ \/   __>    _\
|  Y Y  \  |   |  \   ___/|  | |   ___/\___  \|  |
|__|_|  /  |___|  /\______>  |  \______>_____/|  |
      \/ \/     \/         \/                  \/

[sfan5]

AFAIK Windows doesn't support the ncurses --terminal so that's to be expected.

[mrGoodWolf]

Btw it does it on debian

[rubenwardy]

I suggest removing the ASCII logo or just closing this issue. This isn't worth spending any time fixing

[Zughy]

For how nice it can be, I agree with the removal - considering the few issues we've seen

[AFCMS]

I suggest removing the ASCII logo or just closing this issue. This isn't worth spending any time fixing

Only when using with --terminal ? Because I really like the ASCII logo :(

[hlqkj]

As long as the cause of the broken ASCII logo doesn't break anything else in the output when using --terminal, I guess it can just be removed when using that switch.