Skip to content

Jaroslaw KOllar

My feedback

5 results found

  1. 127 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    As part of the investigation into the cause of this issue, we personally reached out to many of you over email. We have so far heard from only some of you.

    Of the responses we have received, the conclusion we’ve come to is:
    This issue was intermittent, happened once during the course of work but somehow got resolved and has not happened again. This issue can’t be reproduced now.

    Over a period of time, this thread has not thrown any fresh clues on why this issue seems to occur randomly for some and then seems to resolve itself. So we’re closing this thread.

    However, even though we’re closing this thread, if you again run into this issue any time on a consistent basis, please report it here on UserVoice (in a new thread) with supporting assets like:
    A) a test file,
    B) detailed steps to replicate the issue
    C) any…

    Jaroslaw KOllar supported this idea  · 
  2. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jaroslaw KOllar shared this idea  · 
  3. 56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Jaroslaw KOllar commented  · 

    This is the case for weeks now. I have the Problems since CC17 on High Sierra. Its like working on ice :/ It seems random. Had this five times yesterday. Restarting INDD solves it for me, and there ist no loss (damages files opens like it should). But very annoying, i guess it has something to do with the new apple file system.

    Jaroslaw KOllar supported this idea  · 
    An error occurred while saving the comment
    Jaroslaw KOllar commented  · 

    The Error is still there after macOS and latest CC18 Update.

    Files are safed in the user-folder on an APFS-SSD (MBP 2016, 1TB). Occurs maybe one or two times a day. InDesign is "up" almost all day, i realised, that there might be a connection to the time INDD is running. Closing/restarting solves the issue. While the issue is active, i cannot save or load any file – all seem broken.

    An error occurred while saving the comment
    Jaroslaw KOllar commented  · 

    Same here. Re-Starting solves that issue. I got a shock first, when the first "file is damaged" message appeared today.

  4. 61 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello All,

    Thank you for your patience all this while. The fix of the issue is now part of InDesign’s latest update, Id 13.1

    Update your InDesign through Creative Cloud app to Id 13.1

    Thanks,
    Abhinav

    An error occurred while saving the comment
    Jaroslaw KOllar commented  · 

    Regarding Fix: Win only?

    Jaroslaw KOllar supported this idea  · 
  5. 321 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Jaroslaw KOllar supported this idea  · 

Feedback and Knowledge Base