2008-11-07 20:12:27 |
Jordan |
bug |
|
|
added bug |
2008-11-07 22:23:19 |
chadwik |
None: status |
New |
Incomplete |
|
2008-11-07 22:23:19 |
chadwik |
None: bugtargetdisplayname |
Ubuntu |
linux (Ubuntu) |
|
2008-11-07 22:23:19 |
chadwik |
None: bugtargetname |
ubuntu |
linux (Ubuntu) |
|
2008-11-07 22:23:19 |
chadwik |
None: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
2008-11-07 22:23:19 |
chadwik |
None: title |
Bug #295311 in Ubuntu: "Backlight brightness does not change on Gateway P-6317 laptop" |
Bug #295311 in linux (Ubuntu): "Backlight brightness does not change on Gateway P-6317 laptop" |
|
2008-11-08 15:25:19 |
Eagle Knight |
bug |
|
|
added attachment 'dmesg_lspciwnn.zip' (dmesg_lspciwnn.zip) |
2008-11-13 01:27:56 |
Jordan |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
2008-11-13 01:36:50 |
Jordan |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
2008-11-14 15:12:13 |
chadwik |
linux: status |
Incomplete |
Confirmed |
|
2008-11-14 15:12:13 |
chadwik |
linux: assignee |
|
ubuntu-kernel-team |
|
2008-11-14 15:12:13 |
chadwik |
linux: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
Jordan - Thanks for adding the logs, passing this on to the kernel team.
Eagle Knight - Please repost that info as a separate bug, be sure to include your make of laptop in the title. This may turn out to be caused by the same bug but best to make a separate report until we can be sure, thanks.
|
|
2009-03-05 09:03:46 |
brotherquintus |
bug |
|
|
added attachment 'lspci' (lspci) |
2011-07-14 03:39:31 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Won't Fix |
|