xpra icon
Bug tracker and wiki

Opened 6 months ago

Closed 6 months ago

#2659 closed defect (worksforme)

CWD of new xpra server is not sanitized (i.e. ~)

Reported by: stdedos Owned by: stdedos
Priority: minor Milestone: 4.0
Component: server Version: 3.0.x
Keywords: Cc:


Splitting from #2606

Are invocations "sanitized"?

What invocation?

Is local invocation "equivalent" to what I would get if I did it remotely?

I'm not sure I understand the question. Is it related to this ticket?

From remote start, gnome-terminal seems to start in different CWD all the time.

It depends what type of remote start you are using.
Unless you change the chdir option, the server starts does not change the CWD, so this will be set by the caller. (ie: for ssh start, whatever sshd + shell are using)

After seeing #2604, I started closing all apps in the client, so I can re-start it anew.

When I started the new client, the cwd of the spawning gnome-terminal was the same as the last directory I cded to on the previous instance of the client.

Change History (2)

comment:1 Changed 6 months ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos


cd /
xpra start --start=xterm --attach=yes

Running pwd in the xterm shows /.

Doing the same thing in "~" or any other path gives the expected result: the path of the commands started by the server is where the server was started from.

When starting a server via ssh, the CWD is always "~".

If you find that this is not the case, please provide specific command lines to reproduce.

comment:2 Changed 6 months ago by Antoine Martin

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.