The 'history -a' in /etc/bashrc (introduced by commit 9ca3d30, apparently as suggested in bug 815810) doesn't appear to serve any purpose, as there shouldn't be any new history lines to append at that point in the shell's lifecycle. In any case, this and any other history commands should not be run from startup scripts, as they may irreparably modify the history before any opportunity for the user to make changes to related settings. (Found while trying to track down occasional loss/corruption of history on login, although likely not the cause.)
Thank you for the report. Looks like this statement can be safely removed from the config. Other distributions either don't have one or have it disabled due to issues with NFS mounted /home or system recovery issues.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This still hasn't been removed in 34, nor have I found a better answer as to why this keeps happening: ╶➤ set |grep ^HIST HISTCONTROL=ignoreboth HISTFILE=/home/rob/.bash_history HISTFILESIZE=20000 HISTSIZE=20000 HISTTIMEFORMAT='%Y-%m-%d %H:%M:%S ' ╶➤ history |tail -1 1520 2021-06-23 02:45:25 history |tail -1 It was ~5600 lines a week ago, which is still far short of the 10000 that should be saved with that config.
Still in 35. What's holding up the removal of this one line?
Please, could you answer the below questions? 1. If you remove 'history -a' from /etc/bashrc, does it solve the problem with losing cmd history for you? 2. Do you have steps/reproducer which would be showing 'history -a' in /etc/bashrc irreparably modifies the history? Thanks!
1. Unsure; I'd given up on the now years-long effort to get this single line removed, and moved all of my history files to non-default locations on systems that see heavy interactive use. I haven't suffered further loss of history since making that change. 2. Not beyond what's in comment #3. The problem is intermittent, occurring on the order of once every few weeks; possibly related to multiple simultaneous logins racing, or system reboots, or ... Let's turn that latter question on its head, though: why is 'history -a' in /etc/bashrc at all? What purpose could it possibly serve? How is leaving it there not obviously incorrect? The off-handed comment in bug 815810 that is apparently responsible was without explanation at the time, and hasn't been explained since. This issue was also brought up years ago in bug 1193590, which seemed to generate decent consensus that it should be removed -- yet here we are, in another nearly two year old bug for a one line fix. The level of effort required to undo this is not at all commensurate with that required to add it in the first place...
Hi Rob, Thank you a lot for the extensive background info. The fix will be in the upcoming release: https://pagure.io/setup/c/713606713d65bf956ef4c98f4c82085bdfd9ba69?branch=master
FEDORA-2022-13c2b1e6db has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-13c2b1e6db
FEDORA-2022-d37f9b1e8b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d37f9b1e8b
FEDORA-2022-d37f9b1e8b has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d37f9b1e8b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d37f9b1e8b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-13c2b1e6db has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-13c2b1e6db` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-13c2b1e6db See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-13c2b1e6db has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d37f9b1e8b has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.