Affinity Suite V2 on Linux [ Wine ]

[bmael]

OK

Publisher seems to works now ! Thank you very much !

I have to try it.

Can you help again me with the high resolution screen of my mac ? Everything is to small.

[Spirit]

29 minutes ago, bmael said:

Can you help again me with the high resolution screen of my mac ? Everything is to small.

As per the wiki guide, change your screen DPI in wine. Not sure why you're running linux on a mac though...

[Daegalus]

15 minutes ago, Spirit said:

As per the wiki guide, change your screen DPI in wine. Not sure why you're running linux on a mac though...

I would guess is they were a Mac user, or got a mac used, or even a gift. So Linux on Mac isn't crazy. I was able to give life to my mom's old Macbook Air for another 5 years, before she got herself something new, by putting Ubuntu on it back in the day for her.

[bmael]

Thank you very much ! I can now try in good condition this software.

Why Linux on a Mac ? For ideological reason of course.

It's not an old but recent MacBook Pro (16'' 2019 with i7 12 core) I use professionally but I would like to switch on Linux for long time. I have also to switch from Adobe to Affinity.

[bmael]

I still have this error at startup :

ls -l /var/crash
total 28760
-rw-r----- 1 root whoopsie 29011804 oct.   1 21:14 _opt_wines_affinity-photo3-wine9.13-part3_bin_wine-preloader.0.crash
-rw-r----- 1 root whoopsie   435893 oct.   2 16:08 _usr_lib_xorg_Xorg.0.crash

Any idea ?

[breathless19]

8 hours ago, Spirit said:

Not sure why you're running linux on a mac though...

Because Mac's are essentially the nicest machines in their form factor (laptops or the mini's).  Installing Linux, as already stated, adds new life to these machines, but allows you to keep a OSX aesthetic with Gnome while also getting away from all the privacy invasion that is already starting in OSX, as well as what is coming in the near future.    A better question is why NOT run Linux on a Mac, particularly if philosophically you lean towards freedom / FOSS?  

[bmael]

👍

[bmael]

4 minutes ago, breathless19 said:

Because Mac's are essentially the nicest machines in their form factor (laptops or the mini's).  Installing Linux, as already stated, adds new life to these machines, but allows you to keep a OSX aesthetic with Gnome while also getting away from all the privacy invasion that is already starting in OSX, as well as what is coming in the near future.    A better question is why NOT run Linux on a Mac, particularly if philosophically you lean towards freedom / FOSS?  

👍

[Wanesty]

On 10/5/2024 at 10:54 AM, Spirit said:

If they do, @Wanesty, maybe it makes sense to update the guide with this?

the steps you listed are exactly what winetricks is supposed to do, i might open an issue on their repo if it is still an ongoing issue but i'm suspecting it's been fixed and it's just a matter of winetricks not being updated on your distro's repo

9 hours ago, bmael said:

I tried again without "sudo" and it worked.

do not EVER run something with superuser privilege unless you know you need to or the software tells you, you need to.

 

also with the linux on mac discussion, yea the new arm macs are interesting performance and build quality wise, if apple weren't so greedy with ram and storage space- or even better! wasn't such an ass about locking down everything so much: with Asahi linux's work they honestly are excellent machine to run linux on

[ElementalWarrior]

14 minutes ago, breathless19 said:

Because Mac's are essentially the nicest machines in their form factor (laptops or the mini's).  Installing Linux, as already stated, adds new life to these machines, but allows you to keep a OSX aesthetic with Gnome while also getting away from all the privacy invasion that is already starting in OSX, as well as what is coming in the near future.    A better question is why NOT run Linux on a Mac, particularly if philosophically you lean towards freedom / FOSS?  

While Apple mac's are very nice computers. I don't agree with their business practices. Primarily about how they treat their hardware. The fact that a device "owner" cannot simply replace a button, or a screen, without profit capture by Apple, and the replacement done by Apple. But also you cannot side load your own binaries onto their phones.

So I put my "vote" of my money, elsewhere.

 

[breathless19]

20 minutes ago, ElementalWarrior said:

While Apple mac's are very nice computers. I don't agree with their business practices. Primarily about how they treat their hardware. The fact that a device "owner" cannot simply replace a button, or a screen, without profit capture by Apple, and the replacement done by Apple. But also you cannot side load your own binaries onto their phones.

So I put my "vote" of my money, elsewhere.

 

I'm with you on all of that.   I was speaking mainly about just the "niceness" of the hardware, but you are correct that they are quite douchey about how they lock the hardware down.

[LKhez08]

On 10/2/2024 at 12:37 PM, Winduss said:

I've tried this multiple times. A few months ago I've got it to work no problem on Kubuntu 22.04 but now on Fedora 41 I've not been so lucky. It's missing packages for compiling the 32bit version of Wine as mentioned in this guide.

When using the podman way of building wine, it compiles. But I've found a guide for it to run it inside Bottles and then it complains about missing a certain DLL file relating to .NET framework. Even after installing all of them.

So right now I don't know what to do.

Fedora 40 KDE Plasma, I'm stuck at the same point here. I tried the original guide by @Wanesty several months ago with no luck.
Now I tried again with this guide using podman and bottles:
https://www.standingpad.org/posts/2024/06/affinity-on-linux/

Everything is okay until installing dotnet dependencies. dotnet35 fails during installation, dotnet48 completes but I think it's missing something.
 Installing dotnet48, bottles terminal says:

002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2).
0088:err:hid:initialize_device 0x30 usage not found, unsupported device
0088:err:hid:initialize_device 0x30 usage not found, unsupported device
0150:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0150:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
01fc:err:ole:com_get_class_object class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
01fc:err:ole:com_get_class_object no class object {2b72133b-3f5b-4602-8952-803546ce3344} could be created for context 0x1
0420:err:ole:com_get_class_object class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0420:err:ole:com_get_class_object no class object {2b72133b-3f5b-4602-8952-803546ce3344} could be created for context 0x1
0420:err:ole:com_get_class_object class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0420:err:ole:create_server class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0420:err:ole:com_get_class_object no class object {2b72133b-3f5b-4602-8952-803546ce3344} could be created for context 0x15
0450:err:ole:com_get_class_object class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0450:err:ole:com_get_class_object no class object {2b72133b-3f5b-4602-8952-803546ce3344} could be created for context 0x1
0450:err:ole:com_get_class_object class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0450:err:ole:create_server class {2b72133b-3f5b-4602-8952-803546ce3344} not registered
0450:err:ole:com_get_class_object no class object {2b72133b-3f5b-4602-8952-803546ce3344} could be created for context 0x15

 

 Installing dotnet35, bottles terminal says:

002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2).
0088:err:hid:initialize_device 0x30 usage not found, unsupported device
0088:err:hid:initialize_device 0x30 usage not found, unsupported device
0154:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
0154:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
01a4:err:winediag:CorIsLatestSvc If this function is called, it is likely the result of a broken .NET installation
01a4:err:eventlog:ReportEventW L".NET Runtime Optimization Service (clr_optimization_v4.0.30319_32) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown\n"
01c0:err:winediag:CorIsLatestSvc If this function is called, it is likely the result of a broken .NET installation
01c0:err:eventlog:ReportEventW L".NET Runtime Optimization Service (clr_optimization_v4.0.30319_64) - Tried to start a service that wasn't the latest version of CLR Optimization service. Will shutdown\n"

and during the on screen win-install:

0154:err:msidb:TransformView_set_row trying to modify existing column
0230:err:eventlog:ReportEventW L"System.TypeInitializationException: The type initializer for 'System.ServiceModel.Install.IisHelper' threw an exception. ---> System.TypeLoadException: Could not load type of field 'System.ServiceModel.Install.Configuration.IIS7ConfigurationLoader:serverManager' (0) due to: Could not load"...
0230:err:eventlog:ReportEventW L"   --- End of inner exception stack trace ---\r\n"
0230:err:eventlog:ReportEventW L"  at Microsoft.Tools.ServiceModel.CommandArguments..ctor (System.String[] args) [0x003e2] in <b26c266450894ba4be93dee1b269237f>:0 \r\n"
0230:err:eventlog:ReportEventW L"  at Microsoft.Tools.ServiceModel.ServiceModelReg.Run (System.String[] args) [0x00000] in <b26c266450894ba4be93dee1b269237f>:0 \r\n"
0230:err:eventlog:ReportEventW L"  at Microsoft.Tools.ServiceModel.ServiceModelReg.TryRun (System.String[] args) [0x00031] in <b26c266450894ba4be93dee1b269237f>:0"
0154:err:msi:execute_script Execution of script 0 halted; action L"[C:\\windows\\Microsoft.NET\\Framework\\v3.0\\Windows Communication Foundation\\ServiceModelReg.exe /r /x /y /v;dummy;C:\\windows\\Microsoft.NET\\Framework\\v2.0.50727\\<=>S-1-5-21-0-0-0-1000<=>{2BA00471-0328-3743-93BD-FA813353A783}]DD_CA_InstallXwsRegExe_X86.3643236F_FC70_11D3_A536_00902"... returned 1603
0154:err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1603

I just wanted to post my experience here, maybe it will help someone with more knowledge. I'm still very VERY new to linux, so I probably won't able to reply to any technical question I'm going to hold on my Windows partition, I'll try again in a few months I guess.
 

[Wanesty]

On 10/14/2024 at 3:44 PM, LKhez08 said:

I tried the original guide by @Wanesty several months ago with no luck.

i recently updated the dependencies list and switched to a new way of compiling wine that does not require 32bits dependencies so maybe give it an other go if you have time on your hands!

https://affinity.liz.pet/

[Mike4263]

After having significant problems with Windows, I recently re-installed Fedora intending to dual boot, but broke my EFI bootloader in the process.  Oops.  The rare use of Affinity was one of the sole remaining apps that required Windows.  After messing with this for a few hours, I was finally able to get this installed and working!

Big thanks to @ElementalWarrior and @Wanesty for the great work on getting this working. Also, @Peter Werner 's post helped me trouble shoot a few things.  I started with the guide on page 1 and it wasn't until I skipped to the end and found the new website (can you update the original post with that URL?).  I was going through the wine compilation guide by hand adding dependencies one at a time before I found the nice new guide!

On fedora 40, I think you are missing the libxkbcommon-devel package.  I needed to add that for wayland support.  

After the initial guide didn't work, I tried a variety of things and ultimately got it working:

• Started with a fresh .wine directory
• Uninstalled wine-core and winetricks.  Got Winetricks from GitHub instead
• Ran the winetricks dotnet48 and corefonts commands independently without the --unattended .  They seemed to progress further that way 
• Set my version to win10 as my metadata was from windows 10
• Everytime I run wineboot I get this error: 

002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).

.  I suspect that there is a GUI to admin things but I've never gotten it to appear.  Not sure if I'm missing out on it

I notice that the image seems to flicker in/out if you click out of the app, but I haven't done any actual work with it yet so I don't know how big of a deal that is.  Now to neatly package this away for the 2 times a year I actually need to edit something.  Thanks again!

-Mike

[OzNate]

After trying this on several systems, I am finding that different versions of dependencies seem to create a lot of headaches. If someone could containerise this whole thing, maybe it would be better.

[Wanesty]

On 10/17/2024 at 11:37 PM, Mike4263 said:

can you update the original post with that URL?

i cannot edit posts this old, a moderator has to

On 10/17/2024 at 11:37 PM, Mike4263 said:

• Everytime I run wineboot I get this error: 

002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).

.  I suspect that there is a GUI to admin things but I've never gotten it to appear.  Not sure if I'm missing out on it

nope, wineboot is not supposed to show anything, it's simply creating the wineprefix for you.
you can safely proceed with the rest!

On 10/17/2024 at 11:37 PM, Mike4263 said:

002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).

this exactly should not actually cause any issue, like ever

On 10/17/2024 at 11:37 PM, Mike4263 said:

I notice that the image seems to flicker in/out if you click out of the app, but I haven't done any actual work with it yet so I don't know how big of a deal that is.

check the troubleshooting page!

 

 

21 hours ago, OzNate said:

After trying this on several systems, I am finding that different versions of dependencies seem to create a lot of headaches. If someone could containerise this whole thing, maybe it would be better.

you could use distrobox and spin up an ArchLinux container, it should be the most likely one to work as it's the one i'm mainly maintaining

[Marcus_st]

On 8/29/2024 at 5:41 PM, d-7 said:

Today I face this problem on Linux when launching the app, "Affinity Photo" was installed the 2024-08-28 and I don't have a firewall activated.

"Sorry there was a problem launching the application. Cannot communicate with other Affinity apps. Please ensure the app is up-to-date and that your firewall isn't blocking local network traffic."

 

Well after rebooting, now is working again. I log in with the account just in case (because I have the V2 Universal License).

So, compiling and starting with vulkan worked on the first try.
But I get the same error message with all affinity2 programs. Affinity 1 programs work.
 

Does anyone have an idea how to solve the issue? Restarting did not work for me...

 

[Wanesty]

2 hours ago, Marcus_st said:

So, compiling and starting with vulkan worked on the first try.
But I get the same error message with all affinity2 programs. Affinity 1 programs work.
 

Does anyone have an idea how to solve the issue? Restarting did not work for me...

if affinity v1.10 and before work properly then it may be an issue with the winmd files, trying different ones from an up to date win10/win11 machine may fix the issue!

[Marcus_st]

11 hours ago, Wanesty said:

if affinity v1.10 and before work properly then it may be an issue with the winmd files, trying different ones from an up to date win10/win11 machine may fix the issue!

First of all, many thanks for all your effort and also for your very fast response!

Unfortunately, that did not do it. I've tried the winmd files of 3 different windows installations, but no luck.
I am getting an error message though indicating an issue with bcrypt.

01b0:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
01b0:err:bcrypt:BCryptGenerateSymmetricKey no encryption support

I've also tried installing firefox and opening a website. It fails and I get the same error message.
Unfortunately, I did not find a solution yet.

As Affinity 2 requires internet access at the first launch for licensing checks, that might be the issue. Affinity 1 does not need a network connection.

What I've tried:

• setcap on wine64-preloader and wine-preloader -> now ping works in cmd
• setting bcrypt to native in winecfg library settings
• running winetricks crypt32

It did not solve the issue so far...

[Marcus_st]

51 minutes ago, Marcus_st said:

First of all, many thanks for all your effort and also for your very fast response!

Unfortunately, that did not do it. I've tried the winmd files of 3 different windows installations, but no luck.
I am getting an error message though indicating an issue with bcrypt.

01b0:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
01b0:err:bcrypt:BCryptGenerateSymmetricKey no encryption support

I've also tried installing firefox and opening a website. It fails and I get the same error message.
Unfortunately, I did not find a solution yet.

As Affinity 2 requires internet access at the first launch for licensing checks, that might be the issue. Affinity 1 does not need a network connection.

What I've tried:

• setcap on wine64-preloader and wine-preloader -> now ping works in cmd
• setting bcrypt to native in winecfg library settings
• running winetricks crypt32

It did not solve the issue so far...

I've tried everything again but facing the same issue.

Also installing wine-mono failed with the error message "unexpected checksum...aborting installation of corrupted file".

I've tried to install wine-mono manually but I cannot find a corresponding version for wine 7.9. There is only wine 7.6 and wine 7.10 listed on the wine-mono website. All wine-mono versions I've tried (7.2 - 7.4) lead to an exception when launching Desinger 2.

[Ignore]

On 10/5/2024 at 10:54 AM, Spirit said:

I managed to complete the installation on Fedora 40, KDE, Wayland.

The installation is a bit of an adventure, but here's the steps that appear to fully function, starting from a newly initialized prefix, with the 9.13-part3 fork.

This fixes the andale32 error during setup of the prefix and the mscoree.dll error when trying to run the installer.

1 - Install prefix as per the guide

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wineboot --init

2 - Remove mono via uninstaller

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine uninstaller

3 - Manually install dotnet40(download from MS) under winxp64, using the UI

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity winecfg -v winxp64
rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine ~/./Downloads/dotNetFx40_Full_x86_x64.exe 

4 - Force wine to stop deleting mscoree when failing to install dotnet48

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine reg add "HKCU\\Software\\Wine\\DllOverrides" /v "*mscoree" /t REG_SZ /d "native" /f

5 - Install dotnet48(download from MS) manually under win7, using the UI

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity winecfg -v win7
rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine ~/./Downloads/NDP48-x86-x64-AllOS-ENU.exe

 

6 - Replace broken corefonts cabinets(.exe) files in the cache with ones from sourceforge

https://sourceforge.net/projects/corefonts/files/the fonts/final/

Download all of these except wd97vwr32.exe, then copy them to cache:

cd fonts
cp * ~/.cache/winetricks/corefonts/

 

7 - Install corefonts

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity winetricks --force --unattended corefonts

This step should complete without SHA mismatches. If it does, remove --unattended, run it, then when the first collision happens, replace the files before proceeding. It should pick them up.

 

8 - Copy WinMetadata from Windows 10/11(as per the guide)

cp --recursive [WinMetadata folder path] "$HOME/.wineAffinity/drive_c/windows/system32/WinMetadata"

 

9 - Install something from Affinity under win11

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine winecfg -v win11
rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine ~/./Downloads/affinity-photo-msi-2.5.5.exe

 

10 - Run it, then change to Vulkan if flickering.

 

I'm not great at linux, so some of these steps may be unnecessary, but this is how I made it work.

@prehensile @bmael please try to reproduce these steps, maybe they'll also work for you.

If they do, @Wanesty, maybe it makes sense to update the guide with this?

This finally made it "stable" on my EndeavourOS install, thank you. Sometimes it still crashes on startup while loading the fonts, but if i try again it usually works. Saving .afpub works and exporting as .pdf works aswell. I haven't tried exporting as .png or other rasterized formats yet though.

[StandingPad]

I've been looking into the issue of settings not being saved, my best guess is that Affinity is somehow unable to get the window size and position when it tries to output preferences (which would explain why it sometimes work with the virtual desktop). That said, I haven't been able to inspect the function calls performed when settings are saved, so it's just a guess

Edited October 22, 2024 by StandingPad

[StandingPad]

On 10/14/2024 at 1:44 PM, LKhez08 said:

Fedora 40 KDE Plasma, I'm stuck at the same point here. I tried the original guide by @Wanesty several months ago with no luck.
Now I tried again with this guide using podman and bottles:
https://www.standingpad.org/posts/2024/06/affinity-on-linux/

I should note that the guide I made using Bottles is a little outdated (I've been meaning to update it for a while but haven't gotten around to it yet), and uses a different branch of ElementalWarrior's fork of WINE (a branch based on Wine 9.13, so a tad bit newer than what's been tried and tested here).

[OzNate]

On 10/19/2024 at 12:07 PM, Wanesty said:

you could use distrobox and spin up an ArchLinux container, it should be the most likely one to work as it's the one i'm mainly maintaining

Oh, cool, I wasn't aware of that tool. It looks promising! I'll try it out. Thanks!

[SerpentStriker]

Hi All,

I just started using Affinity Publisher on Windows and it was impressive, however using the linux port has not worked for me. I am stuck on this process.
This is the first step using rum, I am not sure what to do since this is my first time reading all this. I have no terminal experience to diagnose this, but I have some kind of idea of what it may imply.

rum ElementalWarrior-8.3 "/home/simon/.WineAffinity" winetricks dotnet48 corefonts
Rumming /opt/wines/ElementalWarrior-8.3 (wine-7.9-5443-gd0fe9b9ab64) in: /home/simon/.WineAffinity
Executing cd /usr/bin
------------------------------------------------------
warning: Your version of wine 7.9-5443-gd0fe9b9ab64 is no longer supported upstream. You should upgrade to 8.x
------------------------------------------------------
------------------------------------------------------
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 20240105 - sha256sum: 17da748ce874adb2ee9fed79d2550c0c58e57d5969cc779a8779301350625c55 with wine-7.9-5443-gd0fe9b9ab64 and WINEARCH=win64
Executing w_do_call dotnet48
------------------------------------------------------
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 internal
------------------------------------------------------
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 internal
Executing w_do_call dotnet40
------------------------------------------------------
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 internal
------------------------------------------------------
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 internal
04d4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
04d4:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
04d4:err:systray:initialize_systray Could not create tray window
Executing w_do_call winxp
------------------------------------------------------
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 
Executing wine winecfg -v winxp64
------------------------------------------------------
warning: Running /opt/wines/ElementalWarrior-8.3/bin/wineserver -w. This will hang until all wine processes in prefix=/home/simon/.WineAffinity terminate
------------------------------------------------------
Executing cd /home/simon/.cache/winetricks/dotnet40
Executing wine dotNetFx40_Full_x86_x64.exe
0044:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0044:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
0044:err:systray:initialize_systray Could not create tray window
0094:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0094:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0094:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0094:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0024:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
0024:fixme:clusapi:OpenCluster ((null)) stub!
0024:fixme:clusapi:ClusterOpenEnum (DEADBEEF, 4) stub!
0024:fixme:clusapi:ClusterEnum (DEADBEEF, 0, 0053F930, 0066EEF0, 261) stub!
0024:fixme:clusapi:ClusterCloseEnum (DEADBEEF) stub!
0024:fixme:clusapi:CloseCluster (DEADBEEF) stub!
0024:fixme:advapi:DecryptFileW (L"C:\\03b8e250912393f5e7770e3f\\", 00000000): stub
0108:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0108:err:winediag:nodrv_CreateWindow L"The graphics driver is missing. Check your build!"

I do have wine-staging installed and I have manually installed the dotnet40 but not sure what the error is with display driver is missing. I have tried installing the 32bit drivers using this:

sudo apt install libgl1-mesa-dri:i386 libgl1:i386

But that did not fix the problem. I am stumped and any directions could help me successfully get through with the installation, would be appreciated.

Thanks.

 

Edited November 1, 2024 by SerpentStriker