Bug#807045: winetricks output: wineserver not found!

[Xavier Ortiz]

Package: winetricks
Version: 0.0+20141009+svn1208-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
typing "winetricks" in console
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
console output :

------------------------------------------------------
wineserver not found!
------------------------------------------------------


* What outcome did you expect instead?

winetricks to run

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (400, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages winetricks depends on:
ii cabextract 1.6-1
ii p7zip 9.20.1~dfsg.1-4.2
ii unzip 6.0-20
ii wget 1.17-1
ii wine 1.8~rc2-1
ii wine64 1.8~rc2-1
ii zip 3.0-11

Versions of packages winetricks recommends:
ii gksu 2.0.2-9
ii sudo 1.8.12-1
ii xdg-utils 1.1.1-1
ii zenity 3.18.1.1-1

Versions of packages winetricks suggests:
ii libwine 1.8~rc2-1

-- no debconf information

[Jens Reyer]

Hi,

do you have wine32 installed? If not please execute:
sudo dpkg --add-architecture i386 &&
sudo apt update &&
sudo apt install wine32

Greets
jre

[Jens Reyer]

[Sorry, sent the mail to early]
The first two lines are unnecessary on your system.

Now, if you have wine32 installed and it still doesn't work, please try
the following (all in the same terminal):
export WINEARCH=win32
export WINE=/usr/bin/wine
export WINESERVER=/usr/lib/i386-linux-gnu/wine/wineserver
winetricks ...

Please tell us your findings

Greets
jre

[Joseph Bisch]

Hi,

It looks like libwine or libwine-development should be a dependency of
winetricks, since winetricks doesn't appear to run without wineserver,
and wineserver is part of libwine. See this page for the package info:
[0].

It looks like you can trace the dependency chain from wine to libwine
on Wheezy and earlier releases, but starting with Jessie, libwine is
no longer part of the recursive dependencies of wine.

For now, installing libwine should fix the issue.

[0] - https://packages.debian.org/search?suite=stretch&arch=any&mode=path&searchon=contents&keywords=wineserver

Cheers,
Joseph

[Jens Reyer]

On 12/09/2015 03:17 PM, Joseph Bisch wrote:
> Hi,
>
> It looks like libwine or libwine-development should be a dependency of
> winetricks, since winetricks doesn't appear to run without wineserver,
> and wineserver is part of libwine. See this page for the package info:
> [0].
>
> It looks like you can trace the dependency chain from wine to libwine
> on Wheezy and earlier releases, but starting with Jessie, libwine is
> no longer part of the recursive dependencies of wine.

No, not exactly. Even in Jessie/Stretch libwine is always installed if
you install wine, because:
- wine depends on wine32 OR wine64
- wine32 depends on libwine:i386 [1]
- wine64 depends on libwine:amd64

So you'll always end up with a libwine (or several), the question is
only from which architectures they are.
What I suspected is that only wine64 and libwine:amd64 are installed,
and winetricks can't cope with that. And I verified that - indeed this
results in the mentioned problem.

So you either install wine32 additionally to the already installed
wine64 (recommended), or you do the following (with only wine64 installed:
export WINESERVER=/usr/lib/x86_64-linux-gnu/wine/wineserver
export WINEPREFIX="$HOME/.wine64"
winetricks

The same/similar is true for the -development packages.

I'd suggest to maybe add the wine64-only workaround to the README and
change the depends to the following:

wine32|wine32-development|wine64|wine64-development

This removes unnecessary duplicates and expresses that 32-bit is
preferred to 64-bit and stable to -development.

However IMO it is NOT feasible to only depend on 32-bit packages,
because they are not available in every setup.

Greets
jre


[1]: simplifying with "i386" and "amd64" here, but this matches exactly
the system the bug was reported from: e.g. wine32 is available on /some/
32-bit architectures and depends on libwine of the same architecture.