Ferramentas VMware estão travando com acesso root no Ubuntu 14.04.2

0

Estou tentando ativar o login da raiz gráfica com comandos no Ubuntu 14.04.2:

sudo passwd root
sudo sh -c 'echo "greeter-show-manual-login=true" >> /etc/lightdm/lightdm.conf'

Partes da falha de ferramentas do VMware associada ao lightdm

Existe alguma maneira de ativar o acesso root graficamente no menu de login sem entrar em conflito com as ferramentas da VMware?

# ~/.profile: executed by Bourne-compatible login shells.

se ["$ BASH"]; então   if [-f ~ / .bashrc]; então     . ~ / .bashrc   fi fi mesg n

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"] & amp; & amp; retorno

# 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] & amp; & amp; eval "$ (SHELL = / bin / sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)

se [-z "$ debian_chroot"] & amp; & amp; [-r / etc / debian_chroot]; então     debian_chroot = $ (cat / etc / debian_chroot) fi

# set a fancy prompt (non-color, unless we know we "want" color)

caso "$ TERM" em     xterm-color) color_prompt = sim ;; 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

se [-n "$ force_color_prompt"]; então     if [-x / usr / bin / tput] & amp; & amp; tput setaf 1 > & amp; / dev / null; então     # Temos suporte de cores; assuma que é compatível com Ecma-48     # (ISO / IEC-6429). (A falta de tal apoio é extremamente rara, e tal     # um caso tenderia a suportar setf em vez de setaf.)     color_prompt = yes     outro     color_prompt =     fi fi

if ["$ color_prompt" = sim]; então     PS1 = '$ {debian_chroot: + ($ debian_chroot)} [\ 033 [01; 32m] \ u @ \ h [\ 033 [00m]: [\ 033 [01; 34m] \ w [\ 033 [00m] \ $ ' outro     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

caso "$ TERM" em 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

se [-x / usr / bin / dircolors]; então     teste -r ~ / .dircolors & amp; & amp; 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'

# 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.

se [-f ~ / .bash_aliases]; então     . ~ / .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
    
por Sterling Butters 25.03.2015 / 17:10

1 resposta

0

Execute este comando

sudo gedit /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf

Em seguida, adicione esta afirmação

greeter-show-manual-login=true

Reinicie sua máquina e ela deve funcionar.

    
por Faizan Akram Dar 25.03.2015 / 18:04