Login Screen Settings greyed out and unlock button non-responsive

Bug #570885 reported by myownserver
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Expired
Low
Unassigned
gnome-keyring-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gdm

Description: Ubuntu 10.04 LTS
Release: 10.04
gdm:
  Installed: 2.30.0-0ubuntu5
  Candidate: 2.30.0-0ubuntu5
  Version table:
 *** 2.30.0-0ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

When launching System > Administration > Login Screen, the Login Screen Settings window opens, but everything is greyed out. I click on the "Unlock" button, but it is un-responsive.
When I looked at the processes, I found it is the gdmsetup with the id 6532.
So I then opened Terminal and tried launching it both with and without sudo, but I get the same error both times:

david@david-desktop:~$ gdmsetup
** (gdmsetup:6558): DEBUG: init delay=10
** (gdmsetup:6558): DEBUG: "/usr/share/xsessions/une-efl-guest-restricted.desktop" is hidden or contains non-executable TryExec program

** (gdmsetup:6558): DEBUG: "/usr/share/xsessions/guest-restricted.desktop" is hidden or contains non-executable TryExec program

** (gdmsetup:6558): DEBUG: "/usr/share/xsessions/une-guest-restricted.desktop" is hidden or contains non-executable TryExec program

** (gdmsetup:6558): WARNING **: Error calling GetValue('daemon/DefaultSession'): Key not found
** (gdmsetup:6558): DEBUG: Init default session found:'(null)'
** (gdmsetup:6558): DEBUG: GdmUserManager: Found current seat: /org/freedesktop/ConsoleKit/Seat1
** (gdmsetup:6558): DEBUG: GdmUserManager: running 'ck-history --frequent --seat='Seat1' --session-type='''
** (gdmsetup:6558): DEBUG: GdmUserManager: explicitly skipping user: nobody
** (gdmsetup:6558): DEBUG: GdmUserManager: user icon changed
** (gdmsetup:6558): DEBUG: adding monitor for '/home/david/.face'
** (gdmsetup:6558): DEBUG: Getting list of sessions for user 1000
** (gdmsetup:6558): DEBUG: Found 1 sessions for user david
** (gdmsetup:6558): DEBUG: GdmUser: adding session /org/freedesktop/ConsoleKit/Session1
** (gdmsetup:6558): DEBUG: GdmUserManager: sessions changed user=david num=1
** (gdmsetup:6558): DEBUG: GdmUserManager: added session for user: david
** (gdmsetup:6558): DEBUG: GdmUserManager: history output: david 8

** (gdmsetup:6558): DEBUG: GdmUserManager: history output: (null) 2

** (gdmsetup:6558): WARNING **: Unable to parse history: (null) 2

** (gdmsetup:6558): DEBUG: init user='david' auto=True

I'm able to launch other applications such as Synaptic Package Manager, Update Manager, etc. without any issues.
As of the time I'm writing this, I have also ran all updates and rebooted since.
I've checked and the user I'm using is a sudoer.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gdm 2.30.0-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Apr 27 13:40:51 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1)
NonfreeKernelModules: nvidia
Package: gnome-keyring-manager
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
myownserver (imchillindave) wrote :
tags: added: gdm login screen unlock
removed: apport-bug lucid
Revision history for this message
Victor Vargas (kamus) wrote :

I tried to reproduce this issue here but everything works fine, have you checked that PolicyKit Agent is running in your session?

Changed in gdm (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
John Vivirito (gnomefreak) wrote :

I wasnt sure of the package but gdm made most sense when i told him to file the bug report.
I am unable to reproduce this.

After speaking to the reporter in IRC it seems this is not the only problem but other admin menu entries do not unlock. I will ask him to give a count of everything under system>admin that fails/works
Im adding gnome-keyring task to this bug as it seems to be default. i will ask the reporter to use apport-collect hopefully it will grab needed info for gnome-keyring

Revision history for this message
John Vivirito (gnomefreak) wrote :

Sorry we overlapped but thanks for getting to it. I will leave you guys to it.

Revision history for this message
myownserver (imchillindave) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
myownserver (imchillindave) wrote :

It is running:
david@david-desktop:~$ ps aux |grep policykit
root 1296 0.0 0.0 54692 4828 ? S 12:09 0:01 /usr/lib/policykit-1/polkitd
david 1303 0.0 0.1 161868 7036 ? S 12:09 0:00 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
david 7107 0.0 0.0 7620 1004 pts/1 S+ 14:33 0:00 grep --color=auto policykit

Revision history for this message
myownserver (imchillindave) wrote :
Revision history for this message
myownserver (imchillindave) wrote :

This is the full list.

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

gnome-keyring-manager is deprecated for several cycles and not shipped in recent versions, not a bug in that one

Changed in gnome-keyring-manager (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

how do you start your session? could you run ck-list-sessions and copy the log there?

Revision history for this message
John Vivirito (gnomefreak) wrote :

Disabling compiz fixed it for him.

affects: gdm (Ubuntu) → compiz (Ubuntu)
Revision history for this message
John Vivirito (gnomefreak) wrote :

I asked him to disable it than that and another issue he was having both work now.

Revision history for this message
myownserver (imchillindave) wrote :

Final notes:
It appears there was a number of issues and it was all traced back to compiz being the culprit.
A list of the issues I found were these:
* The above mentioned issue.
* System > Administration > Users Settings - Buttons there not working correctly.
* Cannot add items or remove them from the Launch Bar.
* Cannot reboot/shutdown since it only took me to the login screen in gnome. Hard-restart was required.

The solution:
Go into "Preferences > Appearance > Visual Effects" and make sure it is set to "None".
If it already was, you may have a different issue.
Once you've done this, reboot ( which you may have to do a hard-restart ) and then check again. Everything worked accordingly after doing this.

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

there is no reason compiz should do a difference there

affects: compiz (Ubuntu) → gdm (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

reading the current comment the user blames compiz but several issues are listed and the bug is not really of any use there, seems rather an user question and description of local issue than a bug report

affects: gdm (Ubuntu) → compiz (Ubuntu)
Changed in compiz (Ubuntu):
status: Incomplete → New
affects: compiz (Ubuntu) → gdm (Ubuntu)
affects: gdm (Ubuntu) → compiz (Ubuntu)
affects: compiz (Ubuntu) → gdm (Ubuntu)
affects: gdm (Ubuntu) → compiz (Ubuntu)
affects: compiz (Ubuntu) → gdm (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

reassigning to compiz if launchpad works now

affects: gdm (Ubuntu) → compiz (Ubuntu)
Revision history for this message
myownserver (imchillindave) wrote :

@Sebastien Bacher
I worked with John Vivirito on the initial issue, which is the topic of this bug and the other things I mentioned in #13 I noticed as we went, which were all fixed once compiz was no longer being used.
Therefore I assumed it had some role (to what level I do not know) in the other issues as well since they were similar in behavior and all seemed to be linked to compiz.

Revision history for this message
ursaminor (ursa-juvenis) wrote :

I have the same problem as well. I cannot unlock Login Screen Settings. I looked for a resolution and used the following:

1. Open Terminal.

2. Open the custom.conf file with gedit: gksu gedit /etc/gdm/custom.conf

3. Enter configuration values:

[daemon]
AutomaticLoginEnable=true
AutomaticLogin=lani

4. Reboot.

The unlock works and the automatic login is set. But after shutdown or reboot the Login Screen Settings has been reset to manual login and unlock does not work.

tags: added: lucid
David Barth (dbarth)
tags: added: 0.8
Revision history for this message
Yashkirat Singh (yashkirat) wrote :

I have the same problem, that is, the Login Screen is greyed out, including the unlock button.

Note: I just installed Natty Narwhal (Ubuntu 11.04) on my system. I have a Radeon 2600 XT video card, AMD Athlon 64 X2 Dual Core Processor 6400+ and 4 gigs of RAM . I was not able to login successfully the first time. I had to log-in using the Ubuntu Desktop Edition (Safe Mode). I have since rebooted back into "Safe Mode" and the Login Screen is still greyed out.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Is this still an issue with Natty? Could you please test and comment back? thanks in advance.

Changed in compiz (Ubuntu):
status: New → Incomplete
Revision history for this message
Brett Hunsaker (bhunsaker) wrote :

I can confirm that this still happens on natty. This system is an upgrade.

policykit agent is running

Also see the user settings buttons not working

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

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
Revision history for this message
David Brasil da Cunha (davidbrasilcunha) wrote :

Sorry, i don't know if it i can post it here, but anyway...

In my case it had nothing to do with compiz.
I had the same problem twice and i solved both on the same way: "Reinstalling GDM". (in one case i had to uninstall the LightDM and then reinstall GDM)

Thanx.

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.