Well, /usr/lib/pm-utils/power.d/laptop-tools currently only sets settings in /proc/sys/vm, not the hdparm settings. Those settings will stick across a suspend, so there's really no bug there currently.
It may be that the hdparm calls should be moved from power.sh into pm-utils/power.d/laptop-tools, in which case the problem is transferred over there; now that script has to run after suspend and not just after a power change (which it didn't before).
Again, I have no opinion on where the solution should ultimately lie. I'm hoping the experts on the ins-and-outs of these scripts will be able to choose where the best fix should go (and reassign the bug to a different project if necessary).
Well, /usr/lib/ pm-utils/ power.d/ laptop- tools currently only sets settings in /proc/sys/vm, not the hdparm settings. Those settings will stick across a suspend, so there's really no bug there currently.
It may be that the hdparm calls should be moved from power.sh into pm-utils/ power.d/ laptop- tools, in which case the problem is transferred over there; now that script has to run after suspend and not just after a power change (which it didn't before).
Again, I have no opinion on where the solution should ultimately lie. I'm hoping the experts on the ins-and-outs of these scripts will be able to choose where the best fix should go (and reassign the bug to a different project if necessary).