problem opening jupyter notebook on debian 10

Create a file /home/raman/.bashrc then paste this into it:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/home/raman/anaconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
eval "$__conda_setup"
else
if [ -f "/home/raman/anaconda3/etc/profile.d/conda.sh" ]; then
. "/home/raman/anaconda3/etc/profile.d/conda.sh"
else
export PATH="/home/raman/anaconda3/bin:$PATH"
fi
fi
unset __conda_setup
# <<< conda initialize <<<


If you installed anaconda in a different directory adjust the directory as needed according to your setup. Then source it: source /home/raman/.bashrc
Then try running anaconda-navigator again.
 


open it up with a text editor geany , kate , nano or other and post contents here but copy and paste of f33.. should cause a problem if you "append it" below whats there

there will be no permission problem since its in your own home , so you have all rights


nice bit of bash for you too @raman kumar you see the nested "if" statements of the form

if //start of If conditional statement
condition

etc

fi //end
 
A file named /home/raman/.bashrc already exists.

how to acess that folder?
 

Attachments

  • Screenshot_20200928_144251.png
    Screenshot_20200928_144251.png
    89.9 KB · Views: 322
open it up with a text editor geany , kate , nano or other and post contents here but copy and paste of f33.. should cause a problem if you "append it" below whats there

there will be no permission problem since its in your own home , so you have all rights


nice bit of bash for you too @raman kumar you see the nested "if" statements of the form

if //start of If conditional statement
condition

etc

fi //end
@raman kumar Open a terminal and then do: cat /home/raman/.bashrc and share the output here.
 
raman@raman:~$ cat /home/raman/.bashrc
# ~/.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
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# 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

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# 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|*-256color) 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

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
#alias ll='ls -l'
#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 ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/home/raman/anaconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
eval "$__conda_setup"
else
if [ -f "/home/raman/anaconda3/etc/profile.d/conda.sh" ]; then
. "/home/raman/anaconda3/etc/profile.d/conda.sh"
else
export PATH="/home/raman/anaconda3/bin:$PATH"
fi
fi
unset __conda_setup
# <<< conda initialize <<<

raman@raman:~$
 
# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/home/raman/anaconda3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
eval "$__conda_setup"
else
if [ -f "/home/raman/anaconda3/etc/profile.d/conda.sh" ]; then
. "/home/raman/anaconda3/etc/profile.d/conda.sh"
else
export PATH="/home/raman/anaconda3/bin:$PATH"
fi
fi
unset __conda_setup
# <<< conda initialize <<<

raman@raman:~$
As I thought the most important part for anaconda is in there already. So when you source this file: source /home/raman/.bashrc , you should get a shell like this:
Code:
raman@raman:~$ source .bashrc 
(base) ramman@raman:~$
 
how to source that file? what to type in terminal?
You need to open a terminal, then you need to type this in your terminal to source your .bashrc file.
Code:
source /home/raman/.bashrc
Then other option is to logout of your system en to then log back in which should also then automatically do it for you.
 
raman@raman:~$ source /home/raman/.bashrc
raman@raman:~$ su
Password:
root@raman:/home/raman# source /home/raman/.bashrc
(base) root@raman:/home/raman# anaconda-navigator
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
 
raman@raman:~$ source /home/raman/.bashrc
raman@raman:~$ su
Password:
root@raman:/home/raman# source /home/raman/.bashrc
(base) root@raman:/home/raman# anaconda-navigator
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
As I said before, you don't need to keep showing what happens when you do it as root user. Just logout of your system and back in and then show me what terminal looks like as normal user, so raman@raman.
 
What happens when you run the following in a terminal:
Code:
which anaconda-navigator
 
raman@raman:~$
raman@raman:~$
raman@raman:~$ which anaconda-navigator
raman@raman:~$
raman@raman:~$
 

Members online


Top