Affinity Suite v2.0.4 on linux [ Wine ]

[ElementalWarrior]

57 minutes ago, Grunt said:

Do you mean WinRT?

Some of the winter work yes. I hacked in code to activation factory logic iirc. But the mechanism to do that isn't appropriate broadly to support all software expect to run under wine

[azuredusk10]

Thanks for your hard work with this!
 

Has anyone managed to build wine on Fedora 38? The list of dependencies in the guide contains several packages with incorrect names. When I managed to hunt the correct names down and install them, I could only get the Wine64 build to work and not the Wine32. It kept asking for freetype development headers, which I believe I had installed but it wasn’t recognising.

 

I tried various other guides for installing dependencies for Fedora but I couldn’t get past that error. 
 

If anyone could share the Fedora build I would greatly appreciate it!

[Wanesty]

29 minutes ago, azuredusk10 said:

It kept asking for freetype development headers

Wine's building documentation mentions it as : freetype-devel. But this exact name is mentioned the updated Guide so i'm not sure where your issue is coming from.

Conciser posting the list of packages with modified package names so i can update the guide !

[Kastas]

33 minutes ago, azuredusk10 said:

Has anyone managed to build wine on Fedora 38?

I had similar experience on Fedora.

I circumvented local dependencies by using Daegalus wine-builder, which worked like magic.

On 3/28/2023 at 10:37 AM, Daegalus said:

Stayed up way too late getting this working but here is the Docker image. Readme is in the github repo or the package page, take a look to see how to use it. I successfully compiled a ElementalWarrior build with this.

https://github.com/daegalus/wine-builder

https://github.com/daegalus/wine-builder/pkgs/container/wine-builder

podman pull ghcr.io/daegalus/wine-builder

[Daegalus]

1 hour ago, azuredusk10 said:

Thanks for your hard work with this!
 

Has anyone managed to build wine on Fedora 38? The list of dependencies in the guide contains several packages with incorrect names. When I managed to hunt the correct names down and install them, I could only get the Wine64 build to work and not the Wine32. It kept asking for freetype development headers, which I believe I had installed but it wasn’t recognising.

 

I tried various other guides for installing dependencies for Fedora but I couldn’t get past that error. 
 

If anyone could share the Fedora build I would greatly appreciate it!

I did this on Fedora 38, and it was a nightmare. For some dependencies you can't have the 64bit and the 32bit at the same time, they overwrite each other. So you have to switch between builds. I even had to do it in Debian in the docker image I made.

I eventually gave up and made the `wine-builder` linked above to get around it. When I get some free time, I might even switch it to using Arch and the PKGBUILD deps like ElementalWarrior suggested, but for now it works fine for building.

[Wanesty]

25 minutes ago, Daegalus said:

I did this on Fedora 38, and it was a nightmare. For some dependencies you can't have the 64bit and the 32bit at the same time, they overwrite each other. So you have to switch between builds. I even had to do it in Debian in the docker image I made.

oh damn sound like a nightmare

[Daegalus]

52 minutes ago, Wanesty said:

oh damn sound like a nightmare

Ya, but its not just Fedora. Ubuntu and Debian do the same thing for Samba as 1 example. My script ontop of the debian docker image requires me to do this package flipping for 2 libraries. I think fedora had it for many more, but its not an isolated issue with just Fedora.

[Wanesty]

45 minutes ago, Daegalus said:

Ubuntu and Debian do the same thing for Samba as 1 example

i don't believe samba support is that necessary for wine (or is it required to access mounted SMB share ?)

but overall yes i believe i've seen a few warns while configuring the wine32 build.

[Daegalus]

5 minutes ago, Wanesty said:

i don't believe samba support is that necessary for wine (or is it required to access mounted SMB share ?)

but overall yes i believe i've seen a few warns while configuring the wine32 build.

Its needed for NetBIOS and other networking/sharing stuff in Windows, which Wine has support for. its libsamba specifically, no thte entire samba install. Either way, I wanted to make my wine-builder generic, so even if its not super needed for Affinity, someone else might use it. I just made sure all optional features were enabled that weren't a huge hassle to enable.

[azuredusk10]

2 hours ago, Kastas said:

I had similar experience on Fedora.

I circumvented local dependencies by using Daegalus wine-builder, which worked like magic.

This worked!!

With only a handful of commands, wine has successfully been built. No messing around with dependencies.

I installed wine-builder by running the installation command from the repo:

podman pull ghcr.io/daegalus/wine-builder

I then downloaded ElementalWarrior's wine fork:

git clone https://gitlab.winehq.org/ElementalWarrior/wine.git ElementalWarrior-wine
git checkout affinity-photo2-wine87

I changed directory into the directory "ElementalWarrior-wine" and ran:

podman run -v ./:/wine-builder/wine-src:Z wine-builder

(Note: the :Z was needed for Fedora, but isn't needed for other distros. Check the wine-builder readme)

The build completed without errors. Thanks so much @Daegalus for building this tool. Now to see if I can get Affinity to run with the rest of ElementalWarrior's guide!

[azuredusk10]

I'm having some trouble installing dotnet48 with winetricks.

This is the command I ran from the guide (replacing $HOME with the absolute path):

rum ElementalWarrior-[version] $HOME/.wineAffinity winetricks dotnet48 corefonts

This is the final output I got in the terminal:

Executing load_winxp 
Executing wine winecfg -v winxp64
------------------------------------------------------
warning: Running /usr/bin/wineserver -w. This will hang until all wine processes in prefix=/home/chriswood/.wineAffinity terminate
------------------------------------------------------
Executing cd /home/chriswood/.cache/winetricks/dotnet40
Executing wine dotNetFx40_Full_x86_x64.exe
002c:fixme:winediag:LdrInitializeThunk wine-staging 8.6 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0024:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
010c:err:environ:init_peb starting L"Y:\\dotnet40\\dotNetFx40_Full_x86_x64.exe" in experimental wow64 mode
010c:err:module:load_wow64_ntdll failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
Application could not be started, or no application associated with the specifie
d file.
ShellExecuteEx failed: Internal error.

------------------------------------------------------
warning: Note: command wine dotNetFx40_Full_x86_x64.exe returned status 1. Aborting.

There were lots of warnings about using a 64-bit WINEPREFIX before that.

Any ideas what I could try next?

[Kastas]

10 minutes ago, azuredusk10 said:

I'm having some trouble installing dotnet48 with winetricks.

...

Any ideas what I could try next?

Yes, looks familiar.

Additionally I installed Wine from Software.

 

[Wanesty]

1 hour ago, azuredusk10 said:

There were lots of warnings about using a 64-bit WINEPREFIX before that.

Winetricks does that a lot, it's not really too relevant nowadays tho

maybe installing mono when it propose you to could help if you haven't done it, otherwise just delete the prefix and try again i guess, maybe check for errors in the configuration/build output

[azuredusk10]

2 hours ago, Kastas said:

Yes, looks familiar.

Additionally I installed Wine from Software.

 

Thanks for the tip. I found that installing wine from Software didn't solve the problem, but installing via the command line did for some reason on my Fedora 38 Framework laptop.

sudo dnf install wine

dotnet48 now successfully installs using winetricks.

When I go to run an exe installer file though, e.g. affinity-photo-msi-2.1.0.exe, an empty window appears:

This is the end of the terminal output a few seconds after opening:

0118:fixme:wbemprox:class_object_QueryInterface interface {00000144-0000-0000-c000-000000000046} not implemented
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDE0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDD8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDD8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDB0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDA0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDA0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0134:err:d3d:wined3d_context_gl_update_window Failed to get a device context for window 0093EB50.

Nothing happens for about 3 minutes, and then the terminal goes crazy with about 15 lines appearing every second. Here's what I managed to copy + paste. The fans on my laptop ramp up to maximum at this point.

0118:fixme:wbemprox:class_object_QueryInterface interface {00000144-0000-0000-c000-000000000046} not implemented
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDE0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDD8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDD8, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDB0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDA0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0118:fixme:ole:thread_context_callback_ContextCallback 01433B54, 019C81F0, 0068DDA0, {d7174f82-36b8-4aa8-800a-e963ab2dfab9}, 2, 00000000
0134:err:d3d:wined3d_context_gl_update_window Failed to get a device context for window 0093EB50.
0140:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet
0138:fixme:thread:NtQueryInformationThread ThreadIsIoPending info class not supported yet

Is this expected behaviour, or should I see something in the Affinity Photo window?

[Larry3d]

15 hours ago, azuredusk10 said:

This worked!!

With only a handful of commands, wine has successfully been built. No messing around with dependencies.

I installed wine-builder by running the installation command from the repo:

podman pull ghcr.io/daegalus/wine-builder

I then downloaded ElementalWarrior's wine fork:

git clone https://gitlab.winehq.org/ElementalWarrior/wine.git ElementalWarrior-wine
git checkout affinity-photo2-wine87

I changed directory into the directory "ElementalWarrior-wine" and ran:

podman run -v ./:/wine-builder/wine-src:Z wine-builder

(Note: the :Z was needed for Fedora, but isn't needed for other distros. Check the wine-builder readme)

The build completed without errors. Thanks so much @Daegalus for building this tool. Now to see if I can get Affinity to run with the rest of ElementalWarrior's guide!

Hi,

I'm trying to install Affinity Photo 1.10.6 using Wine on my system, but I'm encountering error messages. My operating system is Fedora 38. Here is the command I used:

rum ElementalWarrior-8.3 "/home/larry/.WineAffinity" wine "/home/larry/Downloads/affinity/affinity-photo-1.10.6.exe"

The error messages I'm receiving are as follows:

002c:err:wineboot:process_run_key Error running cmd L"C:\windows\system32\winemenubuilder.exe -a -r" (126). 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0024:fixme:imm:ImeSetActiveContext himc 00010054, flag 0x1 stub! 00cc:fixme:imm:ImeSetActiveContext himc 0000000000010026, flag 0 stub! 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 22E3FE98

I would greatly appreciate if someone could assist me in resolving this issue. Thank you in advance!

 

[Wanesty]

19 hours ago, azuredusk10 said:

Is this expected behaviour, or should I see something in the Affinity Photo window?

did you copied the WinMetadata files ?

are your opengl/vulkan drivers installed/up to date ?

did you run the installer with rum and in the right wineprefix ?

is your wineprefix version to win10 or win11 ?

 

if yes to all of them maybe try to swap the renderer to vulkan or opengl as mentioned : here

 

also the some(most) fixme errors are often just warns and can be ignored if you don't see them causing issues directly

[azuredusk10]

17 hours ago, Wanesty said:

did you copied the WinMetadata files ?

are your opengl/vulkan drivers installed/up to date ?

did you run the installer with rum and in the right wineprefix ?

is your wineprefix version to win10 or win11 ?

 

if yes to all of them maybe try to swap the renderer to vulkan or opengl as mentioned : here

 

also the some(most) fixme errors are often just warns and can be ignored if you don't see them causing issues directly

Yep, I coped the WinMetadata files in 2 places to be sure:

drive_c/windows/system32/WinMetadata

and

drive_c/Windows/System32/WinMetadata

I updated all packages on my system. Opengl and vulkan are installed and working.

I used the .wineAffinity prefix and opened the installer via rum

And the wineprefix version is set to win11

Swapping the renderer didn't help unfortunately.

Interestingly, if I abort the wine process in the terminal with Control + C and then repeat the command, I get a second window that appears and says "The installer is already opened". So the installer is definitely running, it's just not visible!

 

I think I'll stop things here. I've found that Inkscape has come a long way since I last tried it and Inkscape + Scribus now fill my needs well enough there as a freelance web designer.

Thanks very much for your support and if there's anything I can do to help debug or test things, I'll keep an eye on this thread!

[Wollhut]

ok so i found some time and tried this. I'm on fedora 38 so i also had the dependency problems. I then used the builder from Daegalus and compiled wine. Didn't get any errors so i guess it works, thank you so much for that! Before i tried it i unsurprisingly got stuck in dependency hell. Anyway now I'm stuck at the part where i should use rum to create a wineprefix. When I do this part i get stuck (i made the path absolute and used 8.3 as instead of [version]):

rum ElementalWarrior-[version] $HOME/.wineAffinity wineboot --init

This is what the terminal shows:

Wine prefix doesn't exist, do you want to create it? [Y/n] 
Rumming /opt/wines/ElementalWarrior-8.3 (wine-8.7) in: /home/myusername/.wineAffinity
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
004c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0054:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0054:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0054:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0054:err:ole:start_rpcss Failed to open RpcSs service
004c:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
004c:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
004c:err:ole:apartment_get_local_server_stream Failed: 0x80004002
004c:fixme:imm:ImeSetActiveContext himc 000000000001002C, flag 0 stub!
002c:fixme:imm:ImeSetActiveContext himc 000000000001004A, flag 0x1 stub!
0090:fixme:file:NtLockFile I/O completion on lock not implemented yet
0090:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
00a0:fixme:imm:ImeSetActiveContext himc 0000000000010088, flag 0x1 stub!
0090:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
0090:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
00f4:fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
011c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
011c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
011c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
011c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
wine: configuration in L"/home/myusername/.wineAffinity" has been updated.
0154:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
[myusername@fedora bin]$ 004c:err:ole:start_rpcss Failed to start RpcSs service
0170:err:rpc:I_RpcReceive we got fault packet with status 0x1c010003
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" failed to start: 1053
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 1115
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"winebus" failed to start: 1115
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"PlugPlay" failed to start: 1115
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"Eventlog" failed to start: 1115
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"nsiproxy" failed to start: 1115
0164:fixme:service:scmdatabase_autostart_services Auto-start service L"NDIS" failed to start: 1115

It gets stuck on the last line and stops eventually, letting me potentially type new commands.

Any help would be appreciated as this is way out of my skillset.

Could it help if I tried the bottles guide from here instead?

[Kastas]

2 minutes ago, Wollhut said:

...

Any help would be appreciated as this is way out of my skillset.

...

Same happens to me on Fedora. I just ignore it and proceed with next command. All Affinity apps work after.

[Wollhut]

30 minutes ago, Kastas said:

Same happens to me on Fedora. I just ignore it and proceed with next command. All Affinity apps work after.

Thanks, i tried this and the next step with dotnet48 worked. Sadly when i tried this:

rum ElementalWarrior-8.3 $HOME/.wineAffinity wine winecfg -v win11

i got this:

Rumming /opt/wines/ElementalWarrior-8.3 (wine-8.7) in: /home/myusername/.wineAffinity
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (126).
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005

and when i tried installing publisher I'm having the same issues as azuredusk10  mentioned having a window that is empty. I tried it with both renderers, opengl and vulkan but I had the same issue on both.

[Wanesty]

12 hours ago, Wollhut said:

It gets stuck on the last line and stops eventually, letting me potentially type new commands.

yea it's expected behavior, if it doesn't give you actual errors and you can proceed with the next steps without errors then it's all fine !

 

11 hours ago, Wollhut said:

0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005

i don't believe those warns (fixme =/= err) are causing issue by themselves, however it's weird that the affinity installer does not render.

so same questions as :

but also did you tried to install a .exe or a .msix ? (only the exe(msi in a exe wrapper) are supported on wine currently)

edit for more info :
try restarting the wineserver by killing it after changing the version or when affinity freeze, commands here

Edited June 9, 2023 by Wanesty

[Wollhut]

19 hours ago, Wanesty said:

 

Yes, i checked the drivers before i tried switching them but i had the same issue with either one of them. I also copied the WinMetadata folder with its files into the system32 folder.

19 hours ago, Wanesty said:

but also did you tried to install a .exe or a .msix ? (only the exe(msi in a exe wrapper) are supported on wine currently)

edit for more info :
try restarting the wineserver by killing it after changing the version or when affinity freeze, commands here

Thanks for the tip with restarting the wineserver, sadly it did not work with that.

I installed from the .exe files so this should not be the issue as well.

Since the window appears and just doesn't render i'm guessing the problem is not on the rum side but rather has something to do with wine or the .exe file, right? I could only get the 2.1.0 files maybe if i find the 2.0.4 installers it could work better. <-- didn't work

Also i tried it with wine 8.3 and not 8.7 so this will be something I'll try in the future.

If that doesn't work my only other idea would be to compile wine manually, but i will propably not be able to manouver myself through dependency hell successfully.

If anyone got ideas what i else i could do i would be happy to try it.

I'm already glad I got this far with the help of you guys because i feel like i already learned a lot by doing this stuff.

 

[Wanesty]

1 hour ago, Wollhut said:

If that doesn't work my only other idea would be to compile wine manually

i haven't look at it from too close but you can probably build the 8.7 branch with Daegalus 's docker !

also if you use discord regularly, have time available and if you want to, send me a dm here so we can try to troubleshoot stuff in voice chat !

Edited June 9, 2023 by Wanesty

[Wollhut]

19 hours ago, Wanesty said:

i haven't look at it from too close but you can probably build the 8.7 branch with Daegalus 's docker !

also if you use discord regularly, have time available and if you want to, send me a dm here so we can try to troubleshoot stuff in voice chat !

Ok i tried it with the 8.7 branch, it worked just as good as 8.3 but sadly i had the exact same issue with the installer not rendering. 
I probably won’t find time for the next 2 months but when I’m getting back i will gladly send you a dm so we can troubleshoot in voice chat

[azuredusk10]

Sounds like the same problem I had. I’ll have some free time in a couple of weeks and am happy to troubleshoot it over discord voice chat @Wanesty