Hide Forgot
Description of problem: Only user that is able to login to Fedora 16 is root user. Version-Release number of selected component (if applicable): gdm-3.1.92-1.fc16.x86_64 How reproducible: Every login Steps to Reproduce: 1. 2. 3. Actual results: Get the icon something has gone wrong with the login and must logout. Expected results: Additional info: User home directories are auto mounted and login information is NIS served. Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 2 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=4 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 4 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=7 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 7 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=8 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 8 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=1 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 1 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=11 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 11 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=6 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 6 signals Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=10 0x4055b0 Oct 1 08:52:26 redwood gdm-password][2040]: DEBUG(+): GdmSignalHandler: Registe ring for 10 signals Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserMa nager: Seat loading sequence complete, so trying to set loaded property Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserMa nager: Seat still actively loading, so not setting loaded property Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserMa nager: calling 'ListCachedUsers' Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: ListCachedUsers finished, will set loaded property after list is fully loaded Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: tracking new user with object path /org/freedesktop/Accounts/User1000 Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: user 'dhighley' is now loaded Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: tracking user 'dhighley' Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: not yet loaded, so not emitting user-added signal Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: no pending users, trying to set loaded property Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: Seat still actively loading, so not setting loaded property Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): Failed to identify the current session: Unable to lookup session information for process '2040' Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: seat unloaded, so trying to set loaded property Oct 1 08:52:26 redwood gdm-password][2040]: AccountsService-DEBUG(+): ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property Oct 1 08:52:26 redwood dbus-daemon[994]: Launching FprintObject Oct 1 08:52:26 redwood dbus[994]: [system] Successfully activated service 'net.reactivated.Fprint'
We believe that this is no longer an issue in the fedora 16 beta release. May have been fixed by finding and fixing an selinux avc issue. module mysystem 1.0; require { type nfs_t; type system_dbusd_t; class file read; } #============= system_dbusd_t ============== allow system_dbusd_t nfs_t:file read;