Description of problem: Network-provided users can't log in through GDM. They stall after accepting the password and are never presented with a desktop. Version-Release number of selected component (if applicable): gdm-2.29.6-1.fc13 How reproducible: Every time Steps to Reproduce: Install sssd >= 1.1.0 and authconfig >= 6.1.2 Run authconfig-gtk and set up the following settings (valid during the SSSDByDefault Test Day) User Account Database: LDAP LDAP Search Base DN: dc=fedoraproject,dc=org LDAP Server: ldaps://fedoraproject.org (download an appropriate certificate. For the test day it's http://jlaska.fedorapeople.org/sssd/cacert.asc) Leave "Use TLS to encrypt connections" unchecked Authentication Method: LDAP Hit apply. Now logout (or switch users) and attempt to log in as a user provided by LDAP. (E.g. user 'sssdtest10016' with password 'sssdtest') Actual results: Password is accepted and GDM begins the process to load the desktop environment, but it hangs with nothing on the screen but the mouse cursor and the background visible. Expected results: The user should be presented with a functional desktop environment. Additional info: From /var/log/messages: Mar 30 15:15:06 dhcp-100-3-105 gdm-binary[1619]: DEBUG(+): GdmDisplay: Adding authorization for user:sssdtest10017 on display :1 Mar 30 15:15:06 dhcp-100-3-105 gdm-binary[1619]: DEBUG(+): GdmDisplay: Adding user authorization for sssdtest10017 Mar 30 15:15:06 dhcp-100-3-105 gdm-simple-slave[3576]: WARNING: Failed to add user authorization: could not find user "sssdtest10017" on system Mar 30 15:15:06 dhcp-100-3-105 gdm[3649]: ******************* START ********************************** Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: [Thread debugging using libthread_db enabled] Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: [New Thread 0x7f5d9fbf7710 (LWP 3581)] Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: 0x00007f5da7cbc59d in waitpid () from /lib64/libpthread.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #0 0x00007f5da7cbc59d in waitpid () from /lib64/libpthread.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #1 0x000000000041f11b in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #2 0x000000000041f1c7 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #3 <signal handler called> Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #4 0x00007f5da71fb955 in raise () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #5 0x00007f5da71fd135 in abort () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #6 0x00007f5da75af184 in g_assertion_message () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #7 0x00007f5da75af730 in g_assertion_message_expr () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #8 0x000000000041af1c in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #9 0x00007f5da7588db2 in g_main_context_dispatch () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #10 0x00007f5da758cb98 in ?? () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #11 0x00007f5da758d0a5 in g_main_loop_run () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #12 0x00000000004072d5 in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #13 0x00007f5da71e6d2d in __libc_start_main () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #14 0x0000000000406f79 in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #15 0x00007fff1e939148 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #16 0x000000000000001c in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #17 0x0000000000000003 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #18 0x00007fff1e939da9 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #19 0x0000000000000000 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Thread 2 (Thread 0x7f5d9fbf7710 (LWP 3581)): Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #0 0x00007f5da7cbba4d in read () from /lib64/libpthread.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #1 0x00007f5da7589f9b in ?? () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #2 0x00007f5da75b2164 in ?? () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #3 0x00007f5da7cb3e11 in start_thread () from /lib64/libpthread.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: one () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Thread 1 (Thread 0x7f5da8872700 (LWP 3576)): Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #0 0x00007f5da7cbc59d in waitpid () from /lib64/libpthread.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #1 0x000000000041f11b in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #2 0x000000000041f1c7 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #3 <signal handler called> Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #5 0x00007f5da71fd135 in abort () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #6 0x00007f5da75af184 in g_assertion_message () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: 0x00007f5da75af730 in g_assertion_message_expr () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #8 0x000000000041af1c in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #9 0x00007f5da7588db2 in g_main_context_dispatch () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #10 0x00007f5da758cb98 in ?? () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #11 0x00007f5da758d0a5 in g_main_loop_run () from /lib64/libglib-2.0.so.0 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: ilable. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #12 0x00000000004072d5 in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #13 0x00007f5da71e6d2d in __libc_start_main () from /lib64/libc.so.6 Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #14 0x0000000000406f79 in dbus_message_append_args () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: bol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #15 0x00007fff1e939148 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #16 0x000000000000001c in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #17 0x0000000000000003 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #18 0x00007fff1e939da9 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: mbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #19 0x0000000000000000 in ?? () Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: No symbol table info available. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: A debugging session is active. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: #011Inferior 1 [process 3576] will be detached. Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: Quit anyway? (y or n) [answered Y; input not from terminal] Mar 30 15:15:07 dhcp-100-3-105 gdm[3649]: ******************* END ********************************** From http://git.gnome.org/browse/gdm/tree/daemon/gdm-display-access-file.c#n212 static gboolean _get_uid_and_gid_for_user (const char *username, uid_t *uid, gid_t *gid) { struct passwd *passwd_entry; g_assert (username != NULL); g_assert (uid != NULL); g_assert (gid != NULL); errno = 0; passwd_entry = getpwnam (username); if (passwd_entry == NULL) { return FALSE; } *uid = passwd_entry->pw_uid; *gid = passwd_entry->pw_gid; return TRUE; } The problem here is that if getpwnam(username) returns NULL, errno needs to be checked for EINTR. This indicates that a signal was received while waiting for the blocking call to return, and getpwnam() should be retried.
This is still a problem with Fedora 14. KDM works with SSSD.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping