no log in screen due to lightdm greeter not being installed

Bug #816646 reported by GodNobody
100
This bug affects 26 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

just updated to lightdm 0.9 but now login issn't working anymore...

I had to go back to gdm to log in again....

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Tue Jul 26 23:06:05 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: lightdm
UpgradeStatus: Upgraded to oneiric on 2011-07-22 (3 days ago)
mtime.conffile..etc.lightdm.lightdm.conf: 2011-07-26T22:48:10.562849

Revision history for this message
GodNobody (godnobody) wrote :
Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Anthony Hook (anthonyhook) wrote :

I am also having this issue, what other attachments would be useful?

Revision history for this message
Anthony Hook (anthonyhook) wrote :

The issue was lightdm-gtk-greeter was not installed, according to IRC channel #ubuntu+1:

17:59 < micahg > a new upload ubuntu3 of lightdm was done ~20 minutes ago, that should fix the issues

Revision history for this message
Omer Akram (om26er) wrote :

lightdm 0.9.2-0ubuntu3 it seems removed lightdm-greeter-example-gtk but did not install lightdm-gtk-greeter had to manually install it :/

Changed in lightdm (Ubuntu):
importance: Undecided → High
importance: High → Medium
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Should be really really fixed in:

lightdm (0.9.2-0ubuntu4) oneiric; urgency=low

  * debian/control: depends on the greeters rather than recommends, seems some
    users still get no greeter after upgrade otherwise

Date: Wed, 27 Jul 2011 19:10:47 +0200

Could you please confirm ?

Changed in lightdm (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

I can't retest as I installed it manually but I guess we can close this as fixed as depends would strictly install it on update.

Changed in lightdm (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
John Johansen (jjohansen) wrote :

I can confirmed fixed with my recent update.

Revision history for this message
Guy Stone (stoneguy3) wrote :

Also confirming fix (via #816906)

Revision history for this message
Sam_ (and-sam) wrote :

Just did partitial upgrade of pending packages, even it stated to upgrade lightdm it wasn't installed. Reboot stops with black screen waiting. Switch to tty, install lightdm, reboot resulted in bringing back some kind of login screen, but unfortunately not unity-greeter which I used before.

Revision history for this message
Sam_ (and-sam) wrote :
Revision history for this message
Jamon Terrell (q-launchpad-jamonterrell-com) wrote :

This appears to be a problem still with machines where unity-2d is installed but unity-3d isn't. I fixed it by sudo apt-get remove lightdm, and sudo apt-get install ubuntu-desktop (which reinstalled both packages, as well as unity-greeter... my guess is that just installing unity-greeter would have solved the issue).

Martin Pool (mbp)
summary: - new update in oneiric broke start-up
+ no log in screen due to lightdm greeter not being installed
Revision history for this message
Kevin Turner (keturn) wrote :

This claims "Fix Released", but I have here an oneiric install (upgraded from natty) that has lightdm, attempts to start lightdm, but no greeter installed.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I'm reopening this because I'm in a similar situation as Kevin. My friend's computer does not come up to a greeter login after updating it from natty to oneiric. I put the following into root's crontab for now to take of the situation.

@reboot sleep 22; service lightdm stop;service lightdm start

Changed in lightdm (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

My friend's computer *does* have unity-greeter installed, though. Kevin, are you sure that is not the case for you? Please provide more information.

Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen closed bug because you have an issue which is similar, often it turns that issues are different and hijacking bugs this way just create confusion by email spamming users and mixing bugs in a same ticket

Changed in lightdm (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Sebastien, I'm not hijacking any bugs. But #12 claims that the exact situation that is supposed to be fixed by this ticket is not fixed for him. I thought the same applied to me. That's enough to assume that a ticket was closed prematurely and warrants reopening. I still consider that the proper way to deal with a situation like this. Thank you for your consideration.

Kevin, I won't reopen this ticket now although I think it should be open at this point in time. I'd rather not have a status war . But please be sure to let us know what your situation is nonetheless.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Rolf, that bug was due to system where no greeter is installed, you wrote "My friend's computer *does* have unity-greeter installed" so what makes you think it's the "the system has no greeter" installed issue you are having?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

That's why "I thought the same applied to me." When I realized this bug was only about lightdm not starting because a particular package was missing I would have closed the ticket again. But #12 explicitly said to be having the issue and no greeter installed. I thought he deserved a fair chance to reconfirm the situation.

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.