[SOLVED] Mystic home folder inside home folder.

Question

Hello,
for some time now I observe the repeated creation of a mystic home folder inside my home folder. E.g. if my user name is user, the folder /home/user/home/user/ is created (supposedly at booting time). I use arch linux with gdm and xmonad started from a .xsession file.
Do you have any ideas or suggestions about logs that I could provide?
Thanks,
Fazky
Last edited by fazky (2013-10-10 14:50:48)

Answer 1

@SolarBoyMatt: Yes, it appears along with everything else and it is empty (sorry, I forgot to post this ...). I am not convinced that it is created at boot time, but if I delete it, it appears again after I reboot the laptop.
@jasonwryan: No, it is not a symlink. The folder is empty. The only shell initialization file that I changed from the default ones is ~/.bashrc
# ~/.bashrc
PATH=$PATH:/home/dominik/bin/
export PATH
export ALTERNATE_EDITOR=emacs EDITOR=emacsclient VISUAL=emacsclient
# for sudo bash completion
complete -cf sudo
# Bash completion
if [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
# Test for an interactive shell. There is no need to set anything
# past this point for scp and rcp, and it's important to refrain from
# outputting anything in those cases.
if [[ $- != *i* ]] ; then
# Shell is non-interactive. Be done now!
return
fi
# Bash won't get SIGWINCH if another process is in the foreground.
# Enable checkwinsize so that bash will check the terminal size when
# it regains control. #65623
# http://cnswww.cns.cwru.edu/~chet/bash/FAQ (E11)
shopt -s checkwinsize
# Enable history appending instead of overwriting. #139609
shopt -s histappend
# Change the window title of X terminals
case ${TERM} in
xterm*|rxvt*|Eterm|aterm|kterm|gnome*|interix)
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\007"'
screen)
PROMPT_COMMAND='echo -ne "\033_${USER}@${HOSTNAME%%.*}:${PWD/$HOME/~}\033\\"'
esac
use_color=false
# Set colorful PS1 only on colorful terminals.
# dircolors --print-database uses its own built-in database
# instead of using /etc/DIR_COLORS. Try to use the external file
# first to take advantage of user additions. Use internal bash
# globbing instead of external grep binary.
safe_term=${TERM//[^[:alnum:]]/?} # sanitize TERM
match_lhs=""
[[ -f ~/.dir_colors ]] && match_lhs="${match_lhs}$(<~/.dir_colors)"
[[ -f /etc/DIR_COLORS ]] && match_lhs="${match_lhs}$(</etc/DIR_COLORS)"
[[ -z ${match_lhs} ]] \
&& type -P dircolors >/dev/null \
&& match_lhs=$(dircolors --print-database)
[[ $'\n'${match_lhs} == *$'\n'"TERM "${safe_term}* ]] && use_color=true
if ${use_color} ; then
# Enable colors for ls, etc. Prefer ~/.dir_colors #64489
if type -P dircolors >/dev/null ; then
if [[ -f ~/.dir_colors ]] ; then
eval $(dircolors -b ~/.dir_colors)
elif [[ -f /etc/DIR_COLORS ]] ; then
eval $(dircolors -b /etc/DIR_COLORS)
fi
fi
if [[ ${EUID} == 0 ]] ; then
PS1='\[\033[01;31m\]\h\[\033[01;34m\] \W \$\[\033[00m\] '
else
PS1='\[\033[01;32m\]\u@\h\[\033[01;34m\] \w \$\[\033[00m\] '
fi
alias ls='ls --color=auto'
alias grep='grep --colour=auto'
else
if [[ ${EUID} == 0 ]] ; then
# show root@ when we do not have colors
PS1='\u@\h \W \$ '
else
PS1='\u@\h \w \$ '
fi
fi
# Try to keep environment pollution down, EPA loves us.
unset use_color safe_term match_lhs
#add color to man pages
export LESS_TERMCAP_mb=$'\E[01;31m' # begin blinking
export LESS_TERMCAP_md=$'\E[01;38;5;74m' # begin bold
export LESS_TERMCAP_me=$'\E[0m' # end mode
export LESS_TERMCAP_se=$'\E[0m' # end standout-mode
export LESS_TERMCAP_so=$'\E[38;5;246m' # begin standout-mode - info box
export LESS_TERMCAP_ue=$'\E[0m' # end underline
export LESS_TERMCAP_us=$'\E[04;38;5;146m' # begin underline
There doesn't seem to be anything suspicious in here.
@drcouzelis: No, the user-dirs file looks fine.
@Trilby: This is my fstab file, there doesn't seem to be an error:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
# /dev/sda4
UUID=6770128b-c26d-4474-b369-68b1802e1222 / ext4 rw,relatime 0 1
# /dev/sda3
UUID=aec81631-a927-40af-8a5d-85ca27e5dc35 /boot ext4 rw,relatime,stripe=4 0 2
# /dev/sda2
UUID=1D04-16EA /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
# /dev/sda5
UUID=743ec024-dfe0-4b1f-a10d-7ecaf026bc85 /var ext4 rw,relatime 0 2
# /dev/sda6
UUID=b28a3641-1ae4-4545-8919-aab6c6781057 /home ext4 rw,relatime 0 2
Regarding the journalctl boot log: This is quite an extensive document but I can post it, if you want to. Maybe only some parts of it are interesting?
Thanks for all your suggestions,
Fazky