When I try to install the winetricks script from the q4wine package, I get the error 'Warning: The interactive shell could not be found.'

Question

When I try to install the winetricks script from the q4wine package, I get the error 'Warning: The interactive shell could not be found.'

saber716rus opened this issue 3 years ago · comments

The program is installed from aur. https://aur.archlinux.org/packages/q4wine
The problem is that when I try to install winetricks from the program or install lib, so from the program, I come across such an error. "Warning: The interactive shell could not be found."
Operating System: Manjaro Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.10.42-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 6 × AMD FX(tm)-6300 Six-Core Processor
Memory: 7.7 ГиБ of RAM
Graphics Processor: GeForce GT 630/PCIe/SSE2

Oleksii S. Malakhov · Answer 1 · Thu Jul 08 2021 00:54:34 GMT+0800 (China Standard Time)

hi @saber716rus

You may need to check console binary setting at q4wine settings : General -> Utils

More likely this could be b/c missing or wrong binary path

Nikolay · Answer 2 · Thu Jul 08 2021 19:40:43 GMT+0800 (China Standard Time)

As you can see, there is a working terminal and everything is correct at the address. The system is installed on ssd and mounted f2fs.

MR Chowdhury · Answer 3 · Fri Jul 09 2021 02:28:26 GMT+0800 (China Standard Time)

Hi,
Sorry for bumping this thread.
I'm having the exact same issues on Manjaro Linux.

System info
Operating System: Manjaro Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.10.42-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics
Memory: 5.8 GiB of RAM
Graphics Processor: AMD Radeon™ Vega 11 Graphics

Oleksii S. Malakhov · Answer 4 · Mon Jul 12 2021 04:30:33 GMT+0800 (China Standard Time)

hm....
interesting... i can't reproduce this on my system.
can you build q4wine with DEBUG option enabled and add console output?

on my system it runs winetricks as follows:

[DD] winetricks args:  ("--noclose", "-e", "/bin/sh", "-c", "env WINEPREFIX='/home/brezerk/.wine' WINE='/usr/bin/wine' WINELOADER='/usr/bin/wine' WINESERVER='/usr/bin/wineserver' /usr/bin/sh -c \"/home/brezerk/.config/q4wine/winetricks --no-isolate 7zip\" ; echo '== Press Enter to Close =='; read n")

Oleksii S. Malakhov · Answer 5 · Mon Jul 12 2021 04:36:35 GMT+0800 (China Standard Time)

seems like in your case the issue with '/bin/sh' part. What is the value for sh setting in General -> System?

Nikolay · Answer 6 · Mon Jul 12 2021 05:12:13 GMT+0800 (China Standard Time)

seems like in your case the issue with '/bin/sh' part. What is the value for sh setting in General -> System?

shell zsh

Nikolay · Answer 7 · Mon Jul 12 2021 05:15:11 GMT+0800 (China Standard Time)

[nikolanp@kolyab-tobefilledbyoem ~]$ q4wine [ii] Loading translation: "q4wine_ru_RU" qt.svg: <input>:7064: Could not resolve property: #radialGradient3709 qt.svg: <input>:647:190: Could not resolve property: #linearGradient5167 qt.svg: <input>:647:190: Could not resolve property: #linearGradient5167 qt.svg: <input>:6354: Could not resolve property: #linearGradient5167 qt.svg: <input>:6354: Could not resolve property: #linearGradient5167 qt.svg: <input>:5672: Could not resolve property: #radialGradient3709 qt.svg: <input>:647:190: Could not resolve property: #linearGradient5167 qt.svg: <input>:5672: Could not resolve property: #radialGradient3709 qt.svg: <input>:7064: Could not resolve property: #radialGradient3709 qt.svg: <input>:684: Could not resolve property: #pattern5614 qt.svg: <input>:684: Could not resolve property: #pattern5626 qt.svg: <input>:684: Could not resolve property: #pattern5614 qt.svg: <input>:684: Could not resolve property: #pattern5626 qt.svg: <input>:679: Could not resolve property: #pattern5614 qt.svg: <input>:679: Could not resolve property: #pattern5626 qt.svg: <input>:7092: Could not resolve property: #linearGradient3592 qt.svg: <input>:7092: Could not resolve property: #linearGradient7999 qt.svg: <input>:7092: Could not resolve property: #radialGradient2943 qt.svg: <input>:6850: Could not resolve property: #radialGradient2943 qt.svg: <input>:6354: Could not resolve property: #linearGradient5167 qt.svg: <input>:6354: Could not resolve property: #linearGradient5167 qt.svg: <input>:7064: Could not resolve property: #radialGradient3709 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 qt.svg: <input>:4290: Could not resolve property: #pattern5614 qt.svg: <input>:4290: Could not resolve property: #pattern5626 [nikolanp@kolyab-tobefilledbyoem ~]$

Oleksii S. Malakhov · Answer 8 · Tue Jul 13 2021 02:19:10 GMT+0800 (China Standard Time)

shell zsh

@saber716rus ic. can you set it to sh? you may find sh binary via which sh

Nikolay · Answer 9 · Mon Jul 19 2021 19:06:50 GMT+0800 (China Standard Time)

The problem has disappeared, but there is a request, make sure that after executing the winetricks scripts, the shell window should be auto-closed.

Oleksii S. Malakhov · Answer 10 · Mon Jul 26 2021 17:16:49 GMT+0800 (China Standard Time)

I'll need to take a look why it does not work with zsh tho. Are you using any special .zshrc?

As for > make sure that after executing the winetricks scripts, the shell window should be auto-closed.

You need to remove --noclose from q4wine console settings.