Comment 22 for bug 498980

I was having the exact same issue described here, but my solution was not quite the same so I thought I would add my comments.

After upgrading to 9.10 my suspend stopped working. Looking in the logs pointed the finger at Pulse Audio and removing the pulseaudio package fixed the problem as others noted. I finally decided to look for a proper fix and found this thread, which described my exact setup and issue (encrypted home directory, pusleaudio failing on suspend).

I confirmed that I had the same issue of sudo getting a Segmentation Fault when it was executed in the /usr/lib/pm-utils/sleep.d/01PulseAudio file, exactly as described above. I saw the confirmed fix of changing the /etc/sudoers file and thought 'Great, this should fix my problem.' However, my sudoers file had not been altered at all so no luck.

I went back to the comments about /etc/pam.d/common-*' and removing the line @include common-pammount' which was thought to be a red herring. I commented out the include line in the file /etc/pam.d/common-auth and tested sudo again and it worked! I confirmed that the sudo lines from 01PusleAudio will Seg Fault when this line is included and work when it is not. (sudo -H -u \#$i pacmd) i.e. when root tries to sudo to me. Suspend worked fine after that.

So, to summarize my fix: Comment out the line '@include common-parmmount' from the file /etc/pam.d/common-auth.

I know Pulse Audio has already been changed to use su instead of sudo, but there are two questions that still seem to remain: 1. Why does sudo seg fault at all when I assume it did not in the previous version of Ubuntu (my suspend worked fine before the upgrade)? 2. Should these include lines be removed since they seem to no longer be needed and actually do cause errors. Patching Pulse Audio might just gloss over the problem until is shows up somewhere else.