In the logon process for individual users, is there any way to make the seahorse-agent start up later? I ask this because it seems that when AD users logon to my Hardy desktops that are joined to the domain, these users are getting kicked off right away because of "could not get password information for UID of current process" and "failed due to unknown user id" errors. The users logon okay, but the desktop gives a "your session only lasted 10 seconds" warning, shows the "UID" errors, and returns to the Ubuntu logon screen. According to the error log, these errors pertain to seahorse-agent.
At first I thought these errors were caused by improper AD authentication since they only happen to AD users (not local users). Now I'm thinking that seahorse-agent is starting up before the AD user has some other, primary local credentials and that some other process should be starting before seahorse. Any ideas?
Adv Reply
Bookmarks