Software⏱️ 3 min read📅 2026-06-11

How to Fix: Getting bash error: -bash: eval: line 184: syntax error near unexpected token `(' -bash: eval: line 184: `export CONDA_PROMPT_MODIFIER='(base) ''

A bash error is occurring when opening the Ubuntu 18.06 terminal on Windows, and has tried reinstalling Ubuntu and Anaconda without success.

Quick Answer: Try updating or reinstalling the relevant packages to resolve the issue.

When opening the Ubuntu 18.06 terminal on Windows, you may encounter an error that prevents the terminal from functioning properly. This issue affects users who are running the terminal in Windows and have installed Anaconda.

This error can be frustrating as it prevents you from using the terminal to run commands or access your files. In this guide, we will walk you through the steps to troubleshoot and resolve this issue.

⚠️ Common Causes

  • The first main reason why this error occurs is due to a syntax error in the bash configuration file. This error can be caused by an incorrect or missing character in the bash configuration file, which prevents the terminal from loading properly.
  • Another possible cause of this error is related to the Anaconda installation on your system. Although reinstalling Ubuntu and Anaconda did not resolve the issue, it's worth investigating if there are any conflicts between the two installations.

🛠️ Step-by-Step Verified Fixes

Update bash configuration file

  1. Step 1: Open the terminal and type `nano ~/.bashrc` to edit the bash configuration file. This will allow you to inspect the contents of the file and identify any potential issues.
  2. Step 2: Search for any suspicious or incorrect characters in the file, such as the one that caused the syntax error. If you find any, correct them immediately.
  3. Step 3: Save the changes to the file by pressing `Ctrl+X`, then `Y`, and finally `Enter`. This will update the bash configuration file with the corrected changes.

Clear cache and restart terminal

  1. Step 1: Open a new terminal window or close and reopen the existing one. This will clear any cached data that may be causing issues.
  2. Step 2: Type `clear` to clear the terminal screen, and then type `source ~/.bashrc` to reload the bash configuration file.

✨ Wrapping Up

If you have followed these steps and still encounter the error, it's possible that there is a more complex issue at play. In this case, consider seeking further assistance from a system administrator or IT professional. However, for most users, updating the bash configuration file and clearing cache should resolve the issue.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions