Hibernation unreliable after security update

[nglnx]

Binary package hint: libnss3-1d

After today's security updates proposed by update-notifier, hibernation in my laptop, which worked flawlessly, started working unreliably (hanging the system or refusing to hibernate and returning to open session)

Thinking it could have something to do with the updates, I decided to revert the libnss3-1d update ( 3.12.0.3-0ubuntu5.8.10.1) to the previous version (3.12.0.3-0ubuntu5). Hibernation started working perfectly again!!. (Note: I tested hibernation multiple times, under multiple loads and use cases, to be extra sure it was working again)

I know this seems strange, since at first glance the package has nothing to do with hibernation, but I'm thinking that maybe this update causes some weird interaction with some other part of the system, which in turn interferes with hibernation (maybe network-manager?)

[Alexander Sack (asac)]

does networkmanager still work for you?

[Alexander Sack (asac)]

also does anything else not work for you? are you using evolution with ssl pop/imap/smtp ... testing would be great.

[Alexander Sack (asac)]

importance high as this is a regression candidate.

[nglnx (nglnx)]

Thanks Alexander for your prompt reply. This is so wierd I would never think of filing a bug like this between two so differently parts of the systems if it were not for fact that reverting this pacakge solved the problem. (Even more so being a security update)

Answering your questions: Yes Network Manager works (I connect to a wired network only, so I don't know if wireless protected networks work) and evolution with ssl pop/smtp works. I had already tested these after doing a apt-cache rdepends libnss3-1d to see which software as directly affected by this library. Hibernation worked without even a glitch since day one of Intrepid's release up until today.

I've been contributing for a long time, and I know that good bug reports need good information for others to reproduce the behavior. However, it has been difficult to pertinent information. I've scanned .xsession-errors, log files (messages, auth.log, kern.log and so on) and nothing.

Also, I hadn't made configuration changes to my system for some time before the update and was also carefull no to make changes after the update in order to better detect what caused this bug.

Sorry if i couldn't be more helpfull.

[Alexander Sack (asac)]

can you confirm that upgrading will make this problem come back? also remember to reboot to remove and eventual side effects. thanks!

[nglnx (nglnx)]

Yes, making the upgrade again causes the problem to return, even taking into account a reboot.

[Travis Whitaker (pi-boy-travis)]

Could you give us more information about your setup?

[nglnx (nglnx)]

No longer using Intrepid nor the computer where this manifested itself. Closing the bug report due to the lack of information and because nobody else seemed to be affected