Yes, it's fixed in 2.6.32-35.78. For whatever reason the buglinks were all changed to bug 843904 when the patches were reapplied, so the status didn't changed automatically.
Yes, it's fixed in 2.6.32-35.78. For whatever reason the buglinks were all changed to bug 843904 when the patches were reapplied, so the status didn't changed automatically.