Login loop for one user after Ubuntu update












0















Yesterday, I updated my Ubuntu instance using the Software Updater. Here's the relevant entry from /var/log/apt/history.log:



Start-Date: 2019-01-16  08:05:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.265'
Upgrade: libkrb5-3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5-3:i386 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:i386 (1.16-2build1, 1.16-2ubuntu0.1), python-samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libwbclient0:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libgjs0g:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-dsdb-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libarchive13:amd64 (3.2.2-3.1ubuntu0.1, 3.2.2-3.1ubuntu0.2), libgnome-bluetooth13:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), gjs:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), libk5crypto3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libk5crypto3:i386 (1.16-2build1, 1.16-2ubuntu0.1), gnome-bluetooth:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), php-pear:amd64 (1:1.10.5+submodules+notgz-1ubuntu1, 1:1.10.5+submodules+notgz-1ubuntu1.18.04.1), krb5-locales:amd64 (1.16-2build1, 1.16-2ubuntu0.1), samba-libs:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libpam-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libcaca0:amd64 (0.99.beta19-2build2~gcc5.3, 0.99.beta19-2ubuntu0.18.04.1), libkrb5support0:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5support0:i386 (1.16-2build1, 1.16-2ubuntu0.1), gir1.2-gnomebluetooth-1.0:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), samba-common:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libnss-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-vfs-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), smbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-common-bin:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), linux-firmware:amd64 (1.173.2, 1.173.3)
End-Date: 2019-01-16 08:17:09


After the update, I find myself unable to login after shutting down my system and rebooting. The system boots into the GUI login screen. After entering the password, it attempts to load the desktop manager. Unfortunately, it fails. After showing nothing more than a blank screen with the mouse pointer in it, it returns to the GUI login screen. This happens for just a single user account (unfortunately the primary user account). I am able to login and logout without any problem from other user accounts.



I have attempted the following (most of the suggestions from here):




  1. I have verified that .Xauthority and .ICEAuthority have the right permissions.

  2. I have verified that /tmp has the right permissions.

  3. I removed the propriety Nvidia driver (downloaded from the website; it had to be reinstalled after every kernel upgrade but as evident from the log entry above, the recent upgrade did not upgrade the kernel) and replaced with nvidia-driver-390, the package suggested by sudo ubuntu-drivers devices.



$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: nvidia



  1. I switched from lightdm to gdm3 using sudo dpkg-reconfigure gdm3

  2. I checked .xsession-errors and most of the entries are of the form:dbus-update-activation-environment: setting. Nothing there seems out of place.

  3. The .bashrc file contain the following additions:



# Aliases #
alias pcat="pygmentize -f terminal256 -O style=native -g"
mkdircd(){
# create a director and change to it
echo "creating directory $1"
mkdir $1
cd $1
}
alias mcd=mkdircd
export PATH="$PATH:/home/wneo/path_to_a_web_framework"

#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="/home/wneo/.sdkman"
[[ -s "/home/wneo/.sdkman/bin/sdkman-init.sh" ]] && source "/home/wneo/.sdkm an/bin/sdkman-init.sh"

#The following is to get go tools to work
export PATH="$PATH:$GOPATH/bin"


None of these edits were made immediately before or after the update.



Please help.










share|improve this question

























  • Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

    – guiverc
    5 hours ago











  • @guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

    – wneo
    5 hours ago











  • $HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

    – guiverc
    4 hours ago








  • 1





    There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

    – wneo
    2 hours ago


















0















Yesterday, I updated my Ubuntu instance using the Software Updater. Here's the relevant entry from /var/log/apt/history.log:



Start-Date: 2019-01-16  08:05:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.265'
Upgrade: libkrb5-3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5-3:i386 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:i386 (1.16-2build1, 1.16-2ubuntu0.1), python-samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libwbclient0:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libgjs0g:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-dsdb-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libarchive13:amd64 (3.2.2-3.1ubuntu0.1, 3.2.2-3.1ubuntu0.2), libgnome-bluetooth13:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), gjs:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), libk5crypto3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libk5crypto3:i386 (1.16-2build1, 1.16-2ubuntu0.1), gnome-bluetooth:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), php-pear:amd64 (1:1.10.5+submodules+notgz-1ubuntu1, 1:1.10.5+submodules+notgz-1ubuntu1.18.04.1), krb5-locales:amd64 (1.16-2build1, 1.16-2ubuntu0.1), samba-libs:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libpam-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libcaca0:amd64 (0.99.beta19-2build2~gcc5.3, 0.99.beta19-2ubuntu0.18.04.1), libkrb5support0:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5support0:i386 (1.16-2build1, 1.16-2ubuntu0.1), gir1.2-gnomebluetooth-1.0:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), samba-common:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libnss-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-vfs-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), smbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-common-bin:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), linux-firmware:amd64 (1.173.2, 1.173.3)
End-Date: 2019-01-16 08:17:09


After the update, I find myself unable to login after shutting down my system and rebooting. The system boots into the GUI login screen. After entering the password, it attempts to load the desktop manager. Unfortunately, it fails. After showing nothing more than a blank screen with the mouse pointer in it, it returns to the GUI login screen. This happens for just a single user account (unfortunately the primary user account). I am able to login and logout without any problem from other user accounts.



I have attempted the following (most of the suggestions from here):




  1. I have verified that .Xauthority and .ICEAuthority have the right permissions.

  2. I have verified that /tmp has the right permissions.

  3. I removed the propriety Nvidia driver (downloaded from the website; it had to be reinstalled after every kernel upgrade but as evident from the log entry above, the recent upgrade did not upgrade the kernel) and replaced with nvidia-driver-390, the package suggested by sudo ubuntu-drivers devices.



$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: nvidia



  1. I switched from lightdm to gdm3 using sudo dpkg-reconfigure gdm3

  2. I checked .xsession-errors and most of the entries are of the form:dbus-update-activation-environment: setting. Nothing there seems out of place.

  3. The .bashrc file contain the following additions:



# Aliases #
alias pcat="pygmentize -f terminal256 -O style=native -g"
mkdircd(){
# create a director and change to it
echo "creating directory $1"
mkdir $1
cd $1
}
alias mcd=mkdircd
export PATH="$PATH:/home/wneo/path_to_a_web_framework"

#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="/home/wneo/.sdkman"
[[ -s "/home/wneo/.sdkman/bin/sdkman-init.sh" ]] && source "/home/wneo/.sdkm an/bin/sdkman-init.sh"

#The following is to get go tools to work
export PATH="$PATH:$GOPATH/bin"


None of these edits were made immediately before or after the update.



Please help.










share|improve this question

























  • Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

    – guiverc
    5 hours ago











  • @guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

    – wneo
    5 hours ago











  • $HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

    – guiverc
    4 hours ago








  • 1





    There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

    – wneo
    2 hours ago
















0












0








0








Yesterday, I updated my Ubuntu instance using the Software Updater. Here's the relevant entry from /var/log/apt/history.log:



Start-Date: 2019-01-16  08:05:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.265'
Upgrade: libkrb5-3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5-3:i386 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:i386 (1.16-2build1, 1.16-2ubuntu0.1), python-samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libwbclient0:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libgjs0g:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-dsdb-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libarchive13:amd64 (3.2.2-3.1ubuntu0.1, 3.2.2-3.1ubuntu0.2), libgnome-bluetooth13:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), gjs:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), libk5crypto3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libk5crypto3:i386 (1.16-2build1, 1.16-2ubuntu0.1), gnome-bluetooth:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), php-pear:amd64 (1:1.10.5+submodules+notgz-1ubuntu1, 1:1.10.5+submodules+notgz-1ubuntu1.18.04.1), krb5-locales:amd64 (1.16-2build1, 1.16-2ubuntu0.1), samba-libs:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libpam-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libcaca0:amd64 (0.99.beta19-2build2~gcc5.3, 0.99.beta19-2ubuntu0.18.04.1), libkrb5support0:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5support0:i386 (1.16-2build1, 1.16-2ubuntu0.1), gir1.2-gnomebluetooth-1.0:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), samba-common:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libnss-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-vfs-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), smbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-common-bin:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), linux-firmware:amd64 (1.173.2, 1.173.3)
End-Date: 2019-01-16 08:17:09


After the update, I find myself unable to login after shutting down my system and rebooting. The system boots into the GUI login screen. After entering the password, it attempts to load the desktop manager. Unfortunately, it fails. After showing nothing more than a blank screen with the mouse pointer in it, it returns to the GUI login screen. This happens for just a single user account (unfortunately the primary user account). I am able to login and logout without any problem from other user accounts.



I have attempted the following (most of the suggestions from here):




  1. I have verified that .Xauthority and .ICEAuthority have the right permissions.

  2. I have verified that /tmp has the right permissions.

  3. I removed the propriety Nvidia driver (downloaded from the website; it had to be reinstalled after every kernel upgrade but as evident from the log entry above, the recent upgrade did not upgrade the kernel) and replaced with nvidia-driver-390, the package suggested by sudo ubuntu-drivers devices.



$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: nvidia



  1. I switched from lightdm to gdm3 using sudo dpkg-reconfigure gdm3

  2. I checked .xsession-errors and most of the entries are of the form:dbus-update-activation-environment: setting. Nothing there seems out of place.

  3. The .bashrc file contain the following additions:



# Aliases #
alias pcat="pygmentize -f terminal256 -O style=native -g"
mkdircd(){
# create a director and change to it
echo "creating directory $1"
mkdir $1
cd $1
}
alias mcd=mkdircd
export PATH="$PATH:/home/wneo/path_to_a_web_framework"

#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="/home/wneo/.sdkman"
[[ -s "/home/wneo/.sdkman/bin/sdkman-init.sh" ]] && source "/home/wneo/.sdkm an/bin/sdkman-init.sh"

#The following is to get go tools to work
export PATH="$PATH:$GOPATH/bin"


None of these edits were made immediately before or after the update.



Please help.










share|improve this question
















Yesterday, I updated my Ubuntu instance using the Software Updater. Here's the relevant entry from /var/log/apt/history.log:



Start-Date: 2019-01-16  08:05:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.265'
Upgrade: libkrb5-3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5-3:i386 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libgssapi-krb5-2:i386 (1.16-2build1, 1.16-2ubuntu0.1), python-samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libwbclient0:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libgjs0g:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), samba:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-dsdb-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libarchive13:amd64 (3.2.2-3.1ubuntu0.1, 3.2.2-3.1ubuntu0.2), libgnome-bluetooth13:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), gjs:amd64 (1.52.1-1ubuntu1, 1.52.5-0ubuntu18.04.1), libk5crypto3:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libk5crypto3:i386 (1.16-2build1, 1.16-2ubuntu0.1), gnome-bluetooth:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), php-pear:amd64 (1:1.10.5+submodules+notgz-1ubuntu1, 1:1.10.5+submodules+notgz-1ubuntu1.18.04.1), krb5-locales:amd64 (1.16-2build1, 1.16-2ubuntu0.1), samba-libs:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libpam-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libcaca0:amd64 (0.99.beta19-2build2~gcc5.3, 0.99.beta19-2ubuntu0.18.04.1), libkrb5support0:amd64 (1.16-2build1, 1.16-2ubuntu0.1), libkrb5support0:i386 (1.16-2build1, 1.16-2ubuntu0.1), gir1.2-gnomebluetooth-1.0:amd64 (3.28.0-2, 3.28.0-2ubuntu0.1), samba-common:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libnss-winbind:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-vfs-modules:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), smbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), samba-common-bin:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.5, 2:4.7.6+dfsg~ubuntu-0ubuntu2.6), linux-firmware:amd64 (1.173.2, 1.173.3)
End-Date: 2019-01-16 08:17:09


After the update, I find myself unable to login after shutting down my system and rebooting. The system boots into the GUI login screen. After entering the password, it attempts to load the desktop manager. Unfortunately, it fails. After showing nothing more than a blank screen with the mouse pointer in it, it returns to the GUI login screen. This happens for just a single user account (unfortunately the primary user account). I am able to login and logout without any problem from other user accounts.



I have attempted the following (most of the suggestions from here):




  1. I have verified that .Xauthority and .ICEAuthority have the right permissions.

  2. I have verified that /tmp has the right permissions.

  3. I removed the propriety Nvidia driver (downloaded from the website; it had to be reinstalled after every kernel upgrade but as evident from the log entry above, the recent upgrade did not upgrade the kernel) and replaced with nvidia-driver-390, the package suggested by sudo ubuntu-drivers devices.



$ lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: nvidia



  1. I switched from lightdm to gdm3 using sudo dpkg-reconfigure gdm3

  2. I checked .xsession-errors and most of the entries are of the form:dbus-update-activation-environment: setting. Nothing there seems out of place.

  3. The .bashrc file contain the following additions:



# Aliases #
alias pcat="pygmentize -f terminal256 -O style=native -g"
mkdircd(){
# create a director and change to it
echo "creating directory $1"
mkdir $1
cd $1
}
alias mcd=mkdircd
export PATH="$PATH:/home/wneo/path_to_a_web_framework"

#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="/home/wneo/.sdkman"
[[ -s "/home/wneo/.sdkman/bin/sdkman-init.sh" ]] && source "/home/wneo/.sdkm an/bin/sdkman-init.sh"

#The following is to get go tools to work
export PATH="$PATH:$GOPATH/bin"


None of these edits were made immediately before or after the update.



Please help.







18.04 login






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 6 hours ago







wneo

















asked 6 hours ago









wneowneo

52




52













  • Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

    – guiverc
    5 hours ago











  • @guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

    – wneo
    5 hours ago











  • $HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

    – guiverc
    4 hours ago








  • 1





    There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

    – wneo
    2 hours ago





















  • Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

    – guiverc
    5 hours ago











  • @guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

    – wneo
    5 hours ago











  • $HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

    – guiverc
    4 hours ago








  • 1





    There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

    – wneo
    2 hours ago



















Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

– guiverc
5 hours ago





Check you have some free space in your $HOME (/home/user/) directory. GUI requires work files to be created on login, if this fails (usually due to lack of space) the login aborts & user is returned to login screen (no messages are given to user). All other accounts (with space in their $HOME) will be able to login, and all can login via tty or text-terminal.

– guiverc
5 hours ago













@guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

– wneo
5 hours ago





@guiverc There's 78G of free space in the unpartitioned HDD where / is mounted. I assume there are no folder specific quotas.

– wneo
5 hours ago













$HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

– guiverc
4 hours ago







$HOME - if you echo $HOME in terminal you'll see the directory that requires space, ie. your /home/user/ (if your $USER = "user" or your username=user). If you have a separate /home partition; it needs the space. If you have user quota's, the user may have filled their quota & gui work.files can't be created. You can fill space happily when logged into, files are created on login so that's the time free space is required (enough space). Login via term, and df -h & check you have enough space in your user directory (whatever device that's mounted on)

– guiverc
4 hours ago






1




1





There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

– wneo
2 hours ago







There were no quotas. After 24 hours of tinkering, I just gave up and upgraded to 18.10. Thank you very much for your comments.

– wneo
2 hours ago












1 Answer
1






active

oldest

votes


















0














After 24 hours of tinkering, I gave up and upgraded to 18.10.



sudo do-release-upgrade


After upgrade, the login screen wouldn't still show up. However, I was able to startX after booting into recovery mode, choosing failsafeX, dropping to console and then starting X. After a couple of reboots, I was able to see my desktop albeit in an incorrect resolution. Downloading and installing the latest drivers from Nvidia fixed the problem of resolution. The display is also crispier than it has ever been. However, I am still not able to get a login screen. I still have to follow the procedure mentioned above i.e boot into recovery mode, etc., I'll update this answer once I find a fix.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110489%2flogin-loop-for-one-user-after-ubuntu-update%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    After 24 hours of tinkering, I gave up and upgraded to 18.10.



    sudo do-release-upgrade


    After upgrade, the login screen wouldn't still show up. However, I was able to startX after booting into recovery mode, choosing failsafeX, dropping to console and then starting X. After a couple of reboots, I was able to see my desktop albeit in an incorrect resolution. Downloading and installing the latest drivers from Nvidia fixed the problem of resolution. The display is also crispier than it has ever been. However, I am still not able to get a login screen. I still have to follow the procedure mentioned above i.e boot into recovery mode, etc., I'll update this answer once I find a fix.






    share|improve this answer




























      0














      After 24 hours of tinkering, I gave up and upgraded to 18.10.



      sudo do-release-upgrade


      After upgrade, the login screen wouldn't still show up. However, I was able to startX after booting into recovery mode, choosing failsafeX, dropping to console and then starting X. After a couple of reboots, I was able to see my desktop albeit in an incorrect resolution. Downloading and installing the latest drivers from Nvidia fixed the problem of resolution. The display is also crispier than it has ever been. However, I am still not able to get a login screen. I still have to follow the procedure mentioned above i.e boot into recovery mode, etc., I'll update this answer once I find a fix.






      share|improve this answer


























        0












        0








        0







        After 24 hours of tinkering, I gave up and upgraded to 18.10.



        sudo do-release-upgrade


        After upgrade, the login screen wouldn't still show up. However, I was able to startX after booting into recovery mode, choosing failsafeX, dropping to console and then starting X. After a couple of reboots, I was able to see my desktop albeit in an incorrect resolution. Downloading and installing the latest drivers from Nvidia fixed the problem of resolution. The display is also crispier than it has ever been. However, I am still not able to get a login screen. I still have to follow the procedure mentioned above i.e boot into recovery mode, etc., I'll update this answer once I find a fix.






        share|improve this answer













        After 24 hours of tinkering, I gave up and upgraded to 18.10.



        sudo do-release-upgrade


        After upgrade, the login screen wouldn't still show up. However, I was able to startX after booting into recovery mode, choosing failsafeX, dropping to console and then starting X. After a couple of reboots, I was able to see my desktop albeit in an incorrect resolution. Downloading and installing the latest drivers from Nvidia fixed the problem of resolution. The display is also crispier than it has ever been. However, I am still not able to get a login screen. I still have to follow the procedure mentioned above i.e boot into recovery mode, etc., I'll update this answer once I find a fix.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 2 hours ago









        wneowneo

        52




        52






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110489%2flogin-loop-for-one-user-after-ubuntu-update%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            GameSpot

            connect to host localhost port 22: Connection refused

            Getting a Wifi WPA2 wifi connection