ubuntu 11.10登录返回初始屏幕

ubuntu 11.10登录返回初始屏幕,ubuntu,ubuntu-11.10,vmware-player,Ubuntu,Ubuntu 11.10,Vmware Player,我正在vmware 4.0播放器上运行Ubuntu11.10。我有个问题,希望你能帮忙 当我登录到闪屏时,ubuntu会获取我的密码,但会立即将我返回闪屏。这只发生在1个用户(另一个用户登录正常)的情况下。当我使用F1登录时,我能够成功登录(注意:它会抛出一个错误“export:29::bad variable name”) 我已尝试:删除.config/gnome会话目录并修改/tmp(sudo chmod-ra+w/tmp)上的权限,如下所述: (我知道这是错误的版本,但值得一试。) 我还尝

我正在vmware 4.0播放器上运行Ubuntu11.10。我有个问题,希望你能帮忙

当我登录到闪屏时,ubuntu会获取我的密码,但会立即将我返回闪屏。这只发生在1个用户(另一个用户登录正常)的情况下。当我使用F1登录时,我能够成功登录(注意:它会抛出一个错误“export:29::bad variable name”)

我已尝试:删除.config/gnome会话目录并修改/tmp(sudo chmod-ra+w/tmp)上的权限,如下所述: (我知道这是错误的版本,但值得一试。)

我还尝试了Alt+SysRq+R+S+E+I+U+B,如下所述:

最后,我删除了.Xsession并安装了libglib2.0,如下所述:

还有其他建议或资源需要检查吗? 蒂亚

下面是.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
[ -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'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# 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

您是否修改了主文件夹中的默认.bashrc?像“执行官什么的”

我知道这听起来很奇怪,但我有一个类似的问题,即使我是用KDE而不是gnome工作


嗯,顺便问一下,你能把你的.bashrc发出去吗?尤其是第25到35行。

您是否修改了主文件夹中的默认.bashrc?像“执行官什么的”

我知道这听起来很奇怪,但我有一个类似的问题,即使我是用KDE而不是gnome工作


嗯,顺便问一下,你能把你的.bashrc发出去吗?特别是第25至35行。

谢谢@Delk。我记得我更改了.profile,这似乎是导致错误的原因。我删除了我添加的行,现在我可以登录了。谢谢@delk。我记得我更改了.profile,这似乎是导致错误的原因。我删除了我添加的行,现在我可以登录了。添加此评论以防其他人感兴趣。要登录终端(在问题中称为F1方法),当您进入登录屏幕时,按,将进入终端(并访问您的个人资料)。如果其他人感兴趣,请添加此评论。要登录终端(在问题中称为F1方法),当您进入登录屏幕时,按,将进入终端(并访问您的个人资料)。