On 06/08/2011 02:00 PM, Chris Tooley wrote:
> Hello All
>
> Using 6rolling, I cannot login through GDM. I can, however, login with SSH.
>
> Here is some possibly relevant info from various log files:
>
> ---------------
> /var/log/secure (excerpt)
> ---------------
> Jun 8 11:38:47 heplw44 pam: gdm-password[4892]:
> pam_unix(gdm-password:auth): authentication failure; logname= uid=0
> euid=0 tty=:0 ruser= rhost= user=ctooley
> Jun 8 11:38:48 heplw44 pam: gdm-password[4892]:
> pam_sss(gdm-password:auth): authentication success; logname= uid=0
> euid=0 tty=:0 ruser= rhost= user=ctooley
> Jun 8 11:38:48 heplw44 pam: gdm-password[4892]:
> pam_unix(gdm-password:session): session opened for user ctooley by (uid=0)
> Jun 8 11:38:48 heplw44 polkitd(authority=local): Unregistered
> Authentication Agent for session /org/freedesktop/ConsoleKit/Session17
> (system bus name :1.117, object path
> /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
> (disconnected from bus)
> Jun 8 11:38:48 heplw44 pam: gdm-password[4892]:
> pam_unix(gdm-password:session): session closed for user ctooley
> Jun 8 11:38:50 heplw44 polkitd(authority=local): Registered
> Authentication Agent for session /org/freedesktop/ConsoleKit/Session19
> (system bus name :1.130
> [/usr/libexec/polkit-gnome-authentication-agent-1], object path
> /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
>
> ---------------
> /var/log/messages (excerpt)
> ---------------
> Jun 8 11:38:48 heplw44 automount[1853]: set_tsd_user_vars: failed to
> get group info from getgrgid_r
> Jun 8 11:38:48 heplw44 NetworkManager[1627]:<error>
> [1307558328.303252] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
> Jun 8 11:38:48 heplw44 gnome-keyring-daemon[5021]: Couldn't unlock
> login keyring with provided password
> Jun 8 11:38:48 heplw44 gnome-keyring-daemon[5021]: Failed to unlock
> login on startup
> Jun 8 11:38:48 heplw44 NetworkManager[1627]:<error>
> [1307558328.420407] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
> Jun 8 11:38:48 heplw44 NetworkManager[1627]:<error>
> [1307558328.716734] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
> Jun 8 11:38:48 heplw44 kernel: [fglrx] IRQ 32 Disabled
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Firegl kernel thread PID: 5115
> Jun 8 11:38:49 heplw44 kernel: [fglrx] IRQ 32 Enabled
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Gart USWC size:1184 M.
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Gart cacheable size:469 M.
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Reserved FB block: Shared
> offset:0, size:1000000
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Reserved FB block: Unshared
> offset:f94b000, size:3b5000
> Jun 8 11:38:49 heplw44 kernel: [fglrx] Reserved FB block: Unshared
> offset:1fff4000, size:c000
> Jun 8 11:38:49 heplw44 NetworkManager[1627]:<error>
> [1307558329.828334] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
> Jun 8 11:38:50 heplw44 gdm-simple-greeter[5158]: Gtk-WARNING:
> gtkwidget.c:5460: widget not within a GtkWindow
> Jun 8 11:38:53 heplw44 NetworkManager[1627]:<error>
> [1307558333.448251] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
> Jun 8 11:38:53 heplw44 NetworkManager[1627]:<error>
> [1307558333.448768] [nm-manager.c:1313] user_proxy_init(): could not
> init user settings proxy: (3) Could not get owner of name
> 'org.freedesktop.NetworkManagerUserSettings': no such name
>
> ---------------
> cat /var/log/Xorg.0.log | grep EE
> ---------------
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (II) Loading extension MIT-SCREEN-SAVER
> (EE) PreInit returned NULL for "HDA Intel PCH Headphone"
> (EE) config/hal: NewInputDeviceRequest failed (8)
>
> ---------------
> cat /var/log/gdm/\:0.log | grep EE
> ---------------
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (EE) PreInit returned NULL for "HDA Intel PCH Headphone"
> (EE) config/hal: NewInputDeviceRequest failed (8)
>
> ---------------
> cat /var/log/gdm/\:0-greeter.log
> ---------------
> ** (<unknown>:5139): DEBUG: Client registered with session manager:
> /org/gnome/SessionManager/Client1
> ** (process:5158): DEBUG: Greeter session pid=5158 display=:0.0
> xauthority=/var/run/gdm/auth-for-gdm-GLhNhn/database
>
> (polkit-gnome-authentication-agent-1:5155): GLib-GObject-WARNING **:
> cannot register existing type `_PolkitError'
>
> (polkit-gnome-authentication-agent-1:5155): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> Failed to play sound: File or data not found
> gdm-simple-greeter[5158]: Gtk-WARNING: gtkwidget.c:5460: widget not
> within a GtkWindow
> Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message
> with a timestamp of 0 for 0x1e0002b (Login Wind)
> Window manager warning: meta_window_activate called by a pager with a 0
> timestamp; the pager needs to be fixed.
>
>
> ---------------
> cat /var/log/gdm/\:0-slave.log.1
> ---------------
> pam: gdm-password[4892]: pam_unix(gdm-password:auth): authentication
> failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ctooley
> pam: gdm-password[4892]: pam_sss(gdm-password:auth): authentication
> success; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=ctooley
> pam: gdm-password[4892]: pam_unix(gdm-password:session): session opened
> for user ctooley by (uid=0)
> pam: gdm-password[4892]: pam_unix(gdm-password:session): session closed
> for user ctooley
>
>
> These were the only files in /var/log modified at the same time as an
> attempted login with GDM. (the excerpts are the only entries at the same
> time)
>
> Can anyone direct me to some way of diagnosing this? I see a number of
> warnings and errors but searching google doesn't seem to return anything
> propitious...
>
> -Chris Tooley
I appears that you succesfully logged in via GDM the second time, but I
assume that you weren't able to get in.
When that happens to one of my users, the first thing I look at is their
home area.
Make sure it exists, make sure it's read/write for that user on login,
and make sure the file system for their home area isn't full (overquota
or something like that.)
Troy
--
__________________________________________________
Troy Dawson [log in to unmask] (630)840-6468
Fermilab ComputingDivision/SCF/FEF/SLSMS Group
__________________________________________________
|
