You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running it on Debian 12 KDE. Here are the errors when trying to use it with kdialog, which it automatically chooses:
$ WINEPREFIX=/home/xiaolong/PlayOnLinux\'s\ virtual\ drives/lf2_wine_prefix_32bit ./winetricks
Executing cd.
Using winetricks 20250102-next - sha256sum: 93280026a9226cdd4b24c93efe9920f883418922f6e2a4c7e610fa054f0bfea1 with wine-8.0 (Debian 8.0~repack-4) and WINEARCH=win32
QSocketNotifier: Can only be used with threads started with QThread
winetricks GUI enabled, using kdialog 22.12.3
QSocketNotifier: Can only be used with threads started with QThread
x: 100 y: 100 w: 600 h: 400
QSocketNotifier: Can only be used with threads started with QThread
x: 100 y: 100 w: 600 h: 400
/tmp/winetricks.eqw2oAci/w.xiaolong.27686/kdialog.sh: 1: Syntax error: "(" unexpected
QSocketNotifier: Can only be used with threads started with QThread
x: 100 y: 100 w: 600 h: 400
The error /tmp/winetricks.eqw2oAci/w.xiaolong.27686/kdialog.sh: 1: Syntax error: "(" unexpected happens, when I try to Install a Windows DLL or component:
Clicking "OK" there causes the error and I get back to the same dialog again.
So I searched around the issues in this repo and found, that one can change the GUI used to zenity. I tried that, but also ran into a syntax error:
$ WINEPREFIX=/home/xiaolong/PlayOnLinux\'s\ virtual\ drives/lf2_wine_prefix_32bit ./winetricks --gui=zenity
Executing cd.
winetricks GUI enabled, using zenity 3.44.0
Using winetricks 20250102-next - sha256sum: 93280026a9226cdd4b24c93efe9920f883418922f6e2a4c7e610fa054f0bfea1 with wine-8.0 (Debian 8.0~repack-4) and WINEARCH=win32
Executing mkdir -p /home/xiaolong/.cache/winetricks
/tmp/winetricks.RmmU7oXx/w.xiaolong.32485/zenity.sh: 1: Syntax error: Unterminated quoted string
This error happens already when I Select the default wineprefix and click "OK" there:
So both currently seem to be broken, and as a consequence I seem unable to use the current latest winetricks script. I am not sure things would be any different, if I installed using the make command, but I would rather like to not install into system directories, if I see a breakage in it and later might have to tediously clean up again.
Is there any simple fix? Maybe I am doing something wrong?
The text was updated successfully, but these errors were encountered:
ZelphirKaltstahl
changed the title
Current latest stable bugs, syntax errors
Current latest stable bugs, syntax errors, kdialog and zenity
Jan 16, 2025
No need to install Winetricks since it is a plain shell script, so nothing wrong there (though might want to make sure you are running the version of Winetricks you think you are running (for example, not a system-installed one when want to run one you just downloaded)).
So far I can't reproduce here with kdialog-24.12.1 at least, but can try some more later.
It seems that the current latest stable script, that I downloaded from https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks today (2025-01-16) has syntax errors.
I am running it on Debian 12 KDE. Here are the errors when trying to use it with
kdialog
, which it automatically chooses:The error
/tmp/winetricks.eqw2oAci/w.xiaolong.27686/kdialog.sh: 1: Syntax error: "(" unexpected
happens, when I try toInstall a Windows DLL or component
:Clicking "OK" there causes the error and I get back to the same dialog again.
So I searched around the issues in this repo and found, that one can change the GUI used to zenity. I tried that, but also ran into a syntax error:
This error happens already when I
Select the default wineprefix
and click "OK" there:So both currently seem to be broken, and as a consequence I seem unable to use the current latest
winetricks
script. I am not sure things would be any different, if I installed using themake
command, but I would rather like to not install into system directories, if I see a breakage in it and later might have to tediously clean up again.Is there any simple fix? Maybe I am doing something wrong?
The text was updated successfully, but these errors were encountered: