On 04/10/2015 03:13 PM, KennoVO wrote:
> As long as the current LTS (i.e. 331) drivers are not fixed, I think it
> is wrong to set the status for nvidia-drivers-ubuntu to "Fix Released".
> Can someone with the necessary permissions please undo the status change
> by royalsabz (mehrshad-5843) ? And set the importance to "High", while
> you're at it? This is a really important high-impact bug that should be
> as high as possible on the agenda until it's completely fixed for all
> currently supported releases. In this light, the apparent casual lack of
> attention from Canonical's side is beyond my comprehension. I can only
> speculate they're too busy making Vivid attractive enough to lure in new
> users, and are forgetting about keeping long-time users.
>
> To the people who think that's the right thing to do: please try to
> weigh the potential harm caused by delaying Vivid a day or so against
> the actual harm of having thousands of long-time users' desktops
> breaking en masse because of running seemingly-innocuous kernel
> updates...
>
Bump.
On 04/10/2015 03:13 PM, KennoVO wrote: drivers- ubuntu to "Fix Released".
> As long as the current LTS (i.e. 331) drivers are not fixed, I think it
> is wrong to set the status for nvidia-
> Can someone with the necessary permissions please undo the status change
> by royalsabz (mehrshad-5843) ? And set the importance to "High", while
> you're at it? This is a really important high-impact bug that should be
> as high as possible on the agenda until it's completely fixed for all
> currently supported releases. In this light, the apparent casual lack of
> attention from Canonical's side is beyond my comprehension. I can only
> speculate they're too busy making Vivid attractive enough to lure in new
> users, and are forgetting about keeping long-time users.
>
> To the people who think that's the right thing to do: please try to
> weigh the potential harm caused by delaying Vivid a day or so against
> the actual harm of having thousands of long-time users' desktops
> breaking en masse because of running seemingly-innocuous kernel
> updates...
>