Christopher M. Penalver, I still don't understand why this bug should be marked invalid.
Martin Gamwell Dawids, marking this bug Invalid is well within Ubuntu > Bug Control and Ubuntu Bug Squad triage procedures as noted in > > https://wiki.ubuntu.com/Bugs/Responses#Bugs_resolved_after_update_or_config_change > . > Following your link I read: *Occasionally bug reporters will indicate that a bug has been fixed after some software update or after changing a configuration value back to its default value. These bug reports should be set to 'Invalid' since we don't know the root cause. * As I have pointed out, updating my 10.04LTS system did *not* fix the bug. The bug still exist and I can reproduce it any day. But after spending several hours (20-30) doing kernel bisecting to do the community a favor and after having found exactly which kernel introduced the bug, I upgraded my system to a newer *main *version of Ubuntu namely 12.04LTS which uses a newer kernel by default and therefore does not have the problem. However, the problem still exists on 10.04LTS server and everybody installing this *still supported* version (10.04LTS server is supported until 2015-04) will have the problem described. As well, the Ubuntu Kernel team has made it clear they prefer a single, > separate report per user, per hardware combination, per problem. For more > on this, please see please see the Ubuntu Kernel team article: > > https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports > > the Ubuntu Bug Control team and Ubuntu Bug Squad team article: > > https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue > > and Ubuntu Community article: > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette Can you explain exactly what the problem is. This is exactly what my report is: a separate report per user, per hardware combination, per problem. This is reported by me (per user), reproduced on my hardware (per hardware combination) and there is one problem reporter (per problem). > As this bug is marked Invalid, if you have any further questions about > this you are welcome to contact me directly, or take this to a more > appropriate forum. > > Thank you for your understanding. > After spending many hours of doing exactly as you have asked me to do, debugging this problem and pinning down exactly when the problem was introduced I must admit that I feel like a complete fool when you then mark the bug as invalid because I am so kind to inform you that the bug is in 10.04LTS but not in 12.04LTS. Would you please reconsider your decision once more. After comment #18 the bug was marked Confirmed. In comment #19 I was so kind to inform you that this is a 10.04LTS bug only. After that you marked the bug Invalid even though the problem still exists in 10.04LTS and can be reproduced by me on my hardware. /Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066496 Title: fit-pc2 on Ubuntu 10.04 hangs/freezes after high network load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
