Hi Michael, Ben,
On Wed, May 27, 2020 at 7:23 PM Michael Schwendt <mschwendt(a)gmail.com> wrote:
On Wed, 27 May 2020 12:07:35 -0400, Ben Cotton wrote:
> On Wed, May 27, 2020 at 4:30 AM Suvayu Ali wrote:
> >
> > Lately all my bug reports tend to go like this. Are others having the
> > same experience?
>
> I understand the frustration. My bugs get closed EOL, too. For what
> it's worth, 3633 bugs were closed EOL for Fedora 30. This is
> considerably lower than Fedora 29 (4958) and Fedora 28 (4681).
>
> The Fedora Join SIG is here to help new contributors get started if
> you're interested:
>
https://docs.fedoraproject.org/en-US/fedora-join/index.html
That process would not have helped with this kernel bugzilla ticket
opened in 2019-08-18. But the response in March 2020 suggested reproducing
the issue with Fedora 31 and reassigning the ticket, if the issue is still
reproducible. That has not been done.
The fundamental problem here is that it has taken a very long time for
somebody to respond to the bug reporter. There has been no guidance and
no hint whether anyone "somewhere" would be interested in looking into
this issue.
It took so long, that the bug report became irrelevant. I have since
moved to a different country, with a different job, and don't have
access to the original machine. In fact, as mentioned in the bug, I
could reproduce a similar issue in similar hardware, with Fedora 31.
The old hardware was Ryzen 5 2400G, and the second one was Ryzen 7 PRO
3700U (a mobile CPU with similar design, don't get confused with the
2xxx vs 3xxx naming). No response. Even more importantly, this
started as a regression bug that renders a system unbootable; my
understanding of Fedora and Linux kernel policy says that's very high
severity, and still I saw absolutely no response. Ironically, the bug
on 3700U got almost resolved by a very recent Fedora 32 kernel update
this month (that's 10 months, and 2 distro upgrades later). Given
the apathy, I had not bothered any more to file a bug report
specifically for the 3700U.
This is not the first time, I had purchased the 2400G within the first
month of its release back in Feb-Mar 2018. Understandably there were
issues (system unbootable to a desktop), even then, my bug reports did
not get a single response, me talking to myself, reporting back with
my experiments and attempted workarounds. With the release of a new
kernel series, about 2-3 months later, all issues were resolved. In
the least, I could have helped test any bleeding edge kernels. I have
been using Fedora for over a decade, have contributed to the
distribution in many different ways (packaging, testing, etc). This
is not a one off issue, I have had bugs open for many other packages,
all have faced the same fate. If I can't participate in the
community, when I'm competent, and willing, I will regrettably move,
despite loving the distro; most likely to Arch.
Cheers,
--
Suvayu
Open source is the future. It sets us free.