On Linux Mint 22.3 Cinnamon (or any Linux system), executing a non-existent command typically results in a command not found error. However, if your system is instead trying to execute a file like /usr/lib/python3.*/sitecustomize.py when you run a non-existent command, this is not standard behavior and usually indicates an unusual or misconfigured shell or system setup.

Here’s why this might be happening and how to investigate:

Possible Causes

1. Custom Shell Configuration

• If you or a system administrator have modified your shell configuration (e.g., .bashrc, .bash_profile, or /etc/bash.bashrc), it’s possible that a line is intercepting unknown commands and attempting to execute them as Python scripts.
• Look for lines like:
  bash

  Copy

  alias unknown_command='python3 /usr/lib/python3.*/sitecustomize.py'

  or
  bash

  Copy

  function unknown_command() { python3 /usr/lib/python3.*/sitecustomize.py; }

  in your shell configuration files.

2. Python sitecustomize.py Interception

• The sitecustomize.py file is a Python module that can be loaded automatically when Python starts. If your shell is configured to run Python for unknown commands, it might be using this mechanism to "interpret" the command as a Python script.
• This is highly unusual and not a standard feature of Python or Linux.

3. Malware or Unwanted Modifications

• It’s possible that malware or an unauthorized script is intercepting commands and redirecting them to Python.
• Check for suspicious entries in:
  • ~/.bashrc
  • ~/.bash_profile
  • /etc/bash.bashrc
  • /etc/profile
  • /etc/profile.d/
  • Any shell startup scripts in /etc/

4. Custom command_not_found_handle Function

• Some systems allow defining a custom function to handle command not found errors. If this function is misconfigured, it could try to execute Python scripts.
• Check for:
  bash

  Copy

  command_not_found_handle() {
      python3 /usr/lib/python3.*/sitecustomize.py "$@"
  }

How to Investigate

1. Check Shell Configuration Files

Run:

grep -r "sitecustomize.py" ~/.bashrc ~/.bash_profile /etc/bash.bashrc /etc/profile /etc/profile.d/

or

grep -r "unknown_command" ~/.bashrc ~/.bash_profile /etc/bash.bashrc /etc/profile /etc/profile.d/

2. Check for Custom command_not_found_handle

Run:

type command_not_found_handle

If it returns a function, examine its content:

declare -f command_not_found_handle

3. Check for Aliases or Functions

Run:

alias

and

type -a unknown_command

to see if unknown_command is aliased or defined as a function.

4. Check for Python Interception

Run:

strace -f -e execve bash -c "unknown_command" 2>&1 | grep exec

This will show what file is actually being executed when you run the non-existent command.

How to Fix It

If you find the culprit, remove or comment out the offending line in your shell configuration files. For example:

# Remove or comment out:
# alias unknown_command='python3 /usr/lib/python3.*/sitecustomize.py'

Then, reload your shell:

source ~/.bashrc

Summary Table

If you share the output of the commands above, I can help you pinpoint the exact cause and solution!