after typing password on login screen, login screen returns

[HJZ]

I am running a dual boot system.
Installed trusty (amd64) from usb stick - without formatting the install partition.
Upon restart the login screen appears all right. But after typing the password, the screen turns black for a split second - and the login screen appears again - without any comments.
If I type a wrong password, I get the incorrect password message on the login screen.
If I choose the guest login, unity appears and is perfectly operational.
What can I do?
Thanks so much!
Hans

[Filip Sohajek (filip-sohajek-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:

  apport-collect 1358479

[Gunnar Hjalmarsson (gunnarhj)]

Especially, can you please attach the /var/log/lightdm/lightdm.log file to the bug report.

[HJZ (fam-zentel)]

Dear Filip,

Thanks so much for your reply!
yes, I had obviously submitted my report twice.

Could you please advise on how to open a terminal, if I cannot log into
the system? I guess, the guest account would not report the error.

Best regards,
Hans

On 20.08.2014 18:03, Filip Sohajek wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command, as it will
> automatically gather debugging information, in a terminal:
>
> apport-collect 1358479
>
> ** Package changed: unity (Ubuntu) => lightdm (Ubuntu)
>

[HJZ (fam-zentel)]

Dear Gunnar,
Thanks for your support!
I'd love to do as requested ... once I am in the system.
Can I access these files from the guest account or a live system?
Reason: I cannot log into the system, because I can't get past the login
screen.
Hans

On 20.08.2014 19:19, Gunnar Hjalmarsson wrote:
> Especially, can you please attach the /var/log/lightdm/lightdm.log file
> to the bug report.
>
> ** Changed in: lightdm (Ubuntu)
> Status: New => Incomplete
>

[Gunnar Hjalmarsson (gunnarhj)]

From the login screen you can open a console using Ctrl+Alt+F1, log in and copy the file to a place where it can be accessed from a guest session (e.g. /var/tmp). Then you can return to the login screen with Ctrl+Alt+F7 and enter a guest session.

[HJZ (fam-zentel)]

Dear Gunnar,
I am very sorry, but obviously not well versed with such issues - Ubuntu
was just too reliable so far :-)
I am in the terminal and did first install the apport program. Now I am
told that the system waits to hear from launchpad ...
I am logged into launchpad from another computer but that doesn't
authorize the program.
What do I have to do?
Thanks so much again!
Hans

On 20.08.2014 20:37, Gunnar Hjalmarsson wrote:
>>From the login screen you can open a console using Ctrl+Alt+F1, log in
> and copy the file to a place where it can be accessed from a guest
> session (e.g. /var/tmp). Then you can return to the login screen with
> Ctrl+Alt+F7 and enter a guest session.
>

[HJZ (fam-zentel)]

Thank you very much, Gunnar!

I opened the console, installed apport; now the program waits for launchpad to grant access - which it doesn't.
how can I grant access in launchpad, if I am logged in with another computer?
Thank you for your advise!
Hans

[HJZ (fam-zentel)]

Thank you very much, Gunnar!

I opened the console, installed apport; now the program waits for
launchpad to grant access - which it doesn't.
how can I grant access in launchpad, if I am logged in with another
computer?
Thank you for your advise!
Hans

-------- Forwarded Message --------
Subject: [Bug 1358479] Re: after typing password on login screen, login
screen returns
Date: Wed, 20 Aug 2014 19:40:05 -0000
From: HJZ <email address hidden>
Reply-To: Bug 1358479 <email address hidden>
To: <email address hidden>

Thank you very much, Gunnar!

I opened the console, installed apport; now the program waits for
launchpad to grant access - which it doesn't.
how can I grant access in launchpad, if I am logged in with another
computer?
Thank you for your advise!
Hans

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1358479

Title:
  after typing password on login screen, login screen returns

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  I am running a dual boot system.
  Installed trusty (amd64) from usb stick - without formatting the
install partition.
  Upon restart the login screen appears all right. But after typing the
password, the screen turns black for a split second - and the login
screen appears again - without any comments.
  If I type a wrong password, I get the incorrect password message on
the login screen.
  If I choose the guest login, unity appears and is perfectly operational.
  What can I do?
  Thanks so much!
  Hans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1358479/+subscriptions

[Gunnar Hjalmarsson (gunnarhj)]

Hmm.. I don't know how you would do that from a console.

Instead, can you please copy the log file I asked about:

sudo cp /var/log/lightdm/lightdm.log /var/tmp
sudo chmod +r /var/tmp/lightdm.log

and then attach it here from a guest session.

[HJZ (fam-zentel)]

Hello Gunnar,

Thank you for your patients!

Below the file. Hope it helps ...

Kind regards,
Hans

[+0.04s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.04s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=982
[+0.04s] DEBUG: Loading configuration dirs from
/usr/share/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.04s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.04s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.04s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.04s] DEBUG: Loading configuration from
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.04s] DEBUG: Loading configuration dirs from
/usr/local/share/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration dirs from
/etc/xdg/lightdm/lightdm.conf.d
[+0.04s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.04s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.11s] DEBUG: Registered seat module xlocal
[+0.11s] DEBUG: Registered seat module xremote
[+0.11s] DEBUG: Registered seat module unity
[+0.11s] DEBUG: Registered seat module surfaceflinger
[+0.95s] DEBUG: Adding default seat
[+0.95s] DEBUG: Seat: Starting
[+0.95s] DEBUG: Seat: Creating greeter session
[+0.95s] DEBUG: Seat: Creating display server of type x
[+0.95s] DEBUG: Deactivating Plymouth
[+0.98s] DEBUG: Using VT 7
[+0.98s] DEBUG: Seat: Starting local X display on VT 7
[+0.98s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.98s] DEBUG: DisplayServer x-0: Writing X server authority to
/var/run/lightdm/root/:0
[+0.98s] DEBUG: DisplayServer x-0: Launching X Server
[+0.98s] DEBUG: Launching process 1077: /usr/bin/X -core :0 -seat seat0
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.98s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.98s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.98s] DEBUG: Registering seat with bus path
/org/freedesktop/DisplayManager/Seat0
[+1.64s] DEBUG: Loading users from org.freedesktop.Accounts
[+1.64s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+3.03s] DEBUG: Got signal 10 from process 1077
[+3.03s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+3.03s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+3.03s] DEBUG: Quitting Plymouth; retaining splash
[+3.06s] DEBUG: Seat: Display server ready, starting session authentication
[+3.06s] DEBUG: Session pid=1113: Started with service 'lightdm-greeter',
username 'lightdm'
[+3.09s] DEBUG: Session pid=1113: Authentication complete with return value
0: Success
[+3.09s] DEBUG: Seat: Session authenticated, running command
[+3.09s] DEBUG: Session pid=1113: Running command
/usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+3.10s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+3.10s] DEBUG: Session pid=1113: Logging to
/var/log/lightdm/x-0-greeter.log
[+3.13s] DEBUG: Activating VT 7
[+3.13s] DEBUG: Activating login1 session /org/freedesktop/login1/session/c1
[...

[Gunnar Hjalmarsson (gunnarhj)]

I can't see anything odd there - maybe someone else can, or maybe it was a dead end.

Let's try another thing. The fact that you can enter a guest session indicates that the problem lies somewhere in your home directory. So let's move it away temporarily:

sudo mv /home/tapjz /home/tapjz.bak
sudo cp -rT /etc/skel/ /home/tapjz
sudo chown -R tapjz:tapjz /home/tapjz

Then go back with Ctrl+Alt+F7 and try to log in.

[HJZ (fam-zentel)]

Dear Gunnar,
wow, boots up fine.
but, of course, can't find my docs ...
Hans

On 20.08.2014 23:14, Gunnar Hjalmarsson wrote:
> I can't see anything odd there - maybe someone else can, or maybe it was
> a dead end.
>
> Let's try another thing. The fact that you can enter a guest session
> indicates that the problem lies somewhere in your home directory. So
> let's move it away temporarily:
>
> sudo mv /home/tapjz /home/tapjz.bak
> sudo cp -rT /etc/skel/ /home/tapjz
> sudo chown -R tapjz:tapjz /home/tapjz
>
> Then go back with Ctrl+Alt+F7 and try to log in.
>

[Gunnar Hjalmarsson (gunnarhj)]

If you want, you can copy or move your documents to 'the new' home directory. For instance:

mv /home/tapjz.bak/Documents /home/tapjz

But, of course, we still don't know what caused the problem.

[HJZ (fam-zentel)]

Thanks again, Gunnar!
I am already working on that.
All the best
Hans

On 21.08.2014 00:41, Gunnar Hjalmarsson wrote:
> If you want, you can copy or move your documents to 'the new' home
> directory. For instance:
>
> mv /home/tapjz.bak/Documents /home/tapjz
>
> But, of course, we still don't know what caused the problem.
>
> ** Changed in: lightdm (Ubuntu)
> Status: Incomplete => New
>

[Rolf Leggewie (r0lf)]

Do you still have that old home directory lying around? I suspect your .Xauthority file was owned by root. That would make this ticket a dupe of bug 1268283.