Comment 27 for bug 1025638

Revision history for this message
penalvch (penalvch) wrote : Re: 168c:002c frequent disconnects

Rolf Leggewie, I PM'ed you but received no response.

Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025638/comments/25 , that is Brad Figg's bot marking it Confirmed because the apport-collect information was provided.

Regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1025638/comments/26 , nobody appreciates your negative, incorrect presumptions. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind.

Regarding the technical merits of this report, the current outstanding minimum requirements of this report are:
+ Is this a regression?
+ Does this problem occur in mainline?
+ Does this occur with other wireless access points?
+ Does the access point in Hong Kong have some firmware bug or access policy that does not permit Ubuntu/Linux clients?
+ What is the manufacturer and model of the access point?

So, unless you can provide all the information mentioned above, and previously requested, unfortunately, this report is, at best, frivolous.

I empathize that it sucks when you get into situations where you expect things to work, and they do not. But, if one cannot see through a bug to it's conclusion by providing minimum requirement information for a developer to work on it, expecting a miracle and not getting it is no reason to keep a report open, nor be rude.

This report is being closed within policy of both the Ubuntu Kernel Team and Ubuntu Bug Control as per https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Invalid . If you have any further questions about this, please feel free to E-Mail me directly and we can discuss further.

If you can provide the minimum requirements, please reopen the report with this information, and we can work together on getting this fixed asap.

Thank you for your understanding.