The maintainers are for the most part about "packaging" kernels. They rarely seem to ever work on kernel bugs, nor have the time to do such investigate even if they have the time. They are not here to answer you questions, and they are overworked. If someone is paying them, whoever that is, is setting their priorities and their priorities are not to do their job. If they aren't paid well then if they help some ok, but no one is owed a response. Looking at your above bug you filed that went well, and the comments, the above bug was duplicated by a number of people and that moves its priority up in the stack. It was also trivial to duplicate and did not required any special hardware and/or setup. it is a likely easy to fix bug. They like easy bugs. Any bug that looks hard and/or are not duplicated by others are going to get a pass and that is the simply the way it works. For the most part you must help yourself. If the bug is in any way complicated the goal of the support analyst is not to help you but to make you go away (and this is when you have a contract with a company and are paying big money). Without your paying they don't have any reason to waste your time by replying and asking you endless questions on something they have no idea about. The only SLA they seem to have is to find all of bz on EOL products and respond and close them. The rest of the community will help you when they have time, they do not owe you anything, and be happy that sometimes someone is willing to help you. And don't bitch about not getting a response, there is no requirement that anyone responds to any post you make, you are owed nothing. The fact that you seem to think you deserve a response would seem to indicate a lack of understanding of a "community". The comments on this thread about how to fix the issues by removing packages from being maintained seems that many just don't get that and they think they are owed something. You can argue that reality of how the community works should be different, but at the end of the day that would not be a community with each member having their own self-interests that sometimes allow them to help you. On Fri, May 29, 2020 at 6:41 PM Suvayu Ali <fatkasuvayu+linux@xxxxxxxxx> wrote: > > On Fri, May 29, 2020 at 6:57 PM Roger Heflin <rogerheflin@xxxxxxxxx> wrote: > > > > I don't believe the kernel.org developers work out of the fedora > > bugzilla (or any distro's bugzilla), so no one who knows anything is > > likely to find and/or see the bug. > > > > To get a kernel developer you would need to at least post a summary to > > the kernel subsystem list if you know which subsystem or the main > > kernel if you don't. > > > > And the kernel.org guys do not care about any testing done on a fedora > > delivered kernel as they don't know what code is in it, so you would > > need to install a kernel.org kernel and bot from it and verify you > > have the issue on the newest released one. > > I wish people read the thread or even posts carefully before > responding. I'm well aware that kernel developers are not watching > the Redhat BZ, but the maintainers are. > > Anyway, here's an example of a healthy exchange on BZ: > > - I reported this bug on Tuesday: > https://bugzilla.redhat.com/show_bug.cgi?id=1840432 > - There was some discussion > - Today it got marked as a duplicate of this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1840780 > - The maintainer had commented on the second bug on Wednesday that he > is too busy, and unlikely to find time to investigate > - On Thursday another person dug through the upstream repo, found the > commit that fixes the issue, determined that simply updating to the > latest version from upstream would fix the crash, and as a bonus > pointed to the underlying reason that caused the crash. > - Earlier today the maintainer did a scratch build of the latest > release, and asked for testing > - I happened to be online, after testing I responded that the build works > - Quite likely there will be a new release next week that pushes out the update. > > -- > Suvayu > > Open source is the future. It sets us free. > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
