shell-init: error <...> after running ecryptfs-mount-private

Bug #1825728 reported by Kipras Melnikovas on 2019-04-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
Undecided
Unassigned

Bug Description

After manually unmounting the home directory:

```bash
cd /
$ ecryptfs-umount-private

Sessions still open, not unmounting

$ ecryptfs-umount-private

INFO: Your private directory has been unmounted.
INFO: To see this change in your current shell:
  cd /home/kipras

```

and then manually re-mounting the home directory:

```bash
$ ecryptfs-mount-private

Enter your login passphrase:

Inserted auth tok with sig [THE_SIGNATURE] into the user session keyring

INFO: Your private directory has been mounted.
INFO: To see this change in your current shell:
  cd /home/kipras

```

Everything seems to work. However, if I launch another terminal, I get the following error:

```
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
```

If I `cd ~`, the terminal works fine as expected. BUT, if I launch another terminal - the same `shell-init` error comes up. It keeps happening every time I open a new terminal.

---

Signing out and then signing back in makes the problem go away.

---

I'm using arch linux.

```
$ uname -a

Linux arch-usb 5.0.7-arch1-1-ARCH #1 SMP PREEMPT Mon Apr 8 10:37:08 UTC 2019 x86_64 GNU/Linux
```

---

Also, this is probably not related since this comes from NodeJS, but I also get these errors together with the `shell-init` error:

```
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
path.js:975
      const path = i >= 0 ? args[i] : process.cwd();
                                              ^

Error: ENOENT: no such file or directory, uv_cwd
    at Object.resolve (path.js:975:47)
    at Function.Module._resolveLookupPaths (internal/modules/cjs/loader.js:550:17)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:648:20)
    at Function.Module._load (internal/modules/cjs/loader.js:580:25)
    at Module.require (internal/modules/cjs/loader.js:711:19)
    at require (internal/modules/cjs/helpers.js:14:16)
    at /home/kipras/.config/nvm/versions/node/v11.13.0/lib/node_modules/npm/bin/npm-cli.js:19:21
    at Object.<anonymous> (/home/kipras/.config/nvm/versions/node/v11.13.0/lib/node_modules/npm/bin/npm-cli.js:153:3)
    at Module._compile (internal/modules/cjs/loader.js:805:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:816:10)
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v11.13.0 --silent` to unset it.
```

description: updated
tags: added: ecryptfs-mount-private
tags: added: directories getcwd parent shell-init
tags: added: parent-directories
removed: directories parent
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers