Not to worry, for some reason it has chosen not to provide the information, we will have to collect the info ourselves which will require a little work on your behalf I'm afraid.
If you could open the terminal again and run the following commands, separately and by pressing enter after each one.
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).
The if you go to "Places" > "Home folder" at the top of your screen you should find the four .log files from above in there.
You need to go back to the bug report on launchpad and attach these files to the bug report. You can do this by clicking on the text "add attachment or patch" which is located at the bottom of the screen below the add comment box. Thank you.
@Andreas Bulling
Not to worry, for some reason it has chosen not to provide the information, we will have to collect the info ourselves which will require a little work on your behalf I'm afraid.
If you could open the terminal again and run the following commands, separately and by pressing enter after each one.
1) uname -a > uname-a.log signature > version.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).
The if you go to "Places" > "Home folder" at the top of your screen you should find the four .log files from above in there.
You need to go back to the bug report on launchpad and attach these files to the bug report. You can do this by clicking on the text "add attachment or patch" which is located at the bottom of the screen below the add comment box. Thank you.