kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #93560
[Bug 395753] Re: Bluetooth and WLAN enabled after resume
Friedrich Graeter, thank you for reporting this bug to Ubuntu. Jaunty reached EOL on October 23, 2010.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases
Is this reproducible in the latest release of Ubuntu via
http://cdimage.ubuntu.com/daily-live/current/ ?
If so, please execute the following via a terminal in order for the necessary debugging information to be attached:
apport-collect 395753
** Package changed: pm-utils (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/395753
Title:
Bluetooth and WLAN enabled after resume
Status in linux package in Ubuntu:
Incomplete
Bug description:
If I had disabled Bluetooth or WLAN on my notebook and make
suspend-2-ram and resume again, they got re-activated.
This is a bad behavior for various reasons:
1. Network manager got confused, because it still thinks, that WLAN is
inactive - but the WLAN LED is online.
2. I have to disable BT / WLAN again. I don't want to do this over and
over. Often, I suspend my computer only for some minutes, just to
bring in from one place to another (like walking from my home, to the
university - or changing the train). And after that, its annoying to
deactivate BT and WLAN again.
3. If I forgot to disable it again, the WLAN chip will consume power
of my battery (and perhaps the BT too).
It would be better, if the last state got recovered. So if BT or WLAN
was deactivated before suspend, it should be deactivated after resume.
If it was activated, it should be re-activated.
This problem exists still in Jaunty. My hardware is:
WLAN: Intel 3945
Bluetooth: Dell Computer Corp. Wireless 355 Bluetooth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/395753/+subscriptions