https://bugs.winehq.org/show_bug.cgi?id=49923
--- Comment #2 from ttallink@googlemail.com --- (In reply to Jacek Caban from comment #1)
Why do you need wineconsole in the first place? Before removing the backend, default Wine console handling was extended to support most of curses backend functionality (without relying on curses library). Ideally, you should be able to change your systemd service to run your application directly by wine instead of through wineconsole. Please give it a try.
The whole purpose of wineconsole is to run applications that don't have a GUI.. I tried the main wine binary but it requires a running X.Org server as well as a display, even if the binary you are running does not need either of those.
I tried working around the issue, but on a server where I only have terminal / ssh sessions, it's simply impossible - wineconsole with the curses backend works perfectly fine with a very small memory footprint (< 10mb's) and there is no replacement for it (except for maybe rewriting my application but it relies on Windows-exclusive header files / structures and I don't feel like copying them all to convert my app into a native binary).
So, my request remains: Please re-add the curses backend, without it, I can no longer spawn wineconsole as a service to host the backend of my software - many other people doing the same will also be affected while there is no need to remove the curses backend in the first place, it was working without any problems.
Best Regards, William