Winetricks not opening with Lutris runtime enabled

Support
1

Hi folks!

Well, easy to describe: When the Lutris runtime is enabled, I’m not able to open winetricks (via right-clicking the game). With Lutris runtime diabled, it works.

This is the output, when I try to open winetricks, while I started Lutris via terminal:

$ lutris
INFO     2017-10-07 18:31:42,406 [lutriswindow]:Connectellwut

(lutris:32758): Gtk-WARNING **: Allocating size to GtkToolItem 0x564f20cdb380 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
Using winetricks 20170517-next - sha256sum: 06062b1c8e561fed5223c09cd3031252e02c313d3b8b89bef213a771d691f3d2 with wine-2.15 (Staging) and WINEARCH=win32
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
------------------------------------------------------
You are running winetricks-20170517-next, latest upstream is winetricks-20170823!
------------------------------------------------------
------------------------------------------------------
You should update using your distribution's package manager, --self-update, or manually.
------------------------------------------------------
zenity: /home/cedric/.local/share/lutris/runtime/steam/amd64/lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /usr/lib/libatk-bridge-2.0.so.0)
zenity: /home/cedric/.local/share/lutris/runtime/steam/amd64/lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /usr/lib/libatspi.so.0.0.1)
zenity: symbol lookup error: /usr/lib/libgstvideo-1.0.so.0: undefined symbol: orc_program_new_from_static_bytecode

Also my desktop info:

$ cat /tmp/lutris-desktop-info.txt 
Desktop Info for Lutris

Environment variables:
DESKTOP_SESSION=i3
GDMSESSION=i3
SHELL=/bin/bash

Distribution:
LSB Version:	1.4
Distributor ID:	Arch
Description:	Arch Linux
Release:	rolling
Codename:	n/a
Linux trollwut 4.13.4-1-ARCH #1 SMP PREEMPT Thu Sep 28 08:39:52 CEST 2017 x86_64 GNU/Linux

Running desktop processes:
56 kdevtmpfs
841 gnome-keyring-d
885 indicator-kdeco
936 kdeconnectd
1039 gnome-keyring-d

OpenGL info:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 387.12
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.0 NVIDIA 387.12
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 387.12
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

RAM info:
              total        used        free      shared  buff/cache   available
Mem:            31G         16G        673M        1.3G         14G         13G
Swap:          2.0G          0B        2.0G

CPU info:
model name	: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz

Wine info:
Wine installed system wide: /usr/bin/wine
Version: wine-2.18 (Staging)

Is this a known problem and is there a fix for it?

2

The biggest question is, what does the variable do when it’s active.

3

Can’t follow what you mean?

This is the console log with the Lutris runtime DISABLED, where the winetricks actually works:

Using winetricks 20170517-next - sha256sum: 06062b1c8e561fed5223c09cd3031252e02c313d3b8b89bef213a771d691f3d2 with wine-2.18 (Staging) and WINEARCH=win32
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
------------------------------------------------------
You are running winetricks-20170517-next, latest upstream is winetricks-20170823!
------------------------------------------------------
------------------------------------------------------
You should update using your distribution's package manager, --self-update, or manually.
------------------------------------------------------
zenity: /home/cedric/.local/share/lutris/runtime/steam/amd64/lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /usr/lib/libatk-bridge-2.0.so.0)
zenity: /home/cedric/.local/share/lutris/runtime/steam/amd64/lib/x86_64-linux-gnu/libdbus-1.so.3: no version information available (required by /usr/lib/libatspi.so.0.0.1)
zenity: symbol lookup error: /usr/lib/libgstvideo-1.0.so.0: undefined symbol: orc_program_new_from_static_bytecode
Using winetricks 20170517-next - sha256sum: 06062b1c8e561fed5223c09cd3031252e02c313d3b8b89bef213a771d691f3d2 with wine-2.18 (Staging) and WINEARCH=win32
------------------------------------------------------
You are running winetricks-20170517-next, latest upstream is winetricks-20170823!
------------------------------------------------------
------------------------------------------------------
You should update using your distribution's package manager, --self-update, or manually.
------------------------------------------------------
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
4

The variable LUTRIS_RUNTIME when it’s set to 1 (on) it obviously does something different that prohibits the winetricks to run. My question is what’s the behind reason to have the variable set to 1 on default. The console printout does not tell what the problem is really.

The only thing I can get from that is that winetricks-script itself does it’s regular error, in other words… somewhere along the line the lutris variable interrupt/crashes/prohibits winescript to run but we as end-users cannot know what. So the question goes to the Lutris developers to answer.

Note: I tried to tackle this problem myself but the only answer I got was to disable the variable (set it to 0). Not by the developers… I think.

1 Like