Cannot get Window Session Manager to work





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I installed the Window Session Manager under Ubuntu 18.04 LTS and probably got something wrong. I then executed the instructions in the Git repository, but still no luck: when I save a session, I get the error lwsm: save Test UNKNOWN ERROR (Test is the session name I gave).



Here is the output from running lwsm in a terminal:



lwsm: no config file present or it contains invalid json. Creating new one...
/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:57
throw err;
^

ReferenceError: fs is not defined
at Object.mkdirSync (/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:54:5)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/lib/index.js:33:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/cmd.js:3:14)









share|improve this question

























  • @Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

    – AlwaysLearning
    Oct 15 '18 at 12:00




















0















I installed the Window Session Manager under Ubuntu 18.04 LTS and probably got something wrong. I then executed the instructions in the Git repository, but still no luck: when I save a session, I get the error lwsm: save Test UNKNOWN ERROR (Test is the session name I gave).



Here is the output from running lwsm in a terminal:



lwsm: no config file present or it contains invalid json. Creating new one...
/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:57
throw err;
^

ReferenceError: fs is not defined
at Object.mkdirSync (/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:54:5)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/lib/index.js:33:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/cmd.js:3:14)









share|improve this question

























  • @Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

    – AlwaysLearning
    Oct 15 '18 at 12:00
















0












0








0


1






I installed the Window Session Manager under Ubuntu 18.04 LTS and probably got something wrong. I then executed the instructions in the Git repository, but still no luck: when I save a session, I get the error lwsm: save Test UNKNOWN ERROR (Test is the session name I gave).



Here is the output from running lwsm in a terminal:



lwsm: no config file present or it contains invalid json. Creating new one...
/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:57
throw err;
^

ReferenceError: fs is not defined
at Object.mkdirSync (/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:54:5)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/lib/index.js:33:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/cmd.js:3:14)









share|improve this question
















I installed the Window Session Manager under Ubuntu 18.04 LTS and probably got something wrong. I then executed the instructions in the Git repository, but still no luck: when I save a session, I get the error lwsm: save Test UNKNOWN ERROR (Test is the session name I gave).



Here is the output from running lwsm in a terminal:



lwsm: no config file present or it contains invalid json. Creating new one...
/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:57
throw err;
^

ReferenceError: fs is not defined
at Object.mkdirSync (/usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js:54:5)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/lib/index.js:33:8)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/usr/local/lib/node_modules/linux-window-session-manager/cmd.js:3:14)






18.04 gnome-shell-extension






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 15 '18 at 12:01







AlwaysLearning

















asked Oct 15 '18 at 8:10









AlwaysLearningAlwaysLearning

242312




242312













  • @Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

    – AlwaysLearning
    Oct 15 '18 at 12:00





















  • @Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

    – AlwaysLearning
    Oct 15 '18 at 12:00



















@Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

– AlwaysLearning
Oct 15 '18 at 12:00







@Xen2050 Sorry. Forgot to specify: Ubuntu 18.04 LTS. I don't understand your second question. The extension appears, but does not do the job.

– AlwaysLearning
Oct 15 '18 at 12:00












2 Answers
2






active

oldest

votes


















2














This is not a permanent fix, but as a workaround, I found that if you edit /usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js and add



const fs = require('fs');


at the top, then lwsm should work for you.






share|improve this answer


























  • Indeed! I find it very strange that no one asked about this issue before.

    – AlwaysLearning
    Oct 16 '18 at 5:59











  • @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

    – smacdav
    Oct 16 '18 at 15:39



















0














Follow the troubleshooting guide on the github page:
https://github.com/johannesjo/linux-window-session-manager



I had the same issue. to fix it i followed the instuctions from the link above and added the program names and commands to the ~/.lwsm/config.json



For example:



if Sublime Text 3 didnt open, I added to the WM_CLASS_AND_EXECUTABLE_FILE:{

this:



"subl3.Subl3": "subl3"


The first part is the name of the application and the second part is the command that it should run to open it.



Dont forget the "," at the end of the previous entry in the json.



You also have to update the saved session after you change the config.json






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083862%2fcannot-get-window-session-manager-to-work%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2














    This is not a permanent fix, but as a workaround, I found that if you edit /usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js and add



    const fs = require('fs');


    at the top, then lwsm should work for you.






    share|improve this answer


























    • Indeed! I find it very strange that no one asked about this issue before.

      – AlwaysLearning
      Oct 16 '18 at 5:59











    • @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

      – smacdav
      Oct 16 '18 at 15:39
















    2














    This is not a permanent fix, but as a workaround, I found that if you edit /usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js and add



    const fs = require('fs');


    at the top, then lwsm should work for you.






    share|improve this answer


























    • Indeed! I find it very strange that no one asked about this issue before.

      – AlwaysLearning
      Oct 16 '18 at 5:59











    • @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

      – smacdav
      Oct 16 '18 at 15:39














    2












    2








    2







    This is not a permanent fix, but as a workaround, I found that if you edit /usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js and add



    const fs = require('fs');


    at the top, then lwsm should work for you.






    share|improve this answer















    This is not a permanent fix, but as a workaround, I found that if you edit /usr/local/lib/node_modules/linux-window-session-manager/lib/utility.js and add



    const fs = require('fs');


    at the top, then lwsm should work for you.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Oct 15 '18 at 20:28









    zx485

    1,47131315




    1,47131315










    answered Oct 15 '18 at 19:38









    smacdavsmacdav

    362




    362













    • Indeed! I find it very strange that no one asked about this issue before.

      – AlwaysLearning
      Oct 16 '18 at 5:59











    • @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

      – smacdav
      Oct 16 '18 at 15:39



















    • Indeed! I find it very strange that no one asked about this issue before.

      – AlwaysLearning
      Oct 16 '18 at 5:59











    • @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

      – smacdav
      Oct 16 '18 at 15:39

















    Indeed! I find it very strange that no one asked about this issue before.

    – AlwaysLearning
    Oct 16 '18 at 5:59





    Indeed! I find it very strange that no one asked about this issue before.

    – AlwaysLearning
    Oct 16 '18 at 5:59













    @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

    – smacdav
    Oct 16 '18 at 15:39





    @AlwaysLearning I was a bit surprised by that, myself, when I found your question after having exactly the same problem.

    – smacdav
    Oct 16 '18 at 15:39













    0














    Follow the troubleshooting guide on the github page:
    https://github.com/johannesjo/linux-window-session-manager



    I had the same issue. to fix it i followed the instuctions from the link above and added the program names and commands to the ~/.lwsm/config.json



    For example:



    if Sublime Text 3 didnt open, I added to the WM_CLASS_AND_EXECUTABLE_FILE:{

    this:



    "subl3.Subl3": "subl3"


    The first part is the name of the application and the second part is the command that it should run to open it.



    Dont forget the "," at the end of the previous entry in the json.



    You also have to update the saved session after you change the config.json






    share|improve this answer




























      0














      Follow the troubleshooting guide on the github page:
      https://github.com/johannesjo/linux-window-session-manager



      I had the same issue. to fix it i followed the instuctions from the link above and added the program names and commands to the ~/.lwsm/config.json



      For example:



      if Sublime Text 3 didnt open, I added to the WM_CLASS_AND_EXECUTABLE_FILE:{

      this:



      "subl3.Subl3": "subl3"


      The first part is the name of the application and the second part is the command that it should run to open it.



      Dont forget the "," at the end of the previous entry in the json.



      You also have to update the saved session after you change the config.json






      share|improve this answer


























        0












        0








        0







        Follow the troubleshooting guide on the github page:
        https://github.com/johannesjo/linux-window-session-manager



        I had the same issue. to fix it i followed the instuctions from the link above and added the program names and commands to the ~/.lwsm/config.json



        For example:



        if Sublime Text 3 didnt open, I added to the WM_CLASS_AND_EXECUTABLE_FILE:{

        this:



        "subl3.Subl3": "subl3"


        The first part is the name of the application and the second part is the command that it should run to open it.



        Dont forget the "," at the end of the previous entry in the json.



        You also have to update the saved session after you change the config.json






        share|improve this answer













        Follow the troubleshooting guide on the github page:
        https://github.com/johannesjo/linux-window-session-manager



        I had the same issue. to fix it i followed the instuctions from the link above and added the program names and commands to the ~/.lwsm/config.json



        For example:



        if Sublime Text 3 didnt open, I added to the WM_CLASS_AND_EXECUTABLE_FILE:{

        this:



        "subl3.Subl3": "subl3"


        The first part is the name of the application and the second part is the command that it should run to open it.



        Dont forget the "," at the end of the previous entry in the json.



        You also have to update the saved session after you change the config.json







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 25 at 13:16









        Bogdan IonescuBogdan Ionescu

        1




        1






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083862%2fcannot-get-window-session-manager-to-work%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Category:香港粉麵

            List *all* the tuples!

            Channel [V]