I no longer can test this bug. The computer doesn't function any more. BR, Jason
On Tue, Aug 13, 2013 at 1:37 PM, Christopher M. Penalver < [email protected]> wrote: > encompass, 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 images are available from http://cdimage.ubuntu.com > /daily-live/current/ . > > 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: > > apport-collect -p linux <replace-with-bug-number> > > 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 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: > kernel-fixed-upstream > kernel-fixed-upstream-VERSION-NUMBER > > where VERSION-NUMBER is the version number of the kernel you tested. For > example: > kernel-fixed-upstream-v3.11-rc5 > > 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: > needs-upstream-testing > > If the mainline kernel does not fix this bug, please add the following > tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-VERSION-NUMBER > > As well, please remove the tag: > needs-upstream-testing > > 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: > kernel-unable-to-test-upstream > kernel-unable-to-test-upstream-VERSION-NUMBER > > Once testing of the upstream kernel is complete, please mark this bug's > Status as Confirmed. Please let us know your results. Thank you for your > understanding. > > ** Tags removed: bluetooth led > ** Tags added: needs-kernel-logs needs-upstream-testing > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/182101 > > Title: > Bluetooth light comes on but I don't think I have blue tooth. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182101/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/182101 Title: Bluetooth light comes on but I don't think I have blue tooth. Status in “linux” package in Ubuntu: Incomplete Bug description: When I boot up the system for the first time ever I have seen the bluetooth light has turned on. Now this wouldn't bother me, except I don't think I have bluetooth. :/ Interesting bug, but I think it would be important to make sure I do or don't. I would love to found out how to test something like that. ;) I have found that the light is not on after coming from some hibernations. For example now. It also does the beep telling me the there was something wrong while I came out of hibernation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
