pwd is changed when opening a new tab from withing a symbolic link

[K t]

Binary package hint: gnome-terminal

Normally when you open up a new tab your pwd i the new tab remains the same as your pwd in the old tab.

However, If you have navigated into a directory structure that contains symbolic links and open up a new tab, your pwd is changed to the absolute path, bypassing any symbolic links.

For example:

cd ~
mkdir temp
cd temp
ln -s /media drives
cd drives
# at this point 'pwd' should show ~/temp/drives
# however if a new tab is opened, 'pwd' would show /media

This is in Gnome 2.32.0 on Ubuntu 10.10

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Tue Nov 30 16:25:23 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1623): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
 (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Daniel Aguerrevere (dannns)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 263637, so it is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Additionally this is reported upstream in https://bugzilla.gnome.org/show_bug.cgi?id=502146. According to a gnome-terminal developer it looks very difficult that this bug could be fixed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.