Pauls

when the beachball is spinning can you go to activity monitor and inspect the hung process, ( Select process then use View, Inspect Process). If you send us the report it may give a clue to why it is freezing

I've managed to recreate the crash changing the case of the running header field but I cant recreate the other crashes. Would it be possible to get the crash report (from the console app) when those occur ?

Certainly please use this link to upload the file

does the paste work if you use PDF, PNG or Serif Persona Nodes?

If you use Paste Special which formats are listed in the dialog ? I suspect the device independent bitmap option is being applied by default and there is a known bug with that ( which looks scheduled to be fixed in 2.2 )

Could you supply us with a file that is in use when the app is crashing and some actions that cause the app to crash please

in the pages panel you can right click and select add pages from file

it's certainly an interesting co-incidence do you have some users with similar graphics hardware that are in a working state ?

The graphics driver is fiarly recent have the problems started since that was updated on their systems ?

In the users folder you will find a log.txt file - if you could send one of those please e.g C:\Users\<user>\.affinity\Photo\2.0\log.txt Also do the affected users have any of the 3rd party apps listed here (e.g. d3dgear)

The crash report type is often associated with graphics drivers or inconsistent .Net installations. You could try following DanC's instructions here to uninstall and reinstall the relevant graphics drivers. The .net repair tool can also be worth trying if the above brings no joy. is it still possible to create a brand new document ?

1. Try disabling OpenCL from Settings/Performance 2 If that doesnt work try setting the renderer to 'Warp' Have you tried opening the file from a local HD?

If you add the pages from file and before you save the document look at the endnotes section I removed some of the later ones and then the document would save and reload for me

it appears to be something to do with global numbering within the document and possibly notes. You can try creating a new document then adding all the pages from the crashing file. However you may run into the same problem again. I'll get the issue logged in the meantime

the dictionary files are html pages rather than the actual dictionary. You will need to download them again - it's surprisingly easy to download the wrong thing from github if that's where you got it from we have some hunspell dictionaries linked on this post

not directly according to the crash report but maybe it has a knock on effect.

could you attach that fr-FR folder and a sample documnet please. I'll see if I can replicate the crash

looking at the crash report it may be due to spelling dictionaries - have you installed any yourself?

Yes this appears to be a bug which I've logged.

this may be due to the naming of the templates would it be possible to get a listing of the filenames in the template folder(s) also are your editing operations causing any files to be added or removed from the templates folder

every time I've calibrated my monitor brightness is usually set quite high so you will be over adjusting to make it look right on your monitor setup. Using the 32 bit Linear colour workspace is contributing to the export problems too i suspect- I would stick with 16 bit personally and you'll end up with closer matches even if you export to a std sRGB colour workspace

I can recreate this so I'll get it logged - looks like some sort of thread locking problem

do you have "full keyboard access" turned on ?

@Pyanepsionwe think we'll get this fixed for 2.2

and that is now logged