Why is vdirsyncer choking?












0














I had vdirsyncer running just fine for eons, on a computer that I don't use every day (or even every week). And then about a month ago I tried to run vdirsyncer sync and it choked with:



Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
ImportError: No module named 'encodings'

Current thread 0x00007f9038c2b740 (most recent call first):
Aborted (core dumped)


I don't remember screwing around in my python settings so I don't know why it would have just stopped working. I suspect that someone who spends more time in Python than I do these days might know what happened?



I'd like to fix this without trashing python, which currently defaults to 2.7 unless I specify that I want python3.



I found a question that cites the same error text, but the answer there recommends unsetting $PYTHONHOME and I haven't set it:



Fatal Python error: Py_Initialize: Unable to get the locale encoding … SyntaxError: invalid syntax Aborted (core dumped)









share



























    0














    I had vdirsyncer running just fine for eons, on a computer that I don't use every day (or even every week). And then about a month ago I tried to run vdirsyncer sync and it choked with:



    Could not find platform independent libraries <prefix>
    Could not find platform dependent libraries <exec_prefix>
    Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
    Fatal Python error: Py_Initialize: Unable to get the locale encoding
    ImportError: No module named 'encodings'

    Current thread 0x00007f9038c2b740 (most recent call first):
    Aborted (core dumped)


    I don't remember screwing around in my python settings so I don't know why it would have just stopped working. I suspect that someone who spends more time in Python than I do these days might know what happened?



    I'd like to fix this without trashing python, which currently defaults to 2.7 unless I specify that I want python3.



    I found a question that cites the same error text, but the answer there recommends unsetting $PYTHONHOME and I haven't set it:



    Fatal Python error: Py_Initialize: Unable to get the locale encoding … SyntaxError: invalid syntax Aborted (core dumped)









    share

























      0












      0








      0







      I had vdirsyncer running just fine for eons, on a computer that I don't use every day (or even every week). And then about a month ago I tried to run vdirsyncer sync and it choked with:



      Could not find platform independent libraries <prefix>
      Could not find platform dependent libraries <exec_prefix>
      Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
      Fatal Python error: Py_Initialize: Unable to get the locale encoding
      ImportError: No module named 'encodings'

      Current thread 0x00007f9038c2b740 (most recent call first):
      Aborted (core dumped)


      I don't remember screwing around in my python settings so I don't know why it would have just stopped working. I suspect that someone who spends more time in Python than I do these days might know what happened?



      I'd like to fix this without trashing python, which currently defaults to 2.7 unless I specify that I want python3.



      I found a question that cites the same error text, but the answer there recommends unsetting $PYTHONHOME and I haven't set it:



      Fatal Python error: Py_Initialize: Unable to get the locale encoding … SyntaxError: invalid syntax Aborted (core dumped)









      share













      I had vdirsyncer running just fine for eons, on a computer that I don't use every day (or even every week). And then about a month ago I tried to run vdirsyncer sync and it choked with:



      Could not find platform independent libraries <prefix>
      Could not find platform dependent libraries <exec_prefix>
      Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
      Fatal Python error: Py_Initialize: Unable to get the locale encoding
      ImportError: No module named 'encodings'

      Current thread 0x00007f9038c2b740 (most recent call first):
      Aborted (core dumped)


      I don't remember screwing around in my python settings so I don't know why it would have just stopped working. I suspect that someone who spends more time in Python than I do these days might know what happened?



      I'd like to fix this without trashing python, which currently defaults to 2.7 unless I specify that I want python3.



      I found a question that cites the same error text, but the answer there recommends unsetting $PYTHONHOME and I haven't set it:



      Fatal Python error: Py_Initialize: Unable to get the locale encoding … SyntaxError: invalid syntax Aborted (core dumped)







      shell-script python





      share












      share










      share



      share










      asked 4 mins ago









      Amanda

      408215




      408215






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f492165%2fwhy-is-vdirsyncer-choking%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2funix.stackexchange.com%2fquestions%2f492165%2fwhy-is-vdirsyncer-choking%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

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt