Ticket #1170 (closed defect: fixed)
lightdm should wait for AFS to come up
Reported by: | jdreed | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | Current Semester |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | debathena-lightdm-config 1.9 | |
Upstream bug: | LP:483506 |
Description
In the Upstart world, it's possible for the greeter to come up before AFS is ready. In a pinch, our greeter can refuse to do anything until AFS comes up if an AFS user is logging in. In reality, there's probably a better way to do this. Perhaps it involves upstart-ifying AFS?
Change History
comment:3 Changed 12 years ago by jdreed
The LP bug suggests changing lightdm's upstart job to add and stopped rc RUNLEVEL=[2345] to the start on conditional, which will wait until all sysV init scripts have finished starting. It notes that this slows down boot, I don't think we care.
comment:4 Changed 12 years ago by jdreed
Something is wacky here, because this should have set DEBATHENA_HOME_TYPE to missing, and I should have gotten the error. WTF?
comment:5 Changed 12 years ago by jdreed
- Fixed in version set to debathena-lightdm-config 1.7
Ah, lightdm itself is trying to access the user's homedir and failing. We could also try and catch this in the session setup scripts, but "meh".
It's also possible that pam_debathena_hometype should fail under some cases and we can let PAM take care of this?