mount error when installed using snap











up vote
2
down vote

favorite
1












On Ubuntu 16.04, I installed cloudcompare using snap following:



sudo snap install cloudcompare


However, I get the following error when trying to launch it:



$ sudo cloudcompare.CloudCompare 
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_AUR1hM//home: Permission denied


How do I fix this?










share|improve this question
























  • Any chance this is in a lxd container?
    – Kyle
    Dec 1 '17 at 17:03










  • No, I am not running this inside a container.
    – tejaskhot
    Dec 2 '17 at 17:58















up vote
2
down vote

favorite
1












On Ubuntu 16.04, I installed cloudcompare using snap following:



sudo snap install cloudcompare


However, I get the following error when trying to launch it:



$ sudo cloudcompare.CloudCompare 
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_AUR1hM//home: Permission denied


How do I fix this?










share|improve this question
























  • Any chance this is in a lxd container?
    – Kyle
    Dec 1 '17 at 17:03










  • No, I am not running this inside a container.
    – tejaskhot
    Dec 2 '17 at 17:58













up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





On Ubuntu 16.04, I installed cloudcompare using snap following:



sudo snap install cloudcompare


However, I get the following error when trying to launch it:



$ sudo cloudcompare.CloudCompare 
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_AUR1hM//home: Permission denied


How do I fix this?










share|improve this question















On Ubuntu 16.04, I installed cloudcompare using snap following:



sudo snap install cloudcompare


However, I get the following error when trying to launch it:



$ sudo cloudcompare.CloudCompare 
cannot perform operation: mount --rbind /home /tmp/snap.rootfs_AUR1hM//home: Permission denied


How do I fix this?







mount snap






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 21 '17 at 4:50

























asked Nov 21 '17 at 4:44









tejaskhot

176310




176310












  • Any chance this is in a lxd container?
    – Kyle
    Dec 1 '17 at 17:03










  • No, I am not running this inside a container.
    – tejaskhot
    Dec 2 '17 at 17:58


















  • Any chance this is in a lxd container?
    – Kyle
    Dec 1 '17 at 17:03










  • No, I am not running this inside a container.
    – tejaskhot
    Dec 2 '17 at 17:58
















Any chance this is in a lxd container?
– Kyle
Dec 1 '17 at 17:03




Any chance this is in a lxd container?
– Kyle
Dec 1 '17 at 17:03












No, I am not running this inside a container.
– tejaskhot
Dec 2 '17 at 17:58




No, I am not running this inside a container.
– tejaskhot
Dec 2 '17 at 17:58










2 Answers
2






active

oldest

votes

















up vote
1
down vote













Try running it without sudo? I tried running with sudo and got a different error related to permission, but running it without works for me.



EDIT:



The answer above is wrong. According to this bug, this will happen when /home is a symlink to a different directory.



To fix this, you need your /home directory to be a real directory. You can run the following command to remove the symlink and create an actual directory in /home.



sudo rm -R /home && sudo mkdir -p /home/${whoami} && sudo chmod ugo+rwx /home/$whoami



Alternatively, you can create a different user to run cloudcompare if you do not wish to modify your system.






share|improve this answer























  • Tried this, but no luck.
    – tejaskhot
    Dec 2 '17 at 17:58










  • Hi, I've modified the answer, hope it helps.
    – daniellim
    Dec 5 '17 at 4:12










  • Seriously sudo rm -R /home ? xD Good luck with that
    – l3l0
    Nov 19 at 15:13


















up vote
0
down vote













I had this exact problem and was able to fix it using a bind mount instead of a symlink. In my case I had a symlink for my home dir to /data/home. Start by removing that;



rm /home


Then edit your /etc/fstab and add the line;



/data/home      /home   none    bind


Reboot to test and /data/home will be mounted to /home






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',
    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%2f978639%2fmount-error-when-installed-using-snap%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








    up vote
    1
    down vote













    Try running it without sudo? I tried running with sudo and got a different error related to permission, but running it without works for me.



    EDIT:



    The answer above is wrong. According to this bug, this will happen when /home is a symlink to a different directory.



    To fix this, you need your /home directory to be a real directory. You can run the following command to remove the symlink and create an actual directory in /home.



    sudo rm -R /home && sudo mkdir -p /home/${whoami} && sudo chmod ugo+rwx /home/$whoami



    Alternatively, you can create a different user to run cloudcompare if you do not wish to modify your system.






    share|improve this answer























    • Tried this, but no luck.
      – tejaskhot
      Dec 2 '17 at 17:58










    • Hi, I've modified the answer, hope it helps.
      – daniellim
      Dec 5 '17 at 4:12










    • Seriously sudo rm -R /home ? xD Good luck with that
      – l3l0
      Nov 19 at 15:13















    up vote
    1
    down vote













    Try running it without sudo? I tried running with sudo and got a different error related to permission, but running it without works for me.



    EDIT:



    The answer above is wrong. According to this bug, this will happen when /home is a symlink to a different directory.



    To fix this, you need your /home directory to be a real directory. You can run the following command to remove the symlink and create an actual directory in /home.



    sudo rm -R /home && sudo mkdir -p /home/${whoami} && sudo chmod ugo+rwx /home/$whoami



    Alternatively, you can create a different user to run cloudcompare if you do not wish to modify your system.






    share|improve this answer























    • Tried this, but no luck.
      – tejaskhot
      Dec 2 '17 at 17:58










    • Hi, I've modified the answer, hope it helps.
      – daniellim
      Dec 5 '17 at 4:12










    • Seriously sudo rm -R /home ? xD Good luck with that
      – l3l0
      Nov 19 at 15:13













    up vote
    1
    down vote










    up vote
    1
    down vote









    Try running it without sudo? I tried running with sudo and got a different error related to permission, but running it without works for me.



    EDIT:



    The answer above is wrong. According to this bug, this will happen when /home is a symlink to a different directory.



    To fix this, you need your /home directory to be a real directory. You can run the following command to remove the symlink and create an actual directory in /home.



    sudo rm -R /home && sudo mkdir -p /home/${whoami} && sudo chmod ugo+rwx /home/$whoami



    Alternatively, you can create a different user to run cloudcompare if you do not wish to modify your system.






    share|improve this answer














    Try running it without sudo? I tried running with sudo and got a different error related to permission, but running it without works for me.



    EDIT:



    The answer above is wrong. According to this bug, this will happen when /home is a symlink to a different directory.



    To fix this, you need your /home directory to be a real directory. You can run the following command to remove the symlink and create an actual directory in /home.



    sudo rm -R /home && sudo mkdir -p /home/${whoami} && sudo chmod ugo+rwx /home/$whoami



    Alternatively, you can create a different user to run cloudcompare if you do not wish to modify your system.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 5 '17 at 4:12

























    answered Nov 30 '17 at 12:01









    daniellim

    134




    134












    • Tried this, but no luck.
      – tejaskhot
      Dec 2 '17 at 17:58










    • Hi, I've modified the answer, hope it helps.
      – daniellim
      Dec 5 '17 at 4:12










    • Seriously sudo rm -R /home ? xD Good luck with that
      – l3l0
      Nov 19 at 15:13


















    • Tried this, but no luck.
      – tejaskhot
      Dec 2 '17 at 17:58










    • Hi, I've modified the answer, hope it helps.
      – daniellim
      Dec 5 '17 at 4:12










    • Seriously sudo rm -R /home ? xD Good luck with that
      – l3l0
      Nov 19 at 15:13
















    Tried this, but no luck.
    – tejaskhot
    Dec 2 '17 at 17:58




    Tried this, but no luck.
    – tejaskhot
    Dec 2 '17 at 17:58












    Hi, I've modified the answer, hope it helps.
    – daniellim
    Dec 5 '17 at 4:12




    Hi, I've modified the answer, hope it helps.
    – daniellim
    Dec 5 '17 at 4:12












    Seriously sudo rm -R /home ? xD Good luck with that
    – l3l0
    Nov 19 at 15:13




    Seriously sudo rm -R /home ? xD Good luck with that
    – l3l0
    Nov 19 at 15:13












    up vote
    0
    down vote













    I had this exact problem and was able to fix it using a bind mount instead of a symlink. In my case I had a symlink for my home dir to /data/home. Start by removing that;



    rm /home


    Then edit your /etc/fstab and add the line;



    /data/home      /home   none    bind


    Reboot to test and /data/home will be mounted to /home






    share|improve this answer

























      up vote
      0
      down vote













      I had this exact problem and was able to fix it using a bind mount instead of a symlink. In my case I had a symlink for my home dir to /data/home. Start by removing that;



      rm /home


      Then edit your /etc/fstab and add the line;



      /data/home      /home   none    bind


      Reboot to test and /data/home will be mounted to /home






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        I had this exact problem and was able to fix it using a bind mount instead of a symlink. In my case I had a symlink for my home dir to /data/home. Start by removing that;



        rm /home


        Then edit your /etc/fstab and add the line;



        /data/home      /home   none    bind


        Reboot to test and /data/home will be mounted to /home






        share|improve this answer












        I had this exact problem and was able to fix it using a bind mount instead of a symlink. In my case I had a symlink for my home dir to /data/home. Start by removing that;



        rm /home


        Then edit your /etc/fstab and add the line;



        /data/home      /home   none    bind


        Reboot to test and /data/home will be mounted to /home







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 30 at 1:00









        Stephen Bancroft

        11




        11






























            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.





            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%2faskubuntu.com%2fquestions%2f978639%2fmount-error-when-installed-using-snap%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

            Quarter-circle Tiles

            build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

            Mont Emei