Closed pomomayu closed 9 months ago
If you press Ctrl+C, do you get a stack trace with more information?
Hey made some adjustments and it worked on the second try. This time the system was rebooted, and the Chromium cache was added to 10-ignore.sh. Not sure if either of these were the root cause. Closing this for now.
In the previous attempt the system had just been updated with pacman -Syu. The system had not been rebooted before running aconfmgr, but I didn't think it would affect anything. And yes I was backing up my Chromium cache! I'm protective of the state of my browser hah.
General description of the problem:
During the most recent system backup aconfmgr never closed out when it finishes. It never returns to the command line. See the log section below. This is where it stops. This did not happen during previous backups. There's nothing unique about way we use aconfmgr.
Steps to reproduce the problem:
$ ./aconfmgr --config ~/my/config save
aconfmgr stops here:
Configuration:
Expected result:
aconfmgr should finish!
Actual result:
No response
Log:
Additional context:
No response