Jump to content

Alex White

Members
  • Content Count

    23
  • Joined

  • Last visited

Posts posted by Alex White


  1. Thanks - that video is very clear and for some reason I wasn't seeing that.

    Then inspiration struck! 

    My text boxes are defined on the 'master' pages. That is why it is greyed out in the text popup and doesn't appear in the context toolbar. When I go and edit the master pages I can see the other things in the context toolbar including the columns chooser.

    So problem is solved. Well, nearly solved. I've turned the LH master page into two columns, but every time I attempt to turn the RH master into two columns it crashes the application hard! But that must be a different bug.

     

    Thanks for your help in getting to the bottom of my problem here. 


  2. 9 hours ago, Jon P said:

    Hi Alex,

    It would easiest for us to have a look at the file.

    If you could upload it here we can take a look into what might be causing it: https://www.dropbox.com/request/xJcQpCVh1VbAtdYYCypw

    Thanks

    Thanks, I've just uploaded the file to that location. I'd been working on it in all the previous betas without any problems, but the last two have caused crashes on opening it. Hopefully it will be easy to spot why!


  3. I have had the same problem with build 192 and now with 206. I've attached the crash dump, and this is the headline information from it. 

    Essentially as soon as I open the file that I've been working with in earlier betas, the application crashes as soon as it has displayed the current page in that file - the application terminates and disappears.

    The file is 50mb, and I'm happy to share it with you, but I'd prefer not to share it publicly.

     

    Process:               Affinity Publisher Beta [27111]
    Path:                  /Applications/Affinity Publisher Beta.app/Contents/MacOS/Affinity Publisher Beta
    Identifier:            com.seriflabs.affinitypublisher.beta
    Version:               1.7.0 (1.7.0.206)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Affinity Publisher Beta [27111]
    User ID:               502

    Date/Time:             2018-12-13 23:20:59.902 +0000
    OS Version:            Mac OS X 10.14.1 (18B75)
    Report Version:        12
    Bridge OS Version:     3.1 (16P1065)
    Anonymous UUID:        50C13EB4-078E-D6AE-5478-2472589AD615

    Sleep/Wake UUID:       A2066777-9BD1-409E-AA3E-0CEDEEB66649

    Time Awake Since Boot: 880000 seconds
    Time Since Wake:       1200 seconds

    System Integrity Protection: enabled

    Crashed Thread:        22  Dispatch queue: com.apple.root.default-qos

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00007fef24364fb0
    Exception Note:        EXC_CORPSE_NOTIFY

    Termination Signal:    Segmentation fault: 11
    Termination Reason:    Namespace SIGNAL, Code 0xb
    Terminating Process:   exc handler [27111]

    affinity publisher crash dump.txt


  4. I still have the problem that I found in .192 - I have a file that I've been working on and if I attempt to open it in 206 I have the same experience as I had in 192 - the application immediately crashes into oblivion.

     

    This is the start of the crash dump (full dump is attached)

     

    Process:               Affinity Publisher Beta [27111]
    Path:                  /Applications/Affinity Publisher Beta.app/Contents/MacOS/Affinity Publisher Beta
    Identifier:            com.seriflabs.affinitypublisher.beta
    Version:               1.7.0 (1.7.0.206)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Affinity Publisher Beta [27111]
    User ID:               502

    Date/Time:             2018-12-13 23:20:59.902 +0000
    OS Version:            Mac OS X 10.14.1 (18B75)
    Report Version:        12
    Bridge OS Version:     3.1 (16P1065)
    Anonymous UUID:        50C13EB4-078E-D6AE-5478-2472589AD615

    Sleep/Wake UUID:       A2066777-9BD1-409E-AA3E-0CEDEEB66649

    Time Awake Since Boot: 880000 seconds
    Time Since Wake:       1200 seconds

    System Integrity Protection: enabled

    Crashed Thread:        22  Dispatch queue: com.apple.root.default-qos

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00007fef24364fb0
    Exception Note:        EXC_CORPSE_NOTIFY

    Termination Signal:    Segmentation fault: 11
    Termination Reason:    Namespace SIGNAL, Code 0xb
    Terminating Process:   exc handler [27111]

    affinity publisher crash dump.txt


  5. 7 hours ago, frankwolfraum said:

    Can't start Affinity Publisher Beta anymore. I never had a problem with the previous versions. But neither a restart nor a reinstallation solves the trouble. Here are the screenshots that I could make. Anybody else with the same problem?

     

    Bildschirmfoto 2018-12-11 um 11.08.59.png

    Bildschirmfoto 2018-12-11 um 11.10.13.png

    Bildschirmfoto 2018-12-11 um 11.10.26.png

    If you glance two posts higher up it appears you are facing a very similar problem as me! 

    Exc_bad_access

    I do hope there is a solution!


  6. Just updated to this beta and a document which I'd been working on in the previous beta crashes the entire application as soon as it loads. The document in question is 54Mb in size. 

     

    The crash report starts like this, I could probably attach a whole crash log if that would be useful. Alternatively I could send you the document (I'd rather not post the document in a public forum).

     

    Process:               Affinity Publisher Beta [24438]
    Path:                  /Applications/Affinity Publisher Beta.app/Contents/MacOS/Affinity Publisher Beta
    Identifier:            com.seriflabs.affinitypublisher.beta
    Version:               1.7.0 (1.7.0.192)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Affinity Publisher Beta [24438]
    User ID:               502

    Date/Time:             2018-12-10 20:33:39.336 +0000
    OS Version:            Mac OS X 10.14.1 (18B75)
    Report Version:        12
    Bridge OS Version:     3.1 (16P1065)
    Anonymous UUID:        50C13EB4-078E-D6AE-5478-2472589AD615

    Sleep/Wake UUID:       C28DE6B2-6D7D-4467-A45E-73470234EB5B

    Time Awake Since Boot: 790000 seconds
    Time Since Wake:       2400 seconds

    System Integrity Protection: enabled

    Crashed Thread:        1  Dispatch queue: com.apple.root.default-qos

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       EXC_I386_GPFLT
    Exception Note:        EXC_CORPSE_NOTIFY
     


  7. On my Mac I have cut, copy and paste mapped to ctrl-x, ctrl-c and ctrl-v (because the standard cmd-x etc makes for uncomfortable key chords for me).

    The problem that I'm seeing on the current version of the publisher beta is that I can't use ctrl-v to put text into a text frame. I can right-click and select paste from the context menu, but I can't use either ctrl-v or cmd-v to paste the text. 

    ctrl-c to copy and ctrl-x to cut are working fine. Only ctrl-v has a problem for some reason. 

     

    version 1.7.0.174

×
×
  • 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.