Comment 3 for bug 287462

I just did. No improvement. I think that the main difference with the duplicate bug is that no device has been removed or inserted, in my case, so there's no new device to match to a driver or preference, since the exact same device is there after operation is resumed from sleep/hibernate. Perhaps the real trick would be to make g-s-d aware of when *it* has been resumed, so that it rescans all hardware upon being restored? Or have I misunderstood and this is that what this patch is already supposed to do?