VirtualBox runs as root, Critical Error as user












4















I've just done a fresh install of VirtualBox 4.3.10 on a relatively fresh install of 14.04 (Trusty) and am seeing the below error when attempting to start VB as a normal user



Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)


When I start as root, it appears to be working just fine. So, I'm guessing this is a permissions thing, but I don't know where to start as far as figuring out what exactly has the wrong permissions.



I've actually tried several different installation methods including the .deb's from oracle's website, Ubuntu Software Center, and via 'sudo apt-get install virtualbox'. I get the same result regardless of installation method.



Any ideas?










share|improve this question























  • Perfect, thank you. Feel free to add this as answer so I can award you the points.

    – GoldPaintedLemons
    Sep 18 '14 at 23:30











  • ok, I have added it.

    – g_p
    Sep 19 '14 at 7:26
















4















I've just done a fresh install of VirtualBox 4.3.10 on a relatively fresh install of 14.04 (Trusty) and am seeing the below error when attempting to start VB as a normal user



Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)


When I start as root, it appears to be working just fine. So, I'm guessing this is a permissions thing, but I don't know where to start as far as figuring out what exactly has the wrong permissions.



I've actually tried several different installation methods including the .deb's from oracle's website, Ubuntu Software Center, and via 'sudo apt-get install virtualbox'. I get the same result regardless of installation method.



Any ideas?










share|improve this question























  • Perfect, thank you. Feel free to add this as answer so I can award you the points.

    – GoldPaintedLemons
    Sep 18 '14 at 23:30











  • ok, I have added it.

    – g_p
    Sep 19 '14 at 7:26














4












4








4


1






I've just done a fresh install of VirtualBox 4.3.10 on a relatively fresh install of 14.04 (Trusty) and am seeing the below error when attempting to start VB as a normal user



Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)


When I start as root, it appears to be working just fine. So, I'm guessing this is a permissions thing, but I don't know where to start as far as figuring out what exactly has the wrong permissions.



I've actually tried several different installation methods including the .deb's from oracle's website, Ubuntu Software Center, and via 'sudo apt-get install virtualbox'. I get the same result regardless of installation method.



Any ideas?










share|improve this question














I've just done a fresh install of VirtualBox 4.3.10 on a relatively fresh install of 14.04 (Trusty) and am seeing the below error when attempting to start VB as a normal user



Failed to create the VirtualBox COM object.
The application will now terminate.
Callee RC: NS_BASE_STREAM_WOULD_BLOCK (0x80470007)


When I start as root, it appears to be working just fine. So, I'm guessing this is a permissions thing, but I don't know where to start as far as figuring out what exactly has the wrong permissions.



I've actually tried several different installation methods including the .deb's from oracle's website, Ubuntu Software Center, and via 'sudo apt-get install virtualbox'. I get the same result regardless of installation method.



Any ideas?







14.04 permissions virtualbox software-installation root






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Sep 18 '14 at 3:06









GoldPaintedLemonsGoldPaintedLemons

13514




13514













  • Perfect, thank you. Feel free to add this as answer so I can award you the points.

    – GoldPaintedLemons
    Sep 18 '14 at 23:30











  • ok, I have added it.

    – g_p
    Sep 19 '14 at 7:26



















  • Perfect, thank you. Feel free to add this as answer so I can award you the points.

    – GoldPaintedLemons
    Sep 18 '14 at 23:30











  • ok, I have added it.

    – g_p
    Sep 19 '14 at 7:26

















Perfect, thank you. Feel free to add this as answer so I can award you the points.

– GoldPaintedLemons
Sep 18 '14 at 23:30





Perfect, thank you. Feel free to add this as answer so I can award you the points.

– GoldPaintedLemons
Sep 18 '14 at 23:30













ok, I have added it.

– g_p
Sep 19 '14 at 7:26





ok, I have added it.

– g_p
Sep 19 '14 at 7:26










2 Answers
2






active

oldest

votes


















1














Deleting ~/.config/VirtualBox should solve your problem.



Delete is using rm -r ~/.config/VirtualBox and start you virtual box.
`






share|improve this answer

































    0














    I had the same problem; it seems to have happened because my ~/.VirtualBox folder was owned by root, and so I had lost write permissions. Perhaps a consequence of running sudo virtualbox at some point.



    The folder was empty, so I just deleted it with sudo rm -d ..., otherwise something like sudo chown myname.myname ~/.VirtualBox would fix the owner/group.






    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%2f525421%2fvirtualbox-runs-as-root-critical-error-as-user%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









      1














      Deleting ~/.config/VirtualBox should solve your problem.



      Delete is using rm -r ~/.config/VirtualBox and start you virtual box.
      `






      share|improve this answer






























        1














        Deleting ~/.config/VirtualBox should solve your problem.



        Delete is using rm -r ~/.config/VirtualBox and start you virtual box.
        `






        share|improve this answer




























          1












          1








          1







          Deleting ~/.config/VirtualBox should solve your problem.



          Delete is using rm -r ~/.config/VirtualBox and start you virtual box.
          `






          share|improve this answer















          Deleting ~/.config/VirtualBox should solve your problem.



          Delete is using rm -r ~/.config/VirtualBox and start you virtual box.
          `







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 27 at 17:09

























          answered Sep 19 '14 at 7:26









          g_pg_p

          12.9k24661




          12.9k24661

























              0














              I had the same problem; it seems to have happened because my ~/.VirtualBox folder was owned by root, and so I had lost write permissions. Perhaps a consequence of running sudo virtualbox at some point.



              The folder was empty, so I just deleted it with sudo rm -d ..., otherwise something like sudo chown myname.myname ~/.VirtualBox would fix the owner/group.






              share|improve this answer




























                0














                I had the same problem; it seems to have happened because my ~/.VirtualBox folder was owned by root, and so I had lost write permissions. Perhaps a consequence of running sudo virtualbox at some point.



                The folder was empty, so I just deleted it with sudo rm -d ..., otherwise something like sudo chown myname.myname ~/.VirtualBox would fix the owner/group.






                share|improve this answer


























                  0












                  0








                  0







                  I had the same problem; it seems to have happened because my ~/.VirtualBox folder was owned by root, and so I had lost write permissions. Perhaps a consequence of running sudo virtualbox at some point.



                  The folder was empty, so I just deleted it with sudo rm -d ..., otherwise something like sudo chown myname.myname ~/.VirtualBox would fix the owner/group.






                  share|improve this answer













                  I had the same problem; it seems to have happened because my ~/.VirtualBox folder was owned by root, and so I had lost write permissions. Perhaps a consequence of running sudo virtualbox at some point.



                  The folder was empty, so I just deleted it with sudo rm -d ..., otherwise something like sudo chown myname.myname ~/.VirtualBox would fix the owner/group.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 30 '16 at 16:42









                  mwfearnleymwfearnley

                  1,02221120




                  1,02221120






























                      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%2f525421%2fvirtualbox-runs-as-root-critical-error-as-user%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

                      flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                      Mangá

                       ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕