Affinity Suite V2 on Linux [ Wine ]

[Astonish]

Hello @Wanesty!Thank you for your reply, I appreciate your time! In these days I tried, on my laptop, your guide on fresh install of:

• Garuda Hyprland - it works
• Linux Mint - it works
• Big Linux - it works
• Fedora - it doesn't work
• Nobara - it doesn't work
• Archcraft - it doesn't work
• CachyOs - it didn't work
• EndeavourOS - it doesn't work (but it works on my Desktop)

So as you had mentioned, it is definitely something to do with drivers and distro as well for each computer but I could not find the issue. So now I am running it on Linux Mint.

Please forgive me, I have a question, how do you find the dependencies? I tried to do it on OpenSuse Tumbleweed as well, I tried to find some of the equivalent of the dependencies + Wine documents to see OpenSuse dependencies. But still it wasn't enough and I was messing on something. How do you find dependencies for a given distro?

I posted on Reddit my Linux Mint desktop screenshots and I chose the Affinity Photo as a cover photo! And several people are asking me how I had it run and I am sending people to this forum thread and to your installation guide!

 

[Astonish]

4 hours ago, JCristina said:

Thank Peter.. If it is a .NET issue, how would we force load it or would I do a complete rebuild from scratch to see if it works itself out? Thanks.

 

Hello, I had issues with dotnet files with Fedora too. Just a question, would it be a viable option to try a different distro? I could not make it work in Fedora but I tried Linux Mint, and it works for example!

[Peter Werner]

6 hours ago, JCristina said:

Thank Peter.. If it is a .NET issue, how would we force load it or would I do a complete rebuild from scratch to see if it works itself out? Thanks.

 

I'm not familiar enough with WINE to know what the right way to approach this is and whether it would be safe to just run the stock installer from Microsoft. But @TrippyHippyDan seems to describe the same problem in this post, maybe they can tell you what ultimately solved it for them.

Personally, I'd first look at this line from the Wanesty guide and check if it causes any error messages that could be helpful in tracking down the problem.

Quote

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

 

[jhob101]

On 8/17/2024 at 8:58 PM, Zode said:

@jhob101 Have you tried installing vcrun2015 through winetricks? That solved the crash on export issue for me.

I get a load of errors, which I think are related to it not being a 32bit wineprefix:

 

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.

 

and then:

0024:err:environ:init_peb starting L"Y:\\vcrun2015\\vc_redist.x86.exe" in experimental wow64 mode
0024:err:module:import_dll Library ucrtbase.dll (which is needed by L"C:\\windows\\system32\\sechost.dll") not found
0024:err:module:import_dll Library sechost.dll (which is needed by L"C:\\windows\\system32\\advapi32.dll") not found
0024:err:module:import_dll Library advapi32.dll (which is needed by L"C:\\windows\\system32\\gdi32.dll") not found
0024:err:module:import_dll Library ucrtbase.dll (which is needed by L"C:\\windows\\system32\\gdi32.dll") not found
0024:err:module:import_dll Library ucrtbase.dll (which is needed by L"C:\\windows\\system32\\sechost.dll") not found

plus loads more of the same.  

I presume I might have to rebuild it?  But how do I get it to install the 32bit dlls as well as 64bit?

[JCristina]

I certain could install Mint instead of using Fedora.. I figured I would wait to see if anyone has a fix before copying all of my app setups and moving everything to a new OS. Appreciate you reply and help.

[JCristina]

Thanks Peter.. Here's what we receive.

[Peter Werner]

50 minutes ago, JCristina said:

Here's what we receive.

This seems like it is already installed, so it should theoretically be finding it.

Googling the error, I found this thread on the WINE forums, and the last answer by user jkfloris claims this:

Quote

The installation of .Net may fail. If this happens, try to install it again, or use a new wineprefix.

WINEPREFIX=$HOME/GarminExpr winetricks --force -q dotnet48

So in your case, if you want to try reinstalling dotnet first, that would be again the line you used to install dotnet but with added parameters --force -q (you can skip the fonts).

No idea if that will fix it, but it may be worth a shot. Otherwise I'd start from scratch with a new prefix and hope that solves it.

EDIT: Also this tip on Github looks promising

[JCristina]

Thank you Peter.. So far.. The results.

 

Installed without an issue.

 

 

 

Sadly.. Error!!  Might be time to move from Fedora and see is Mint will make it happen... Wish there was a clear issue that could be resolved instead of jumping OS based on apps but, it is what it is I guess.

[bendangelo]

Hey, I got this working on a fresh install of Nobara 40 gnome version. I couldn't get this working on popos 22.04.

I want to know if it's possible to put this inside some sort of flatpak so it's easier to install? Only issue is getting the winmetadata.

[Daegalus]

38 minutes ago, bendangelo said:

Hey, I got this working on a fresh install of Nobara 40 gnome version. I couldn't get this working on popos 22.04.

I want to know if it's possible to put this inside some sort of flatpak so it's easier to install? Only issue is getting the winmetadata.

A Flatpak is possible, but you are right about the win metadata. But that can be easily added to the right folder after Flatpak install.

Not pretty, but possible. We could also make an Installer/Launcher of sorts, similar to how they do for Genshin Impact, to install Wine and patches and such, asks for where the installer and win metadata is, and sets everything up accordingly.

All doable, I just don't have time right now to do it.

[JCristina]

Good to here something besides Mint, this is working with (Nobara 40 gnome version). thank you for that!

 

[Astonish]

3 hours ago, bendangelo said:

Hey, I got this working on a fresh install of Nobara 40 gnome version. I couldn't get this working on popos 22.04.

I want to know if it's possible to put this inside some sort of flatpak so it's easier to install? Only issue is getting the winmetadata.

And on my laptop, all AMD, AMD 6800hs cpu and igpu, it didn't work on fresh Nobara install. So most probably it has got something to do with the hardware as well.

1 hour ago, JCristina said:

Good to here something besides Mint, this is working with (Nobara 40 gnome version). thank you for that!

 

On my experience, it worked on Garuda Linux too and my desktop worked on EndeavourOS too. It definitely has nothing to do with distros and it has more to do with my lack of Linux skills, but well, it is how my personal experience is. I have now installed Linux Mint on my desktop with Nvidia as well and it works with that hardware too but your experience may vary depending on your hardware.

 

EDIT: Now that I think, I tried it on the KDE version of fresh Nobara with the Nobara customizations. I don't know if some dependencies installed with Gnome (which may not be installed with KDE ) helped with the set-up or if it is my hardware+distro. Just brain storming

[JCristina]

I'm using Fedora 40 Gnome and it will not work.. Might do a Mint build tonight with Gnome and see if my results are the same as yours. I also have an older 1070 Nvidia card..

Edited August 20 by JCristina

[StandingPad]

8 hours ago, bendangelo said:

Hey, I got this working on a fresh install of Nobara 40 gnome version. I couldn't get this working on popos 22.04.

I want to know if it's possible to put this inside some sort of flatpak so it's easier to install? Only issue is getting the winmetadata.

I've been using Daegalus' Wine builder container to build the patched WINE versions, which is close I guess

[jhob101]

On 8/17/2024 at 8:58 PM, Zode said:

@jhob101 Have you tried installing vcrun2015 through winetricks? That solved the crash on export issue for me.

Tried last night to get vcrun2015 installed, but kept getting those errors about missing DLLs in system32, which was odd as they are there.  Rebuilt the wine prefix a number of times to no avail.  Also now getting the same errors when trying to install Affinity Photo so no sure what's going on there.  My kernel did update to 6.8.0-40-generic yesterday, not sure if that might be a factor?

But anyway, I did notice in winetricks the mfc140 library, which is listed as part of vcrun2015, so thought I'd have a go at installing that instead, and it did install without error.

Just tried exporting from Photo, and it works without crashing!

Massive kudos to you for working this out and a huge thanks from me!

[jhob101]

On 8/14/2024 at 9:42 AM, Astonish said:

- When I am exporting, the program crashes, closes, with an error

With the help of @Zode I think I have this one cracked now.

Try:

rum ElementalWarrior-wine $HOME/.wineAffinity winetricks -q -f mfc140

This worked for me and I can now export with no crash!

[jhob101]

The final hurdle I'd like to get over now is that on starting Affinity Photo it will randomly crash while loading the fonts on startup.  Not always at the same font, but I'd say 2/3 times I start the application it crashes, then third time it will start fine.

Any ideas what might be causing this and I could resolve it?

[jhob101]

Another fix, I was getting a lot of flickering where the image would go black until clicked on but setting

renderer=vulkan

In winetricks has resolved this.  I did this through the GUI, not sure how to run it via commandline but I'm sure someone can advise.

I did:

rum ElementalWarrior-wine $HOME/.wineAffinity winetricks

Then Select the default wineprefix > Change Settings > Select renderer=vulkan

Which seems to have resolved it, no more flickering.

EDIT: This is already covered in @Wanesty's guide:

https://codeberg.org/wanesty/affinity-wine-docs/src/branch/guide-wine9.13-part3/Tips-n-Fixes.md#fixing-flickering-and-other-visual-glitches

Edited August 21 by jhob101
Link to Wanesty's docs

[Astonish]

8 hours ago, JCristina said:

I'm using Fedora 40 Gnome and it will not work.. Might do a Mint build tonight with Gnome and see if my results are the same as yours. I also have an older 1070 Nvidia card..

Hello! I don't belleive that the older card should cause an issue, but well, in Linux and generally in computers, sometimes little differences of hardware can cause a different issue which can be fixed, but I lack the technical knowledge, so I changed the distro for that reason. Unfortunately all that I can do is share my experience with my specific hardware. 🫤

3 minutes ago, jhob101 said:

Another fix, I was getting a lot of flickering where the image would go black until clicked on but setting

renderer=vulkan

In winetricks has resolved this.  I did this through the GUI, not sure how to run it via commandline but I'm sure someone can advise.

I did:

rum ElementalWarrior-wine $HOME/.wineAffinity winetricks

Then Select the default wineprefix > Change Settings > Select renderer=vulkan

Which seems to have resolved it, no more flickering.

Hello,

I think that this is explained in the installation guide's "Tips'n'Fixes" section: https://codeberg.org/wanesty/affinity-wine-docs/src/branch/guide-wine9.13-part3/Tips-n-Fixes.md

@Wanesty is suggesting to run this command to use vulkan, which I did as well and fixed the same issues for me:

Quote

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity winetricks renderer=vulkan

I guess that this is what you were searching for.

I have a question about the export fix. I have installed all the Affinity suite and they are running fine right now, except the known export issue. To apply the fix that you mention, after running the winetricks command, do I have to reinstall everything or else I just need to run that command and then I launch my apps?

[jhob101]

21 minutes ago, Astonish said:

I think that this is explained in the installation guide's "Tips'n'Fixes" section: https://codeberg.org/wanesty/affinity-wine-docs/src/branch/guide-wine9.13-part3/Tips-n-Fixes.md

Thanks, hadn't spotted that!  Old news then I guess.

Quote

I have a question about the export fix. I have installed all the Affinity suite and they are running fine right now, except the known export issue. To apply the fix that you mention, after running the winetricks command, do I have to reinstall everything or else I just need to run that command and then I launch my apps?

No need to reinstall everything, just run 

rum ElementalWarrior-wine $HOME/.wineAffinity winetricks -q -f mfc140

in your wine prefix and then re-launch the app.

I've taken to making a copy of the working wine prefix before making any changes, just in case it messes up.

cp -r ~/.wineAffinity ~/.wineAffinity-bak

and then trying whatever change I want to make.

[Zethnos]

I'm still having this issue when I run:

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

I get this:

Rumming /opt/wines/affinity-photo3-wine9.13-part3 (wine-7.9-15231-ga7c9b19e1a2) in: /home/owner/.wineAffinity
/usr/local/bin/rum: line 27: winetricks: command not found

I've tried reinstalling and using alternate commands for the dot net, but I can't get passed this step.

The installer did start and install designer, but it won't run because of a dot net error.

Edited August 21 by Zethnos

[jhob101]

51 minutes ago, Zethnos said:

I'm still having this issue when I run:

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

I get this:

Rumming /opt/wines/affinity-photo3-wine9.13-part3 (wine-7.9-15231-ga7c9b19e1a2) in: /home/owner/.wineAffinity
/usr/local/bin/rum: line 27: winetricks: command not found

Looks like you've not got winetricks installed.  Assuming you're using apt package manager run:

sudo apt install winetricks

and try again

[Zethnos]

3 hours ago, jhob101 said:

Looks like you've not got winetricks installed.  Assuming you're using apt package manager run:

sudo apt install winetricks

and try again

Thank you! I ended up reinstalling kubuntu and doing it all fresh, but with the added step of installing winetricks before doing anything else and I got it all working just fine! I really appreciate it.

The only issues I seem to be having now (a minor one really) is that I've set up the desktop icon and pinned it to my taskbar. When it launches, it changes the app icon to the file I have set, but when I close affinity it goes back to a blank page looking icon. Is there a way to fix that?

Also, is there a way to make affinity files launch designer and open on click instead of having to open designer myself and drag and drop?

[JCristina]

23 hours ago, bendangelo said:

Hey, I got this working on a fresh install of Nobara 40 gnome version. I couldn't get this working on popos 22.04.

I want to know if it's possible to put this inside some sort of flatpak so it's easier to install? Only issue is getting the winmetadata.

Thanks for this.. I'm going to try to due a FRESH install of Nobara tonight as see if it works.

[Wanesty]

On 8/20/2024 at 9:15 AM, Astonish said:

In these days I tried, on my laptop, your guide on fresh install of:

• Garuda Hyprland - it works
• Linux Mint - it works
• Big Linux - it works
• Fedora - it doesn't work
• Nobara - it doesn't work
• Archcraft - it doesn't work
• CachyOs - it didn't work
• EndeavourOS - it doesn't work (but it works on my Desktop)

you're crazy, but wow, thanks
 

On 8/20/2024 at 9:15 AM, Astonish said:

how do you find the dependencies? I tried to do it on OpenSuse Tumbleweed as well, I tried to find some of the equivalent of the dependencies + Wine documents to see OpenSuse dependencies. But still it wasn't enough and I was messing on something. How do you find dependencies for a given distro?

in the guide there is a link to "dependencies listed in Wine's documentation" so i got them from there, however it is missing some so i'm not too sure, for archlinux there's build config files available for every package:

arch package page of wine, click on "source files" hosted on gitlab and in this repo you have a PKGBUILD file with the build dependencies, pkgbuild files are arch specific tho, but maybe there's an equivalent for other distro

 

10 hours ago, jhob101 said:

But anyway, I did notice in winetricks the mfc140 library, which is listed as part of vcrun2015, so thought I'd have a go at installing that instead, and it did install without error.

Just tried exporting from Photo, and it works without crashing!

interesting find!
i'll try it on my side and if it doesn't cause regressions(like vcrun2015 used to) i will add it to the guide!