Unable to log in

Bug #1069283 reported by Ian Nicholson
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Confirmed
High
Unassigned

Bug Description

Happened to an upgrade to 12.10

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: lightdm 1.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
Date: Sun Oct 21 00:19:43 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ian Nicholson (imnichol) wrote :
Revision history for this message
Peter Antoniac (pan1nx) wrote :

Can you login in the console?

If yes, try to move your .bashrc. At least for me, that solved the problem. But to be more accurate, check your .xsession-errors also...
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Peter Antoniac (pan1nx) wrote :

The other way around is to boot from CD/USB, mount the disk with the home and then look into your .xsession-error
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Revision history for this message
Peter Antoniac (pan1nx) 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 1069283

This will help us to find and resolve the problem. Bear in mind that you may need to install the python-launchpadlib package from the universe repository. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report. Thanks in advance!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: lightdm (Ubuntu) → lightdm
Changed in lightdm:
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Ian Nicholson (imnichol) wrote : Re: [Bug 1069283] Re: Unable to log in

On 10/23/2012 01:36 AM, Peter Antoniac 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 1069283
>
> This will help us to find and resolve the problem. Bear in mind that you
> may need to install the python-launchpadlib package from the universe
> repository. Additionally, when prompted to give apport-collect
> permissions for Launchpad you will need to give it at least the ability
> to "Change Non-Private" data as it will be adding information to your
> bug report. Thanks in advance!
>
> When reporting bugs in the future please use apport, either via the
> appropriate application's "Help -> Report a Problem" menu or using
> 'ubuntu-bug' and the name of the package affected. You can learn more
> about this functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> ** Package changed: lightdm (Ubuntu) => lightdm
>
> ** Changed in: lightdm
> Importance: Undecided => High
>
> ** Changed in: lightdm
> Status: Confirmed => Incomplete
>
Done. I tried logging via tty and moving my .bashrc as well, but that
didn't resolve the issue.
I can upload whatever logs are needed, I just don't know how.

Peter Antoniac (pan1nx)
Changed in lightdm:
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Peter Antoniac (pan1nx) wrote :

Thank you for your patience...

Did you check the .xsession-errors file in your home directory (of the user that you try to log in)?

That might give you and us a clue to what is going on there behind the scenes.

Thanks!

Revision history for this message
Ian Nicholson (imnichol) wrote :

On 10/24/2012 12:47 AM, Peter Antoniac wrote:
> Thank you for your patience...
>
> Did you check the .xsession-errors file in your home directory (of the
> user that you try to log in)?
>
> That might give you and us a clue to what is going on there behind the
> scenes.
>
> Thanks!
>
I did, but I have no idea how to read it. Is there a way that I can
upload it to launchpad from the command line?

Revision history for this message
Peter Antoniac (pan1nx) wrote :

Apport-collect with add information...

On Wednesday 24 October 2012 14:14:57 you wrote:
> On 10/24/2012 12:47 AM, Peter Antoniac wrote:
> > Thank you for your patience...
> >
> > Did you check the .xsession-errors file in your home directory (of the
> > user that you try to log in)?
> >
> > That might give you and us a clue to what is going on there behind the
> > scenes.
> >
> > Thanks!
>
> I did, but I have no idea how to read it. Is there a way that I can
> upload it to launchpad from the command line?
--
-
 Peter Antoniac, PhD
 https://launchpad.net/~pan1nx
 GIT/CS a C+++ UL+++$ w--- PGP++ e++++

BOFH excuse #97:

Small animal kamikaze attack on power supplies

Revision history for this message
Ian Nicholson (imnichol) wrote :

Here's the relevant .xsession-errors file

Ian Nicholson (imnichol)
Changed in lightdm:
status: Incomplete → Confirmed
Peter Antoniac (pan1nx)
Changed in lightdm:
status: Confirmed → Incomplete
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Peter Antoniac (pan1nx) wrote :

Thanks for reporting this bug and supporting logs. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

But still, you could also try to login using a new user. If it works, it might be that your session information is the cause and not the Dispaly Manager.

Changed in lightdm:
status: Incomplete → Confirmed
Revision history for this message
Ian Nicholson (imnichol) wrote :

On 10/29/2012 03:36 AM, Peter Antoniac wrote:
> Thanks for reporting this bug and supporting logs. Since this bug has
> enough information provided for a developer to begin work, I'm going to
> mark it as confirmed and let them handle it from here. Thanks for taking
> the time to make Ubuntu better!
>
> But still, you could also try to login using a new user. If it works, it
> might be that your session information is the cause and not the Dispaly
> Manager.
>
It's actually been crashing before I'm able to try to log in. I think
it's crashing when LightDM starts.

Revision history for this message
Ian Nicholson (imnichol) wrote :

As of yesterday, my updated system does not bring me to the login screen. I am able to log in from a terminal, but lightdm doesn't start.

Revision history for this message
Ian Nicholson (imnichol) wrote :

I am still experiencing this bug, but I installed GDM which gives me a graphical login so I can at least get to my desktop. There is still a 2 or 3 second period where I still see glitched text on VT7 before GDM takes over though.

Revision history for this message
graingert (tagrain) wrote :

@imnichol is this bug fixed with the nouveau drivers?

Otherwise bug 1093376 is probably not a dupe of this bug

Revision history for this message
Ian Nicholson (imnichol) wrote :

On 12/24/2012 02:39 PM, graingert wrote:
> @imnichol is this bug fixed with the nouveau drivers?
>
> Otherwise bug 1093376 is probably not a dupe of this bug
>
No, it is not fixed with nouveau.

Revision history for this message
graingert (tagrain) wrote :

bug 1093376 is probably not a dupe of this bug then

Revision history for this message
vmkivinen (cyvi-) wrote :

I managed to get rid of the problem by deleting .Xauthority (got the tip from another bug report IIRC). It seems that owner of the problematic .Xauthority is root, whereas the owner of the new .Xauthority is the user. Could it be a file access issue?

Revision history for this message
Ian Nicholson (imnichol) wrote :

On 01/10/2013 06:53 PM, vmkivinen wrote:
> I managed to get rid of the problem by deleting .Xauthority (got the tip
> from another bug report IIRC). It seems that owner of the problematic
> .Xauthority is root, whereas the owner of the new .Xauthority is the
> user. Could it be a file access issue?
>
I've tried this, and I don't think it always fixed the problem permanently.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.