[tor-bugs] #10030 [Tor bundles/installation]: Tor pluggable transport bundle does not work in OS X Mavericks
Tor Bug Tracker & Wiki
blackhole at torproject.org
Mon Nov 4 20:19:47 UTC 2013
#10030: Tor pluggable transport bundle does not work in OS X Mavericks
------------------------------------------+------------------------------
Reporter: msfc | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor bundles/installation | Version: Tor: 0.2.4.16-rc
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
------------------------------------------+------------------------------
Comment (by dcf):
Replying to [comment:14 aze]:
> On 10.9 Mavericks
>
> {{{
> cat /tmp/pathtest.txt
> /
> /usr/bin:/bin:/usr/sbin:/sbin:/usr/sbin
> }}}
Thanks. It looks like this change in working directory is the direct cause
of the problem.
Somehow the app bundle manages to launch Vidalia and Vidalia manages to
launch Tor. But Tor isn't able to launch its pluggable transports. We
should find out what Vidalia or other startup script is doing differently
that makes it work.
I found reports in other software that seem to have the same cause:
* [https://bugreports.qt-project.org/browse/QTBUG-34300
QDir::currentPath() not returning current application's folder pathname
under OSX 10.9 Mavericks]
* [https://qt-project.org/forums/viewthread/34019 QDir::currentPath() OSX
10.9 Mavericks bug]
* [https://code.google.com/p/eiskaltdc/issues/detail?id=1442 Mac OS X
10.9: problem with loading program icons]
The first link says that `QDir::currentPath()` returns `"/"` (or an empty
string, it's not clear), while `QApplication::applicationDirPath()`
returns something useful. So we could check out what
`QApplication::applicationDirPath()` does.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10030#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list