Jump to content
yaycreative

After update to El Capitan, both Photo and Designer won’t open files

Recommended Posts

Hey community!

 

I have been working professionally with Affinity since the release of Designer and am quite happy with it. Now I had to upgrade to El Capitan (10.11.2) from 10.9.5 and since the upgrade, both Affinity Designer and Photo can’t open my files any more – no matter where they are (wether it’s the server or locally in my user folder). It always says that there aren’t the right permissions. I checked that and my user (as well as all other relevant users) have full rights on the files.

 

I downloaded the fixed Betas (though they are older than my current ones – Designer Beta is v1.3.5) and they’re showing the same problems.

 

Also, starting the applications seems way slower than before, starting with a small white splash screen.

 

Can you please help?

Thank you in advance!

Share this post


Link to post
Share on other sites

Yeah, this could possibly be it. I just ran into this thing myself. Interestingly, Pages, TextEdit and all Apple-apps have the same issue while Adobe’s, for example, are all working fine.

Am trying to repair permissions via Cocktail first … let’s see.
if this doesn’t work, can I deactivate SIP?

Share this post


Link to post
Share on other sites

Okay, I now repaired all the permissions, disabled SIP (via this tutorial) and the problem is still present. Interestingly, I can save new files to my iCloud folder while I can’t open existing ones, even if I copy them to the iCloud folder. Same with Pages and other Apple apps, btw. 
Basically, I am currently not able to edit my existing files which is a huge problem for me. Of course, I reinstalled both apps before without any effect.

 

I’m on this system:

MacBook Pro 15" 8,2 (early 2011)

2,2 GHz 1333 MHz DDR3

16 GB RAM

Fusion Drive consisting of 1TB HDD and 256GB Angelbird SSD wrk for Mac (with native TRIM)

Mac OS X 10.11.2 (15C50)

 

latest Affinity Designer and Photo versions

 

I appreciate any help! Thank you!

Share this post


Link to post
Share on other sites

Unfortunately not. I am running an Angelbird SSD in my Fusiondrive array and it has a native TRIM. The mentioned problem only applies to third-party SSDs which use the TRIM enabler.

 

But thank you very much for the idea!

 

I myself am running out of ideas now … :(

do you have any more? Going to get a bit desperate …

Share this post


Link to post
Share on other sites

Hey Andy!

Yeah, you were right! Just made a new user and – boom – it seems to work just fine. But what to do now? I could delete my existing user account and restore it from Time Machine to a new one. Not sure, though, if this will do the trick. Do you have an idea what to do now?

Share this post


Link to post
Share on other sites

Okay guys, I have to admit yesterday evening I finally gave up. After creating a new user, at first everything worked fine there. But then, after a while, there were the same problems. I then tried to delete the original user and restore it from Time Machine, but the Migration Assistant didn’t work – probably the same problem. I then wanted to reinstall a clean version of EC, but my USB drive got corrupted and I couldn’t install it online because there was a wrong keyboard mapping so that I couldn’t enter my Apple ID. Strange things were happening there …

 

Finally, I gave up and reverted the whole system back to Mavericks – BTW for that, I had to delete the whole partition for some reason. Am a bit sad it didn’t work, as I am not able to use RightFont, which was my original reason for the upgrade, and EC seemed quite a bit faster and more responsive than Mavericks. But in the end I don’t have any more time to invest in this. Already lost three working days on it.

 

Thank you all for your kind help!

 

Best,

Bene

Share this post


Link to post
Share on other sites

Okay, in the meantime I’ve bought a new Mac which came with El Capitan pre-installed. Now I realized that still, neither Designer nor Photo does open any file. I also installed the latest Photo Beta, but still no luck. Is there still no fix to this? C’mon guys, I seriously want to give you a chance over PS & AI, but you have to get it to work!  ;)

 

Edit:

Specs are:
MacBook Pro 13" with El Capitan 10.11.6
3.1 GHz i7
16GB 1867 MHz DDR3
512 GB SSD
Intel Iris Graphics 6100 1536 MB

Share this post


Link to post
Share on other sites

I talked to a support guy via FB messenger and he asked me to post a screenshot of one of the files which apparently (according to the console) couldn’t be opened because of wrong file permissions while startup of Designer/Photo. Maybe someone can help?

It seems to me as not a single file can be opened by Serif apps, wether it is a font file or a .psd or .afdesign file.
Oh, and I have the latest RightFont installed, if this might be connected to the issue.
 

post-25631-0-23946100-1490259123_thumb.png

Share this post


Link to post
Share on other sites

Sorry to hear that you're still having issues with our apps and your machine.

 

Have you installed the latest update for our apps from the Mac App Store? When opening a file are you using File> Open Recent? 

Share this post


Link to post
Share on other sites

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.


×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.