problem opening jupyter notebook on debian 10

Edit your .bashrc file and comment out the conda part so that it looks like this:
# >>> 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
#f [ -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 <<<

And below that add the following:
source /home/raman/anaconda3/bin/activate root

Then logout and log back in.
 


how to open .bashrc file as it is not visible on raman folder?
Use your favorite text edit. For example if you have gedit installed you can run:
Code:
gedit /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 <<<
 
Use your favorite text edit. For example if you have gedit installed you can run:
Code:
gedit /home/raman/.bashrc
Replace gedit with a text editor that is installed on your system.
 
Edit your .bashrc file and comment out the conda part so that it looks like this:
# >>> 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
#f [ -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 <<<

And below that add the following:
source /home/raman/anaconda3/bin/activate root

Then logout and log back in.
I already told you what to do in an earlier post.
 
(base) raman@raman:~$ spyder
libpng warning: bKGD: invalid
libpng warning: bKGD: invalid
libpng warning: bKGD: invalid
libpng warning: bKGD: invalid




yes i was able to open spyder
 
That looks good since you have (base) in your shell now. Are you able to open anaconda-navigator now?
 
jupyter is also working fine.


(base) raman@raman:~$ anaconda-jupyter
bash: anaconda-jupyter: command not found
(base) raman@raman:~$ jupyter-notebook
[I 16:28:17.435 NotebookApp] JupyterLab extension loaded from /home/raman/anaconda3/lib/python3.8/site-packages/jupyterlab
[I 16:28:17.435 NotebookApp] JupyterLab application directory is /home/raman/anaconda3/share/jupyter/lab
[I 16:28:17.437 NotebookApp] Serving notebooks from local directory: /home/raman
[I 16:28:17.437 NotebookApp] The Jupyter Notebook is running at:
[I 16:28:17.438 NotebookApp] http://localhost:8888/?token=582c849f2e5093269b12bb4f4c3e18b6ecc011f0ac2630d7
[I 16:28:17.438 NotebookApp] or http://127.0.0.1:8888/?token=582c849f2e5093269b12bb4f4c3e18b6ecc011f0ac2630d7
[I 16:28:17.438 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 16:28:17.467 NotebookApp]

To access the notebook, open this file in a browser:
file:///home/raman/.local/share/jupyter/runtime/nbserver-4780-open.html
Or copy and paste one of these URLs:
http://localhost:8888/?token=582c849f2e5093269b12bb4f4c3e18b6ecc011f0ac2630d7
or http://127.0.0.1:8888/?token=582c849f2e5093269b12bb4f4c3e18b6ecc011f0ac2630d7
 
So problem solved?
 
what should i study to become able to solve such problem in future? i am a student of M.Sc. physics at IIT kanpur. would i be able open it through icon in toolbar or on desktop
 
what should i study to become able to solve such problem in future? i am a student of M.Sc. physics at IIT kanpur. would i be able open it through icon in toolbar or on desktop
Read a book about Linux basics. There are plenty available, for example this one, and there is also a forum topic with some learning resources. Otherwise you can do a google search or look for other books about Linux on amazon.

Also some of the courses on udemy with high ratings and at least 1000 students are good learning resources as well, just search for "linux basics" or "linux for beginners" . For example this course.
 
:rolleyes: 97 posts here, and 5 pages, and not a single "Thank you very much for all your help" from the OP - take note, @raman kumar , that if you wish further help in this Forum, you might want to brush up on your manners?

Thank you @f33dm3bits on behalf of the Forum, for going the extra yards in this matter, and also Andy @captain-sensible for your contributions :)

I followed the instructions provided at the link mentioned earlier

https://docs.anaconda.com/anaconda/install/linux/

and had no problems whatsoever in installing it on my Debian 10 'Buster' KDE.

In addition to the resources provided in the previous post, there is also a free course, 40 hours and an exam, self-paced running for at least 6 years now that I am aware of, provided by a collaboration between The Linux Foundation and edX. You can find it here

https://www.edx.org/learn/linux

You have to register first before you can see the course content. I ran it in early 2015 I think, and it was very good.

Wizard
 
i am very sorry . please forgive your pupil . i am highly indebted to you all my mentors and trainer. thanks to you all
 

Members online


Latest posts

Top