Jump to content

Recommended Posts

Posted

What OS are you using Photo 2 Beta on?

What happens when you try to open it?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted

I'm on a clean install of Windows 11 with the lastest update. (clean install of windows three days ago)

image.png.b7c8c2126f31a108d12c254be87b5df5.png

 

Quote

What happens when you try to open it? :

Nothing. I don't see even a service being fired in Task Manager.

I restarted the PC, uninstall and install again the BETA version using the MSIX installer.

 

And, uninstalled the antivirus

 

  • Staff
Posted

Thanks for that Log, I was hoping there may be something in the CrashReports folder there to look into, see attached:

image.png

Serif Europe Ltd. - www.serif.com

  • Staff
Posted

Ah in which case it may be that it's not getting as far as generating a crash report (looking at your Publisher.zip this does seem to be the case), I assume you have no issues running 2.0.4 up (as there are some crash reports in that folder)?

Are you able to go into Windows Event Viewer after a failed run up of 2.1 Beta, and look into the Windows Logs/Application section and see if there are any errors relating to Publisher.exe, and paste what is in there if so?

Serif Europe Ltd. - www.serif.com

Posted (edited)

Right.

I uninstalled BOTH APublishers V2.0.4 and 2.1.0.171208. To then reinstall them using .EXE installers and restarted the PC.

 

1. This problem still exists (V2.0.4)( outside of scope of this bug report): 

 

 

2. The bug regarding this post still exists:

I can see the errors in Windows event manager. See file  For Serif.evtx + .wer files attached for the time stapms 11:13 and 11:14 today.

 

 

3. The crash reports are still empty in the BETA folder.

 

Please let me know if I can help further.

 

Report.wer Report.wer

Edited by JosueVivas
Typo
  • Staff
Posted

Thanks for the event viewer, it seems to be errorr'ing when attempting to create one of the user data folders, which lines up with why there are no folders (including a crash report folder) in there.

Do you mind confirming if you are the only user account on that machine and that it is an admin?

Can you also open up a run prompt and type in %ProgramData% and let me know if that opens up C:\ProgramData?

Serif Europe Ltd. - www.serif.com

Posted
Quote

Do you mind confirming if you are the only user account on that machine and that it is an admin?

Yes. Only one account and it is admin. The PC is not controlled by a "corporate account" that pushes Windows Policies.

 

Quote

Can you also open up a run prompt and type in %ProgramData% and let me know if that opens up C:\ProgramData?

 

It does open C:\ProgramData

 
  • Staff
Posted

Thanks, do you mind also confirming you have no issues manually creating a folder within %ProgramData%\Affinity and %Userprofile%\.affinity?

Serif Europe Ltd. - www.serif.com

  • Staff
Posted

Can you ensure that %ProgramData%\Affinity\Publisher\2.0 (Beta) exists and try running the app up again and seeing if you get the same issue? The fact it had to elevate when creating a folder in %ProgramData%\Affinity is interesting and not normal behavior, and could be related to the issue you are seeing.

It could be worth ensuring the app is run as admin

Serif Europe Ltd. - www.serif.com

  • Staff
Posted
39 minutes ago, JosueVivas said:

However

Folder . affintiy/Publisher does not have BETA folder

image.png.a6a114fc37d9d8d1c0615970d57ff8d0.png

Hi JosueVivas,

I just wanted to add that this is correct. In 2.1 the EXEs store their user data %AppData%\Affinity\Publisher\
where as the MSIXs will store theirs in %userprofile%\Affinity\Publisher\ as your screenshot shows.

Posted

Guys, can I just say that now I'm running Publisher V2.0.4 as administrator everytime I open the app, the performace is supperior: the time to save a document went from 2 minutes to seconds! (I bearly see the progress bar prompt "saving").

This ticket made me think what would happen if I run the stable version as administrator and I can tangible difference. Also, no more crashes.

Looking forward for version 2.1

 

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.