"Logging in..." not logging in

[Errol Atterbury]

$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

$ apt-cache policy lightdm
lightdm:
  Installed: 1.2.1-0ubuntu1
  Candidate: 1.2.1-0ubuntu1
  Version table:
 *** 1.2.1-0ubuntu1 0
        500 http://za.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

$ apt-cache policy ubuntu-tweak
ubuntu-tweak:
  Installed: 0.7.0-1~precise4
  Candidate: 0.7.0-1~precise4
  Version table:
 *** 0.7.0-1~precise4 0
        100 /var/lib/dpkg/status

$ uname -a
Linux myhost 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

see this thread: http://ubuntuforums.org/showthread.php?p=11889897#post11889897

Some folk are experiencing a greeter problem.
When one logins, the greeter will say, "Logging in..." but it never does so and simply stays on that screen.
In looking at what's going on, it would seem that ubuntu-tweak may have a role to play in that situation... but we can't be sure.
It would seem that reverting to gdm is a solution.
Please look at those posts and if there is info that we can provide, I'm sure that those who have posted will do so.

[Errol Atterbury (errolbury)]

There seems to be a permissions problem (related to /usr/share/backgrounds and ~/Pictures) and is repeatable whenever the default wallpaper is selected that is set to periodically change.

[Errol Atterbury (errolbury)]

It doesn't seem to be a ubuntu-tweak problem after all... whether you use it or background-settings to configure a desktop wallpaper, the problem will eventually occur.

There is however no consistency... on occasion one of the other std wallpapers may also lock up the login process as well. If one configures the greeter screen to have the same background as the current desktop which is an image from ~/Pictures, then the and the login process will also lock up. Using gradient colors instead of a wallpaper is one surefire workaround.

[Launchpad Janitor (janitor)]

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