Public bug reported:
Good day!
I'm using Ubuntu 13.04. After I started my machine I found myself unable
to login into Unity: LightDM started successfully, but every time I
entered my password and hit <Enter> the screen became blank for a moment
and LightDM restarted itself. I rebooted the machine but nothing
changed.
At the same time I was able to login to both my account using CLI and to
Unity session of another user on the same machine.
Here is the contents of /var/log/upstart/lightdm.log
################ lightdm.log starts #####################
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
/bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority /home/boris/.Xauthority:
Success
Stopping PAM conversation, interaction requested but not supported
################ lightdm.log ends #######################
After this I inspected my home folder with 'ls -al | grep Xauth' on the
account of .Xauthority files and found this:
****************** ls -al /home/boris | grep Xauth
*************************
-rw------- 1 boris boris 176 окт. 16 00:22 .Xauthority
-rw-rw-r-- 1 boris boris 0 июля 31 00:25 .Xauthority.4BIT0W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:57 .Xauthority.5D472W
-rw-rw-r-- 1 boris boris 118 сент. 7 13:53 .Xauthority.80772W
-rw-rw-r-- 1 boris boris 59 авг. 27 21:27 .Xauthority.AGBH2W
-rw-rw-r-- 1 boris boris 0 июля 25 01:07 .Xauthority.IAVU0W
-rw-rw-r-- 1 boris boris 0 авг. 7 00:54 .Xauthority.ILXO1W
-rw-rw-r-- 1 boris boris 59 авг. 29 00:19 .Xauthority.JVJ61W
-rw-rw-r-- 1 boris boris 118 сент. 5 23:12 .Xauthority.K14N2W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:25 .Xauthority.KE6W2W
-rw-rw-r-- 1 boris boris 0 июля 25 07:16 .Xauthority.Q9LR0W
-rw-rw-r-- 1 boris boris 118 авг. 31 23:59 .Xauthority.TMPX2W
-rw-rw-r-- 1 boris boris 118 сент. 13 00:27 .Xauthority.X1DE3W
-rw-rw-r-- 1 boris boris 118 сент. 7 12:52 .Xauthority.YPI62W
-rw-rw-r-- 1 boris boris 0 авг. 1 01:20 .Xauthority.Z3170W
************************************************************************
The same command for the account that I was able to log into (seldom
used) produced
::::::::::::::: ls -al /home/veronika/ | grep Xauth
::::::::::::::::::::::::::::::::::::::
-rw------- 1 veronika veronika 58 окт. 16 08:33 .Xauthority
-rw-rw-r-- 1 veronika veronika 0 сент. 13 14:28 .Xauthority.4Z3F3W
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Seeing this, I decided to move all the Xauthority files in my home
directory to a temporary folder and tried to login again, this time,
successfully. Here is the current output of 'ls -al /home/boris | grep
Xauth':
^^^^^^^^^^^^^^ ls -al /home/boris | grep Xauth ^^^^^^^^^^^^^^^^^^^^^^^^
-rw------- 1 boris boris 58 окт. 16 08:39 .Xauthority
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
** Affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Good day!
I'm using Ubuntu 13.04. After I started my machine I found myself unable
to login into Unity: LightDM started successfully, but every time I
entered my password and hit <Enter> the scree became blank for a moment
and LightDM restarted itself. I rebooted the machine but nothing
changed.
At the same time I was able to login to both my account using CLI and to
Unity session of another user on the same machine.
Here is the contents of /var/log/upstart/lightdm.log
################ lightdm.log starts #####################
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success # Tried to login for a couple of times
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success # into my account
'boris'
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
- /bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
# Somewhere here I logged into
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success # another account and
issued
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success # df -kh to see if I
had space on
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success # HDD
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
+ /bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
################ lightdm.log ends #######################
After this I inspected my home folder with 'ls -al | grep Xauth' on the
account of .Xauthority files and found this:
****************** ls -al /home/boris | grep Xauth
*************************
-rw------- 1 boris boris 176 окт. 16 00:22 .Xauthority
-rw-rw-r-- 1 boris boris 0 июля 31 00:25 .Xauthority.4BIT0W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:57 .Xauthority.5D472W
-rw-rw-r-- 1 boris boris 118 сент. 7 13:53 .Xauthority.80772W
-rw-rw-r-- 1 boris boris 59 авг. 27 21:27 .Xauthority.AGBH2W
-rw-rw-r-- 1 boris boris 0 июля 25 01:07 .Xauthority.IAVU0W
-rw-rw-r-- 1 boris boris 0 авг. 7 00:54 .Xauthority.ILXO1W
-rw-rw-r-- 1 boris boris 59 авг. 29 00:19 .Xauthority.JVJ61W
-rw-rw-r-- 1 boris boris 118 сент. 5 23:12 .Xauthority.K14N2W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:25 .Xauthority.KE6W2W
-rw-rw-r-- 1 boris boris 0 июля 25 07:16 .Xauthority.Q9LR0W
-rw-rw-r-- 1 boris boris 118 авг. 31 23:59 .Xauthority.TMPX2W
-rw-rw-r-- 1 boris boris 118 сент. 13 00:27 .Xauthority.X1DE3W
-rw-rw-r-- 1 boris boris 118 сент. 7 12:52 .Xauthority.YPI62W
-rw-rw-r-- 1 boris boris 0 авг. 1 01:20 .Xauthority.Z3170W
************************************************************************
The same command for the account that I was able to log into (seldom
used) produced
- ::::::::::::::::::::::::::::: ls -al /home/veronika/ | grep Xauth
+ ::::::::::::::: ls -al /home/veronika/ | grep Xauth
::::::::::::::::::::::::::::::::::::::
-rw------- 1 veronika veronika 58 окт. 16 08:33 .Xauthority
-rw-rw-r-- 1 veronika veronika 0 сент. 13 14:28 .Xauthority.4Z3F3W
-
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
+
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Seeing this, I decided to move all the Xauthority files in my home
directory to a temporary folder and tried to login again, this time,
successfully. Here is the current output of 'ls -al /home/boris | grep
Xauth':
^^^^^^^^^^^^^^ ls -al /home/boris | grep Xauth ^^^^^^^^^^^^^^^^^^^^^^^^
-rw------- 1 boris boris 58 окт. 16 08:39 .Xauthority
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
** Description changed:
Good day!
I'm using Ubuntu 13.04. After I started my machine I found myself unable
to login into Unity: LightDM started successfully, but every time I
- entered my password and hit <Enter> the scree became blank for a moment
+ entered my password and hit <Enter> the screen became blank for a moment
and LightDM restarted itself. I rebooted the machine but nothing
changed.
At the same time I was able to login to both my account using CLI and to
Unity session of another user on the same machine.
Here is the contents of /var/log/upstart/lightdm.log
################ lightdm.log starts #####################
- Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
- /bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
+ Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
+ /bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
################ lightdm.log ends #######################
After this I inspected my home folder with 'ls -al | grep Xauth' on the
account of .Xauthority files and found this:
****************** ls -al /home/boris | grep Xauth
*************************
-rw------- 1 boris boris 176 окт. 16 00:22 .Xauthority
-rw-rw-r-- 1 boris boris 0 июля 31 00:25 .Xauthority.4BIT0W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:57 .Xauthority.5D472W
-rw-rw-r-- 1 boris boris 118 сент. 7 13:53 .Xauthority.80772W
-rw-rw-r-- 1 boris boris 59 авг. 27 21:27 .Xauthority.AGBH2W
-rw-rw-r-- 1 boris boris 0 июля 25 01:07 .Xauthority.IAVU0W
-rw-rw-r-- 1 boris boris 0 авг. 7 00:54 .Xauthority.ILXO1W
-rw-rw-r-- 1 boris boris 59 авг. 29 00:19 .Xauthority.JVJ61W
-rw-rw-r-- 1 boris boris 118 сент. 5 23:12 .Xauthority.K14N2W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:25 .Xauthority.KE6W2W
-rw-rw-r-- 1 boris boris 0 июля 25 07:16 .Xauthority.Q9LR0W
-rw-rw-r-- 1 boris boris 118 авг. 31 23:59 .Xauthority.TMPX2W
-rw-rw-r-- 1 boris boris 118 сент. 13 00:27 .Xauthority.X1DE3W
-rw-rw-r-- 1 boris boris 118 сент. 7 12:52 .Xauthority.YPI62W
-rw-rw-r-- 1 boris boris 0 авг. 1 01:20 .Xauthority.Z3170W
************************************************************************
The same command for the account that I was able to log into (seldom
used) produced
::::::::::::::: ls -al /home/veronika/ | grep Xauth
::::::::::::::::::::::::::::::::::::::
-rw------- 1 veronika veronika 58 окт. 16 08:33 .Xauthority
-rw-rw-r-- 1 veronika veronika 0 сент. 13 14:28 .Xauthority.4Z3F3W
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Seeing this, I decided to move all the Xauthority files in my home
directory to a temporary folder and tried to login again, this time,
successfully. Here is the current output of 'ls -al /home/boris | grep
Xauth':
^^^^^^^^^^^^^^ ls -al /home/boris | grep Xauth ^^^^^^^^^^^^^^^^^^^^^^^^
-rw------- 1 boris boris 58 окт. 16 08:39 .Xauthority
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1240359
Title:
Unable to login with LightDM on 13.04
Status in “lightdm” package in Ubuntu:
New
Bug description:
Good day!
I'm using Ubuntu 13.04. After I started my machine I found myself
unable to login into Unity: LightDM started successfully, but every
time I entered my password and hit <Enter> the screen became blank for
a moment and LightDM restarted itself. I rebooted the machine but
nothing changed.
At the same time I was able to login to both my account using CLI and
to Unity session of another user on the same machine.
Here is the contents of /var/log/upstart/lightdm.log
################ lightdm.log starts #####################
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
/bin/rm: cannot remove '/run/user/veronika/gvfs': Is a directory
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
Error writing X authority: Failed to write X authority
/home/boris/.Xauthority: Success
Stopping PAM conversation, interaction requested but not supported
################ lightdm.log ends #######################
After this I inspected my home folder with 'ls -al | grep Xauth' on
the account of .Xauthority files and found this:
****************** ls -al /home/boris | grep Xauth
*************************
-rw------- 1 boris boris 176 окт. 16 00:22 .Xauthority
-rw-rw-r-- 1 boris boris 0 июля 31 00:25 .Xauthority.4BIT0W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:57 .Xauthority.5D472W
-rw-rw-r-- 1 boris boris 118 сент. 7 13:53 .Xauthority.80772W
-rw-rw-r-- 1 boris boris 59 авг. 27 21:27 .Xauthority.AGBH2W
-rw-rw-r-- 1 boris boris 0 июля 25 01:07 .Xauthority.IAVU0W
-rw-rw-r-- 1 boris boris 0 авг. 7 00:54 .Xauthority.ILXO1W
-rw-rw-r-- 1 boris boris 59 авг. 29 00:19 .Xauthority.JVJ61W
-rw-rw-r-- 1 boris boris 118 сент. 5 23:12 .Xauthority.K14N2W
-rw-rw-r-- 1 boris boris 118 сент. 5 21:25 .Xauthority.KE6W2W
-rw-rw-r-- 1 boris boris 0 июля 25 07:16 .Xauthority.Q9LR0W
-rw-rw-r-- 1 boris boris 118 авг. 31 23:59 .Xauthority.TMPX2W
-rw-rw-r-- 1 boris boris 118 сент. 13 00:27 .Xauthority.X1DE3W
-rw-rw-r-- 1 boris boris 118 сент. 7 12:52 .Xauthority.YPI62W
-rw-rw-r-- 1 boris boris 0 авг. 1 01:20 .Xauthority.Z3170W
************************************************************************
The same command for the account that I was able to log into (seldom
used) produced
::::::::::::::: ls -al /home/veronika/ | grep Xauth
::::::::::::::::::::::::::::::::::::::
-rw------- 1 veronika veronika 58 окт. 16 08:33 .Xauthority
-rw-rw-r-- 1 veronika veronika 0 сент. 13 14:28 .Xauthority.4Z3F3W
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Seeing this, I decided to move all the Xauthority files in my home
directory to a temporary folder and tried to login again, this time,
successfully. Here is the current output of 'ls -al /home/boris | grep
Xauth':
^^^^^^^^^^^^^^ ls -al /home/boris | grep Xauth
^^^^^^^^^^^^^^^^^^^^^^^^
-rw------- 1 boris boris 58 окт. 16 08:39 .Xauthority
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1240359/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
