Get thrown back to lightdm right after trying to log in

Bug #1076777 reported by Shahar Or
This bug report is a duplicate of:  Bug #1076906: 1.5.0-3ubuntu2 breaks gpg-agent. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libgcrypt11 (Ubuntu)
New
Undecided
Unassigned
lightdm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Dear friends,

Upgrade from quantal to raring, encrypted home.

When I try to login via lightdm, I immediately get thrown back to lightdm after a short dark screen. I suppose that this may be a problem lower in the stack and not in lightdm itself but I figured that this was a good place to start the report. And if I'm informed that apport didn't collect the right log files then I can provide them.

Thanks,
Shahar

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lightdm 1.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.2-0ubuntu2
Architecture: amd64
Date: Fri Nov 9 00:25:43 2012
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-10-12 (758 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
SourcePackage: lightdm
UpgradeStatus: Upgraded to raring on 2012-11-07 (1 days ago)
mtime.conffile..etc.lightdm.users.conf: 2012-10-08T18:04:28

Revision history for this message
Shahar Or (mightyiam) wrote :
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
Iain Lane (laney) wrote :

Can you provide your ~/.xsession-errors file?

I had a similar issues, and mine contained:

  gpg-agent[2807]: Fatal: can't register GNU Pth with Libgcrypt: Not supported

moving .gnupg aside (say `mv ~/.gnupg ~/.gnupg-old') worked around the issue, or reverting libgcrypt11 to 1.5.0-3ubuntu1 both work around the issue for me.

Revision history for this message
Shahar Or (mightyiam) wrote :

Iain, good timing. It is indeed the same issue. Marked as a dupe.

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.