[Bug 1100806] Re: Gnome terminal can't get into parent directoy

[Travis Hoppe]

Bug was found in the Ask Ubuntu page:

http://askubuntu.com/questions/244043/bash-and-getcwd-fails-in-a-nest-
directory-with-a-dash-in-the-command-line#comment303051_244043

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to command-not-found in Ubuntu.
https://bugs.launchpad.net/bugs/1100806

Title:
  Gnome terminal can't get into parent directoy

Status in “command-not-found” package in Ubuntu:
  New

Bug description:

  Open a terminal and run

       mkdir a1
       mkdir a1/a2
       mkdir a1/a2/a3
       mkdir a1/a2/a3/a4
       mkdir a1/a2/a3/a4/foo-bar
       cd a1/a2/a3/a4/foo-bar
       emasc a.cpp &

  Note that is `emasc` misspelled intentionally. For some reason, this
  will close the terminal with no response. This has been confirmed for
  me on two separate computers. It _does not_ work on a separate shell
  screen `Control-Alt-F2` and _only_ with the default terminal `Control-
  Shift-T`. Is something going here that I don't know about?

  This happens more often than I like, but this is the only sequence of
  commands that reproduces the crash(?) every time.

  Navigating to the directory and running bash `getcwd()` fails
  (sometimes...)!

      cd ~/a1/a2/a3/a4/foo-bar
      bash

  With the error:

      shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
      sh: 0: getcwd() failed: No such file or directory

  Again, this only happens on Gnome terminal as far as I can tell.

      lsb_release -rd
      Description:	Ubuntu 12.10
      Release:	12.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1100806/+subscriptions