working directory is always $HOME when using -x or -e

Bug #1781824 reported by Philippe
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Sakura
Expired
Medium
Unassigned

Bug Description

I upgraded sakura from 3.4 to 3.6, and now the working directory when starting sakura with -x or -e is always $HOME, even if you specify -d.

Steps to reproduce:
- cd /usr/bin
- sakura -e 'sh -c "pwd && sleep 1"' -d $(pwd)

Obtained:
My home directory is printed

Expected:
"/usr/bin"
Also, I would expect it to be /usr/bin even if I hadn't specified -d, as it works without -e or -x

Revision history for this message
David Vogt (wingedlabs) wrote :

I have the same problem - except it's even worse for me - it changes sporadically between the intended path and $HOME. Tested with the following commandline:

# reproduce problem
cd /tmp
for _ in `seq 100`; do sakura -e 'bash -c "pwd >> /tmp/paaaath"'; done

# Show stats
sort /tmp/paaaath | uniq -c
     53 /home/dv
     49 /tmp

My version is also 3.6.0, via the official Archlinux package

David Gómez (dabisu)
Changed in sakura:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
David Gómez (dabisu) wrote :

I'm testing with the last version (3.8.0) and I cannot reproduce this problem.

Philippe: I've tested with your command, with and without -d, and the result is always /usr/bin

David: I've tested your script and the result I got is:
sort /tmp/paaaath |uniq -c
    100 /tmp

Could you both please check if this bug is still present? Thanks

David Gómez (dabisu)
Changed in sakura:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Sakura because there has been no activity for 60 days.]

Changed in sakura:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.