Look, obviously you can't solve all bugs in a single ticket, or you'd never get anything done.
However, if you've got more than a hundred people who will still have a problem after a bug is closed, that means there needs to be a new bug created for it, *by the maintainers*! Otherwise you're doing the digital equivalent of sweeping the problem under the rug. This is how it works on every other ticket system. No one else closes a bug and says "hey 100+ users whose problem is not actually fixed ... your problem is fixed! And as a result no other fixes ... like the kind that might actually fix your problem ... will be coming." You can't just screw over 100+ *reporters* (and who knows how many other affected people) by guaranteeing they'll never get a fix, or at best by delaying their fix while you wait for someone to file a new ticket, all so that you can get one more "fixed bug" on your belt notch. You clearly understand the issue, you know the technical details, and you can create a new ticket in all of two minutes. Doing so would get the ball rolling on an actual fix for those 100+ users, instead of throwing them under the bus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs