People,
I did a dnf system-upgrade and now I get this before the completion of each CLI command:
[phr@phil ~]$ ls phr009D777;preexecphr009C',data=iris)' . .
- before I start hacking around, has anyone else seen this?
Thanks,
Phil.
People,
On 2020-01-07 19:23, Philip Rhoades wrote:
People,
I did a dnf system-upgrade and now I get this before the completion of each CLI command:
[phr@phil ~]$ ls phr009D777;preexecphr009C',data=iris)' . .
- before I start hacking around, has anyone else seen this?
I narrowed the problem down to F31 /etc/bashrc:
- I renamed ~/.bashrc and ~/bash_profile to temp files
- opened an xterm -> prompt: "bash-5.0$"
- . /etc/bashrc -> prompt includes: "phr009D777;preexecphr009C\u009D777;preexec\u009C"
I eventually worked out that this string is PS0 - but PS0 does not get set in /etc/bashrc as far as I can see . . I can work around the problem by resetting PS0 in my own bash startup but I would like to know what is going on . . anyone?
Thanks,
Phil.
On Thu, 16 Jan 2020 at 17:20, Philip Rhoades phil@pricom.com.au wrote:
People,
On 2020-01-07 19:23, Philip Rhoades wrote:
People,
I did a dnf system-upgrade and now I get this before the completion of each CLI command:
[phr@phil ~]$ ls phr009D777;preexecphr009C',data=iris)' . .
- before I start hacking around, has anyone else seen this?
I narrowed the problem down to F31 /etc/bashrc:
I renamed ~/.bashrc and ~/bash_profile to temp files
opened an xterm -> prompt: "bash-5.0$"
. /etc/bashrc -> prompt includes:
"phr009D777;preexecphr009C\u009D777;preexec\u009C"
I eventually worked out that this string is PS0 - but PS0 does not get set in /etc/bashrc as far as I can see . . I can work around the problem by resetting PS0 in my own bash startup but I would like to know what is going on . . anyone?
Before bash got PS0 there was bash-preexec.sh https://github.com/rcaloras/bash-preexec/blob/master/bash-preexec.sh. If your system was upgraded serially from before PS0 came to bash this might be leftovers from bash-preexec.sh.
On 2020-01-17 05:19, Philip Rhoades wrote:
- . /etc/bashrc -> prompt includes: "phr009D777;preexecphr009C\u009D777;preexec\u009C"
I eventually worked out that this string is PS0 - but PS0 does not get set in /etc/bashrc as far as I can see . . I can work around the problem by resetting PS0 in my own bash startup but I would like to know what is going on . . anyone?
Well, my /etc/bashrc doesn't contain that. And, your username does contain phr? So, wonder if somehow you managed to edit it?
Since....
dnf whatprovides /etc/bashrc
returns setup-2.13.6-1.fc31.noarch why not try just
dnf reinstall setup
to get the original file back?
On 2020-01-17 05:19, Philip Rhoades wrote:
- . /etc/bashrc -> prompt includes: "phr009D777;preexecphr009C\u009D777;preexec\u009C"
I eventually worked out that this string is PS0 - but PS0 does not get set in /etc/bashrc as far as I can see . . I can work around the problem by resetting PS0 in my own bash startup but I would like to know what is going on . . anyone?
Oh, BTW, I have
[egreshko@f31k ~]$ rpm -q setup setup-2.13.6-1.fc31.noarch
And I know I've not altered /etc/bashrc and I get..
[egreshko@f31k ~]$ sha256sum /etc/bashrc d925e7ec2fdd6861be5f3a6d5a08a1ff13a10d23ebbb8d26717b1b75ca4f118f /etc/bashrc
You should get the same if the file has not be changed if you have the same package version installed
On 1/16/20 1:56 PM, Ed Greshko wrote:
Oh, BTW, I have
[egreshko@f31k ~]$ rpm -q setup setup-2.13.6-1.fc31.noarch
And I know I've not altered /etc/bashrc and I get..
[egreshko@f31k ~]$ sha256sum /etc/bashrc d925e7ec2fdd6861be5f3a6d5a08a1ff13a10d23ebbb8d26717b1b75ca4f118f /etc/bashrc
You should get the same if the file has not be changed if you have the same package version installed
Or you can just do "rpm -V setup" to see if anything has changed.
On 2020-01-17 06:03, Samuel Sieb wrote:
On 1/16/20 1:56 PM, Ed Greshko wrote:
Oh, BTW, I have
[egreshko@f31k ~]$ rpm -q setup setup-2.13.6-1.fc31.noarch
And I know I've not altered /etc/bashrc and I get..
[egreshko@f31k ~]$ sha256sum /etc/bashrc d925e7ec2fdd6861be5f3a6d5a08a1ff13a10d23ebbb8d26717b1b75ca4f118f /etc/bashrc
You should get the same if the file has not be changed if you have the same package version installed
Or you can just do "rpm -V setup" to see if anything has changed.
Or, you could think of 100 different ways to accomplish something in Linux.
On 1/16/20 2:43 PM, Ed Greshko wrote:
On 2020-01-17 06:03, Samuel Sieb wrote:
On 1/16/20 1:56 PM, Ed Greshko wrote:
Oh, BTW, I have
[egreshko@f31k ~]$ rpm -q setup setup-2.13.6-1.fc31.noarch
And I know I've not altered /etc/bashrc and I get..
[egreshko@f31k ~]$ sha256sum /etc/bashrc d925e7ec2fdd6861be5f3a6d5a08a1ff13a10d23ebbb8d26717b1b75ca4f118f /etc/bashrc
You should get the same if the file has not be changed if you have the same package version installed
Or you can just do "rpm -V setup" to see if anything has changed.
Or, you could think of 100 different ways to accomplish something in Linux.
Probably, but using the rpm command, it doesn't matter which version he has. And it's generally applicable for any other package as well.
People,
On 2020-01-17 08:35, George N. White III wrote:
Before bash got PS0 there was bash-preexec.sh [1]. If your system was
upgraded serially from before PS0 came to bash this might be leftovers from bash-preexec.sh.
Sounds plausible - and:
On 2020-01-17 09:03, Samuel Sieb wrote:
On 1/16/20 1:56 PM, Ed Greshko wrote:
Oh, BTW, I have
[egreshko@f31k ~]$ rpm -q setup setup-2.13.6-1.fc31.noarch
I get the same.
And I know I've not altered /etc/bashrc and I get..
[egreshko@f31k ~]$ sha256sum /etc/bashrc d925e7ec2fdd6861be5f3a6d5a08a1ff13a10d23ebbb8d26717b1b75ca4f118f /etc/bashrc
I get the same.
You should get the same if the file has not be changed if you have the same package version installed
Or you can just do "rpm -V setup" to see if anything has changed.
# rpm -V setup .M....... c /etc/fstab S.5....T. c /etc/printcap .M....G.. g /var/log/lastlog
Thanks,
Phil.
-
Ed Greshko -
George N. White III -
Philip Rhoades -
Samuel Sieb