Package Details: torguard 3.90.0-3

Git Clone URL: (read-only)
Package Base: torguard
Description: TorGuard VPN Software Stay private online with TorGuard's anonymous VPN software and connect to 37+ countries worldwide.
Upstream URL:
Licenses: custom
Submitter: coco
Maintainer: coco (thatgeek, dramm)
Last Packager: dramm
Votes: 8
Popularity: 0.383062
First Submitted: 2017-01-25 16:18
Last Updated: 2018-11-02 20:43

Latest Comments

1 2 3 Next › Last »

tomacrisan commented on 2018-11-05 20:53

I had to use Exec=/usr/bin/pkexec /opt/torguard/bin/torguard or as you suggest: Exec=pkexec /opt/torguard/bin/torguard. pkexec would not work for me with the torguard link in /usr/bin.

dramm commented on 2018-11-05 11:57

If pkexec is in your PATH (and it should) you don't need /usr/bin/pkexec, just pkexec

tomacrisan commented on 2018-11-04 23:39

My system has pkexec installed and I never really thought much about what was going on behind the scenes. Gparted does something similar with pkexec when I start it up as an ordinary user.

Perhaps some instructions would be useful for new users installing torguard from the AUR repository versus using the Arch Linux package directly from TorGuard.

Thanks for the suggestion. For my system, Exec=/usr/bin/pkexec /usr/bin/torguard will probably work. I'm not sure if gksudo and kdesudo are around anymore.

dramm commented on 2018-11-04 23:10

I removed the sudoers file that comes with the original package and since that wrapper never worked in my machines (I wrongly assumed that it also didn't work for everybody else) I also removed it. I won't have time to work on this until the next weekend. You can, however, simply edit the torguard.desktop file changing the Exec line to something like: Exec=gksudo /usr/bin/torguard

AFAICT all the wrapper was supposed to do was identify if you use gksudo, kdesudo or pkexec and call it, so by modifying the desktop file you should get the same behaviour. If you don't want to type your password every time you can then add a rule, probably in sudoers.d

tomacrisan commented on 2018-11-04 21:36

So I see what you've changed: the vendor package puts a link in /usr/bin/torguard that points to torguard-wrapper which is a script which prompts for a sudo GUI prompt if one does not have root privileges. Your /usr/bin/torguard link points directly to the torguard executable.

This requires that as a simple user, I need to setup torguard to automatically run as root under my userid or perhaps all user userids. I will have to think about whether I want to do this.

tomacrisan commented on 2018-11-04 19:48

Yes, it runs from sudo but that is the issue; the previous versions and the version directly from Torguard prompt for the superuser password when the program is started. Version 3.90.0-3 posted here does not prompt for the superuser password when started from torguard.desktop or the command line, it simply starts up. Then when attempting to make a connection, it then flags an error.

dramm commented on 2018-11-04 13:56

Try opening it with sudo

tomacrisan commented on 2018-11-04 13:28

Can anyone help me with this? The latest update flags this error when I try to connect to a Torguard VPN server:

:ERROR: Cannot ioctl TUNSETIFF tun: Operation not permitted (errno=1)

The vendor's PKGBUILD install works for 3.90 but in reading the comments here, I understand the vendor's version does not meet Arch Linux standards for being included in the repositories.

camilobog commented on 2018-10-30 20:59

Hi, can you upload the new update? (was released today). Thanks for your work! pd. The official update its here:

but i cant update directly i need your help to install from repository.

eschwartz commented on 2018-09-30 04:05

I didn't say "add qt5-base as a dependency", I said "move the executable to /usr/bin and then add qt5-base as a dependency".

The point is to see if it can work with the system qt5-base, not merely to depend on the system qt5-base and not even use it.

In a similar vein, stunnel, ss-local and shadowsocks are all provided bundled into the prebuilt archive, but they should be possible to debundle just like debundling qt5-base.

Either way, debundling qt5 takes more work than just adding it to the dependencies.