My ~/.profile looks like this :
# enable gnome-keyring-daemon
eval $(gnome-keyring-daemon --start)
export SSH_AUTH_SOCK
# expand user path to local/bin for xterm link
export PATH=$HOME/.local/bin:~/.npm-global/bin:$PATH
Nothing special, just add ~/.npm-global/bin to $PATH to avoid EACCESS error from npm (I use hexo to write blog 
).
It works flawless most of the time ,however ,when I login remotely from SSH ,sometimes $PATH is wrong so hexo could not be found. I have to run source ~/.profile twice to make everything looks normal as the first run of source ~/.profile returns something suspicious like this :
** Message: 16:07:15.517: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
The second run of source ~/.profile returns silent output and everything looks fine now.