Similar error here.
Ubuntu 22.04 LTS, home-directories mounted via NFSv3 under /home/user/*
I am not able to start firefox. Error message:
tstephan@ifb2e5fe:~$ firefox
cannot open path of the current working directory: Permission denied
I included @{HOMEDIRS}+=/home/user/ in
I get the same error "cannot open path of the current working directory:
Permission denied" when trying to open a file located on a filesystem which is
mounted with sshfs.
This is the case for firefox and chromium-browser (both snaps), but not for
google-chrome (not snap).
This is on 22.04. It
Matthieu, more recently a more likely problem has been characterized by Alberto
Mardegan and found the line in question in
https://bugs.launchpad.net/snapd/+bug/1973321
In particular, restarting snapd doesn't help at all for me, so having
the directory mounted before snapd starts doesn't help,
In https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 it is
suggested that the problem is triggered by snapd starting too early
(before autofs mounts any home directory) is there a way to force autofs
to mount an home directory before launching snapd ?
--
You received this bug
With Ubuntu 22 shipping firefox as a snap, it fails to start here :
"cannot open path of the current working directory: Permission denied"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I (using Kerberos) don't the get apparmor DENIED messages that Eric (not
using Kerberos) did, but I get exactly the same "cannot open path of the
current working directory: Permission denied" error.
--
You received this bug notification because you are a member of Desktop
Packages, which is
In our situation home folders are mounted using autofs using NFS v4,
Kerberos is NOT in use.
root@jammy:~# lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04
root@jammy:~# dpkg -l chromium-browser
--snip--
ii chromium-browser 1:85.0.4183.83-0ubuntu2 amd64
I think I'm using 4, but I am set up using autofs and haven't touched
NFS directly:
# /etc/auto.home
* -fstype=nfs,rw,async servername:/nfshome/&
`nfsstat -c` tells me: "Client nfs v4"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Firefox also doesn't work now it is a snap in 22.04.
I think there are still multiple issues here. The original poster seems
to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple
ports, one of which is called something like RPC, but I am not an expert
in this as I have only
** Package changed: chromium-browser (Ubuntu) => snapd (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884299
Title:
Chromium snap won't run with nfs home drive
** Description changed:
My physical computer lab uses nfs home drives. If any user tries to
run chromium browser, it fails.
- I assume it is related to this:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
+ I assume it is related to these:
+
12 matches
Mail list logo