Permission denied error when running apps installed as snap packages - Ubuntu 17.04
I get Permission denied error when running a snap application, where my home directory is mounted on an nfs mount point that does not allow root-write.
This is not an unusual configuration, so I consider this a bug.
The error message:
cannot create user data directory: /home/tcumming/snap/vlc/4: Permission denied
Also had the same problem with ubuntu 16.
Some more info as requested:
Using the ubuntu, "Ubuntu Software" I install a snap application (for example, vlc). When I attempt to run it (from the command line), I get the, "Permission denied" message above.
I had just reinstalled Ubuntu on the machine, so there has been no messing around with the OS. I did preserve my uid:gid so I could mount my prior nfs share.
This is not a problem with the mount point, or nfs. Our mount point is not root-writeable for security reasons.
I guess the question is, should I file a bug report? What are my next steps?
permissions snap nfs
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
add a comment |
I get Permission denied error when running a snap application, where my home directory is mounted on an nfs mount point that does not allow root-write.
This is not an unusual configuration, so I consider this a bug.
The error message:
cannot create user data directory: /home/tcumming/snap/vlc/4: Permission denied
Also had the same problem with ubuntu 16.
Some more info as requested:
Using the ubuntu, "Ubuntu Software" I install a snap application (for example, vlc). When I attempt to run it (from the command line), I get the, "Permission denied" message above.
I had just reinstalled Ubuntu on the machine, so there has been no messing around with the OS. I did preserve my uid:gid so I could mount my prior nfs share.
This is not a problem with the mount point, or nfs. Our mount point is not root-writeable for security reasons.
I guess the question is, should I file a bug report? What are my next steps?
permissions snap nfs
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48
add a comment |
I get Permission denied error when running a snap application, where my home directory is mounted on an nfs mount point that does not allow root-write.
This is not an unusual configuration, so I consider this a bug.
The error message:
cannot create user data directory: /home/tcumming/snap/vlc/4: Permission denied
Also had the same problem with ubuntu 16.
Some more info as requested:
Using the ubuntu, "Ubuntu Software" I install a snap application (for example, vlc). When I attempt to run it (from the command line), I get the, "Permission denied" message above.
I had just reinstalled Ubuntu on the machine, so there has been no messing around with the OS. I did preserve my uid:gid so I could mount my prior nfs share.
This is not a problem with the mount point, or nfs. Our mount point is not root-writeable for security reasons.
I guess the question is, should I file a bug report? What are my next steps?
permissions snap nfs
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
I get Permission denied error when running a snap application, where my home directory is mounted on an nfs mount point that does not allow root-write.
This is not an unusual configuration, so I consider this a bug.
The error message:
cannot create user data directory: /home/tcumming/snap/vlc/4: Permission denied
Also had the same problem with ubuntu 16.
Some more info as requested:
Using the ubuntu, "Ubuntu Software" I install a snap application (for example, vlc). When I attempt to run it (from the command line), I get the, "Permission denied" message above.
I had just reinstalled Ubuntu on the machine, so there has been no messing around with the OS. I did preserve my uid:gid so I could mount my prior nfs share.
This is not a problem with the mount point, or nfs. Our mount point is not root-writeable for security reasons.
I guess the question is, should I file a bug report? What are my next steps?
permissions snap nfs
permissions snap nfs
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
edited Jul 1 '17 at 7:44
David Foerster
28.3k1365111
28.3k1365111
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
asked Jun 29 '17 at 20:51
Tom CummingTom Cumming
3113
3113
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48
add a comment |
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48
add a comment |
3 Answers
3
active
oldest
votes
Same happens in Ubuntu 18.04.
If the user home directory is not under the /home (or /) mount, it not possible to work with snap. My HOMEDIR was on another local SSD disk, but since it was not mounted under /home, every package installed by snap was failing.
Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc.
Maybe snap will be more flexible inthe future, but it is not a priority:
https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont-use-home-user/3352/6
The workaround right now is to remove snap and install things from *.tar.gz or from *.deb packages.
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
add a comment |
Snap apps are confined to a sandbox by default, for security. If you want snap applications to be able to read/write data in your home directory, you should install them in classic mode. Try:
rclone install --classic vlc
This should work for you.
If application sandboxing is a concern, then you might want to look into firejail.
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
add a comment |
You can set the permissions of the Snap Application from the Software Store.
See: http://www.linuxandubuntu.com/home/snap-application-permissions
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f930437%2fpermission-denied-error-when-running-apps-installed-as-snap-packages-ubuntu-17%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Same happens in Ubuntu 18.04.
If the user home directory is not under the /home (or /) mount, it not possible to work with snap. My HOMEDIR was on another local SSD disk, but since it was not mounted under /home, every package installed by snap was failing.
Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc.
Maybe snap will be more flexible inthe future, but it is not a priority:
https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont-use-home-user/3352/6
The workaround right now is to remove snap and install things from *.tar.gz or from *.deb packages.
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
add a comment |
Same happens in Ubuntu 18.04.
If the user home directory is not under the /home (or /) mount, it not possible to work with snap. My HOMEDIR was on another local SSD disk, but since it was not mounted under /home, every package installed by snap was failing.
Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc.
Maybe snap will be more flexible inthe future, but it is not a priority:
https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont-use-home-user/3352/6
The workaround right now is to remove snap and install things from *.tar.gz or from *.deb packages.
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
add a comment |
Same happens in Ubuntu 18.04.
If the user home directory is not under the /home (or /) mount, it not possible to work with snap. My HOMEDIR was on another local SSD disk, but since it was not mounted under /home, every package installed by snap was failing.
Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc.
Maybe snap will be more flexible inthe future, but it is not a priority:
https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont-use-home-user/3352/6
The workaround right now is to remove snap and install things from *.tar.gz or from *.deb packages.
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
Same happens in Ubuntu 18.04.
If the user home directory is not under the /home (or /) mount, it not possible to work with snap. My HOMEDIR was on another local SSD disk, but since it was not mounted under /home, every package installed by snap was failing.
Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc.
Maybe snap will be more flexible inthe future, but it is not a priority:
https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont-use-home-user/3352/6
The workaround right now is to remove snap and install things from *.tar.gz or from *.deb packages.
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
answered Apr 30 '18 at 11:25
estibordoestibordo
49939
49939
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
add a comment |
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
5
5
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
So far snap = worst idea ever. Too soon :-p
– Ligemer
May 12 '18 at 0:48
1
1
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
This is really sad and close to a showstopper, especially for huge deployments where $HOME resides on NFS or CIFS shares mounted via autofs-ldap.
– Sebastian Stark
Jun 9 '18 at 13:33
1
1
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
"Since Canonical is moving to support snap, you will have to loose this kind of nice things, such as HOMEDIRs on other file systems, mounted by NFS, etc." I don't think canonical is going to convince people running Ubuntu in commercial/business environments to stop using centralised network mounted home directories in favor of local ones just so they can use "snap packages"...
– Dean
Jul 30 '18 at 12:43
1
1
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
SSD/HD PCs are all too common nowadays. Many (but not all!) of my /snap/bin/ commands would fail with the misleading "permission denied" error with the input files and the problem could not be resolved by messing with file permissions but by removing the /snap/ package and re-installing them with apt! (Ubuntu 18.04)
– SYK
Oct 10 '18 at 4:58
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
This question, or its cause, is totally underrated in my book. It can't be low priority that things don't work for a major part of the userbase.
– SeveQ
Nov 23 '18 at 8:50
add a comment |
Snap apps are confined to a sandbox by default, for security. If you want snap applications to be able to read/write data in your home directory, you should install them in classic mode. Try:
rclone install --classic vlc
This should work for you.
If application sandboxing is a concern, then you might want to look into firejail.
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
add a comment |
Snap apps are confined to a sandbox by default, for security. If you want snap applications to be able to read/write data in your home directory, you should install them in classic mode. Try:
rclone install --classic vlc
This should work for you.
If application sandboxing is a concern, then you might want to look into firejail.
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
add a comment |
Snap apps are confined to a sandbox by default, for security. If you want snap applications to be able to read/write data in your home directory, you should install them in classic mode. Try:
rclone install --classic vlc
This should work for you.
If application sandboxing is a concern, then you might want to look into firejail.
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
Snap apps are confined to a sandbox by default, for security. If you want snap applications to be able to read/write data in your home directory, you should install them in classic mode. Try:
rclone install --classic vlc
This should work for you.
If application sandboxing is a concern, then you might want to look into firejail.
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
answered Aug 23 '17 at 8:58
PrajjwalPrajjwal
1742
1742
add a comment |
add a comment |
You can set the permissions of the Snap Application from the Software Store.
See: http://www.linuxandubuntu.com/home/snap-application-permissions
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
add a comment |
You can set the permissions of the Snap Application from the Software Store.
See: http://www.linuxandubuntu.com/home/snap-application-permissions
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
add a comment |
You can set the permissions of the Snap Application from the Software Store.
See: http://www.linuxandubuntu.com/home/snap-application-permissions
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
You can set the permissions of the Snap Application from the Software Store.
See: http://www.linuxandubuntu.com/home/snap-application-permissions
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
answered Jan 13 at 4:30
Fabian de BoerFabian de Boer
1
1
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
add a comment |
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
– Kevin Bowen
Jan 13 at 5:07
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f930437%2fpermission-denied-error-when-running-apps-installed-as-snap-packages-ubuntu-17%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
What's the question? How to file a bug report?
– mikewhatever
Jun 29 '17 at 20:57
I am going to guess if you file a bug report it will be marked invalid as it is a configuration problem with nfs and the mount point and not a bug but you can try.
– Panther
Jun 29 '17 at 21:02
Could you please add a little more detail? What exactly did you do, what did you want to achieve and what happened instead? Did you encounter any warning or error messages? Please reproduce them in their entirety in your question. You can select, copy and paste terminal content and most dialogue messages in Ubuntu. (see How do I ask a good question?)
– David Foerster
Jun 30 '17 at 6:23
I edited my original question to address above.
– Tom Cumming
Jul 1 '17 at 1:48