Like many Ubuntu 17.04 users (if not all), I was affected by this bug from day 1:
The fix took a while to appear, but the developer managed to find it a few weeks ago. Even though this bug prevents many Ubuntu users from using their computer at all, the release is expected for June 5.
It's pretty obvious a high severity bug like this one should be top priority and released ASAP, it doesn't look like the ubuntu guys really care about people not being able to use their computers at all.
I wonder if this is the kind of quality we are going to get from Ubuntu from now on. The number of users that don't know how to debug and report this, must be huge. If I get frustrated by the way they handled it, even when I know what happened under the hood, I can't even imagine how many end users end up removing Ubuntu in frustration, and decide "Linux is not for them", due to bugs like this.
<rant mode off>
Yes, I already have a patched working kernel in my computers, but it would be nice to have an article about this.
The fix took a while to appear, but the developer managed to find it a few weeks ago. Even though this bug prevents many Ubuntu users from using their computer at all, the release is expected for June 5.
It's pretty obvious a high severity bug like this one should be top priority and released ASAP, it doesn't look like the ubuntu guys really care about people not being able to use their computers at all.
I wonder if this is the kind of quality we are going to get from Ubuntu from now on. The number of users that don't know how to debug and report this, must be huge. If I get frustrated by the way they handled it, even when I know what happened under the hood, I can't even imagine how many end users end up removing Ubuntu in frustration, and decide "Linux is not for them", due to bugs like this.
<rant mode off>
Yes, I already have a patched working kernel in my computers, but it would be nice to have an article about this.
Comment