Affinity Suite V2 on Linux [ Wine ]

[Wanesty]

10 hours ago, Meteo said:

I discovered that Designer runs in a Bottles with the wine-ge-proton8-8 runner

oh this is pog imma gave to give it a go :)

 

[MrSojek]

On 6/29/2023 at 11:31 PM, Wanesty said:

it look like it cannot access the microsoft store to check the price, look at the console logs it's probably something like that.

maybe try different WinMetadata files and/or try deleting your prefix and starting over from the Setting up your Wineprefix part

(a screenshot of a random bottle that have mshtml disabled)

It does this to prevent wine to try and reinstall mono after you uninstalled it manually.

Thank you for the suggestion but I only have mscoree available in my Libraries tab.
I also tried WinMetadata files from both win 10 and 11 with no luck.

[ElementalWarrior]

3 hours ago, MrSojek said:

Thank you for the suggestion but I only have mscoree available in my Libraries tab.
I also tried WinMetadata files from both win 10 and 11 with no luck.

That libraries tab is not about "available" it's about specifying overrides. IE using a native version, or a wine version.

[MrSojek]

configure: MinGW compiler not found, cross-compiling PE files won't be supported.
configure: libXxf86vm 64-bit development files not found, XFree86 Vidmode won't be supported.
configure: libOSMesa 64-bit development files not found (or too old), OpenGL rendering in bitmaps won't be supported.
configure: OpenCL 64-bit development files not found, OpenCL won't be supported.
configure: pcap 64-bit development files not found, wpcap won't be supported.
configure: libpcsclite not found, smart cards won't be supported.
configure: libsane 64-bit development files not found, scanners won't be supported.
configure: libusb-1.0 64-bit development files not found (or too old), USB devices won't be supported.
configure: libv4l2 64-bit development files not found.
configure: libgphoto2 64-bit development files not found, digital cameras won't be supported.
configure: libgphoto2_port 64-bit development files not found, digital cameras won't be auto-detected.
configure: gstreamer-1.0 base plugins 64-bit development files not found, GStreamer won't be supported.
configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported.
configure: libudev 64-bit development files not found, plug and play won't be supported.
configure: libSDL2 64-bit development files not found, SDL2 won't be supported.
configure: libcapi20 64-bit development files not found, ISDN won't be supported.
configure: libcups 64-bit development files not found, CUPS won't be supported.
configure: libkrb5 64-bit development files not found (or too old), Kerberos won't be supported.
configure: libnetapi not found, Samba NetAPI won't be supported.

configure: WARNING: libgnutls 64-bit development files not found, no schannel support.

configure: Finished.  Do 'make' to compile Wine.

At the end of configuring ElementalWarrior-wine, is any of the things above should be supported?

[Wanesty]

On 7/2/2023 at 12:38 AM, ElementalWarrior said:

it's about specifying overrides

i struggled a bit trying to understand this because nowhere i read it from was clear enough :

Builtin is falling back to the wine global install

Native is reading the DLLs in the executable's directory then in the executable's prefix (it's system32 for exemple)

 

8 hours ago, MrSojek said:

is any of the things above should be supported?

your answer is in the dependency documentation !

but yes, here you'll most likely want libOSMesa, OpenCL and the last warning "libgnutls 64-bit development files"

if you have a good enough CPU and the compiling isn't taking too long, i'd suggest you try using it as is, and if it doesn't work, come back to the compile steps :)

EDIT : if this is the 32bits configuration you're probably fine ignoring them

[Grunt]

On 5/26/2023 at 10:00 AM, Kastas said:

Commonly, at the point of installing exe, I get:

 

Ok, so right now I'm struggling with Debian and finally I feel the pain 😆

But to answer this issue: If you ever encounter missing .NET3.5 when installing any Affinity App and you're scratching your head what the hell, then answer is simple.

On some binary distributions (Debian to name one, but I guess Fedora isn't much better) there is no Mono in standard repository. It's just vanilla Wine and nothing more. So installer is missing even basic functions implemented in dotNET. Simply follow Debian Wine guide and find binary package and if it crashes (because why not?) as in my case, download binary archive and unpack it to appropriate destination manually. I'm not sure if Mono is required later, but just to be able get installer running, there is need to have Mono installed.

Of course, don't forget to set Winver to Win10/Win11 and to install set of 32-bit libraries (almost over 1GB in my case). I've been asked for missing libGL.so.1 and as bonus in my case for libnvidia-glvkspirv (nVidia vulkan translator to something)

$ wine affinity-photo-beta-2.1.1.exe 
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
0130:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0130:fixme:nls:GetFileMUIPath stub: 0x10, L"C:\\windows\\system32\\tzres.dll", (null), 0057DA98, 0035DCA0, 0057DA9C, 0057DA90
0130:fixme:nls:GetFileMUIPath stub: 0x10, L"C:\\windows\\system32\\tzres.dll", (null), 0057DA98, 0035DCA0, 0057DA9C, 0057DA90
0130:fixme:nls:GetFileMUIPath stub: 0x10, L"C:\\windows\\system32\\tzres.dll", (null), 0057DA98, 0035DCA0, 0057DA9C, 0057DA90
0140:fixme:wbemprox:wbem_locator_ConnectServer authentication not supported
0140:fixme:wbemprox:wbem_locator_ConnectServer specific locale not supported
0140:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
0130:fixme:file:NtLockFile I/O completion on lock not implemented yet
0130:fixme:msg:ChangeWindowMessageFilter c04e 00000001
0130:fixme:dwmapi:DwmAttachMilContent (00010070) stub
0144:fixme:gdi:GdiEntry13 stub
The NVIDIA driver was unable to open 'libnvidia-glvkspirv.so.525.116.04'.  This library is required at run time.

The NVIDIA driver was unable to open 'libnvidia-glvkspirv.so.525.116.04'.  This library is required at run time.

0144:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (00000001): monitor setting ignored
0144:fixme:d3d:wined3d_check_device_format_conversion output 00CD3D18, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8X8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub!
0130:fixme:shell:SHGetStockIconInfo (77, 0x101, 0057E760) semi-stub
0130:fixme:shell:SHGetStockIconInfo flags 0x101 not implemented

This issue is again very simple. As Mono is requesting 32-bit libraries you need libGLX and affiliated libs in 32-bit version too. Just to be able to install Affinity apps.

Maybe it will work with dotNET3.5 or dotNET4 or I really I'm not sure what is basic version but as I wasn't able to install Microsoft proprietary dotNET, I had to proceed with Mono and it worked. Hope this helps someone in future.

[Grunt]

And to sum things up:

I finally get the gist of sand-boxing wine into bottle, using containers, etc. Correct me if I'm wrong but there is shared WoW64 to blame. I think, I get it now.

  

On 6/13/2023 at 9:11 AM, Rafael Brucart said:

Prob stupid question. Did Wine 8.10 finish PE conversion? and is the goal of PE meant so you only have to build 64bit wine yet still run 32bit applications; in other words no reliance on building 32bit wine? or have a misunderstood?

And you were right. There is actually experimental WoW64 component/mode "thunking" 32-bit AP calls directly into 64-bit outputs/64-bit Linux calls. And it seems to work. I can't rule out non-intentional lib32 binding (as libraries are in place) but personally, I didn't have to build one line of 32-bit Wine code. Just ./configure --enable-win64 --enable-archs=i386,x86_64 --prefix=/opt/wine in wine-8.11-145-g884cff82148 straight from git. More details tomorrow in near future.

On 6/27/2023 at 1:04 AM, Rafael Brucart said:

Also it maybe worth considering you're on a graphics design forum (not a linux forum) for software that doesn't supply a native Linux installer. What you consider simple can be challenging for others like myself who are not the greatest with the terminal but would rather spend hours in a struggle than stay with a working Microsoft Windows.

And again you're right. Maybe reason why I would like to discuss further progress more broadly.

 

[Wanesty]

16 hours ago, Grunt said:

On some binary distributions (Debian to name one, but I guess Fedora isn't much better) there is no Mono in standard repository. It's just vanilla Wine and nothing more. So installer is missing even basic functions implemented in dotNET. Simply follow Debian Wine guide and find binary package and if it crashes (because why not?) as in my case, download binary archive and unpack it to appropriate destination manually. I'm not sure if Mono is required later, but just to be able get installer running, there is need to have Mono installed.

why install affinity before mono/dotnet ? why wouldn't just install dotnet48 with winetricks ?

does dotnet itself need mono for the installer to work ?

genuinely confused here ahah-

[Grunt]

@Wanesty: dotnet48 already installed.

Never encountered this bug on Arch Linux but on Debian first thing you're going to see is Affinity Photo/Designer/Publisher Setup requesting .NET 3.5 because it thinks it is disabled in Windows Features app. No idea why. There is of course possibility to install dotnet35 in winetricks but I haven't been successful so Mono is it.

[Wollhut]

Thanks for all the help in with this, I'm amazed the way everyone is doing their best to help and find solutions. I finally got it running.

Sadly for me the vulkan renderer runs very smooth but doesn't render the window for creating a new document which means i can't use it except if i use a VD which brings other problems. The gl renderer shows all the windows but has way more visual glitches.

I seem to be so close, yet so far away. I feel like it would be easier switch to arch and reinstall everything i have on there than it is trying to get it running smoothly on my fedora install right now. So i guess ill leave it here for now and try the arch install on my second hard drive if I find the time.

Thanks again for all the help!

[Wanesty]

53 minutes ago, Wollhut said:

So i guess ill leave it here for now and try the arch install on my second hard drive if I find the time.

exactly what i was about to advise you ahah

54 minutes ago, Wollhut said:

Sadly for me the vulkan renderer runs very smooth but doesn't render the window for creating a new document which means i can't use it except if i use a VD which brings other problems. The gl renderer shows all the windows but has way more visual glitches.

and yes depending on the version of affinity you might have to play with the renderer settings to find one that is the most usable for you

[Grunt]

2 hours ago, Wollhut said:

Sadly for me the vulkan renderer runs very smooth but doesn't render the window for creating a new document

Check in console please for message:

Application requires child window rendering, which is not implemented yet!

It shouldn't be there. WINED3D can handle child window rendering.

[Wollhut]

3 hours ago, Grunt said:

Check in console please for message:

Application requires child window rendering, which is not implemented yet!

It shouldn't be there. WINED3D can handle child window rendering.

Ok i checked, since i'm fairly new to this i'm not sure if i looked in the right place. I started the program via console and then looked at it while affinity was running. The console is mainly outputting fixme errors, nothing about child window handling though.

[Wanesty]

On 7/5/2023 at 7:25 PM, Grunt said:

Application requires child window rendering, which is not implemented yet!

are you sure this is not about the wayland implementation ?

i've never seen this error

[Grunt]

@Wanesty, @Wollhut: If no new document can be created and otherwise entire UI works fine it's either problem with DirectX11 or child window rendering as canvas is created as DX11 surface embedded into UI through child window rendering. Simply watch your console, there should be more info about what's wrong.

 

On 7/3/2023 at 11:47 PM, Grunt said:

More details tomorrow in near future.

And to elaborate more on this topic…we had little private discussion and I came to conclusion: I'm more than 90% sure there is no need to compile Wine in two-pass manner. Affinity suite should work just only with 64-bit version compiled. Therefore no i386 (32-bit) dependencies, no multi-lib or extra i386 repositories needed to comply.

Procedure is simple: git clone most recent version, apply patches, build Wine (without shared WoW64), install it along with dotnet48, WinMetafiles and all corefonts and it should work.

There are two ways to prepare Wine:

• ./configure --enable-win64 - not preferred way of building Wine producing pure wine64, capable running only 64-bit EXE and DLLs. No underling 32-bit DLL ecosystem. Surprisingly if you want and manage to prepare wineprefix manually, Affinity (at least Photo) should be able to boot and carry on. I don't know how but if you want see screenshots, I'm happy to provide.
• ./configure --enable-win64 --enable-archs=i386,x86_64 - preferred and better way. This way x86_64 and i386 DLL libraries will be prepared (without need for 32-bit dependencies, just libc6-i386 I think) and executed in "experimental wow64 mode". This way should be possible to install dotnet40, dotnet48 and maybe even execute Affinity Setup program (EXE). Wine is able to execute 32-bit binaries and translate calls into 64-bit Linux calls in this mode.

Unfortunately, you're very likely to encounter problems. dotNET, winetricks and even EXE installer are reliant on 32-bit API. Share bugs and possible solutions in this thread please. Affinity EXE setup is actually PE32 Intel 80386 (GUI) executable. If you can't install Affinity there are possible ways around:

• Install Affinity elsewhere, pack Affinity folder into archive (tar.bz2, zip) and extract to prepared wineprefix. Least painful and works.
• Extract MSIX installer. Don't ask me how, ask Wanesty. I don't know anything about MSIX.
• 32-bit EXE installer is only self-packed GUI installer with some salt. Upon execution is unpacked into C:\User\yourusername\Temp\AffinitySetup\UID (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). There is SetupUI (PE32 executable (GUI) Intel 80386 Mono/.Net assembly), some language DLLs and Affinity.msi. Affinity.msi is platform independent installer, so simply extract/copy elsewhere and run it with wine msiexec /i Affinity.msi . End result should be Publisher/Designer/Photo installed.

This way should be possible to prepare Wine for any (binary) Linux distribution. Just tested Debian but I believe it shouldn't have been problem on Fedora, OpenSuSE, maybe even Ubuntu derivatives and flavors.

And one tip: Always have proper general Wine prepared as backup. For Debian I can recommend Debian WineHQ Repository. And rum/bottles, I guess.

[Wanesty]

10 hours ago, Grunt said:

Extract MSIX installer. Don't ask me how, ask Wanesty. I don't know anything about MSIX.

.msix are basically just ZIP archives with metadata files, kinda like .deb files are.

this is the content of "affinity-publisher-2.0.4.msix" :

The App folder contain the files that should go into your $USER/.wineAffinity/drive_c/Program Files/Affinity/Publisher 2

(since the example above is Publisher, the App folder should be renamed to Publisher 2).

10 hours ago, Grunt said:

This way should be possible to prepare Wine for any (binary) Linux distribution. Just tested Debian but I believe it shouldn't have been problem on Fedora, OpenSuSE, maybe even Ubuntu derivatives and flavors.

to clarify : the major issue peoples have been having were caused by their distribution not distributing i386 dependencies correctly.

this is because most linux distro are deprecating 32bits/x86 way faster than windows is

 

So using the experimental wow64 build added in wine 8.0  would resolve the build related issues peoples are having on fedora and ubuntu.

from wine's 8.0 announcement post :

*** WoW64

- WoW64 thunks are implemented for essentially all Unix libraries, enabling a
  32-bit PE module to call a 64-bit Unix library. Once the remaining direct
  PE/Unix calls have been removed, this will make it fully possible to run
  32-bit Windows applications without any 32-bit Unix library.

- When the 32-bit Wine loader isn't found, 32-bit applications are started in
  the new experimental "Windows-like" WoW64 mode (where 32-bit code runs inside
  a 64-bit host process). This mode can be enabled by building with the
  '--enable-archs' configure option. This is still under development and not yet
  recommended for general use. Since in case of configuration errors it is
  possible for it to be triggered inadvertently, applications started in this
  mode print the warning "starting in experimental wow64 mode".

THIS IS AN EXPERIMENTAL FEATURE

it is not perfectly implemented yet but as @Grunt said, affinity seem to use 32bits instruction only for the installer, so if you encounter issues with the exe installer try to use the aforementioned msix install.

11 hours ago, Grunt said:

And one tip: Always have proper general Wine prepared as backup. For Debian I can recommend Debian WineHQ Repository. And rum/bottles, I guess.

this is also the case if your distro package Wine Mono as well, having it install systemwide will allow your custom build to create the prefix with mono preinstalled (not mandatory as we're replacing it with dotnet48 but it could help avoid some random issues

 

11 hours ago, Grunt said:

./configure --enable-win64 --enable-archs=i386,x86_64 - preferred and better way. This way x86_64 and i386 DLL libraries will be prepared (without need for 32-bit dependencies, just libc6-i386 I think) and executed in "experimental wow64 mode". This way should be possible to install dotnet40, dotnet48 and maybe even execute Affinity Setup program (EXE). Wine is able to execute 32-bit binaries and translate calls into 64-bit Linux calls in this mode.

i'll try this on my side, figure out a good workflow and edit the guide accordingly in the next few days for newcomers (as every info is already in this and Grunt's post)

[edg22]

Just a couple of updates:

• Using Vulkan in my case drop all the flashing and rendering issues to 0, but to use it I have to also activate the VD
• exporting works without crashing for formats that dont need rasterization (PDF/SVG/EPS), as my workflow needs a lot of individual exporting, before was a deal breaker, now i export as svg and then use Utilso (or any image converter) to get the files to the final format, not perfect but usable

[linohix334]

I am trying to install Affinity 2.1.1 following instructions.

When run installer it's start and after click install get following error:

[ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object
  at SetupUI.MainWindow.OnOperationUpdated (SetupUI.NotificationEventArgs args) [0x000e8] in <3201e8fa1daa452d9c1e28c30bcc4581>:0 
  at SetupUI.MainWindow.<OnLoaded>b__16_0 (SetupUI.NotificationEventArgs args) [0x00000] in <3201e8fa1daa452d9c1e28c30bcc4581>:0 
  at SetupUI.App.OnOperationUpdated (SetupUI.NotificationEventArgs args) [0x0000b] in <3201e8fa1daa452d9c1e28c30bcc4581>:0 
  at SetupUI.App.<StartOperation>b__69_0 (SetupUI.NotificationEventArgs args) [0x00000] in <3201e8fa1daa452d9c1e28c30bcc4581>:0 
  at SetupUI.Operation+<>c__DisplayClass3_0.<NotifyUpdated>b__0 () [0x0001d] in <3201e8fa1daa452d9c1e28c30bcc4581>:0 
  at System.Windows.Threading.ExceptionWrapper.InternalRealCall (System.Delegate callback, System.Object args, System.Int32 numArgs) [0x00067] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.ExceptionWrapper.TryCatchWhen (System.Object source, System.Delegate callback, System.Object args, System.Int32 numArgs, System.Delegate catchHandler) [0x00004] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.WrappedInvoke (System.Delegate callback, System.Object args, System.Int32 numArgs, System.Delegate catchHandler) [0x00001] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.DispatcherOperation.InvokeImpl () [0x00099] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext (System.Object state) [0x00008] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper (System.Object obj) [0x0001d] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 
  at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 
  at MS.Internal.CulturePreservingExecutionContext.Run (MS.Internal.CulturePreservingExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00047] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.DispatcherOperation.Invoke () [0x00016] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.ProcessQueue () [0x00114] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.WndProcHook (System.IntPtr hwnd, System.Int32 msg, System.IntPtr wParam, System.IntPtr lParam, System.Boolean& handled) [0x00061] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at MS.Win32.HwndWrapper.WndProc (System.IntPtr hwnd, System.Int32 msg, System.IntPtr wParam, System.IntPtr lParam, System.Boolean& handled) [0x0003a] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at MS.Win32.HwndSubclass.DispatcherCallbackOperation (System.Object o) [0x00042] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.ExceptionWrapper.InternalRealCall (System.Delegate callback, System.Object args, System.Int32 numArgs) [0x000c6] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.ExceptionWrapper.TryCatchWhen (System.Object source, System.Delegate callback, System.Object args, System.Int32 numArgs, System.Delegate catchHandler) [0x00004] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.WrappedInvoke (System.Delegate callback, System.Object args, System.Int32 numArgs, System.Delegate catchHandler) [0x00001] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0
  at System.Windows.Threading.Dispatcher.LegacyInvokeImpl (System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, System.Object args, System.Int32 numArgs) [0x000fc] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.Invoke (System.Windows.Threading.DispatcherPriority priority, System.Delegate method, System.Object arg) [0x00011] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at MS.Win32.HwndSubclass.SubclassWndProc (System.IntPtr hwnd, System.Int32 msg, System.IntPtr wParam, System.IntPtr lParam) [0x00154] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at (wrapper native-to-managed) MS.Win32.HwndSubclass.SubclassWndProc(intptr,int,intptr,intptr)
  at (wrapper managed-to-native) MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG&)
  at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage (System.Windows.Interop.MSG& msg) [0x0001a] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.PushFrameImpl (System.Windows.Threading.DispatcherFrame frame) [0x0004c] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.PushFrame (System.Windows.Threading.DispatcherFrame frame) [0x00077] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Threading.Dispatcher.Run () [0x00006] in <0c2ea07c5159415f97fb3ecb6b4aafeb>:0 
  at System.Windows.Application.RunDispatcher (System.Object ignore) [0x00023] in <f8fc562f7d244f8692d61d7bd2917f68>:0 
  at System.Windows.Application.RunInternal (System.Windows.Window window) [0x0010d] in <f8fc562f7d244f8692d61d7bd2917f68>:0 
  at System.Windows.Application.Run (System.Windows.Window window) [0x00008] in <f8fc562f7d244f8692d61d7bd2917f68>:0 
  at System.Windows.Application.Run () [0x00009] in <f8fc562f7d244f8692d61d7bd2917f68>:0 
0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 231FFEAC

 

[linohix334]

Quote

The App folder contain the files that should go into your $USER/.wineAffinity/drive_c/Program Files/Affinity/Publisher 2

(since the example above is Publisher, the App folder should be renamed to Publisher 2).

I tried this way too. But then I get different error when try to run Affinity Photo:

00d0:err:winediag:wined3d_dll_init Using the Vulkan renderer.
00d0:err:mscoree:FixupVTableEntry unsupported vtable fixup flags 0
* Assertion at /vagrant/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not set up parent class, due to: Could not load type of field 'Serif.Affinity.Application:<CurrentMicrosoftStorePrices>k__BackingField' 
(20) due to: Could not load file or assembly 'Windows.Services.Store.StoreContract, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:C:\Program Files\Affinity\Photo 2\Serif.Affinity.dll type:Application member:(null) as
sembly:C:\Program Files\Affinity\Photo 2\Photo.exe type:Application member:(null)

 

[Wanesty]

49 minutes ago, linohix334 said:

(20) due to: Could not load file or assembly 'Windows.Services.Store.StoreContract, Version=4.0.0.0,

did you copy the WinMetadata folder ? 👁️👁️

[siwela3573]

Yes, WinMetadata is copied from Windows 10.

Edited July 19, 2023 by siwela3573

[Grunt]

On 7/5/2023 at 10:36 PM, Wollhut said:

Ok i checked, since i'm fairly new to this i'm not sure if i looked in the right place. I started the program via console and then looked at it while affinity was running. The console is mainly outputting fixme errors, nothing about child window handling though.

So back to this bug: Encountered and solved. You have to install corefonts because Affinity is checking font presence when creating new document. If corefonts are not installed result is crash:

0024:err:eventlog:ReportEventW L"Application: Designer.exe\n"
0024:err:eventlog:ReportEventW L"Framework Version: v4.0.30319\n"
0024:err:eventlog:ReportEventW L"Description: The application requested process termination through System.Environment.FailFast(string message).\n"
0024:err:eventlog:ReportEventW L"Message: Unrecoverable system error.\n"
0024:err:eventlog:ReportEventW L"Stack:\n"
0024:err:eventlog:ReportEventW L"   at System.Environment.FailFast(System.String)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Shaping.TypefaceMap.MapUnresolvedCharacters(System.Windows.Media.TextFormatting.CharacterBufferRange, System.Globalization.CultureInfo, System.Globalization.CultureInfo, MS.Internal.FontFace.PhysicalFontFamily, Int32 ByRef, MS.Internal.SpanVector, Int32, Int32 ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Shaping.TypefaceMap.MapByFontFamilyList(System.Windows.Media.TextFormatting.CharacterBufferRange, System.Globalization.CultureInfo, System.Globalization.CultureInfo, System.Windows.Media.FontFamily[], MS.Internal.FontFace.PhysicalFontFamily ByRef, Int32 ByRef, MS.Interna"...
0024:err:eventlog:ReportEventW L"   at MS.Internal.Shaping.TypefaceMap.MapItem(System.Windows.Media.TextFormatting.CharacterBufferRange, System.Globalization.CultureInfo, MS.Internal.Span, MS.Internal.Generic.SpanVector`1<Int32> ByRef, Int32)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Shaping.TypefaceMap.GetShapeableText(System.Windows.Media.TextFormatting.CharacterBufferReference, Int32, System.Windows.Media.TextFormatting.TextRunProperties, System.Globalization.CultureInfo, Boolean, System.Collections.Generic.IList`1<MS.Internal.TextFormatting.TextS"...
0024:err:eventlog:ReportEventW L"   at MS.Internal.Shaping.GlyphingCache.GetShapeableText(System.Windows.Media.Typeface, System.Windows.Media.TextFormatting.CharacterBufferReference, Int32, System.Windows.Media.TextFormatting.TextRunProperties, System.Globalization.CultureInfo, Boolean, System.Collections.Generic.IList`1"...
0024:err:eventlog:ReportEventW L"   at System.Windows.Media.TextFormatting.TextCharacters.MS.Internal.TextFormatting.ITextSymbols.GetTextShapeableSymbols(MS.Internal.Shaping.GlyphingCache, System.Windows.Media.TextFormatting.CharacterBufferReference, Int32, Boolean, Boolean, System.Globalization.CultureInfo, System.Windo"...
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextStore.CreateTextLSRuns(MS.Internal.TextFormatting.TextRunInfo, System.Collections.Generic.IList`1<System.Windows.Media.TextEffect>, System.Globalization.CultureInfo, Int32, Int32, Int32, System.Windows.Media.TextFormattingMode, Boolean, Int32 ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextStore.CreateLSRuns(MS.Internal.TextFormatting.TextRunInfo, System.Collections.Generic.IList`1<System.Windows.Media.TextEffect>, System.Globalization.CultureInfo, Int32, Int32, Int32, System.Windows.Media.TextFormattingMode, Boolean, Int32 ByRef, Int32 "...
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextStore.CreateLSRunsUniformBidiLevel(MS.Internal.SpanVector, MS.Internal.SpanVector, Int32, Int32, Int32, Int32, System.Windows.Media.TextFormattingMode, Boolean, Int32 ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextStore.FetchLSRun(Int32, System.Windows.Media.TextFormattingMode, Boolean, MS.Internal.TextFormatting.Plsrun ByRef, Int32 ByRef, Int32 ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.LineServicesCallbacks.FetchRunRedefined(IntPtr, Int32, Int32, IntPtr, Char*, Int32, Int32 ByRef, Char* ByRef, Int32 ByRef, Int32 ByRef, MS.Internal.TextFormatting.LsChp ByRef, IntPtr ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.UnsafeNativeMethods.LoCreateLine(IntPtr, Int32, Int32, Int32, UInt32, IntPtr, MS.Internal.TextFormatting.LsLInfo ByRef, IntPtr ByRef, Int32 ByRef, MS.Internal.TextFormatting.LsLineWidths ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.UnsafeNativeMethods.LoCreateLine(IntPtr, Int32, Int32, Int32, UInt32, IntPtr, MS.Internal.TextFormatting.LsLInfo ByRef, IntPtr ByRef, Int32 ByRef, MS.Internal.TextFormatting.LsLineWidths ByRef)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Media.TextFormatting.TextFormatterContext.CreateLine(Int32, Int32, Int32, MS.Internal.TextFormatting.LineFlags, IntPtr, IntPtr ByRef, MS.Internal.TextFormatting.LsLInfo ByRef, Int32 ByRef, MS.Internal.TextFormatting.LsLineWidths ByRef)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextMetrics+FullTextLine.FormatLine(MS.Internal.TextFormatting.FullTextState, Int32, Int32, Int32, Int32, Int32, MS.Internal.TextFormatting.LineFlags, MS.Internal.TextFormatting.FormattedTextSymbols)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextMetrics+FullTextLine..ctor(MS.Internal.TextFormatting.FormatSettings, Int32, Int32, Int32, MS.Internal.TextFormatting.LineFlags)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextFormatterImp.FormatLineInternal(System.Windows.Media.TextFormatting.TextSource, Int32, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.Te"...
0024:err:eventlog:ReportEventW L"   at MS.Internal.TextFormatting.TextFormatterImp.FormatLine(System.Windows.Media.TextFormatting.TextSource, Int32, Double, System.Windows.Media.TextFormatting.TextParagraphProperties, System.Windows.Media.TextFormatting.TextLineBreak, System.Windows.Media.TextFormatting.TextRunCache)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.TextBlock.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.StackPanel.StackMeasureHelper(System.Windows.Controls.IStackMeasure, System.Windows.Controls.IStackMeasureScrollData, System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.StackPanel.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Decorator.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Documents.AdornerDecorator.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.MeasureOverrideHelper(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.MeasureOverride(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.UIElement.Measure(System.Windows.Size)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Interop.HwndSource.SetLayoutSize()\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.SetRootVisual()\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.SetRootVisualAndUpdateSTC()\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.SetupInitialState(Double, Double, Double, Double)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.CreateSourceWindow(Boolean)\n"
0024:err:eventlog:ReportEventW L"   at System.Windows.Window.ShowHelper(System.Object)\n"
0024:err:eventlog:ReportEventW L"   at Serif.Affinity.Application.RunSingleInstance()\n"
0024:err:eventlog:ReportEventW L"   at Designer.Application.Main(System.String[])\n"
0024:fixme:advapi:DeregisterEventSource (00000000CAFE4242) stub
0024:fixme:seh:RaiseFailFastException (0000000000418BC0, 0000000000418C60, 0) stub

I'm very thankful for this thread. Back in May/June I just scratched my head where do people even get this weird bugs? It is simple. On Arch all necessary dependencies are somehow already there so its simple PKGBUILD, one install and everything is running how it should. It is not so simple elsewhere. Be diligent and install all necessary dependencies. Best way to install Affinity? Don't run installer. Extract MSI and install affinity manually. UI Installer is another 32-bit dotNET application checking all crap. There is no need for this.

• Be sure proprietary graphical driver is loaded and running. No idea how good ATI/AMD is but on nVidia cards be sure there is not noveau module in kernel. It won't tell you. Everything appears in good shape but Affinity wont be able to boot and result will be crash. (Related to this bug)
• Be sure it's running on right GPU. Again, nothing will tell you but result will be weird behavior and crashes running Affinity on integrated GPU.
• dotnet48, corefonts, WinRT patch and WinMetafiles in place. Everything is hard dependency required in Affinity suite. It won' tell you something is missing, it simply crashes at some point. 

I haven't been successful with winetricks so I had to install all necessary things manually. Now I know it's possible to run Affinity on almost any distribution. Just be careful and install all dependencies. It might seem Affinity requires something special but actually it doesn't. Patches simply aren't in mainline Wine. To this point I don't need:

• 32-bit Wine and 32-bit -dev packages.
• winetricks
• bottles
• rum
• containers and sadbox

Everything can be done manually. But now I get it why some users just use these things. Good luck.

  

On 7/13/2023 at 9:50 PM, edg22 said:

• exporting works without crashing for formats that dont need rasterization (PDF/SVG/EPS), as my workflow needs a lot of individual exporting, before was a deal breaker, now i export as svg and then use Utilso (or any image converter) to get the files to the final format, not perfect but usable

Could you share please crash dump? (contents of the console little before final termination) Rasterization is done and picture is actually on the disk but it crashes afterwards. I'm just checking something.

 

And just as demonstration, after installation Affinity is no more checking Windows version so it's possible to run Photo on Windows7 mode:

At this point I can't recommend official installer. It's not usefull, but more problems than gain.

[siwela3573]

Tried today to copy folder from windows 11 also. I successfully run installer, but still cannot run software.

00d0:err:winediag:wined3d_dll_init Using the Vulkan renderer.
00d0:err:mscoree:FixupVTableEntry unsupported vtable fixup flags 0
* Assertion at /vagrant/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not set up parent class, due to: Could n
ot load type of field 'Serif.Affinity.Application:<CurrentMicrosoftStorePrices>k__BackingField' (20) due to: Could not load file or assembly 'Windows.Services.Store.S
toreContract, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:C:\Program Files\Affinity\Photo 2\Serif.Affinity.dll type:Ap
plication member:(null) assembly:C:\Program Files\Affinity\Photo 2\Photo.exe type:Application member:(null)

00d0:err:mscoree:expect_no_runtimes Process exited with a Mono runtime loaded.

 

Edited July 20, 2023 by siwela3573

[Wanesty]

13 hours ago, Grunt said:

Be sure proprietary graphical driver is loaded and running. No idea how good ATI/AMD is but on nVidia cards be sure there is not noveau module in kernel.

Mesa and AMDGPU are some of the best drivers i've encountered, you pretty much never need AMDGPU-PRO(amd's proprietary distributed of their driver)

 

however yes with Nvidia you will need the proprietary drivers to do pretty much anything, Nouveau is only a display driver it was never really developed further than just being able to display your desktop environment.

this is because of Nvidia only very recently releasing public documentation for their drivers and those are now in the work of being added to the linux kernel as a module but it's not really usable yet.

13 hours ago, Grunt said:

At this point I can't recommend official installer. It's not usefull, but more problems than gain.

it is in the guide because it seemed to be an meaningful step to be sure you did everything properly, if the installer displays you know it'll work.

but yea if none of the app use 32bit but the installer do i'll likely write to unzip the msix

 

8 hours ago, siwela3573 said:

00d0:err:mscoree:expect_no_runtimes Process exited with a Mono runtime loaded.

it seems you didn't uninstalled mono or you didn't installed dotnet48 correctly,
winetricks should be uninstalling mono automatically before installing dotnet48 btw

Edited July 20, 2023 by Wanesty
grammar

[Grunt]

Ok, so I can't test every distribution in the world but I should try at least Fedora Linux.

Final result:

Here are my notes:

Quote

$winecfg -> do not install mono
-winver Windows 10
$wine dotNetFx40_Full_x86_x64.exe //Install dotNET4.0
-winver Windows 7
$ wine ndp48-x86-x64-allos-enu.exe //Install dotNET4.8
//make sure mscoree.dll in system32 and syswow64 is native version, not Wine stub!

-winver Windows 10
-copy WinRT files
-extract corefonts.tar.gz //and install all corefonts:
$wine andale32.exe
$wine arialb32.exe
$wine arial32.exe
$wine comic32.exe
$wine courie32.exe
$wine georgi32.exe
$wine impact32.exe
$wine times32.exe
$wine trebuc32.exe
$wine verdan32.exe
$wine webdin32.exe
-install Display driver /* RPMFusion for Fedora based distros
and DO NOT FORGET to rebuild and _LOAD_ correct initramfs for your kernel! (spent few pointless hours on this issue) */

$ wine affinity-publisher-beta-2.2.0.exe //will need Mono or donNet3.5
 >or wine msiexec /i Affinity.msi
---------------------------------------------------------------------------
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
010c:fixme:file:NtLockFile I/O completion on lock not implemented yet
010c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0118:err:environ:init_peb starting L"C:\\windows\\syswow64\\msiexec.exe" in experimental wow64 mode
010c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
010c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5)
-------------------------------------------------------------------------
$ wine affinity-photo-beta-2.2.0.exe
 >or wine msiexec /i Affinity.msi
$ wine affinity-designer-beta-2.2.0.exe

// Disk space after complete installation:
// /dev/mmcblk0p3        32G   21G   12G  64% /
// 7.4G    .wine/drive_c
// 7.4G    .wine/
// 7.4G    total

-Switch to Vulkan or OpenGL
$ prime-run wine Publisher.exe/Designer.exe/Photo.exe

//Enjoy.

From my experience, installing on binary distribution like Fedora is the worst. Even if you know exactly what to do, you might get stuck. Distributions for experienced users like Arch/Gentoo are the simplest (if you know how to run makepkg, you really don't have to care about anything), Debian is OK (nice binary repo) and Fedora targeting unexperienced users is most complicated. But as you see, it can be done.

• I probably know what is the issue with missing dotNET3.5 even when dotNET(4.0/4.8) is installed. Initializing WINE_PREFIX, files ~/.wine/drive_c/windows/system32/mscoree.dll and ~/.wine/drive_c/windows/syswow64/mscoree.dll are created. These files are "Wine builtin DLL" and are protected. Installing dotNET48 won't be able to overwrite theses two files. Manually delete them, uninstall dotNET, repair installation and always be sure mscoree.dll isn't some Wine stub but is overwritten by installation and DLL's are proprietary. Installing and uninstalling Mono might do the work.
• What shall I do next? My initial idea was to create repository for some binary distribution and maintain binary packages, but:
  • Arch Linux/Manjaro/Gentoo - there isn't anything to maintain. There are recipes for packages (AUR/ebuild) and that's it. Nothing to maintain.
  • Debian - there is already very well maintained repository.  Just wait as WinRT is being already implemented into mainline Wine and final result will be nothing to maintain. In some time it might work just out of box.
  • Fedora - same thing. Is much bigger problem to set up GPU and wine prefix correctly. Compiling patched Wine isn't much hassle.

I should just find out what is wrong in winetricks and I'm done. If any questions, I'm always available here.