• Status Requires Testing
  • Percent Complete
  • Task Type Bug Report
  • Category Stable
  • Assigned To
    André Silva
  • Operating System Hyperbola GNU/Linux-libre
  • Severity Critical
  • Priority Medium
  • Reported Version Milky Way v0.3
  • Due in Version Starfix
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Packages
Opened by fablamar - 16/10/2019
Last edited by André Silva - 17/10/2019

FS#1449 - [torsocks] which: no getcap

Current torsocks version is broken.
It returns the following error when attempting to torify application :

which: no getcap
fablamar commented on 17.10.2019 13:32

@André Silva :

Error is still present with torsocks in "testing" repo.

Example :

rc-service tor start -v
torsocks curl #to display ip used by tor

output :
which: no getcap

So it seems to work but it still displays that "which: no getcap", this wasn't the case before. (in 0.2.9)

André Silva commented on 17.10.2019 16:01
which: no getcap

getcap was moved to /sbin for FHS compliance reasons. So the tor user should be added to the adm group to work it again, eg.

# gpasswd -a tor adm

Please let me know if it works, then i could automatize it through the tor package.

fablamar commented on 17.10.2019 18:01

It doesn't work.
I added tor to adm and restarted tor service.
Also tried to add my username to adm group and restart tor service.
Maybe I need to reboot ? For now I can't because of a current task. I'll let you know later.

fablamar commented on 17.10.2019 21:35

@André Silva :

After a reboot, it works now. But only if I add my username to adm group.
Adding "tor" to adm group as you suggested is not enough.
Let me know if I'm misunderstood something.

Thank you.

Date User Effort (H:M)


Available keyboard shortcuts


Task Details

Task Editing