Comment 13 for bug 1450770

hackel (hackel) wrote :

Um, I came here specifically because I just experienced this error with nginx 1.8.1-1+trusty0. How about we wait for confirmation before changing things?