This bug is 5 years old, and really, it should be a release-blocking bug.
How much more severe can a bug be than causing physical damage, bypassing security, corrupting the filesystem, and causing users to lose work?
It's difficult to believe that Canonical has a competent release manager if they're ignoring this for 5 years.
This bug is 5 years old, and really, it should be a release-blocking bug.
How much more severe can a bug be than causing physical damage, bypassing security, corrupting the filesystem, and causing users to lose work?
It's difficult to believe that Canonical has a competent release manager if they're ignoring this for 5 years.