Error text when opening the terminal

Hello there!

I’m seeing this error messages when opening the terminal:

I’m kinda new to Linux and really new to Tumbleweed. I’m aware I might have commited mistakes when experimenting with different stuff, like downloading NoMachine and deleting it (when I search for the error I see NoMachine mentioned), installing Wine and doing it wrong, trying to fix it, etc.

How can I get rid of these error messages? I know it’s my fault but bare with me. I will provide all the info needed.

Thank you in advance.

It seems it’s related to NoMachine. I tried following these steps but the error persists:

https://forum.nomachine.com/topic/after-uninstall-all-programs-look-for-usr-nx-lib-libnxegl-so

I have never heard of NoMachine before, so I don’t know what it would have changed on your system. But, have you checked your .bashrc file for anything weird?

If you type echo $LD_PRELOAD in the terminal you’ll find that it contains /usr/NX/lib/libnxegl.so. You’ll have to find where this variable is defined and remove the definition (~/.bashrc, ~/.profile, /etc/bash.bashrc, /etc/profile or files sourced therein).

1 Like

Hello, thank you for the response!

I’m not sure what bashrc is, how do I go about removing the definition? In the meantime I will research about bashrc.

The bashrc file is used to set up the user’s shell environment according to their preferences.

It’s a configuration file for the CLI.

It’s a text file you edit with a text editor.

Alright, so this is my bashrc file:

I’m not seeing anything weird but at the same time I don’t know what I’m looking at. Does this look right to you?

Ok the ~/.bashrc file here conatins the following >
cat .bashrc

# Sample .bashrc for SUSE Linux
# Copyright (c) SUSE Software Solutions Germany GmbH

# There are 3 different types of shells in bash: the login shell, normal shell
# and interactive shell. Login shells read ~/.profile and interactive shells
# read ~/.bashrc; in our setup, /etc/profile sources ~/.bashrc - thus all
# settings made here will also take effect in a login shell.
#
# NOTE: It is recommended to make language settings in ~/.profile rather than
# here, since multilingual X sessions would not work properly if LANG is over-
# ridden in every subshell.

test -s ~/.alias && . ~/.alias || true

#Ignore repetitive terminal input
#HISTCONTROL=ignoreboth

#Settings below for bash history file size:
HISTSIZE=80000
HISTFILESIZE=90000

~/.bashrc is for that individual (user). /etc/bash.bashrc is for systemwide variable approach.

I do not know what /usr/etc/bash.bashrc is for specifically.

Thank you! I added those lines to my bashrc file, reboot and now my terminal is nice and clean :sunglasses:

I’m glad things seem to be resolved but be aware the two bottom line are regarding bash terminal history and bash history file size.

Am I good with those values? What do you recommend?

I keep those values.

1 Like

Your actual issue was caused by NoMachine - the evidence is clear.

There is some odd coincidence that the problem went away … probably because of an update.

Those two Bash config entries (HISTSIZE and HISTFILESIZE) are only related to how many command line entries are stored for future reference. They have zero effect on the error output you saw.

Our machines are set to “unlimited”

1 Like

Then I got much to learn. The Tumbleweed road has been awesome so far. Thank you all for your responses.

So you set:
HISTSIZE=unlimited
HISTFILESIZE=unlimited
in ~/.bashrc ?

Actually, my settings are as:

HISTSIZE=-1
HISTFILESIZE=-1

From the bash man page:

HISTFILESIZE - Non-numeric values and numeric values less than zero inhibit truncation. The shell sets the default value to the value of HISTSIZE after reading any startup files.

HISTSIZE - Numeric values less than zero result in every command being saved on the history list (there is no limit). The shell sets the default value to 500 after reading any startup files.

1 Like

ls -la /etc/skel/

Should show you default files/directories for a new user, and you do

cat /etc/skel/.bashrc

Should print the default values/entries for that file.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.