8.10 alpha uses a different method.
** Changed in: libpam-foreground (Ubuntu)
Status: Confirmed => Invalid
--
Unable to start g-v-m
https://bugs.launchpad.net/bugs/34063
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
Fixed in Feisty? That's good. Any chance of an Edgy backport?
I really can't move this machine to Feisty yet (because of possible
breakage).
--
Unable to start g-v-m
https://launchpad.net/bugs/34063
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Fixed in feisty (at least).
--
Unable to start g-v-m
https://launchpad.net/bugs/34063
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Bug 49666 has been marked a duplicate of this bug
--
Unable to start g-v-m
https://launchpad.net/bugs/34063
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Bug 47301 has been marked a duplicate of this bug
--
Unable to start g-v-m
https://launchpad.net/bugs/34063
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I should also mention that everything works great after adding the following to
/etc/pam.d/common-session:
session optionalpam_foreground.so
** Attachment added: "My pam.d directory"
http://librarian.launchpad.net/2555706/pam.d.tar.bz2
--
Unable to start g-v-m
https://launchpad.ne
This seems to bite quite many people. Maybe libpam-foreground could show
an update notification or a debconf note if the PAM configuration was
modified manually?
** Bug 41085 has been marked a duplicate of this bug
** Bug 43035 has been marked a duplicate of this bug
--
Unable to start g-v-m
ht
