Comment 128 for bug 1651635

On 11/02/17 11:07, Kai-Heng Feng wrote:
>> On 2 Nov 2017, at 5:40 PM, Paul Menzel <email address hidden> wrote:
>>
>> @kaihengfeng, I am quite surprised and even angry about your comment.
> My apology.

No problem. Maybe I also have to apologize for my response directed at you.

>> 1. How do you know it’s a Linux kernel issue?
> I don’t. But it’s better to get input from upstream maintainer.

Thank you for creating that issue. I subscribed myself to it.

>> Even if it were, the shipped Linux kernel with Ubuntu 16.04 is far too old, and Linux upstream doesn’t care about old Linux kernel.
> It also happens on upstream Linux kernel.

Fair enough. Unfortunately, some of the early reporters didn’t report back.

>> 2. We bought the system from Dell with Ubuntu. As far as I know, they contract Canonical to do the port. That’s the company you work for.
> That’s correct.
>
>> 3. So why do you ask the reporters, which wasted too much time already experiencing this bug, to report it, and to test your suggestions to open a bug report upstream. If this is the next step, I kindly ask *you* or some of your colleagues at Canonical to do that.
> Well, I help public issues when I have spare time, this one included. I personally also invested some time trying to reproduce the bug.

Thank you for clearing that up, and thank you for doing this in your
spare time. But, that’s not how it should be. When I bought this laptop,
I thought a certain amount of that price goes to “Dell’s GNU/Linux team”
and Canonical, so that people are paid to look into issues. I’d love to
hear more about the relationship between Dell and Canonical, and what
the support includes.

With Dell it’s hard enough to deal with their support, which always
responds that they cannot really help, when GNU/Linux (Ubuntu) is used.

> Anyway, I’ll file an upstream bug then.

Thank you gain.