I'm running FC10 on a laptop and have gone the whole hog and log in using pam_winbind. i.e the laptop is an Win2K3 Active Directory member, and I login using a winbind-created account instead of a true "local" one.
Anyway, a couple of times (since I installed last week) I've found myself unable to unlock the screensaver - syslog showed
Dec 4 15:47:56 tnz-jhaar-dell gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): request failed: No trusted SAM account, PAM error was System error (4), NT error was NT_STATUS_NO_TRUST_SAM_ACCOUNT
Sure enough, logging in as root (as I couldn't login as myself) and running "wbinfo -t" showed it had lost it's trust.
Restarting winbind fixes the problem.
I'd guess the "off again on again" nature of my laptop's network connection is tickling some bug you don't normally see on a server - which has a more stable, permanent network connection.
If anyone picks this bugreport up, I'm happy to turn on debugging,etc to help track it down. I'm sure I'm going to be seeing this quite routinely from now on, as I so pleased I can use a laptop like a Windows user (gasp!) that I'm not giving up on it ;-)
sorry that nobody picked this up. I guess you are not running hat setup anymore and can't say if this is still an issue these days?
This was opened in 2008 - yeah I think it's safe to close. At some stage in the past 10 years this problem has disappeared for me