attach HW profiles to launchpad accounts and reference HW profiles in bug reports

Bug #3382 reported by Sitsofe Wheeler on 2005-10-19
44
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

It would be great if
#1 there were a tool on my Ubuntu desktop that enable me to collect all hardware information from my machine at once and then submit it to launchpad.
#2 there was a way to reference this hardware profile when reporting bugs.

It would make the lives of bug reporters easier as:
#1 Even unskilled people could collect the info.
#2 The info would only need to be collected once. So bug reporters would not have to repeat the same steps over and over again for each HW bug they report.

It would also make the lives of bug fixers easier as:
#1 Launchpad could enable them to query each bug report for affected hardware.
#2 There would be more such information available because it is not such a pain in the ass of the bug reporters anymore.

Please vote for this idea at: http://brainstorm.ubuntu.com/idea/1497/

The Process in more detail:
-----------------------------------
Step #1: Add a GUI driven software to the Ubuntu distro which enables
users to submit their hardware information to a central database.

Step #2: Allow the users to attach the DB IDs to their launchpad
profile (multiple if needed).

Step #3: Allow the user to select which of his machines are affected.

Step #4: Allow the bug fixers to retrieve a list of affected hardware
for a bug from launchpad. Like: give me all USB chipsets of machine IDs
attached to this bug.

How the feature could be used:
----------------------------------------
Take bug #88746 for example where the USB autosuspend feature breaks USB2.0 for some people, while at the same time removing autosuspend would break suspend/hibernate/resume for another crowd.

You could start a simple poll:
#1 Does disabling autosuspend fix your USB2.0 problem ? yes/no
#2 Does disabling autosuspend break your suspend/hibernate/resume? yes/no

If more than one HW profile is registered with your launchpad account
the following question shows up:
#3 Select the systems these answers apply to ? Choose form list.

And at the end you would know not just for how may people disabling
autosuspend works ... but also the exact chipsets that works for!

Brad Bollenbach (bradb) on 2005-11-23
Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Shirish Agarwal (shirishag75) wrote :

This is highly relevant, I hope this gets fixed soon with perhaps a tool or something (either hardinfo) or something else which is easy to upload. One solution could be to have an applet or something which uses something like lshw & puts it in categories.

Joey Stanford (joey) wrote :

2007-05-21: jjs - I hope I can have this scheduled later this year. It's not dead yet. :-)

Changed in malone:
assignee: bradb → nobody
Markus Kienast (elias1884) wrote :

I consider this an extremely valuable extension to launchpad. Imagine if everybody could easily attach his hardware profile to a bug.

Bug fixers could query for hardware similarities to find out which hardware components faulty systems have in common.
One could open a general "hibernation not working" bug and devs could as mentioned above track down, which hardware sucks the most.
They could track down, which of the faulty hardware is out there in the greatest numbers to concentrate their fixing work on that one.

The HW DB Client by the way should also query for whether hibernation and suspend are working, even though this might not be considered important. Maybe it is just not in there, because somebody is afraid of the results. But at least, people could access the DB before they buy a laptop and find out if these things work. How can I query the HW DB by the way?

Shirish Agarwal (shirishag75) wrote :

AFAIK the HW DB cannot be queried or looked into presently.

Markus Kienast (elias1884) wrote :

I think I read somewhere that Ubuntu is integrating some HW DB thingy from RedHat. This could provide the necessary information and should be linked with launchpad.

Markus Kienast (elias1884) wrote :

I find it is absolutely necessary to be able to attach hardware profiles to launchpad user accounts. I would then simply say, this happens on Feisty on my machine XY and the bugfixing guys could immediately access the right record in the HW DB. Now they have to over and over again request us to send lspci outputs, lshw outputs, ....

Isn't it the purpose of programming to relieve us from things that we have to do over and over again in exactly the same way? Isn't that what computers are for, to do exactly these stupid always the same operations?

Please use your voice as bug fixers, as the people most annoyed by this, to get canonical to implement such a feature in launchpad!

Markus Kienast (elias1884) wrote :

I have also filed this feature as a launchpad bug, as I have no idea where it really belongs: https://bugs.launchpad.net/launchpad/+bug/135542

Debian's reportbug command prepares a mail with a lot of useful information, given the name of the affected package or the affected executable. Launchpad should have some place where such info can be cut from some program's output (a customised version of reportbug would do perfectly) and pasted together with the bug report.

All this can only work if the reporter knows which is the executable or package affected.

description: updated

The Debian approach is good. For Debian guys, but not for my Mother though. It would find it best if users could report bugs from within the Ubuntu GUI environment they are used to. However it is hard to give users a gtk GUI for reporting bugs, since you would have to get all the functionality of the launchpad bug reporting section in there. Duplicated effort. Somehow defeats the purpose.

However, actually all they really need is to get a tool that helps them to submit their hardware info - ONCE - and create a launchpad account at the same time (if not previously created). Then they can be taken to launchpad by the "Report a Problem" magic, which actually should have its place in the System menu, not only in the applications Help section! They then, as described above can simply reference which Systems are affected by the bug they report. They would only need to click a checkbox. Not even that, if they only have one single HW profile attached to their account.

However it has to be possible to attach more than one HW profile to your account. I for example manage the machines of my parents and some friends as well. And I usually report their bugs. So I should have a checkbox choice for which System is affected.

Shirish Agarwal (shirishag75) wrote :

[quote] However it has to be possible to attach more than one HW profile to your account. I for example manage the machines of my parents and some friends as well. And I usually report their bugs. So I should have a checkbox choice for which System is affected.[/quote]

same here. I do the same :)

Sitsofe Wheeler (sitsofe) wrote :

Hmm. I see what elias is saying and I'm wondering if this is actually two related bugs (easy gathering tool / database of reports that can be referenced) rather than just one. I believe it should be possible to solve the first without solving the later at the cost of duplicated information in bug reports. The catch with this is that those people who take the time to report multiple issues are the ones who are punished the most until the database part is implemented...

On Thu, 2007-10-25 at 06:37 +0000, Sitsofe Wheeler wrote:
> Hmm. I see what elias is saying and I'm wondering if this is actually
> two related bugs (easy gathering tool / database of reports that can be
> referenced) rather than just one. I believe it should be possible to
> solve the first without solving the later at the cost of duplicated
> information in bug reports. The catch with this is that those people who
> take the time to report multiple issues are the ones who are punished
> the most until the database part is implemented...
>

Please add the bug numbers you are referring to.

elias:
I was thinking of the many bugs where I asked you for the same information you gave elsewhere (so anyone interested can rifle through your bug page).

Hendy Irawan (ceefour) wrote :

+1 for getting this released!!

description: updated
Markus Kienast (elias1884) wrote :

@ Sitsofe Wheeler
[quote] The catch with this is that those people who take the time to report multiple issues are the ones who are punished the most until the database part is implemented...

While actually the DB is already there, somehow, as is the info gathering tool. While I am not sure what exact info the HW DB tool is collection. Anyhow there is even some tool from RedHat I think to have read about some time ago.

But in the end, I would not worry as much about the gathering part as about the "being able to attach to launchpad profile, bug reports and polls" part (read about the poll part in the updated feature description on top). This is the part to concentrate on! The gathering part would already be served well enough, if I could attach one lshw output, one lspci, ... per System, still gathered by hand, to my profile.

The real benefit lies in the advanced possibilities a dev has to track down a bug and therefore a better working distro for me.

archdrone (archdrone) wrote :

+1
I think this feature will improve Ubuntu and give it a competitive advantage.

Alwin Garside (yogarine) wrote :

I really suggest someone writes a blueprint for this suggestion (https://blueprints.launchpad.net/malone/). (It's kinda out of place as a bug report, so there's little chance anyone will notice it here.)

Markus Kienast (elias1884) wrote :

Please vote for this idea at: http://brainstorm.ubuntu.com/idea/1497/

description: updated
Robert Collins (lifeless) wrote :

I'm updating this to reflect our updated bug triage - we don't use the medium category anymore: we pull bugs forward to high from low as our priorities change. This bug, while interesting, isn't in the current roadmap for active development.

Changed in launchpad:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers