It should already be owned by root so the chown
command is not necessary - this:
sudo chown root:root /usr/bin/pidgin
Changes the ownership and group to be owned by root - it probably was owned by root in the first place, as could of be shown by ls -l /usr/bin/*
, so was not necessary.
This command is what 'locks' the app:
sudo chmod 700 /usr/bin/pidgin
This change the permissions so the pidgin can only be read, written to, and executed by the owner (in the case, root - manual for chmod
here). So to run it, you would have to run it as root with something like:
#sudo pidgin
Without the #
. but DON'T RUN IT
However, that is a really bad idea (SO DON'T RUN IT), as any malicious code (there shouldn't be, but some things online can be evil) that is run could infect the system as root has access to everything - also as it run as root it can't use any of the configuration you made as your normal user, as root is a different user entirely.
To 'unlock' it so you can access it, run:
sudo chmod 755 /usr/bin/pidgin
This changes the permissions back.
To lock an app, try the answers @Jacob suggested above:
Can't you find a "milder" solution here: askubuntu.com/questions/548568/… or here: askubuntu.com/questions/445145/password-for-apps/445184#445184? You cannot run pidgin now because only root has permission run it. (and a password is only asked when you use gksu <application>
Also, with commands you find on the internet (most on this site are ok - check all of the answer, the other answers, and comments first though), it may be ideal (particularly when run with sudo
as root) to look up info on the command with chmod --help
, man chmod
, or online, so you can find out what the command actually does.
gksu <application>
.