[HP EliteBook 8530w] Bluetooth keyboards and mice not working after suspend/resume

Bug #1075478 reported by FalFire
132
This bug affects 26 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading to Ubuntu 12.10 I encountered the following problem:

I have my apple wireless bluetooth keyboard paired up to Ubuntu, and it works fine when I boot up my laptop (HP EliteBook 8530w) as soon as I hit the login screen. However, if I then suspend and resume my laptop again, the bluetooth keyboard does not respond anymore. According to the bluetooth GUI applet it is still succesfully paired up and connected, and I see the green light on my keyboard blinking a few times when I hit a key for the first time after resume which is also the case when it _does_ work, but I get no response whatsoever from Ubuntu when typing on my keyboard.

"sudo service bluetooth restart" does not work.

Please let me know what additional information to provide.

Revision history for this message
In , James (james-redhat-bugs) wrote :

Created attachment 576744
Xorg.0.log from problem session

Description of problem:
After a suspend/resume cycle, X no longer recognises my Bluetooth mouse.

 - There's a confounding issue in that sometimes the Bt subsystem doesn't
   come back properly, see Bug 727106. Devices reappear after restarting
   the bluetooth service.

 - Following this, the mouse appears in the devices list in Gnome Shell,
   and other devices (e.g. file transfer from phone) works properly.

 - Upon reconnecting the mouse, messages like

     (WW) evdev: Bluetooth Mouse: device file is duplicate. Ignoring.

   appear in the Xorg logs (attached).

Sometimes waiting for a few hours and then trying again works.

I don't know if this is strictly an evdev bug. Might be udev or bluez or kernel or ... please reassign as appropriate.

Version-Release number of selected component (if applicable):
xorg-x11-drv-evdev-2.6.99.901-7.20120118git9d9c9870c.fc16.x86_64
udev-173-3.fc16.x86_64
bluez-4.96-3.fc16.x86_64
kernel-3.3.0-8.fc16.x86_64
kernel-3.3.1-2.fc16.x86_64
kernel-3.3.1-3.fc16.x86_64
xorg-x11-server-Xorg-1.11.4-3.fc16.x86_64

How reproducible:
Intermittent, but frequent.

Steps to Reproduce:
1. Suspend then resume.
2. Restart bluetooth.service if necessary, according to Bug 727106.
3. Reconnect Bluetooth mouse.

Actual results:
Mouse doesn't work.

Expected results:
Mouse works.

Additional info:

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

*** Bug 811681 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

Either server or udev bug. The last parts of the log show that we get the "device added" event, but we never saw the "device removed" for it.

The config_info string changes, so we don't automatically remove the previous instance when the new one is added.

Lennart, any comments? Is there some race condition that we may suffer from in the server that we don't see the device removed event?

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

Are there any workarounds known, besides restarting X? I don't particularly like having to shut down all programs to restart X.

Revision history for this message
In , Scott (scott-redhat-bugs) wrote :

(In reply to comment #2)
> Either server or udev bug. The last parts of the log show that we get the
> "device added" event, but we never saw the "device removed" for it.
>
> The config_info string changes, so we don't automatically remove the
> previous instance when the new one is added.
>
> Lennart, any comments? Is there some race condition that we may suffer from
> in the server that we don't see the device removed event?

Actually it's increasingly looking like a kernel bug - we're seeing the kernel netlink events with missing or corrupted components and also seeing other signs that pointers aren't going where they're supposed to...

Revision history for this message
In , Pierre-Yves (pierre-yves-redhat-bugs) wrote :

Dan, you might probably just unplug and re-plug the mouse

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

Pierre-Yves: I have internal bluetooth so there is no possibility to unplug anything. However, I have tried cycling power on the mouse and have tried running "systemctl restart bluetooth.service" without success. Restarting X (by logging out and back in) works though.

Revision history for this message
In , Andrew (andrew-redhat-bugs) wrote :

Scott is referring to the debugging we've been doing on Chromium OS. We have some more details in the bug: http://code.google.com/p/chromium-os/issues/detail?id=33813

It's looking like a race condition in the kernel.

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

It is possible that this bug may not be related to bluetooth. I also have the same problem with a USB mouse. Unplugging and plugging back in doesn't fix the problem. This happens sometimes (well, once so far) when resuming from sleep.

    [603892.207] (II) config/udev: Adding input device PIXART USB OPTICAL MOUSE (/dev/input/mouse2)
    [603892.207] (II) No input driver specified, ignoring this device.
    [603892.207] (II) This device may have been added with another device file.
    [603892.209] (II) config/udev: Adding input device PIXART USB OPTICAL MOUSE (/dev/input/event12)
    [603892.209] (**) PIXART USB OPTICAL MOUSE: Applying InputClass "evdev pointer catchall"
    [603892.209] (II) Using input driver 'evdev' for 'PIXART USB OPTICAL MOUSE'
    [603892.209] (**) PIXART USB OPTICAL MOUSE: always reports core events
    [603892.209] (**) evdev: PIXART USB OPTICAL MOUSE: Device: "/dev/input/event12"
    [603892.209] (WW) evdev: PIXART USB OPTICAL MOUSE: device file is duplicate. Ignoring.
    [603892.227] (EE) PreInit returned 8 for "PIXART USB OPTICAL MOUSE"
    [603892.227] (II) UnloadModule: "evdev"

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

did you see a remove event for this device before event12 was added again? can't tell that from the log excerpt you posted, please always provide the full log.

Revision history for this message
In , kpijarski (kpijarski-redhat-bugs) wrote :

I'm having the same problem with apple magic mouse, very frustrating...

Revision history for this message
In , kpijarski (kpijarski-redhat-bugs) wrote :

this is what dmesg gives me:
[ 8307.249323] power_supply hid-B8:F6:B1:1D:C8:F0-battery: driver failed to report `capacity' property: -5
[ 8311.915977] magicmouse 0005:05AC:030D.0007: unknown main item tag 0x0
[ 8311.922708] power_supply hid-B8:F6:B1:1D:C8:F0-battery: driver failed to report `capacity' property: -5
[ 8311.922916] input: Anthony’s Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/bluetooth/hci0/hci0:34/input18
[ 8311.923976] magicmouse 0005:05AC:030D.0007: input,hidraw0: BLUETOOTH HID v3.06 Mouse [Anthony’s Mouse] on 68:5D:43:20:DD:33
[ 8312.053764] traps: upowerd[3633] trap int3 ip:3cdee4e991 sp:7fffdb032dc0 error:0

Revision history for this message
In , Dan (dan-redhat-bugs) wrote :

Created attachment 626561
another problem session

As requested by Peter, a full log of a problem session.

Revision history for this message
In , kpijarski (kpijarski-redhat-bugs) wrote :

I don't know if this helps, but I have found a way to have the mouse back after suspend (but you need to have a second pointer to do that!): before suspend, I have to turn off bluetooth (without turning it off my computer would randomly not suspend at all. anyway, without turning it off there is no chance to have the mouse back after wakeup), and after wakeup I need to turn it on in gnome-shell first, and then cycle the hardware button (disable, and then re-enable BT) to have BT with mouse back. Just cycling the hardware button does NOT work. I think there is something very wrong with the bluetooth drivers in the current kernel (3.6.1 here)! I even had kernel panics after wakeup with bluetooth enabled. For me this is a new thing as I've never actually used BT and always turned it off on startup by default to save battery life, but now that I have a bluetooth mouse I seem to have been thrown back six years in terms of linux useability.

Any idea what to do with this?

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1075478/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → bluez (Ubuntu)
Revision history for this message
FalFire (edward-brinkmann) wrote : Re: Apple wireless bluetooth keyboard not working after suspend/resume

Update: sudo service gdm restart causes the keyboard to work again.

Revision history for this message
steveG (steffen-schreiner) wrote :

I can confirm the bug as described by FalFire. I have a Thinkpad X1 with a Broadcom Bluetooth card. Powering up the machine everything works as expected, once resuming the Apple Wireless Keyboard lights up the LED as usual while connecting, but the keyboard doesn't work at all. Using the main keyboard, one can look at a perfectly 'on' bluetooth applet with the connected keyboard.

12.10, X86_64, latest updates and kernel version 3.5.0-18-generic .

I can not tell exactly, but this problem exists at least since a view kernel versions, as I spottet it already weeks ago.

latest lines form dmesg concerning bluetooth:
----------------------------------------
[634054.136057] apple 0005:05AC:023A.0006: unknown main item tag 0x0
[634057.501035] power_supply hid-10:9A:DD:92:F1:36-battery: driver failed to report `capacity' property: -5
[634057.501475] input: Apple Wireless Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input20
[634057.501963] apple 0005:05AC:023A.0006: input,hidraw3: BLUETOOTH HID v0.50 Keyboard [Apple Wireless Keyboard] on EC:55:F9:FB:7D:7E
[634057.513787] power_supply hid-10:9A:DD:92:F1:36-battery: driver failed to report `capacity' property: -5
[634114.023698] usb 1-1.4: USB disconnect, device number 4
[634118.777855] power_supply hid-10:9A:DD:92:F1:36-battery: driver failed to report `capacity' property: -5
[634123.160050] usb 1-1.4: new full-speed USB device number 6 using ehci_hcd
[634123.255896] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f
[634123.255909] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[634123.255917] usb 1-1.4: Product: Broadcom Bluetooth Device
[634123.255925] usb 1-1.4: Manufacturer: Broadcom Corp
[634123.255931] usb 1-1.4: SerialNumber: EC55F9FB7D7E
[634127.020934] apple 0005:05AC:023A.0007: unknown main item tag 0x0
[634129.100411] power_supply hid-10:9A:DD:92:F1:36-battery: driver failed to report `capacity' property: -5
[634129.100615] input: Apple Wireless Keyboard as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input21
[634129.101116] apple 0005:05AC:023A.0007: input,hidraw3: BLUETOOTH HID v0.50 Keyboard [Apple Wireless Keyboard] on EC:55:F9:FB:7D:7E
[634129.107888] power_supply hid-10:9A:DD:92:F1:36-battery: driver failed to report `capacity' property: -5
----------------------------------------

Revision history for this message
steveG (steffen-schreiner) wrote :

bluetooth restart does not work, neither does a manual rmmod and a bluetooth start.

A gdm restart worked though for me as well.

Any ideas how to debug this further?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
steveG (steffen-schreiner) wrote :

Apparently this is somehow a left-over device file, or so. In the gdm log (see below) I found an error message about the keyboards device file, event18 in my case. Whereas I can cat the file and see output once I use the keyboard, indicating that it actually works concerning kernel/driver.

/var/log/gdm/:0.log
--------------------
(II) config/udev: Adding input device Apple Wireless Keyboard (/dev/input/event18)
(**) Apple Wireless Keyboard: Applying InputClass "evdev keyboard catchall"
(II) Using input driver 'evdev' for 'Apple Wireless Keyboard'
(**) Apple Wireless Keyboard: always reports core events
(**) evdev: Apple Wireless Keyboard: Device: "/dev/input/event18"
(WW) evdev: Apple Wireless Keyboard: device file is duplicate. Ignoring.
(EE) PreInit returned 8 for "Apple Wireless Keyboard"
--------------------

Via the error I found a related bug at redhat: https://bugzilla.redhat.com/show_bug.cgi?id=811534

As it is basically complaining because the file exists, a workaround is to remove the file before suspending. So I placed the command in a new pm script. Not nice but perfectly doing the job for now.

/usr/lib/pm-utils/sleep.d/70bluetooth
-------------
#!/bin/sh
#

case "$1" in
        hibernate|suspend)
  rm -f /dev/input/event18
  ;;
        *) exit $NA
  ;;
esac
-------------

Revision history for this message
Matthias (terrormafia) wrote :

I ran into the same problem with a no-name "Apple Like Bluetooth Mouse": After suspend, it reconnects just fine, but it doesn't move the pointer. The bluetooth applet shows it as connected, and so does "hcitool con", but X complains in its log that "device file is duplicate. Ignoring." and sure enough, "xinput list" still shows the rodent long after I disconnect it (using its hardware power switch, actually):
⎜ ↳ Apple Like Bluetooth Mouse id=13 [slave pointer (2)]

As it turns out, if I do "xinput disable 13" while it is disconnected, and then connect it, the mouse connects, disconnects and reconnects normally.
This appears to work across suspends, as long as I follow the advice / workaround in the redhat bug and disconnect the mouse before suspend. If I don't, I end up with another zombie device that needs disabling, but after that (and reconnecting), the mouse is back to normal once more. (I'm at 3 zombies right now.)

Hope this helps some people until the real bug is fixed...

Revision history for this message
Jamin W. Collins (jcollins) wrote :

This is a seriously annoying bug. I'm not sure this is reported against the correct subsystem. This strikes me as more an evdev or udev issue than a bluez issue.

To work around this for now, I've got a script that will disables any xinput device with "mouse" in it's name.

affects: bluez (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Revision history for this message
Jamin W. Collins (jcollins) wrote :

To be clear, this issue is present with any bluetooth connected evdev input (keyboard or mouse) that is not disconnected prior to a suspend resume cycle.

summary: - Apple wireless bluetooth keyboard not working after suspend/resume
+ bluetooth keyboards and mice not working after suspend/resume
Revision history for this message
Jamin W. Collins (jcollins) wrote : Re: bluetooth keyboards and mice not working after suspend/resume

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.

Revision history for this message
KarlRelton (karllinuxtest-relton) wrote :

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 in the kernel bluetooth code, this leads the code to remove devices from sysfs in the wrong order. This in turn leads to udev events being sent out with truncated device paths.

This in turn causes Xorg evdev to receive the 'remove' events, but ignore them because they cannot match them up.

When the keyboard re-connects, Xorg then sees the 'add' events matching a keyboard it thinks it already has, so ignores them ... so your keyboard doesn't work (or mouse too, if bluetooth as well!).

IMHO This is NOT a problem in Xorg - it is a kernel issue leading to faulty udev events.

Note the Google Chrome people patched their Xorg to work around the issue ... but the real fix should be in the kernel.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Jerry Van Baren (gvb) wrote :

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

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Karl,

Thanks for the pointer to your patches upstream. Will you be submitting the patches for inclusion in the mainline kernel?

affects: xserver-xorg-input-evdev (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
molecule-eye (niburu1) wrote :

James Collins's tip in comment #10 solved my issues.

Revision history for this message
tarraco (xmontana) wrote :

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

Revision history for this message
TJ (tj) wrote :

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.

Revision history for this message
Kyungwon Chun (kwchun) wrote :

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

Revision history for this message
penalvch (penalvch) wrote :

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/ .

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 (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine 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:
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.12

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

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: added: needs-kernel-logs
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Mike Mestnik (cheako) wrote : apport information

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: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe3f8000 irq 16'
   Mixer name : 'VIA VT2020'
   Components : 'HDA:11060441,104383e4,00100100'
   Controls : 54
   Simple ctrls : 23
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfe9bc000 irq 87'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 7
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 12.04
IwConfig:
 lo no wireless extensions.

 eth2 no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-27-generic root=/dev/mapper/fsRoot ro rootfstype=ext4 crashkernel=384M-2G:64M,2G-:128M elevator=deadline radeon.audio=1
ProcVersionSignature: Ubuntu 3.8.0-27.40~precise3-generic 3.8.13.4
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-27-generic N/A
 linux-backports-modules-3.8.0-27-generic N/A
 linux-firmware 1.116~gd~p
RfKill: Error: [Errno 2] No such file or directory
Tags: precise
Uname: Linux 3.8.0-27-generic i686
UpgradeStatus: Upgraded to precise on 2012-01-03 (719 days ago)
UserGroups: adm admin audio cdrom dialout dip disk floppy fuse games kvm libvirtd plugdev pulse-access video
WpaSupplicantLog:

dmi.bios.date: 10/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3029
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Crosshair IV Formula
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3029:bd10/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCrosshairIVFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

tags: added: apport-collected precise
Revision history for this message
Mike Mestnik (cheako) wrote : .etc.asound.conf.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : AcpiTables.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : AlsaDevices.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : AplayDevices.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : BootDmesg.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : Lspci.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : Lsusb.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : PciMultimedia.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : ProcEnviron.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : ProcModules.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : UdevDb.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : UdevLog.txt

apport information

Revision history for this message
Mike Mestnik (cheako) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote : Re: bluetooth keyboards and mice not working after suspend/resume

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-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

tags: removed: apport-collected precise
penalvch (penalvch)
summary: - bluetooth keyboards and mice not working after suspend/resume
+ [HP EliteBook 8530w] Bluetooth keyboards and mice not working after
+ suspend/resume
Changed in evdev:
importance: Unknown → Undecided
status: Unknown → Won't Fix
Revision history for this message
penalvch (penalvch) wrote :

OR using EOL release, no logs, and no response for years.

no longer affects: linux (Ubuntu)
affects: evdev → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Won't Fix → New
no longer affects: linux (Ubuntu)
affects: linux → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Medium → Undecided
status: Confirmed → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.