Bug 699208 – --working-directory argument ignored

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 699208 - --working-directory argument ignored


Summary:	--working-directory argument ignored


Status:	RESOLVED DUPLICATE of bug 697475

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	3.8.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2013-04-29 10:05 UTC by timothyhobbs
Modified:	2013-04-29 10:28 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description timothyhobbs 2013-04-29 10:05:53 UTC

Hello, I'm running an up to date arch linux with bash as my shell.

$ echo $SHELL
/bin/bash

$ pacman -Q bash
bash 4.2.045-1

$ pacman -Q gnome-terminal
gnome-terminal 3.8.1-1

When I open a new window with gnome-terminal, or a new tab, my current working directory is not preserved.

When I run gnome-terminal with the --working-directory the option is ignored(no error message is shown).

However, bash DOES seem to respect the environment.  When I type $bash, the PWD is preserved.

Comment 1 Christian Persch 2013-04-29 10:12:13 UTC

Please read https://live.gnome.org/Terminal/ReportingBugs before reporting bugs.

(In reply to comment #0)
> When I open a new window with gnome-terminal, or a new tab, my current working
> directory is not preserved.

This is covered in the FAQ: https://live.gnome.org/Terminal/FAQ 

> When I run gnome-terminal with the --working-directory the option is ignored(no
> error message is shown).

This works here, must be a bug in your distro.

*** This bug has been marked as a duplicate of bug 697475 ***

Comment 2 timothyhobbs 2013-04-29 10:28:44 UTC

I have send a bug report to the Arch guys, but I'd really like to see some explanation of WHY this change occurred?  What rational is there for this change?