Works once - then stops

[varadins]

Just installed thefuck and used it once on a shutdown -r now command. After the reboot, it's no longer functioning

brew install thefuck

Added the following to my .bashrc

eval $(thefuck --alias)
# You can use whatever you want as an alias, like for Mondays:
eval $(thefuck --alias FUCK)

Successful use after installation

docker@docker1:~$ shutdown -r now
Call to Reboot failed: Interactive authentication required.
docker@docker1:~$ fuck
sudo shutdown -r now [enter/↑/↓/ctrl+c]
[sudo] password for docker: 

Broadcast message from root@docker1 on pts/1 (Tue 2025-08-05 16:23:26 EDT):

The system will reboot now!

Upon login I received two messages with the motd.

Welcome to Ubuntu 24.04.2 LTS (GNU/Linux 6.14.0-27-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/pro

Expanded Security Maintenance for Applications is enabled.

0 updates can be applied immediately.

Last login: Tue Aug  5 09:43:53 2025 from 192.168.1.60
Command 'thefuck' not found, but can be installed with:
sudo apt install thefuck
Command 'thefuck' not found, but can be installed with:
sudo apt install thefuck

When attempting to use the command, I get an error that it's already been configured.

docker@docker1:~$ shutdown -r now
Call to Reboot failed: Interactive authentication required.
docker@docker1:~$ fuck
Seems like fuck alias already configured!
For applying changes run source ~/.bashrc or restart your shell.

Can you please assist me with troubleshooting?

[Petsku01]

The issue you're encountering is that after the reboot, your shell session needs to reload the configuration from .bashrc, but there seems to be some confusion in how thefuck is detecting its configuration state.

Here are the steps to troubleshoot this:

1. First, verify thefuck is still installed via Homebrew:

which thefuck

This should show the path to thefuck (likely something like /home/linuxbrew/.linuxbrew/bin/thefuck).

If that doesn't work, also check:

ls -la $(which thefuck) 2>/dev/null || echo "thefuck not found in PATH"

2. Check your current shell configuration:

cat ~/.bashrc | grep thefuck

This will show you what's currently in your .bashrc file.

3. Try sourcing your .bashrc as the error message suggests:

source ~/.bashrc

4. If that doesn't work, try these solutions:

Option A: Remove and re-add the alias

# Remove the existing lines from .bashrc (more precise regex)
sed -i '/^eval $(thefuck --alias.*)/d' ~/.bashrc

# Add them back
echo 'eval $(thefuck --alias)' >> ~/.bashrc
echo 'eval $(thefuck --alias FUCK)' >> ~/.bashrc

# Source the file
source ~/.bashrc

Option B: Use thefuck's built-in alias generator

# Remove existing thefuck lines more precisely
sed -i '/^eval $(thefuck --alias.*)/d' ~/.bashrc

# Let thefuck generate the proper configuration
thefuck --alias >> ~/.bashrc

# Source the file
source ~/.bashrc

5. If thefuck isn't found at all:

The MOTD messages suggest the system thinks thefuck should be installed via apt. This might indicate that Homebrew's path isn't in your $PATH after reboot. Check if Homebrew is in your path:

echo $PATH | grep linuxbrew

If not, add Homebrew to your path in .bashrc:

echo 'export PATH="/home/linuxbrew/.linuxbrew/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

6. Verify Homebrew installation is intact:

brew list | grep thefuck

If thefuck isn't listed, reinstall it:

brew install thefuck

7. Test the fix:

shutdown -r now
fuck

The most likely cause is that the shell configuration wasn't properly loaded after reboot, or Homebrew's path wasn't preserved in your environment. The solutions above address both the configuration and PATH issues that commonly occur after system reboots.