Xfennec / progress

Linux tool to show progress for cp, mv, dd, ... (formerly known as cv)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

progress doesn't do anything unless run with sudo

JeffFaer opened this issue · comments

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"
$ sudo apt install progress
.
.
.
Preparing to unpack .../progress_0.14-4_amd64.deb ...
Unpacking progress (0.14-4) ...
Setting up progress (0.14-4) ...
Processing triggers for man-db (2.9.1-1) ...
$ progress --version
$ echo $?
0
$ progress --help
$ echo $?
0
$ progress -d
$ echo $?
0
$ sudo progress --version
progress version 0.14
$ sudo progress --help
progress - Coreutils Viewer
---------------------
Shows progress on file manipulations (cp, mv, dd, ...)
.
.
.
$ sudo progress -d
No command currently running: cp, mv, dd, tar, cat, rsync, grep, fgrep, egrep, cut, sort, md5sum, sha1sum, sha224sum, sha256sum, sha384sum, sha512sum, adb, gzip, gunzip, bzip2, bunzip2, xz, unxz, lzma, unlzma, 7z, 7za, zcat, bzcat, lzcat, split, gpg, or wrong permissions.

Is this intentional? progress is exiting 0 without printing anything unless I run it with sudo, but I don't see that mentioned anywhere in the docs, which makes me think I'm holding it wrong

It is not intentional, and I can't reproduce the issue on a fresh Ubuntu 20.04.2.

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"
$ progress -v
progress version 0.14

Is it possible that you have another binary named progress (or an alias) for this user?

Doesn't look like it

$ which progress
/usr/bin/progress
$ alias progress
bash: alias: progress: not found
$ dpkg -S /usr/bin/progress
progress: /usr/bin/progress

There's obviously something specific to this user ;)

A few ideas:

  • call the binary with the full path? /usr/bin/progress -h
  • strace progress?
  • env -i bin/progress -v for a clean environment?
  • create a new unprivileged user?

Aha, it looks like this is my fault

$ /usr/bin/progress -v
progress version 0.14
$ type progress
progress is a function

looks like I had a bash function laying around named progress. Sorry for the noise