1

I am new to Linux. I recently installed WSL2 (Ubuntu 22.04) on Windows 10. Whenever I open the terminal or type bash in the terminal, it keeps giving me an error. (Sorry, I was not able to copy from the terminal.) How do I resolve this?

enter image description here

Error in line 117 inside bashrc file

code inside bashrc starting line 117.

fi export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0 export
LIBGL_ALWAYS_INDIRECT=1 sudo /etc/init.d/dbus start &> /dev/null export DISPLAY=$(cat /etc/resolv.conf | grep
nameserver | awk '{print $2; exit;}'):0.0 export LIBGL_ALWAYS_INDIRECT=1 sudo /etc/init.d/dbus start &>
/dev/null
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0
export LIBGL_ALWAYS_INDIRECT=1
sudo /etc/init.d/dbus start &> /dev/null
Vai_P
  • 21

2 Answers2

3

While @ArthurMeinild's answer is technically correct for fixing the errors, also note that those lines aren't needed on WSL any longer and should probably just be removed entirely.

As @Raffa mentioned in a comment, it appears you copied these from a website and pasted them in, losing the line-breaks on the first attempt.

You should determine why you are trying to use those lines in the first place and probably consider other (IMHO, better) options. Note that WSL has seen some massive changes and improvements over the last 18 months. If you are following instructions on a website/blog that pre-date that, they may be outdated already. And, of course, always be suspect of any website/blog post that doesn't include a posting or updated date.

As for these particular lines, what they do, and why they probably aren't needed:

  • The export DISPLAY line is only needed if you require a third-party X server, which most likely isn't the case any longer. WSL now includes the ability to run GUI applications directly, using WSLg rather than a third-party X server. Please see this answer for information on how to make sure you have updated to the latest release that supports this.

  • Even if you were using a third-party X server, there's a much better (IMHO) version of that DISPLAY line:

    export DISPLAY="$(hostname).local:0"

    See my Super User answer here along with my Stack Overflow explanation.

  • Likewise, LIBGL_ALWAYS_INDIRECT isn't needed with the new WSL implementation.

  • And WSL now can setup and run Systemd and D-Bus directly (if needed, which it often isn't) in the latest releases. See my Systemd answer here for information on how to set it up, and how to determine if you really need it.

  • Even if you were, for some reason, needing to start D-Bus directly at start-up, using sudo to do so in your user rc file isn't the best option. It means you have to type your password each time you start Ubuntu on WSL, which isn't the case normally.

    If you need to start a system service (apart from Systemd) when Ubuntu/WSL starts, create a /etc/wsl.conf file (as sudo) and use the [boot] section as in this answer.

As a result of this, I would highly recommend removing all of those additional lines and using the WSL features that accomplish the same thing directly.

NotTheDr01ds
  • 22,082
2

I think the lines you mention should be laid out like this:

fi 
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0 
export LIBGL_ALWAYS_INDIRECT=1 
sudo /etc/init.d/dbus start &> /dev/null

Remove everything else that is redundant (remove everything after fi on line 117).

Artur Meinild
  • 31,035