New terminals don't start in correct directory if it's a symlink
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| terminator (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Steps to reproduce:
1) Create symlink to an existing directory.
$ mkdir orig
$ ln -s orig link
2) cd into symlink
$ cd link
3) Observe that current working directory is "link".
4) Open a new tab or split current terminal.
Observed behaviour
• New terminal's working directory is the target of the symlink (i.e. 'orig').
Expected behaviour
• New terminal's working directory should be the original directory (i.e. 'link').
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: terminator 0.97-1ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sun Nov 3 14:32:13 2013
InstallationDate: Installed on 2012-12-16 (321 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
PackageArchitec
SourcePackage: terminator
UpgradeStatus: Upgraded to saucy on 2013-10-18 (16 days ago)
| Sparhawk (sparhawkthesecond) wrote | #1 |
| Egmont Koblinger (egmont-gmail) wrote | #2 |
| Egmont Koblinger (egmont-gmail) wrote | #3 |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in terminator (Ubuntu): | |
| status: | New → Confirmed |
vte 0.34 reworks the way the current directory is known, it relies on the shell setting it by OSC 7 escape sequences. Properly upgrading to gtk3 and new vte would solve this issue.