UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
what kind of hardware is it? what do you mean by "for every input" exactly?
probably it is coming from ~/.bashrc, but without knowing more hard to say...
what kind of hardware is it? what do you mean by "for every input" exactly?
probably it is coming from ~/.bashrc, but without knowing more hard to say...
Thanks for your reply!
Been searching in .bashrc for any suspicious lines - nada.
For every line I input in CLI, I get that message.
This is truly odd. No answers, but a few questions:
Do you have anything of that nature installed?
Which terminal emulator are you using?
Have you tried a different one?
Just to clarify, this error occurs when you enter the simplest command, such as ls or pwd?
A web search for the error message indicates that it is likely to a third party package manager: https://opam.ocaml.org/ Is it installed to your system?
This is truly odd. No answers, but a few questions:
Do you have anything of that nature installed?
Which terminal emulator are you using?
Have you tried a different one?
Just to clarify, this error occurs when you enter the simplest command, such as ls or pwd?
A web search for the error message indicates that it is likely to a third party package manager: https://opam.ocaml.org/ Is it installed to your system?
Well, It must be related to the package 'Opam' although I didn't even have that installed. So I tried installing it, hopefully, it'd help to solve the issue - but it didn't.
The error occurs on every command, even just hitting enter for a blank line brings it up.
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi
so you need to find where that opam_env_hook defined/called. It is not that .bashrc as we can see.
see man bash and look for invocation. There you can see the list of the files [probably] involved.
root@ams-VPS2:~/.opam#
[ERROR] In /root/.opam/config:
Field "opam-version" is missing
Fatal error:
OpamFormat.Bad_format(0, 0, "Field "opam-version" is missing")
How do I get rid of it?? this is getting so annoying :-(
root@ams-VPS2:~/.opam#
[ERROR] In /root/.opam/config:
Field "opam-version" is missing
Fatal error:
OpamFormat.Bad_format(0, 0, "Field "opam-version" is missing")
How do I get rid of it?? this is getting so annoying :-(
since you did not reply to my request, i will not reply to yours either.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.