Mike Mestnik, thank you for your comment. Please do not apport-collect to
another reporter's report. Instead, so your hardware may be tracked, could you
please file a new report by executing the following in a terminal while booted
into a Ubuntu repository kernel (not a mainline one) via:
ubuntu
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-27-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog]
Subdevices: 2/2
Subdevice #0: subd
FalFire, 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
The solution of comment #10 does not work for me. However, the solution
from the following link is a good alternative. Just reload the kernel
module, btusb, after resume.
http://osdir.com/ml/ubuntu-bugs/2013-10/msg19334.html
--
You received this bug notification because you are a member of Ubunt
Ubuntu 13.04 and 13.10, up to and including kernel 3.12rc5, are affected
by this and the work-around of disconnecting connected devices during
suspend (from comment #10) does not solve the issue. Bluetooth has to be
disabled and re-enabled to recognise any bluetooth devices.
--
You received this
Me too, I comfirm that the comment #10 solve my problem with my laptop
bluetooth.
Versión 12.04 (precise) de 64-bit
GNOME 3.4.2
samsung-R580-R590 3.2.0-52-generic #78-Ubuntu SMP Fri Jul 26 16:21:44 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a m
James Collins's tip in comment #10 solved my issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075478
Title:
bluetooth keyboards and mice not working after suspend/resume
To manage notificatio
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075478
Title:
bluetooth keyboards and mice not working after suspend/resume
To manag
** Changed in: linux
Status: Unknown => Confirmed
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075478
Title:
bluetooth keyboards and m
@Karl,
Thanks for the pointer to your patches upstream. Will you be submitting
the patches for inclusion in the mainline kernel?
** Package changed: xserver-xorg-input-evdev (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux via
gpothier's tip of logging out and back in is a good work-around. In
fact, you don't have to fully log out, just do a "switch user" (switch
to the login screen) and then log back into your existing session.
Ref:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065157/comments/25
--
You rece
This bug is because of kernel upstream bug
https://bugzilla.kernel.org/show_bug.cgi?id=52471
All the info is in that bug report, including 2 patches to fix it.
In short form, the (doomed to fail by timeout) battery status reporting
injects a 5 second delay in keyboard device removal. Due to races
The attached script disconnects all currently attached bluetooth devices
on suspend, thus completely avoiding this bug.
Place the script in /etc/pm/sleep.d/10_bluetooth-input, and ensure that
its executable.
** Attachment added: "/etc/pm/sleep.d/10_bluetooth-input"
https://bugs.launchpad.net/
13 matches
Mail list logo
