lwsm save doesn't work
See original GitHub issueMy Environment
- Version used: 3.0.1
- Operating Systtem and version: 18.04.3 LTS(ubuntu), gnome-shell(3.28.4)
- Desktop Environment:
- Node version: v12.10.0 I followed guide provided by this article article.
After installation, I wanted to save my session using ‘lwsm save’ command in gnome shell, I got below error instead.
(node:13700) UnhandledPromiseRejectionWarning: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds at boundsError (internal/buffer.js:70:11) at Buffer.readUInt32LE (internal/buffer.js:206:5) at Buffer.unpack (/home/user/.npm-packages/lib/node_modules/linux-window-session-manager/node_modules/x11/lib/unpackbuffer.js:44:32) at /home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:589:45 at step (/home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:63:23) at Object.next (/home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:44:53) at /home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:37:71 at new Promise (<anonymous>) at __awaiter (/home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:33:12) at _decodeProperty (/home/user/.npm-packages/lib/node_modules/linux-window-session-manager/dist/index.js:542:12) (node:13700) 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: 2) (node:13700) [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.
I can’t understand meaning of RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds at boundsError. Is this for not enough ram?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)

Top Related StackOverflow Question
This hopefully should be fixed now. Thanks for all your help! Let me know if this persists for you or if you encounter any other issues.
Meanwhile I suggest to use version v2.1.31 instead. The error should not occur there.