Jump to content
You must now use your email address to sign in [click for more info] ×

SueWAuthor

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by SueWAuthor

  1. Oh! Well, I simply deleted it from the app folder. I didn’t want to delete any preferences like my assets so I figured that would be the best way. Clearly that didn’t work!
  2. This is what the error report says: Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Affinity Publisher [2758]
  3. I’m working on a MacBook Pro running Sonoma. This is urgent as I’m in the middle of a big project. I was running Affinity Publisher (first gen) and changed the display mode in Publisher's settings to light instead of dark. Publisher instantly crashed and I can’t reopen it. I deleted it completely and reinstalled it and I still can’t open it.
  4. Thanks for all your help! I validated the font and it was fine in the font book. But I decided to disable Times New Roman as Times is also running and they seem the same. Maybe they were in conflict? Then I cleared the font cache. However, the program crashed again right away. It particularly crashes when I try to scroll through my pages. Screen Recording 2021-06-17 at 3.53.22 PM.mov
  5. Hi, is this still not a thing? It's kind of impossible to draw and erase when I can't see the size of my brush.
  6. I also got this notice from Terminal after it crashed, I'm not sure if it's helpful? The default interactive shell is now zsh. To update your account to use zsh, please run `chsh -s /bin/zsh`. For more details, please visit https://support.apple.com/kb/HT208050. Sues-MacBook-Pro:~ suewyshynski$ /Applications/Affinity/Affinity\ Publisher.app/Contents/MacOS/Affinity\ Publisher ; exit; 2021-06-15 13:17:31.921 Affinity Publisher[15897:2153096] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2021-06-15 13:17:31.921 Affinity Publisher[15897:2153096] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug. Segmentation fault: 11 logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. Deleting expired sessions...none found. [Process completed]
  7. Thanks Ian! I just tried it, unfortunately it didn't work. The program crashed after around 2 minutes again.
  8. Hi Mike, Thanks for taking the time to help! Unfortunately, it is happening with brand new, totally clean documents (as well as old documents). So stripping out features/images/grids etc isn't an option. But that's a smart suggestion.
  9. Hi Mike, Glad to hear yours is working. If you have any suggestions on how to isolate which feature is causing my crashes, I'd be glad to hear them. I have tried many configurations/workarounds/only running it alone/upgrading operating systems/not allowing it to sleep/disconnecting wifi etc. Thanks, just about to use it again now. Fingers crossed that I can run it for more than 2-5 minutes...
  10. I updated to Big Sur, hoping that might stabilize the program, but it continues to crash around every 5 minutes or so. I have to work in very small time chunks and save obsessively so that I don't lose my files. When the program works, it's great, but this is becoming ridiculous! Does anyone have any solutions? I'm on a 2019 MacBook Pro running Big Sur, tons of memory.
  11. Sorry this is happening to you Ian and gavdpol! I've been using Publisher for around 2 years now and it continually crashes. New files, old files, they all keep breaking the program. I updated to Big Sur, hoping that might stabilize the program, but it continues to crash around every 5 minutes or so. I have to work in very small time chunks and save obsessively so that I don't lose my files. When the program works, it's great, but this is becoming ridiculous! Does anyone have any solutions? I'm on a 2019 MacBook Pro running Big Sur, tons of memory.
  12. Edit, defaults, revert -- that worked!! Thank you loukash I'm not sure why the image isn't appearing above, I'm seeing it on my screen. Anyway, that doesn't matter, you fixed my issue. Thanks!!
  13. Please see this screenshot. There is a white background, but the background is crossed out in the text panel.
  14. Hi, Thanks for the replies. MEB: No, I did not copy text from anywhere. I simply used the text tool and typed four letters: 'Maze'. LOUKASH: Create a text frame in Designer--I'm not sure how to do that, unlike in Publisher. I can create a box and then convert it to a text frame, but then there does not appear to be a way to reset the background. I have tried: - REAPPLY BASE STYLE This reverts the text to Arial, but retains the white background
  15. Affinity Designer v1.9.3 Mac Mojave 10.14.6 I created a file in Designer. When I reopened it to start working on it again, I found that the program is forcing a white background behind any newly added text. No background color is applied to the character. The file has not been opened or modified in any other program. I can't figure out why this is happening. Suggestions? Thanks Egypt Activity Book Cover.afdesign
  16. Thanks, Jon P -- so just now I decided to try one last thing and I was able to open the file. I'm not sure which piece of what I did worked, but I duplicated the file I changed the file name to one word. Before it was "Trace and Learn Hieroglyphics.afpub" including the spaces. I renamed it "Hieroglyphics.afpub" I opened the file It also opened one that had crashed alongside it in recovery mode The renamed file is now working fine Could the issue be with having spaces in the file name? If you're still interested in seeing the broken file, let me know.
  17. Did you find a fix for this? It has now happened to 2 of my files, several months apart.
×
×
  • 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.