The specific message I get is...
hid-sensor-hub 001F:8087:0AC2.0003: timeout waiting for response
from ISHTP device
I am running Ubuntu 22.04 with kernel 5.15.0-27-generic.
Here is my laptop information:
$ sudo dmidecode | grep -A 9 "System Information"
System Information
My laptop's native resolution is:
3840x2160
and this is what I have selected as the display output in GNOME.
I am using 200% scaling.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Attempting to run cheese on a HDPI display in Wayland results in the
following errors:
(cheese:9303): Gdk-CRITICAL **: 10:29:11.221:
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
'GDK_IS_WAYLAND_WINDOW (window)' failed
(cheese:9303): Gdk-WARNING **:
My bluetooth mouse is connected now, but I had to follow a special
process...
WHAT WORKS:
I had to turn OFF my wireless, make sure bluetooth was ON, and then
connect/pair the mouse.
After the bluetooth mouse connected successfully, I was able to turn wi-fi ON
again.
Now, my mouse
I am running artful 17.10.1 with linux-firmware version 1.169.2.
I am assuming that version 1.169.2 also has the fix??
In any case, it does not work.
Also, the work-around (Comment #17) no longer works for me.
$ uname -r
4.13.0-32-generic
$ lsb_release --all
No LSB modules are
I still see this on shutdown with kernel 4.14.
wlo1: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
wlo1: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22)
$ uname -r
4.14.1-041401-generic
$ lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu
** Attachment added: "Bluetooth dmesg for Kernel 4.13"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+attachment/5013196/+files/Bluetooth%20with%20kernel%204.13.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "Bluetooth dmesg for Kernel 4.12"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+attachment/5013195/+files/Bluetooth%20with%20kernel%204.12.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Here are the results:
WORKING: 4.12.0-041200-generic
NOT WORKING: 4.13.0-16-generic
--
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/1729389
Title:
Bluetooth mouse and keyboard
Correction...
Kernel 4.12 is working (I had inadvertently selected the wrong kernel on
the Grub screen during my last test).
$ uname -r
4.12.0-041200-generic
I will continue to test 4.12 to see if the Bluetooth mouse unexpectedly
disconnects.
--
You received this bug notification
So far, not working with 4.14, 4.13, 4.12.
With each kernel, I see the messages:
Bluetooth: hci0 command 0x0c52 tx timeout
Bluetooth: hci0 command 0x0c24 tx timeout
I will continue to test older versions and report back.
--
You received this bug notification because you are a member
Oops, I meant to write "4.14" (not "14.14")
--
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/1729389
Title:
Bluetooth mouse and keyboard connects, works for a few seconds, then
doesn't
With 14.14, it only worked for a few seconds and then stopped.
$ uname -r
4.14.0-041400-generic
Here are some error messages from the logs that may help...
hid-generic 0005:03F0:084C.0006: unknown main item tag 0x0
+hid:0005:03F0:084C.0006
bluetoothd
Can't get HIDP connection info
If I implement the work-around in comment #17 and use kernel 4.13.12, my
bluetooth mouse connects automatically when I reboot.
Unfortunately, the work-around seems to still be required for kernel
4.13.12.
Let me know if there is anything else I can do to help?
--
You received this bug
Hummm... doesn't look good...
Before installing 4.13.12, I reverted the change in comment #17.
$ uname -r
4.13.12-041312-generic
I see these errors in the logs:
bluetoothhd : Failed to add UUID: Not Powered (0x0f)
...and...
Bluetooth: hci0 command 0x0c52 tx timeout
Also, bluetooth
See if the following provides a workaround...
$ sudo gedit /etc/modprobe.d/iwlwifi.conf
# Add to the end:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
options iwlwifi bt_coex_active=0
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Here is the system log where thi message is logged:
kernel: [1.402243] cfg80211: Calling CRDA to update world regulatory domain
kernel: [1.404326] lib80211: common routines for IEEE802.11 drivers
kernel: [1.404336] lib80211_crypt: registered algorithm 'NULL'
kernel: [1.405743] wl:
Issue appears on fresh install of 14.04.1.
$ uname -a
Linux PS001 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename:
Public bug reported:
Broadcom Corporation BCM4352 wi-fi/bluetooth adapter is unable to
find/detect Bluetooth devices, and Bluetooth devices can not see the
Ubuntu PC, even when in pairing mode.
(Here is a similar bug, but for a different device Broadcom device:
** Description changed:
Broadcom Corporation BCM4352 wi-fi/bluetooth adapter is unable to
find/detect Bluetooth devices, and Bluetooth devices can not see the
Ubuntu PC, even when in pairing mode.
- (Here is a similar bug, but for a different device Broadcom device:
+ (Here is a similar
In Ubuntu 13.04 x64 with kernel 3.8, my flopy drive now works perfectly.
The systems recognizes the drive and displays an icon fo it on the Unity
Launcher. I can click on the icon and am able to view the contents of
the disk.
--
You received this bug notification because you are a member of
I was able to successfully build this module in kernel 3.8.0-27 per
comment 29
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173761/comments/29
on 3.11.0-031100rc3-generic).
$ sudo dkms build -m b43b1 -v 6.30.223.95
Kernel preparation unnecessary for this kernel.
Experiencing this issue with upstream Kernel Release Candiadate 3, so I
don't think this is going to be fixed in a future release.
3.11.0-031100rc3-generic #201307290035 SMP Mon Jul 29 04:36:40 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a
23 matches
Mail list logo
