This is ridiculous. I finally upgraded to 10.4 LTS, and this bug is still there! How can a well-known bug with a well-known solution that have both been known for several release cycles make it into an LTS release???
This is ridiculous. I finally upgraded to 10.4 LTS, and this bug is still there! How can a well-known bug with a well-known solution that have both been known for several release cycles make it into an LTS release???