When I start Linux Mint 17.3 in Virtual Box environment, it always fails to GUI login.

I have to change CUI login UI by Shift+Alt+F4, then run startx.

After that everything works fine.

This is the detail of the error:


    syndaemon: no process found
    /etc/mdm/Xsession: Beginning session setup...
    /etc/mdm/Xsession: Executing cinnamon-session-cinnamon failed, will try to run x-terminal-emulator
    /etc/mdm/Xsession: 205: exec: x-terminal-emulator: not found

How can I solve the problem?


#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
#       . "$HOME/.bashrc"

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then

# Add $PATH
export PATH="$HOME/bin:$PATH"
export PATH="/usr/local/sbin:$PATH"
export PATH="$HOME/.rbenv/bin:$PATH"
export PATH='/usr/local/bin:$PATH'

This is my ~/.profile file.

  • try sudo apt-get install cinnamon – Dababi Jan 4 '17 at 7:26
  • I already have it. I got cinnamon is already the newest version.. – ironsand Jan 4 '17 at 8:12
  • Did you edited the /etc/environment or the /etc/profile or the ~/.profile file – Dababi Jan 4 '17 at 8:14
  • At first I renamed ~/.profile then I could login, so as you suggested the problem is in the file. But in the file I'm just adding new paths, I don't get why this causes an error. Am I writing something wrong? – ironsand Jan 13 '17 at 7:38

The problem lies in your ~/.profile, in this line precisely:

export PATH='/usr/local/bin:$PATH'

It should be written with double quotes:

export PATH="/usr/local/bin:$PATH"

Such a line means: define an environment variable named PATH whose content is /usr/local/bin: followed by the current value of PATH (that is $PATH).

If you use single quotes, the value of PATH is literally /usr/local/bin:$PATH and $PATH is no longer substituted with the current value. Basically, you are narrowing your PATH search to /usr/local/bin which explains why x-terminal-emulator is not found, among other things.


I fixed this by upgrading the whole system and rebooting:

# apt-get update
# apt-get upgrade
# reboot

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.