Error 256 lutris

I can confirm it’s not just Arial fonts. I removed that section from the Uplay script and instead it crashed with code 256 on first item that replaced it.

Script in question;

files:
- uplay: https://ubistatic3-a.akamaihd.net/orbit/launcher_installer/UbisoftConnectInstaller.exe
game:
  exe: drive_c/Program Files (x86)/Ubisoft/Ubisoft Game Launcher/UbisoftConnect.exe
  prefix: $GAMEDIR
installer:
- task:
    name: create_prefix
    prefix: $GAMEDIR
- task:
    app: d3dcompiler_43
    description: Installing D3D compiler 43
    name: winetricks
    prefix: $GAMEDIR
- task:
    app: d3dcompiler_47
    description: Installing D3D compiler 47
    name: winetricks
    prefix: $GAMEDIR
- task:
    app: d3dx9
    description: Installing D3D9
    name: winetricks
    prefix: $GAMEDIR
- write_file:
    content: "overlay:n  enabled: falsen  forceunhookgame: falsen  fps_enabled:
       falsen  warning_enabled: falsenuser:n  closebehavior: CloseBehavior_Close"
    file: $GAMEDIR/drive_c/users/$USER/Local Settings/Application Data/Ubisoft Game
      Launcher/settings.yml
- task:
    args: /S
    executable: uplay
    name: wineexec
    prefix: $GAMEDIR

Looks like a problem deeper within Lutris; Is it a change in the scripting language that’s invalidated older scripts or to do with the first understanding of this issue?

Console log;

username@machinename:~$ lutris -i '/home/username/Downloads/ubisoft-connect-latest-skip-arial.json'
2022-08-17 18:20:28,270: Starting Lutris 0.5.10.1
2022-08-17 18:20:28,305: No folder at /home/username/.local/share/lutris/runners/retroarch/
2022-08-17 18:20:28,334: Using NVIDIA drivers 515.48.07 for x86_64
2022-08-17 18:20:28,334: GPU: NVIDIA GeForce GTX 1080 Ti
2022-08-17 18:20:28,334: GPU: 10DE:1B06 1043:85E4 (nvidia drivers)
2022-08-17 18:20:30,153: Startup complete
2022-08-17 18:20:33,382: Getting runner information for wine
2022-08-17 18:20:45,743: Download completed
2022-08-17 18:20:45,744: All files available
2022-08-17 18:20:45,744: All files are available, continuing install
2022-08-17 18:20:45,754: Creating a win64 prefix in /home/username/games/lutris/ubisoft-connect
2022-08-17 18:20:47,120: win64 Prefix created in /home/username/games/lutris/ubisoft-connect
2022-08-17 18:20:47,924: The game doesn't have an executable
Started initial process 19603 from /home/username/.local/share/lutris/runtime/winetricks/winetricks --unattended d3dcompiler_43
Start monitoring process.
Executing mkdir -p /home/username/games/lutris
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
------------------------------------------------------
WINEPREFIX INFO:
Drive C: total 28
drwxrwxr-x  7 username username 4096 Aug 16 22:56 .
drwxrwxr-x  4 username username 4096 Aug 16 23:45 ..
drwxrwxr-x  7 username username 4096 Aug 16 23:00 ProgramData
drwxrwxr-x  6 username username 4096 Aug 16 22:22 Program Files
drwxrwxr-x  7 username username 4096 Aug 16 23:22 Program Files (x86)
drwxrwxr-x  4 username username 4096 Aug 16 22:22 users
drwxrwxr-x 22 username username 4096 Aug 16 22:52 windows

Registry info:
/home/username/games/lutris/ubisoft-connect/system.reg:#arch=win64
/home/username/games/lutris/ubisoft-connect/user.reg:#arch=win64
/home/username/games/lutris/ubisoft-connect/userdef.reg:#arch=win64
------------------------------------------------------
------------------------------------------------------
warning: /home/username/.local/share/lutris/runners/wine/lutris-7.2-2-x86_64/bin/wine cmd.exe /c echo '%AppData%' returned empty string, error message "" 
------------------------------------------------------
Monitored process exited.
Initial process has exited (return code: 256)
All processes have quit
Exit with return code 256
2022-08-17 18:20:48,926: Command exited with code 256
None
2022-08-17 18:20:54,090: Cancelling installation of Ubisoft Connect
2022-08-17 18:20:54,973: Shutting down Lutris

Lutris error screenshot

I can’t answer your question directly since I never tried to install games through Lutris directly.

but I do use Lutris (currently v0.5.10.1), with the newest stable Wine from the winehq website, and then I pair it with GloriousEggroll runner for Lutris for the small amount of games I replay (Mafia series and RDR2(with RDR2 I have to set Wine to Windows 10 mode as if you leave Wine in the default of Windows 7 the game won’t start up)).

basically I use Lutris with newest Wine (from https://wiki.winehq.org/Ubuntu ; I use the ‘stable’ one and after that’s done I issue ‘sudo apt install wine-desktop-files’ which gives you the entries in the Mint menu to configure Wine if needed) paired with the GloriousEggroll custom runner for Lutris (i.e. https://github.com/GloriousEggroll/wine … m/releases ; currently you would download «wine-lutris-GE-Proton7-22-x86_64.tar.xz» and extract it to «~/.local/share/lutris/runners/wine/» and then Lutris should automatically use it. if not, you can force it on the games shortcut in Lutris by right clicking it, select Configure > Runner Options and under ‘Wine version’ you can select the Lutris runner from the drop down menu) and then just make a shortcut in Lutris and guide it to the location of the games main EXE file and then play it.

but off the top of my head if you got a game installer you can probably just install the game like usual through Wine (i.e. double click the installer EXE). once installed, then load up Lutris, make a shortcut and guide it to the location of the games EXE file (which will probably be located in this general location… «~/.wine/drive_c/» ) and play it.

NOTE: to make a shortcut in Lutris it’s simple enough… start Lutris, click «+» in the top left corner, then on menu that pops up select ‘Add locally installed game’. then a ‘Add a new game’ window will appear at which point on the ‘Runner’ text to the right of that says ‘Select a runner from the list’, click that, change it to ‘Wine (Runs Windows games)’, then over on the ‘Game options’ tab under ‘Executable’ you guide it to the location of the games main EXE file (by clicking the ‘browse’). you can tweak more if you want to, but that’s the basic idea.

but looking at what you posted… it seems that «lutris-fshack-7.2-x86_64» is not installed by default. but you can install that in particular directly by going to Lutris’s ‘Preferences > Runners’ and then scroll down to the bottom and see where it says ‘Wine’ and to the right of that is two icons you can click, click the one to the right, which should then open a ‘Manage wine versions’ screen at which point you can click ‘install’ to the right of the «lutris-fshack-7.2» text (maybe if you manually install this fshack stuff first and then do your installer, maybe it will work(?)). but honestly, I suspect that GloriousEggroll runner I posted is probably better in general as with that I can run a game or two that normally don’t seem to work.

for the record… you can install certain versions of the GloriousEggroll runner from within Lutris directly if you want as they are listed as ‘lutris-ge etc’ using what I described above in that general ‘lutris-fshack-7.2’ section.

but looking online a bit for that ‘error code 256’ your getting one user suggested recently (about 4 days or so ago)… «Top right hamburger menu > preferences > global options > disable lutris runtime (toggle this to off aka no orange)» and a user replied saying it worked for them for whatever this is worth.

LINUX AND VMWARE STUFF

This Blog is to share our knowledge and expertise on Linux System Administration and VMware Administration

Wednesday, June 5, 2019

Yum failed with Errno 256 No more mirrors to try — Solved

Situation:
Yum is failed with Errno 256, No more mirrors to try.

root@testserver# yum list available | grep erna
https://rhn.test.com/pulp/repos/shared/lce-lcs_6month_rhel7/ccv-lcs_6month_rhel7/content/dist/rhel/server/7/7Server/x86_64/extras/os/repodata/repomd.

xml: [Errno 14] curl#58 — «SSL peer rejected your certificate as expired.»
Trying other mirror.

One of the configured repositories failed (Red Hat Enterprise Linux 7 Server — Extras (RPMs)),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work «fix» this:

1. Contact the upstream for the repository and get them to fix the problem.

yum-config-manager —save —setopt=rhel-7-server-extras-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-extras-rpms: [Errno 256] No more mirrors to try.
https://rhn.test.com/pulp/repos/shared/lce-lcs_6month_rhel7/ccv-lcs_6month_rhel7/content/dist/rhel/server/7/7Server/x86_64/extras/os/repodata/repomd.

xml: [Errno 14] curl#58 — «SSL peer rejected your certificate as expired.»

Solution:
Becasue of corrupted yum cache, getting this error. So refresh the subscription-manager clean the old cache & run the yum command

Источник

Why does yum return error: [Errno 256] No more mirrors to try ?

Environment

• Red Hat Enterprise Linux
• Red Hat Customer Portal
• Red Hat Subscription Management (RHSM)
• Red Hat Satellite

Issue

• yum update fails with the error : [Errno 256] No more mirrors to try

Resolution

Check the network connectivity. If IP based Firewall is being used then whitelist the IPs that are mentioned in Public CIDR Lists for Red Hat (IP Addresses for cdn.redhat.com) for access to the content delivery network (CDN).

Check what files are present under /etc/yum.repos.d directory by:-

If the system is registered with Red Hat Subscription Manager (RHSM) via subscription-manager, rhel-source.repo and redhat.repo are present.

If any local repositories or any other media repositories are present, remove them by:-

• Remove the old yum cache from the system by running the following commands:

• Check if the valid repositories are getting listed by:-

• If the previous solutions does not work, try reenabling each repository one by one with the following:-

Root Cause

• Possible reasons for this issue:
  • Corrupted yum cache.
  • Inaccessibility of a repository URL from the system due to network-related issues.
  • Presence of customized or other media repositories.
  • Outdated whitelist when using IP-based Firewall configuration to access Red Hat’s Content Delivery Network (CDN).

Diagnostic Steps

• yum update fails with any of the below errors:-

• On Satellite Server it fails with this error as per /var/log/messages

• Check the accessibility of the repository URL in the system/network.

• Check the repositories under /etc/yum.repos.d

• Product(s)
• Red Hat Subscription Management
• Red Hat Satellite
• Red Hat Enterprise Linux
• Red Hat Customer Portal

• Component
• yum

• Category
• Troubleshoot

• Tags
• customer_portal
• rhel
• rhn
• rhn_classic
• rhsm
• satellite
• subscription_management
• yum

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Whichever game I try to install on Lutris returns me with the error code 256

Whichever game I try to install on Lutris returns me with the error code 256

Post by sam007msd » Sun Jul 03, 2022 12:57 am

Re: Whichever game I try to install on Lutris returns me with the error code 256

Post by jstich » Sun Jul 03, 2022 3:56 am

Re: Whichever game I try to install on Lutris returns me with the error code 256

Post by ThaCrip » Wed Jul 13, 2022 1:35 am

I can’t answer your question directly since I never tried to install games through Lutris directly.

but I do use Lutris (currently v0.5.10.1), with the newest stable Wine from the winehq website, and then I pair it with GloriousEggroll runner for Lutris for the small amount of games I replay (Mafia series and RDR2(with RDR2 I have to set Wine to Windows 10 mode as if you leave Wine in the default of Windows 7 the game won’t start up)).

basically I use Lutris with newest Wine (from https://wiki.winehq.org/Ubuntu ; I use the ‘stable’ one and after that’s done I issue ‘sudo apt install wine-desktop-files’ which gives you the entries in the Mint menu to configure Wine if needed) paired with the GloriousEggroll custom runner for Lutris (i.e. https://github.com/GloriousEggroll/wine . m/releases ; currently you would download «wine-lutris-GE-Proton7-22-x86_64.tar.xz» and extract it to «

/.local/share/lutris/runners/wine/» and then Lutris should automatically use it. if not, you can force it on the games shortcut in Lutris by right clicking it, select Configure > Runner Options and under ‘Wine version’ you can select the Lutris runner from the drop down menu) and then just make a shortcut in Lutris and guide it to the location of the games main EXE file and then play it.

but off the top of my head if you got a game installer you can probably just install the game like usual through Wine (i.e. double click the installer EXE). once installed, then load up Lutris, make a shortcut and guide it to the location of the games EXE file (which will probably be located in this general location. «

/.wine/drive_c/» ) and play it.

NOTE: to make a shortcut in Lutris it’s simple enough. start Lutris, click «+» in the top left corner, then on menu that pops up select ‘Add locally installed game’. then a ‘Add a new game’ window will appear at which point on the ‘Runner’ text to the right of that says ‘Select a runner from the list’, click that, change it to ‘Wine (Runs Windows games)’, then over on the ‘Game options’ tab under ‘Executable’ you guide it to the location of the games main EXE file (by clicking the ‘browse’). you can tweak more if you want to, but that’s the basic idea.

but looking at what you posted. it seems that «lutris-fshack-7.2-x86_64» is not installed by default. but you can install that in particular directly by going to Lutris’s ‘Preferences > Runners’ and then scroll down to the bottom and see where it says ‘Wine’ and to the right of that is two icons you can click, click the one to the right, which should then open a ‘Manage wine versions’ screen at which point you can click ‘install’ to the right of the «lutris-fshack-7.2» text (maybe if you manually install this fshack stuff first and then do your installer, maybe it will work(?)). but honestly, I suspect that GloriousEggroll runner I posted is probably better in general as with that I can run a game or two that normally don’t seem to work.

for the record. you can install certain versions of the GloriousEggroll runner from within Lutris directly if you want as they are listed as ‘lutris-ge etc’ using what I described above in that general ‘lutris-fshack-7.2’ section.

but looking online a bit for that ‘error code 256’ your getting one user suggested recently (about 4 days or so ago). «Top right hamburger menu > preferences > global options > disable lutris runtime (toggle this to off aka no orange)» and a user replied saying it worked for them for whatever this is worth.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

WoeUSB not working / Exit Code: 256

WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sat Jan 05, 2019 11:04 pm

When I try to add the Windows 10 ISO to my flash drive I get an error of (Exit Code: 256). The USB drive is formatted as NTFS and is unmounted but it won’t install.

Mounting source filesystem.
Error: File «/media/woeusb_source_1546743561_19723/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https://github.com/slacka/WoeUSB/wiki/L . limitation for more info.
Unmounting and removing «/media/woeusb_source_1546743561_19723».
You may now safely detach the target device

Re: WoeUSB not working / Exit Code: 256

Post by MrEen » Sat Jan 05, 2019 11:36 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 1:14 am

this means your flash drive is not large enough to hold the win10 iso. i just formatted my really old 8GB flash drive which i have formatted maybe 1000 times to fat32 and i have no issue making windows usb out of it. what is the full name of your win10 iso called? are you trying to make a bootable iso from an .exe update?

did you format your flash drive with the Usb stick Formatter?

Re: WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sun Jan 06, 2019 3:07 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 3:38 pm

it’s complaining about install.wim which is called install.esd is it larger than 4GB ? mine is 2.6GB

Re: WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sun Jan 06, 2019 4:11 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 4:24 pm

rightclick on the .iso and Open With «Disk Image Mounter» but more than likely your copy of install.esd is larger than 4GB which woeusb can’t handle. is this an official microsoft .iso?

try open gparted, select your flash drive and under devices > create new partition table > msdos > EXIT and format with USB FORMATTER NTFS

not sure if woeusb works with ntfs since it does install grub but fat32 will give you a limit at 4GB

you need to get an OFFICIAL copy of windows 10 or create the usb in other windows os with the Windows USB/DVD Download Tool

Re: WoeUSB not working / Exit Code: 256

Post by Vilis » Mon May 13, 2019 1:15 pm

I have the same identical problem using Cinnamon 18.3, but I went further in analyzing it. I installed the Ubuntu repository for WoeUSB, and ran WoeUSB. My copy of Windows 7 Pro is the official Microsoft OEM compatible version, because I have an OEM MS Win. 7 Pro license sticker on my computer, which the local Microsoft rep guided me by phone to verify — it verified as good. Then the Microsoft rep guided me to create a bootable USB stick on a Windows 7 Pro machine I have, using 100% Microsoft software, and that procedure produced a bootable USB stick using my official MS .iso file of OEM Windows 7 Pro 64bit.
So I have a working copy of a USB stick with official MS Win 7 Pro .iso installed on it, made entirely using Windows software, not Linux, to compare with my WoeUSB. Both copies, my 100% Microsoft copy, and my WoeUSB copy are IDENTICAL on my computer screen, plugged in side by side into my computer, until the instant that the WoeUSB installation finishes, when suddenly it crashes in the last milllisecond of installation, and after that millisecond the two copies are no longer identical, but radically different!

Conclusion: THIS IS A VALID COMPLAINT, WHICH I HAVE VALIDATED AS CORRECT, needing attention by the gurus on this forum. The previous guru was wrong in his conclusions.

Re: WoeUSB not working / Exit Code: 256

Post by Vilis » Mon May 13, 2019 1:26 pm

Источник

yum Docker install error Errno 256 Errno 14 HTTPS Error 404 — Not Found

As I have done in the past, I am trying to install docker-ce on RHEL 7(ppc64le) like this:

sudo yum-config-manager —add-repo https://download.docker.com/linux/centos/docker-ce.repo

yum repolist
repo id repo name
docker-ce-stable/x86_64 Docker CE Stable — x86_64

sudo yum install docker-ce
I get the error output below. I have tried all the solutions recommended, but I think the real error is the very last line in the error output which is:

failure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.
https://download.docker.com/linux/centos/7/ppc64le/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 — Not Found

Any suggestions on how to resolve this error?

========= Start error output ==================
https://download.docker.com/linux/centos/7/ppc64le/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 — Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article

h t t p s://access.redhat.com/articles/1320623

If above article doesn’t help to resolve this issue please open a ticket with Red Hat Support.

One of the configured repositories failed (Docker CE Stable — ppc64le),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

Contact the upstream for the repository and get them to fix the problem.

Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

Run the command with the repository temporarily disabled
yum —disablerepo=docker-ce-stable .

Disable the repository permanently, so yum won’t use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use —enablerepo for temporary usage:

or
subscription-manager repos —disable=docker-ce-stable

Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

Источник

Update disclaimer

• Yes, I have checked and my issue is not related to the game updating and plugins not working correctly.

What did you do?

Hi everyone, orry for disturbing but I have found a problem recently on trying to install XIV Launcher from Lutris.

I went on website of Lutris under the FFXIV section, I clicked on the Install button, launched the script and when it tries to install/configure the dotnet40 it gives the error shown in the log output with the 256 return code, probably that’s because it use the old 7.1 runner,I don’t really know.

Please I need you’re help the XIV Launcher is for me the only one for many reasons, and not working is a huge problem (yes, I can try to install the flatpak version, but you all knows that the Lutris version is the best one to configure ACT).

Many many thanks in advance for any help provide,

Platform

Linux (Wine/Proton)

Wine/Proton runner version

Lutris-7.1

Relevant log output

Started initial process 343579 from /home/massimiliano/.local/share/lutris/runtime/winetricks/winetricks --unattended dotnet48 vcrun2019 win10
Start monitoring process.
wget: /home/massimiliano/.local/share/lutris/runtime/Ubuntu-18.04-x86_64/libgnutls.so.30: version `GNUTLS_3_6_3' not found (required by wget)
------------------------------------------------------
warning: Github down? version '' doesn't appear to be a valid version
------------------------------------------------------
------------------------------------------------------
warning: Your version of wine 4.8-22663-gcb3e2c222f5 is no longer supported upstream. You should upgrade to 5.x
------------------------------------------------------
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Using winetricks 20220411-next - sha256sum: 50b745d7f46ead56fd0c9e6d753d53ea0ae368c988434c25d65fec66307e5d4f with wine-4.8-22663-gcb3e2c222f5 (Staging) and WINEARCH=win64
Executing w_do_call dotnet48
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_dotnet48 
------------------------------------------------------
warning: This package (dotnet48) may not fully work on a 64-bit installation. 32-bit prefixes may work better.
------------------------------------------------------
Executing w_do_call remove_mono
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_remove_mono 
------------------------------------------------------
warning: Mono does not appear to be installed.
------------------------------------------------------
Executing w_do_call dotnet40
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_dotnet40 
------------------------------------------------------
warning: This package (dotnet40) may not fully work on a 64-bit installation. 32-bit prefixes may work better.
------------------------------------------------------
------------------------------------------------------
warning: dotnet40 does not yet fully work or install on wine.  Caveat emptor.
------------------------------------------------------
Executing w_do_call remove_mono
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_remove_mono 
------------------------------------------------------
warning: Mono does not appear to be installed.
------------------------------------------------------
Executing w_do_call winxp
Executing mkdir -p /home/massimiliano/Games
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
Executing load_winxp 
reg: The operation completed successfully
Setting Windows version to winxp
Executing /home/massimiliano/.local/share/lutris/runners/wine/lutris-7.1-x86_64/bin/wine regedit /S C:windowsTempset-winver.reg
Executing /home/massimiliano/.local/share/lutris/runners/wine/lutris-7.1-x86_64/bin/wine64 regedit /S C:windowsTempset-winver.reg
------------------------------------------------------
warning: Running /home/massimiliano/.local/share/lutris/runners/wine/lutris-7.1-x86_64/bin/wineserver -w. This will hang until all wine processes in prefix=/home/massimiliano/Games/final-fantasy-xiv-online terminate
------------------------------------------------------
Executing cd /home/massimiliano/.cache/winetricks/dotnet40
Executing /home/massimiliano/.local/share/lutris/runners/wine/lutris-7.1-x86_64/bin/wine dotNetFx40_Full_x86_x64.exe /q /c:install.exe /q
fsync: up and running.
Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Core_x64.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Core_x86.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Extended_x64.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Extended_x86.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bRGB9RAST_x64.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bRGB9Rast_x86.msi...

Preparing: C:8db6088b124fcafc34740b6c4e8bheader.bmp...

Preparing: C:8db6088b124fcafc34740b6c4e8bSplashScreen.bmp...

Preparing: C:8db6088b124fcafc34740b6c4e8bwatermark.bmp...

Preparing: C:8db6088b124fcafc34740b6c4e8bDisplayIcon.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsPrint.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate1.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate2.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate3.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate4.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate5.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate6.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate7.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsRotate8.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsSave.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsSetup.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsstop.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsSysReqMet.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicsSysReqNotMet.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8bGraphicswarn.ico...

Preparing: C:8db6088b124fcafc34740b6c4e8b1033LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1042LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1041LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1037LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1025LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1035LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1030LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1044LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1043LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1040LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1029LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1031LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1036LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1032LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1038LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b2052LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1028LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b3076LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1055LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1053LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b3082LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b2070LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1046LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1049LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8b1045LocalizedData.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bClientParameterinfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bExtendedParameterinfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bParameterInfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bStrings.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bUiInfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bClientUiInfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bExtendedUiInfo.xml...

Preparing: C:8db6088b124fcafc34740b6c4e8bSetupUi.xsd...

Preparing: C:8db6088b124fcafc34740b6c4e8bDHtmlHeader.html...

Preparing: C:8db6088b124fcafc34740b6c4e8b1033eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1025eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1028eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1030eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1031eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1029eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1036eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1035eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1032eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1038eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1037eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1040eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1041eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1042eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1044eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1043eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1046eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1045eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1055eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1053eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b2052eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b1049eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b3082eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b2070eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8b3076eula.rtf...

Preparing: C:8db6088b124fcafc34740b6c4e8bSetup.exe...

Preparing: C:8db6088b124fcafc34740b6c4e8bSetupUtility.exe...

Preparing: C:8db6088b124fcafc34740b6c4e8bSetupEngine.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1025SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1033SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1029SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1030SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1035SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1031SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1036SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1032SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1028SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b2052SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b3076SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1042SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1041SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1037SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1044SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1053SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1055SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1040SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1045SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1046SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1049SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1038SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b2070SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b3082SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8b1043SetupResources.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8bSetupUi.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8bsqmapi.dll...

Preparing: C:8db6088b124fcafc34740b6c4e8bWindows6.0-KB956250-v6001-x64.msu...

Preparing: C:8db6088b124fcafc34740b6c4e8bWindows6.0-KB956250-v6001-x86.msu...

Preparing: C:8db6088b124fcafc34740b6c4e8bWindows6.1-KB958488-v6001-x64.msu...

Preparing: C:8db6088b124fcafc34740b6c4e8bWindows6.1-KB958488-v6001-x86.msu...

Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Core.mzz...

Preparing: C:8db6088b124fcafc34740b6c4e8bnetfx_Extended.mzz...

------------------------------------------------------
warning: Note: command /home/massimiliano/.local/share/lutris/runners/wine/lutris-7.1-x86_64/bin/wine dotNetFx40_Full_x86_x64.exe /q /c:install.exe /q returned status 236. Aborting.
------------------------------------------------------
Monitored process exited.
Initial process has exited (return code: 256)
Exit with return code 256