Comment 73 for bug 212098

Of course after so many steps, and logouts, I had to make some kind of confusion. Please disregard the part in my first comment about the intrusiveness of the UI - the share is *not* partly created with the 0ubuntu5 package, which is exactly what the bug report is about, duh.

Also, if it wasn't clear, in the above confirmation procedure, steps 1-4 are to confirm the bug, 5-9 to confirm that the fix works.

About the libpam part of the bug, since it suffices to enter the password for an administrative task, does this have to happen *after* the package is installed? I mean, can't the authentication needed for the package installation itself be somehow used for this?

I don't know pam deeply, bug even if it doesn't provide this kind of functionality, gksu should still be cached by the time the installation and configuration finishes, so another call for gksu should silently succeed, taking care of the password sync. Or am I missing something here?