wineconsole --backend broken?

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Post Reply
sebunger
Level 1
Level 1
Posts: 5
Joined: Fri Aug 16, 2019 7:07 pm

wineconsole --backend broken?

Post by sebunger » Tue Oct 06, 2020 7:21 pm

Hi,

I'm not entirely sure when this started, but I just noticed that wineconsole --backend=curses appears to be broken. To be precise, it would appear that the option has been removed?!?!

I get the following output:

Code: Select all

wineconsole: Unrecognised command line option

Usage:
  wineconsole [options] <command>

Options:
  <command>                The Wine program to launch in the console.

Example:
  wineconsole cmd
Starts the Wine command prompt in a Wine console.
What's more, the command exits with exit code 0 indicating success when it clearly was not successful. This the main reason why I'm not sure exactly when this started failing.

Of course, without the --backend option wineconsole fails because it attempts to open a display (which it can't because it is running headless).

Any ideas? Does the above suffice as a bug-report or can someone point me to the right please to raise the issue?

jkfloris
Level 8
Level 8
Posts: 1158
Joined: Thu Aug 14, 2014 10:10 am

Re: wineconsole --backend broken?

Post by jkfloris » Wed Oct 07, 2020 4:08 am

In version 5.18 the 'curses' option has been removed.

https://www.winehq.org/announce/5.18
https://source.winehq.org/git/wine.git/ ... d71ff3a5e0
The Wine development release 5.18 is now available.

What's new in this release (see below for details):
- Vulkan shader compilation using the new vkd3d-shader library.
- USER32 library converted to PE.
- Console no longer requires the curses library.
- Support for display modes with various orientations.
- A number of syntax fixes in the WIDL compiler.
- Non-recursive makefiles.
- Various bug fixes.

Post Reply