Comment 24 for bug 1671611

Revision history for this message
Steve Gula (stevegula01) wrote :

I stand corrected... 4.4.0-63 was the first one in update manager to have this issue