'authorization failed' at gnome login

Bug #203755 reported by Elias K Gardner
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Expired
Low
Unassigned
Nominated for Lucid by bsgcic

Bug Description

System: Ubuntu 8.04 hardy 64bit

I have had my system set to auto login for quite some time now. I temporarily turned that off. When the gnome login shows up before I get a chance to enter my username or password an error pops up stating 'authorization failed'. Clicking ok just makes the same error occur again. All I can do is ctrl+alt+backspace and ctrl+alt+del to reboot.

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

Thanks for your report, can you provide us of the auth.log and gdm log ? thanks.

Changed in gdm:
status: New → Incomplete
Revision history for this message
Elias K Gardner (zorkerz) wrote :

I soon discovered there were many more problems with my system. I don't know what happened to begin with to start it all. It was too unusable for me to narrow down any particular issue. This bug can be deleted (i don't know if thats possibly) in any case it will automatically expire if i stop blabbing to it. th,nis

Changed in gdm:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in gdm:
status: Incomplete → Invalid
Revision history for this message
ehpc (ehpc) wrote :

Confirmed. I also had this bug. It appears after installing libpam-gnome-keyring. By default this package forms the following /etc/pam.d/gdm:

#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so readenv=1
auth required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
auth optional pam_gnome_keyring.so
@include common-account
session required pam_limits.so
@include common-session
session optional pam_gnome_keyring.so auto_start
@include common-password
@include common-pamkeyring

And there are two problems.
       First. @include common-pamkeyring. It doesn't exist. I think this is deprecated file from libpam-keyring, it shouldn't be in libpam-gnome-keyring. Anyway, to fix it, just comment it like this #@include common-pamkeyring.
       Second. There is no "auth optional pam_gnome_keyring.so" entry. So you need to add it manually before "session optional pam_gnome_keyring.so auto_start".
After fixing it, you will get this:

#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so readenv=1
auth required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-auth
auth optional pam_gnome_keyring.so
@include common-account
session required pam_limits.so
@include common-session
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
@include common-password
#@include common-pamkeyring

And your login screen will work again!

P.S. auth.log before:
Jan 5 08:44:36 ehpc-desktop gdm[7014]: PAM _pam_init_handlers: error reading /etc/pam.d/gdm
Jan 5 08:44:36 ehpc-desktop gdm[7014]: PAM _pam_init_handlers: [Критическая ошибка - немедленная отмена]
Jan 5 08:44:36 ehpc-desktop gdm[7014]: PAM error reading PAM configuration file
Jan 5 08:44:36 ehpc-desktop gdm[7014]: PAM pam_start: failed to initialize handlers
Jan 5 08:44:37 ehpc-desktop gdm[7014]: PAM _pam_load_conf_file: unable to open /etc/pam.d/common-pamkeyring
Jan 5 08:44:37 ehpc-desktop gdm[7014]: PAM error loading (null)

Changed in gdm:
status: Invalid → Confirmed
Revision history for this message
ehpc (ehpc) wrote :

Forgot to mention, it appears in 8.10 Interpid Ibex 32bit too.

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

not sure why it happens only to some users and how they configured their gdm but it doesn't seem to be an issue

Changed in gdm (Ubuntu):
importance: Medium → Low
Revision history for this message
denick (bratan-lml) wrote :

Thanks! That fixed this issue for me too (jaunty x64).

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

does anybody still get the issue in karmic now?

Changed in gdm (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gdm (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Varun (varunthacker) wrote :

i have the same problem.Ill describe it anyways.
When my network disconnects for a long time (more than 2 mins. or so) then network manager cannot connect to the same network again without restarting the laptop or if i use the commands mentioned:

$ sudo /etc/init.d/network-manager restart
$ sudo restart network-manager

once i restart network manager by this method it reconnects.
I'm using a Lenovo r61 and have upgraded to 9.10 from 9.04 and this problem was not there in 9.04.

please let me know what additional information do i need to provide.

Changed in gdm (Ubuntu):
status: Invalid → New
Revision history for this message
Varun (varunthacker) wrote :

sorry......i had to bug pages open and reported it in the wrong one......my mistake completely...
please change it back to invalid and delete my post. Cant figure out how to delete the post myself..

Sorry once again...

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GDM is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

Changed in gdm (Ubuntu):
status: New → Incomplete
Revision history for this message
phil (ph-schoppe) wrote :

I get the message 'error initiating conversation with authentification system' in Lucid after manually adding '@include common-pamkeyring' to the /etc/pam.d/gdm file. This was supposed to disable nm-applet needing the keyring default pw to connect to my wlan. Now i can't login and don't get a login screen in the tty consoles.

Revision history for this message
bsgcic (bsgcic) wrote :

This issue still present in Lucid.

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

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

Changed in gdm (Ubuntu):
status: Incomplete → Expired
Revision history for this message
dcannell (dcannell-freeshell) wrote :

Just so someone is aware this *IS* a continuing issue. Last night I updated from 2.6.35-28 to 2.6.35-30 and on reboot was unable to login to the GUI. I was able to login to the TTY session however. By making the two edits to /etc/pam.d/gdm I was able to login to the GUI successfully.

Thanks to ehpc, I didn't really want to rebuild this system...

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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