On Mon, Feb 15, 2010 at 07:52:20PM -0000, hexion wrote: > Wow, I'm nobody to teach anyone lessons but... ok, let's analyze this > closure you just did:
Marking a bug as a duplicate is not closing it. > - You didn't wait for the user that reported the issue to confirm whether > adding 'splash' solves the problem. If vmc reports that this bug is not fixed by adding 'splash', the duplicate status can be revisited. > - You didn't even ask the rest of the people (that have confirmed the > issue) if they have that option disabled too. Yes, because if others are experiencing hangs with a different configuration, then that's a different bug. It is extremely counterproductive to use a single bug report to track multiple, possibly unrelated bugs in a single bug report. If the other people who have confirmed this bug are also booting without 'splash' and find that booting with 'splash' fixes their hang, then I'm happy for them, and am happy to say that their bug will probably be fixed soon. If not, then they should file separate bug reports anyway, because their feedback won't help fix the bug vmc reported, and work on fixing this bug won't help them. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- Plymouth AND Automatic Login enabled system freezes https://bugs.launchpad.net/bugs/521175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
