Comment 15 for bug 732174

Christopher,

Marking this bug as invalid is wrong. This bug report has multiple people adding comments confirming that the problem exists. You also have someone as recently as 7 hours ago confirming that the problem exists in the latest release. There's absolutely no reason to close this bug and make others jump through more hoops for the exact same problem. This is especially true considering how long this bug has been open with no actual developer attention yet. This bug was reported over 1 year and 3 months ago. And even though it's very old, not one developer attempted to fix it. Are you implying that a newer bug report of the exact same issue will somehow get more attention than this one?

Closing this bug and forcing others with the exact same problem to open a new one makes it seem like you're just going to keep up the same routine; ignore the bug for long enough until most people give up, then close it out as invalid. This bug is not invalid. It is very valid, and confirmed as still existing in the latest release.

If you need someone to post some details about the bug against the current release, it looks as if Bogdan is the best person for that. Bogdan, can you help by executing the following from your terminal:

ubuntu-bug linux

Thanks,
Tim