Not signed in (Sign In)

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

Ulysses 2.0: Problem saving new (empty) project

Bottom of Page

1 to 14 of 14

  1.  
  1.  
    Hi,

    I'm using and loving Ulysses 2.1.3 (Build 2.1.3) on a Mac Book Pro running OSX 10.7.3. When I try to start a new (empty) project, a menu suggests a name (Something.ulys). When I try to save the file/project that way first, nothing happens. The menu disappears but the file is not saved unless I write some text into the first "New Document". This strikes me as a bug...the program should save as many (empty) projects as I wish...

    Cheers from Berlin and thanks,
    Marcus
    •  
      CommentAuthorgoetz
    • CommentTimeMar 28th 2012 edited
     
    Does this problem also occur in a different folder? For instance, if you switch to your "Desktop" folder, the project should be properly saved there.

    Götz
  3.  
    I just checked. No problem if I switch to the "Desktop" folder. Though still...that shouldn't be. But thanks, this is helpful!
  4.  
    I'm afraid I need to re-open this thread because though I tried it and it worked, the saving now doesn't work anymore. In fact, I cannot figure out at all how to save a new (empty) project. It is most frustrating. In fact the only way I can save an empty project (to the DESKTOP folder or to my ULYSSES folder) is by shutting down Ulysses and reopening the program. Only then will it work...
    •  
      CommentAuthorgoetz
    • CommentTimeApr 6th 2012
     

    Could you contact us via e-mail at support@the-soulmen.com regarding this problem? Also, was there any output to the Console (Applications > Utilities > Console.app)? This might be useful in finding the source of the problem.

  6.  
    I just did that!
    •  
      CommentAuthorgoetz
    • CommentTimeApr 6th 2012
     

    Thanks! We'll take a look at it.

    •  
      CommentAuthorReliStuPhD
    • CommentTimeApr 10th 2012
     
    I'll add to this. I am running into the same problem. Exiting Ulysses and restarting seem to fix things, but I was decidedly unhappy when I realized I was taking a risk in losing an hour's worth of work (I know, I know. Should have saved. But well, I thought I had...). Thankfully, cut & paste and worked. Here are some of the messages form the log. The two projects listed are projects I had closed in order to start a new one:

    4/10/12 1:49:23.785 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Dispensationalism/Scofield,Brookes.ulys(e1a3eff1005ebbbbb841535e27d3c0ae3ad7b4d1;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008b8f09;/users/carlito/dropbox/documents/phd/dispensationalism/scofield,brookes.ulys): Cannot allocate memory
    4/10/12 1:49:28.325 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Contemporary Approaches/Final Paper.ulys(238c1b80f48d9992ec41aa62cc48ce330d76dc09;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008e37e4;/users/carlito/dropbox/documents/phd/contemporary approaches/final paper.ulys): Cannot allocate memory
    4/10/12 1:49:28.326 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Dispensationalism/Scofield,Brookes.ulys(e1a3eff1005ebbbbb841535e27d3c0ae3ad7b4d1;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008b8f09;/users/carlito/dropbox/documents/phd/dispensationalism/scofield,brookes.ulys): Cannot allocate memory
    4/10/12 1:49:28.328 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Contemporary Approaches/Final Paper.ulys(238c1b80f48d9992ec41aa62cc48ce330d76dc09;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008e37e4;/users/carlito/dropbox/documents/phd/contemporary approaches/final paper.ulys): Cannot allocate memory
    4/10/12 1:49:28.330 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Dispensationalism/Scofield,Brookes.ulys(e1a3eff1005ebbbbb841535e27d3c0ae3ad7b4d1;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008b8f09;/users/carlito/dropbox/documents/phd/dispensationalism/scofield,brookes.ulys): Cannot allocate memory
    4/10/12 1:49:53.267 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Contemporary Approaches/Final Paper.ulys(238c1b80f48d9992ec41aa62cc48ce330d76dc09;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008e37e4;/users/carlito/dropbox/documents/phd/contemporary approaches/final paper.ulys): Cannot allocate memory
    4/10/12 1:49:53.269 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Dispensationalism/Scofield,Brookes.ulys(e1a3eff1005ebbbbb841535e27d3c0ae3ad7b4d1;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008b8f09;/users/carlito/dropbox/documents/phd/dispensationalism/scofield,brookes.ulys): Cannot allocate memory
    4/10/12 1:49:53.271 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Contemporary Approaches/Final Paper.ulys(238c1b80f48d9992ec41aa62cc48ce330d76dc09;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008e37e4;/users/carlito/dropbox/documents/phd/contemporary approaches/final paper.ulys): Cannot allocate memory
    4/10/12 1:49:53.272 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Dispensationalism/Scofield,Brookes.ulys(e1a3eff1005ebbbbb841535e27d3c0ae3ad7b4d1;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008b8f09;/users/carlito/dropbox/documents/phd/dispensationalism/scofield,brookes.ulys): Cannot allocate memory
    4/10/12 1:50:31.509 PM fseventsd: implementation_removed_client: did not find client 0x10be5dbe0 for path = '/'
    4/10/12 1:50:31.516 PM Ulysses: kCGErrorIllegalArgument: CGSRemoveWindowFromWindowMovementGroup: Invalid window
    4/10/12 1:50:31.516 PM Ulysses: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    4/10/12 1:51:40.743 PM com.apple.SecurityServer: Killing auth hosts
    4/10/12 1:51:40.743 PM com.apple.SecurityServer: Session 100027 destroyed
    4/10/12 1:51:47.834 PM Ulysses: Unable to consume sandbox extension for /Users/Carlito/Dropbox/Documents/PhD/Contemporary Approaches/Final Paper.ulys(238c1b80f48d9992ec41aa62cc48ce330d76dc09;00000000;0000000000000020;com.apple.app-sandbox.read-write;00000001;0e000002;00000000008e37e4;/users/carlito/dropbox/documents/phd/contemporary approaches/final paper.ulys): Cannot allocate memory
    •  
      CommentAuthorgoetz
    • CommentTimeApr 10th 2012 edited
     

    This is the same problem as reported by Marcus. The essential part is

    Unable to consume sandbox extension [...] Cannot allocate memory

    Ulysses is running in Apple's sandbox. For a reason yet unknown to us, Ulysses has some problems after running it for a longer time period (which also makes it harder for us to reproduce). We have contacted Apple regarding this matter and are working towards a solution. Currently, restarting Ulysses should always fix the problem.

    •  
      CommentAuthorReliStuPhD
    • CommentTimeApr 10th 2012
     
    Thanks for the explanation. This of course raises a ***SERIOUS*** problem that needs to be addressed somehow: if the initial save is successful, how do we know if future saves were not successful? That is, I can always see the "The project has not been saved" message at the lower right *unless I've saved successfully.* Once I've saved, that message disappears and I would have no way of knowing a save was unsuccessful until I later opened a project and found that, say, two hours of work was gone.

    I know this is an unfair burden to you guys in a sense, but as an end user, I absolutely must have a way of know if a save has been successful. Do I need to keep Console open all the time and check for error messages? Is this an error that occurs only with a new project (meaning if I save right away I'm safe)? So on and so forth. I'm growing to like Ulysses quite a bit, but this is a headache I don't need as I try to learn the ins and outs of the program. Any suggestions you have in this regard are welcome.
    •  
      CommentAuthorReliStuPhD
    • CommentTimeApr 11th 2012
     
    This bug is happening far too often for my liking. Is it possible to provide a limited-time version of Ulysses (for download directly from your site) that eliminates the sandboxing until you're able to address this? I'm losing confidence in Ulysses by the minute, most especially after (literally) hundreds of "unable to consume sandbox" error messages in a 10-minutes time span.



    [As a side note (if it will help) I have been struck by the fact that Ulysses automatically closes a project when I create a new one. Whether this intended behavior or not, I wonder if it's related to the sandbox error. In every other program I have, a new "document" (i.e. what Ulysses calls a "project") simple opens a new window such that I could command+~ between them. This does not happen in Ulysses. As far as I can tell, no more than 1 window at a time can be open. Perhaps this is related to the inability of Ulysses to "consume" the other sandboxes (i.e. the implementation of the closing causes the problem).]

    PS As for the length of time to replicate the issue, I was able to replicate within minutes of opening a project.
    •  
      CommentAuthorgoetz
    • CommentTimeApr 11th 2012
     

    ReliStuPhD, could you drop us an email at support@the-soulmen.com to look at the issue in detail? It seems (for us) quite strange that the problem occurs within minutes of opening a project.

    •  
      CommentAuthorReliStuPhD
    • CommentTimeApr 11th 2012
     
    Replied via e-mail
    •  
      CommentAuthorgoetz
    • CommentTimeApr 12th 2012
     

    Thanks!

1 to 14 of 14

  1.