Affinity Suite V2 on Linux [ Wine ]

[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

[markusdd]

Hi Guys!

I just signed up to a) thank @Wanesty and others for their outstanding work on this and b) to confirm that at least under Fedora/nobara 40 the distrobox method seems to work best. I got that running without issue while with the classic approach Wine would not even compile for me anymore after I upgraded from 38/39 a while ago.

So I figured I might as well put in the effort and document everything I did to make that work. I also pieced together the info from this long thread about  .desktop files with distrobox and and managed to make them generic so the homepath isn't hardcoded and icons are properly found. They are in the doc repo linked below as well.

Pull Requests to these docs are welcome. I do want this to be a competition to the original docs but I was lacking an easy 'copy paste' guide for the distrobox approach so I figured I would make one here:

https://github.com/markusdd/affinity-linux-distrobox/

I hope this also brings in more stability across base system updates because the distrobox is kind of self-contained, I really do not facny repeating this whole process with each large OS update 😅

 

I hope this helps somebody!

[Mike Hansen]

Nice job @markusdd. On my nobara40 install, I had to run the distrobox commands with --root before it would work, but beyond that, works nicely

[markusdd]

uh, that should not be necessary actually. using --root is not really recommended for security reasons.

[Mike Hansen]

Yep I know, but it won't work unless I do it 😛

I get the following error:

Quote

mike@Voyager:~/.local/share/applications$ distrobox create -n arch-noroot -i archlinux
Image archlinux not found.
Do you want to pull the image now? [Y/n]: y
Using default tag: latest
permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/images/create?fromImage=archlinux&tag=latest": dial
unix /var/run/docker.sock: connect: permission denied

 

[markusdd]

yeah I would investigate that if I were you this seems to be some underlying permission issue in your homedir or some other setting.

None of this requires root except the /opt/wines dir creation outside the distrobox.

 

EDIT: just saw your edit. Ok, this is a Docker problem. I would advise to use podman instead, which has much less issues in that regard.

 

If you want to keep using docker make sure your user has the proper docker group on your system so the distrobox can access the socket properly in non-root mode.

The docker-ce install is not really clean on Fedora and related RedHat distros anymore out of the box.

Edited November 3, 2024 by markusdd

[Mike Hansen]

Thanks for the advice I installd podman instead, all works perfectly! Thanks again

 

[markusdd]

sure no problem. I should add that to the readme.

[markusdd]

@Wanesty

The only thing does not work even with the arch distrobox approach above is the export of raster formats like PNG

 

installing mfc140 does noting, installing vcrun2015 breaks all afphoto etc. formats, so is useless and needs rollback.

 

Has there been any consensus what helps here? Is it arch related? Would it be worth trying the distrobox with another distribution?

[mysbyxor]

Succeed with the installation on Endeavour OS but i am left with one problem. StudioLink does not work and i cannot activate products. I am shown "No license installed. Activation will be required next startup" at every start up. When trying to access Designer or Photo i am met with red text saying "App launch required".

 

Is this a common issue or even known to not work at all? Any nice fix?

[Ignore]

Is anyone else also not able to open multiple affinity apps at once? Running one of the three works fine for me, but when i try to start another one simultaneously, it crashes at the font loading at startup

[breathless19]

I have no problem running multiple affinity apps at the same time.   I installed mine in an distrobox Arch container for reference...

[Ignore]

I just configured the .desktop files and restartet my endeavour os, and now i can launch all the apps at once.   

I just quickly made a custom wallpaper on the fly, it works so well

[jhob101]

I recently updated my affinity apps to 2.5.5 and am getting an issue where hotkeys aren't recognised by the app the first time I hit them.

For example 

CTRL + N

doesn't do anything but

CTRL + N + N

will open the new document window.

Anyone know why this might be and how to resolve it?

[Daegalus]

Just an fyi, I have some prebuilt wines with the patches from _avg_

I haven't tested them thoroughly or recently, but the build and release pipeline now works, so I can quickly add patches and make new builds.

These are also build on wine-9.21 and I can keep that updated easily.

These builds are based on wine-tkg, so there are some extras and patches already built-in.

Let me know how they work or if you have problems.

https://github.com/daegalus/wine-tkg-affinity

[jhob101]

50 minutes ago, Daegalus said:

Just an fyi, I have some prebuilt wines with the patches from _avg_

I haven't tested them thoroughly or recently, but the build and release pipeline now works, so I can quickly add patches and make new builds.

These are also build on wine-9.21 and I can keep that updated easily.

These builds are based on wine-tkg, so there are some extras and patches already built-in.

Let me know how they work or if you have problems.

https://github.com/daegalus/wine-tkg-affinity

Apologies for being thick, but how do I build this?  I did try and hunt for some documentation that might enlighten me but couldn't find any.  Thanks!

[markusdd]

1 hour ago, Daegalus said:

Just an fyi, I have some prebuilt wines with the patches from _avg_

I haven't tested them thoroughly or recently, but the build and release pipeline now works, so I can quickly add patches and make new builds.

These are also build on wine-9.21 and I can keep that updated easily.

These builds are based on wine-tkg, so there are some extras and patches already built-in.

Let me know how they work or if you have problems.

https://github.com/daegalus/wine-tkg-affinity

This is a very good effort. I have worked with some of the guys on the Nobara Linux discord to get ON1 Photo Raw to run and we've made great progress so far, having it completely running except the AI sharpener and denoiser. If we can get that merged together somewhen to have on workable wine-tkg platform that can run the whole affinity suite and On1 that would be super nice.

[Daegalus]

5 minutes ago, markusdd said:

This is a very good effort. I have worked with some of the guys on the Nobara Linux discord to get ON1 Photo Raw to run and we've made great progress so far, having it completely running except the AI sharpener and denoiser. If we can get that merged together somewhen to have on workable wine-tkg platform that can run the whole affinity suite and On1 that would be super nice.

You don't, this is a prebuilt release. Just download the package in the releases.

You should be able to use it with rum.

[jhob101]

1 minute ago, Daegalus said:

You don't, this is a prebuilt release. Just download the package in the releases.

You should be able to use it with rum.

ah ok, cheers.

I saw the .BUILDINFO and .INSTALL files and thought something needed to be done with them.

I'll give it a go

[Daegalus]

28 minutes ago, jhob101 said:

ah ok, cheers.

I saw the .BUILDINFO and .INSTALL files and thought something needed to be done with them.

I'll give it a go

I think those are pkgbuild related files for Arch. If I understood everything and configured it right, the Arch package should be installable with pacman on Arch 

[Daegalus]

39 minutes ago, markusdd said:

This is a very good effort. I have worked with some of the guys on the Nobara Linux discord to get ON1 Photo Raw to run and we've made great progress so far, having it completely running except the AI sharpener and denoiser. If we can get that merged together somewhen to have on workable wine-tkg platform that can run the whole affinity suite and On1 that would be super nice.

If you guys turn the changes into a patch file, it can easily be dropped in and a build made. We can make a fork for on1 of my repo to keep it clean or we can add it to the affinity one.

Either way, once there are patch files, the rest is easy.

[bmael]

Hi !

I am writing this message because I have not yet managed to create a working desktop shortcut even following the guide.

This line in the terminal works well :

rum affinity-photo3-wine9.13-part3 $HOME/.wineAffinity wine "$HOME/.wineAffinity/drive_c/Program Files/Affinity/Publisher 2/Publisher.exe"

But the .desktop don't. I'm sorry for my poor capacity. Thanks for your help.