Re: Testing requests: blocker bug confirmations

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 26, 2017 at 8:46 AM, Peter Gueckel <pgueckel@xxxxxxxxx> wrote:
> Is working WiFi going to be a requirement for Fedora 26?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1435793
>
> I sure hope so. This morning's kernel has done nothing.
>

If a significant minority were having this problem, I imagine it'd be
a blocker. But I'm not having this problem with any 4.10 kernel on two
totally different laptops with different wireless makes. And I haven't
heard of anyone else having this problem.

First step is to see if anyone has filed a bug upstream against the
same wireless hardware you have. And then you can track that.

If there isn't an upstream bug yet, the unfortunate reality is that
you'll have to file one if you want to get it fixed. Upstream is
pretty good about responding to regressions like this so long as you
narrow it down to a specific kernel version where the regression first
happened; and they're even more responsive when you do a bisect to
narrow down the commit that's likely to blame (probably because a
specific commit puts the regression blame on a specific person, haha).

Anyway, somebody has to do it. If no one does it, it likely won't get
fixed on its own. Also for Fedora 26, we're on 4.11rc8 so you could
just test that and see if the regression is already fixed.


-- 
Chris Murphy
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux