Add Bug Solution box (metadata) to contain what the user must do

Bug #1509453 reported by André Pirard
This bug report is a duplicate of:  Bug #54652: Add a "fix or workaround" field to bug. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

I am one of the victims of the bug I commented here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082215/comments/36

Please read that bug report and my comment.
The following recommendations belong to "Launchpad itself" for Ubuntu.

For the sake of Ubuntu, may I once again recommend:

- to add keywords of the bug description to indicate the affected versions (starting kernel X, fixed in Y)
- to mark as important such things as data destruction, to tick "affects you" (and allow anyone?)
- in addition to "Bug description", to create a "Bug correction" in which any Ubuntu user can find in words he understands how to correct or circumvent his problem in the system version he is using.
No "fixed", "patch released" or "upgrade" please.
- in case the problem occurs with a particular hardware, to insistingly ask the manufacturers to indicate in their specifications "Supported OS: Linux kernel ≥ X or Ubuntu ≥ Y".

It would have saved me days used to run tests, to find out the reason and the correction.
And most of all, it would have saved my neighbour's disk !!!

Revision history for this message
Colin Watson (cjwatson) wrote : Re: Better metadata for data-loss bugs

In general, almost all of this is out of scope for Launchpad itself.

 * We did look into adding explicit database-modelled version information to bug tasks very early on in the design, but it was ruled excessively complicated and it's unlikely that we'll add it at this point.
 * While I certainly agree that data destruction is important, determining this and managing bug importances is up to the maintainers of the project/package in question.
 * Some bugs have workarounds, but many don't, and can only be addressed by upgrading or similar - no matter how much we might wish it to be otherwise. Project maintainers can and do edit bug descriptions to add workaround information at times, which I think is wiser than adding a new "correction" field. We don't have to have explicit fields for every possibility, and adding that would become unmanageable; Launchpad's bug tracking system is already complex.
 * Dealing with manufacturers is clearly not something that Launchpad (as a hosting site) can do.

summary: - Make Launchpad useful for Ubuntu users
+ Better metadata for data-loss bugs
Revision history for this message
André Pirard (a.pirard) wrote :

I'm afraid that, although it's presented as an extreme case, data loss is not the subject of this ticket.
In short, the subject is that there should be a place where to write what the user must do to solve any problem.
Without updating the whole system and getting other problems.
In that bug's case:

This bug was fixed in Kernel 3.8.1.
Use System>Administration>Synaptic and install that kernel or later
linux-image-3.8.1-??-generic
linux-headers-3.8.1-??-generic
reboot and make sure this kernel is running
Failing a "solution" box, I added that text to "Bug Description".
What beats everything is that someone removed it.

Saying that the user shouldn't know is bad Ubuntu advertising.
Saying that he just should update is a bad advice.
It's what I did just with the latest kernel and I got nasty problems.
Fortunately, one can downgrade the kernel and it saved my Ubuntu.
Should I have updated all Ubuntu, I would have had 10 problems.
Just my last Firefox update created 5 problems keeping me busy for 3 weeks.
And that's because Ubuntu does not keep old versions in the depots.

summary: - Better metadata for data-loss bugs
+ Add Bug Solution box (metadata) to contain what the user must do
Revision history for this message
André Pirard (a.pirard) wrote :

This bug report relates to both fixes and workarounds and hence cannot be a duplicate of: Bug #54652: Add a "workaround" field to bug" that only covers workarounds. Unless that bug extends its descriptions to fixes too, of course.

Revision history for this message
William Grant (wgrant) wrote :

There is no material difference.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.