Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

saveSession(): An error occurred Error: could not load data #25

Closed
NinjaTurtle007 opened this issue Oct 3, 2018 · 1 comment
Closed

Comments

@NinjaTurtle007
Copy link

lwsm save test
saveSession(): An error occurred Error: could not load data
at /usr/local/lib/node_modules/linux-window-session-manager/node_modules/jfs/lib/Store.js:209:15
at ReadFileContext.callback (/usr/local/lib/node_modules/linux-window-session-manager/node_modules/jfs/lib/Store.js:94:16)
at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:420:13)
(node:11836) UnhandledPromiseRejectionWarning: Error: could not load data
at /usr/local/lib/node_modules/linux-window-session-manager/node_modules/jfs/lib/Store.js:209:15
at ReadFileContext.callback (/usr/local/lib/node_modules/linux-window-session-manager/node_modules/jfs/lib/Store.js:94:16)
at FSReqWrap.readFileAfterOpen [as oncomplete] (fs.js:420:13)
(node:11836) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11836) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
SAVED SESSION: test

it used to work just fine shortly ago just saving the session without any errors, when i kept saving the same configuration (i was testing something related to other issue) it started throwing this error.

all latest versions

@johannesjo
Copy link
Owner

johannesjo commented Oct 3, 2018

Hey, just looked into it. The error message is correct (it tries to open the session config file, which is not yet created), but misleading, as the program is operating normally and all should work as intended. I'll replace it with a more helpful hint. Thanks for taking your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants