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 682581 - Open file from CLI doesn't use current directory context
Open file from CLI doesn't use current directory context
Status: RESOLVED DUPLICATE of bug 643807
Product: totem
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-08-24 03:06 UTC by Keywan Najafi Tonekaboni
Modified: 2012-08-24 08:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Keywan Najafi Tonekaboni 2012-08-24 03:06:59 UTC 
I tried to open a file from a different  directory from the command line. It appears only, when totem is already running, startet from a different directory:

How to reproduce:

1. Start Totem (e.g. via ALT-F2)

2. Open a Terminal.

3. Change path. It should not be your homedir.

cd /tmp/foo

4.  Run the totem command with a file without an absolute path.
totem bar.ogg

"An error occurred: Location not found." 

The playlist entry refers to "file:///home/user/bar.ogg"

But it works:
- with totem `pwd`/bar.ogg
- when Totem wasn't running before
- when the file is in the directory, from where Totem was started
Comment 1 Bastien Nocera 2012-08-24 08:51:07 UTC 
You're not mentioning the version of Totem, so I supposed it's an old one.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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