Christopher, may I kindly suggest you speak for yourself? Furthermore,
where exactly is the CoC-violation in comment 26? You are throwing
around a bunch of stuff without merit, I'd say.
The link you gave says "Bugs which are not legitimate bugs are set to
Invalid. This can include bugs which failed to provide requested debug
information or bugs which are the result of user error." You are
requesting an ever increasing amount information that is by now simply
IMPOSSIBLE to provide. You are not seriously requesting for me to
contact the airport and ask them for what model of AP they deployed or
else you will not act on this ticket? What if they have more than one
AP, will I need to find out which particular brand I had connected to?
Last time I heard, it was that 802.11x was a standard. I think for now
it's safe to assume that the AP is following the standard. HKG is a
busy and well-maintained airport, I'm sure that if there was a genuine
problem with their setup, they would hear about it and fix it. But not
only that, you will not do anything unless I can prove this is a
regression? How am I supposed to know? It's the first time I ran into
this issue and I reported it the first time I came across it. Do you
want me to test every kernel that was ever released? I guess that's the
next step, hm?
You might not like to hear this but you are being ridiculous with your
requests. Is this the new kernel bug triaging team policy, to request
an ever increasing amount of information so that you can happily close
the ticket as invalid when it's not provided? I already provided a bunch
of unnecessary information and pointed out the violation of the
principle of "Datensparsamkeit".
I understand and agree that it would be nice to see if the problem does
occur in mainline as well, but at the moment it's impossible to verify
that. That doesn't make this ticket invalid. In fact, the link you
provided, explicitly states 'If a bug is in a Confirmed state but has
not yet tested the upstream mainline kernel, tag the bug "needs-
upstream-testing". If a bug has been tested with the upstream kernel,
move the bug to a "Triaged" state."' So, confirmed is the proper state
of this ticket, the tag is already there. I'm quoting officially
published rules, you seem to make up your own along the way, handing out
links that do not support or in fact often even contradict your
arguments.
I might go to HKG again next month or at the end of October or both. If
I do, I will be sure to test mainline. If there is any other tests you
expect, let me know ahead of time. I suggest you close this ticket as
invalid no earlier than in 120 days as seems to be kernel team
expiration policy for "information requested" bugs. I won't object to
setting this ticket to "incomplete" if that made you happier.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025638
Title:
frequent disconnects
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025638/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
