Responses
Differences between revisions 22 and 115 (spanning 93 versions)
|
Size: 10121
Comment: Due to LP bug 815419: 1) Reworded needs-upstream-testing tag so not removed when kernel-unable-to-test-upstream. 2) The pencil is not yellow. The circle is yellow, the pencil is black.
|
Size: 1600
Comment: Emphasize latest: the upstream > the latest upstream
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| <<TableOfContents>> | = Please Test Latest Upstream = |
| Line 5: | Line 5: |
| == Please Test Latest Development == ||<tablestyle="background-color: #eee"> Could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number> <<BR>><<BR>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested. For example: <<BR>> kernel-fixed-upstream-v3.7-rc1-quantal <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: <<BR>> kernel-unable-to-test-upstream <<BR>> kernel-unable-to-test-upstream-VERSION-NUMBER <<BR>> <<BR>> Please let us know your results. Thank you for your understanding. || == Please Test Latest Upstream == ||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested. For example: <<BR>> kernel-fixed-upstream-v3.7-rc1-quantal <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: <<BR>> kernel-unable-to-test-upstream <<BR>> kernel-unable-to-test-upstream-VERSION-NUMBER <<BR>> <<BR>> Please let us know your results. Thank you for your understanding. || == Old With No Activity == ||<tablestyle="background-color: #eee">This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .<<BR>><<BR>> If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number> <<BR>><<BR>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested. For example: <<BR>> kernel-fixed-upstream-v3.7-rc1-quantal <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: <<BR>> kernel-unable-to-test-upstream <<BR>> kernel-unable-to-test-upstream-VERSION-NUMBER <<BR>> <<BR>> Please let us know your results. Thank you for your understanding. || == Suspend == ||<tablestyle="background-color: #eee"> Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number> <<BR>><<BR>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested. For example: <<BR>> kernel-fixed-upstream-v3.7-rc1-quantal <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: <<BR>> kernel-unable-to-test-upstream <<BR>> kernel-unable-to-test-upstream-VERSION-NUMBER <<BR>> <<BR>> Please let us know your results. Thank you for your understanding. || == Hibernate == ||<tablestyle="background-color: #eee"> Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, could you please confirm this issue exists with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ . Please note that one will need to install Ubuntu to test hibernate, as at this time, hibernate does not work in a live environment. If the issue remains, could you please run the following command from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:<<BR>><<BR>> apport-collect -p linux <replace-with-bug-number> <<BR>><<BR>> Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-VERSION-NUMBER <<BR>> <<BR>> where VERSION-NUMBER is the version number of the kernel you tested. For example: <<BR>> kernel-fixed-upstream-v3.7-rc1-quantal <<BR>><<BR>> This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-VERSION-NUMBER <<BR>> <<BR>> As well, please remove the tag: <<BR>> needs-upstream-testing <<BR>> <<BR>> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: <<BR>> kernel-unable-to-test-upstream <<BR>> kernel-unable-to-test-upstream-VERSION-NUMBER <<BR>> <<BR>> Please let us know your results. Thank you for your understanding. || |
||<tablestyle="background-color: #eee"> Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue. <<BR>><<BR>> If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: <<BR>> kernel-fixed-upstream <<BR>> kernel-fixed-upstream-X.Y-rcZ <<BR>> <<BR>> Where X, Y, and Z are numbers corresponding to the kernel version. <<BR>> <<BR>> If the mainline kernel does not fix this bug, please add the following tags: <<BR>> kernel-bug-exists-upstream <<BR>> kernel-bug-exists-upstream-X.Y-rcZ <<BR>> <<BR>> Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. <<BR>> <<BR>> Once testing of the latest upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. <<BR>><<BR>> Thank you for your understanding. || |
Please Test Latest Upstream
Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue. |
Kernel/BugTriage/Responses (last edited 2019-11-04 15:31:40 by penalvch)