I'm actually happier with "Won't Fix" than "Invalid". I'd be even more happy with "Wishlist".
I suppose what I want has become a feature request, but it also used to be the default behavior of apport. In my opinion, "Report the problem..." should not just +1 a statistic, especially in the case that no bug report exists. It's also vague language and should be revised to make it more clear what users should expect. ie. "Report the problem for statistics" and "Report the problem on Launchpad" to distinguish the two completely different meanings of this phrase. Here's how I imagine a better apport: 1. Apport catches a bug. 2. Apport asks the user if they want to report the problem and / or restart the program. 3. If the user would like to report the problem, apport attempts to collect all relevant data and checks launchpad for existing bug reports. 4A. If apport finds any conditions that may restrict the validity of the report (out of date packages, unusual configurations, packages from outside ubuntu's repositories, etc) it informs the user that it will not be able to file a valid report, but can provide instructions on how to prepare the system to file a valid report and how to restart from this point later, and also that the user can be shown search results from launchpad about possibly relevant bugs based on information collected so far if they like. 4B. If apport finds exactly the same issue in another bug report, it informs the user that the issue has already been reported and the user can be added to and shown the bug report on launchpad if they like. 4C. If apport finds no restricting conditions or previous reports of exactly this bug, apport will ask the user if they'd like to create a new bug report. 5. If the user would like to create a new bug report, then apport will take them to launchpad to go through the steps. 6. Finally, if the user had chosen to report the problem, whatever happened from that point on, apport should display a "Thank you for your time" and recap message, telling the user breifly what has happened to their report before closing (on a 30 second timer with a [close] button would be acceptable). My reason for this way of thinking is this: I want to know someone is actually working on my issue. If it's just sending statisticsto a database, and not telling me, without at least showing me an active bug report relevant to my issue, how am I supposed to belive that the problem will ever be solved? Of course the old open-source maxim is to fix it yourself, and at times that's exactly what I've done, but that isn't the way to fix bug 1. Ubuntu needs to send the message that bugs will be handled with good communication and accessible developers - two things that open source software can uniquely provide. I understand that not every developer can be called to account for every issue in every software package available for linux, but apport could go a long way toward making the face of linux "customer service" look better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036965 Title: Apport reports to errors.ubuntu.com, not Launchpad bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1036965/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
