inky icon indicating copy to clipboard operation
inky copied to clipboard

[Bug] Windows: Preview never starts when loading ink files from Documents folder

Open Auroriax opened this issue 2 years ago • 0 comments

On Windows 10, saving an ink file directly into the Documents folder (in my case C:/Users/Tom/Documents/test.ink), and then loading it, will cause the story preview to be stuck loading and never start. According to console errors, the app seems to look for the My Music, My Pictures & My Videos subfolders, yet this Documents folder doesn't have any of those as subfolders.

My workaround was simply to save the ink file in another folder (e.g. saving as C:/Users/Tom/Documents/ink/test.ink worked for me).

Screenshot: afbeelding

Full logs of errors in the console:

ace.js:3532 Automatically scrolling cursor into view after selection change this will be disabled in the next version set editor.$blockScrolling = Infinity to disable this message
warn @ ace.js:3532
internal/fs/watchers.js:164 Uncaught (in promise) Error: EPERM: operation not permitted, watch 'C:\Users\Tom\Documents\My Music'
    at FSWatcher.start (internal/fs/watchers.js:164)
    at Object.watch (fs.js:1232)
    at createFsWatchInstance (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:118)
    at setFsWatchListener (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:165)
    at NodeFsHandler._watchWithNodeFs (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:330)
    at NodeFsHandler._handleDir (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:551)
    at process._tickCallback (internal/process/next_tick.js:68)
internal/fs/watchers.js:164 Uncaught (in promise) Error: EPERM: operation not permitted, watch 'C:\Users\Tom\Documents\My Pictures'
    at FSWatcher.start (internal/fs/watchers.js:164)
    at Object.watch (fs.js:1232)
    at createFsWatchInstance (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:118)
    at setFsWatchListener (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:165)
    at NodeFsHandler._watchWithNodeFs (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:330)
    at NodeFsHandler._handleDir (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:551)
    at process._tickCallback (internal/process/next_tick.js:68)
internal/fs/watchers.js:164 Uncaught (in promise) Error: EPERM: operation not permitted, watch 'C:\Users\Tom\Documents\My Videos'
    at FSWatcher.start (internal/fs/watchers.js:164)
    at Object.watch (fs.js:1232)
    at createFsWatchInstance (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:118)
    at setFsWatchListener (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:165)
    at NodeFsHandler._watchWithNodeFs (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:330)
    at NodeFsHandler._handleDir (C:\Users\Tom\Downloads\Inky_windows_64\Inky-win32-x64\resources\app.asar\node_modules\chokidar\lib\nodefs-handler.js:551)
    at process._tickCallback (internal/process/next_tick.js:68)

Auroriax avatar Jan 12 '22 09:01 Auroriax