[Kernel-packages] [Bug 1557298] Re: Low Energy Keyboard is paired incorrectly
Same issue here on Ubuntu 20.04 5.6.4 Kernel. Logitech MX3 Mouse works. Keyboard does pair difficult. When it pairs connection flickers on off. Same issue with Bose SoundSport headset and Samsung Q90R soundbar. If you need logs please ask and provide commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1557298 Title: Low Energy Keyboard is paired incorrectly Status in Unity Control Center: New Status in bluez package in Ubuntu: Confirmed Bug description: Failed to pair low energy(bluetooth smart, 4.0) keyboard correctly. Bluetooth smart keyboard is unable to use after bluetooth-wizard says "OK". Also the passcode input is also not acting interactively like when pairing with bluetooth 3.0(LegacyPairing) keyboard. Above scenario also being verified with bluetoothctl and blueman. Step to reproduce: 1. open Bluetooth Settings 2. click on Add New Device button 3. select the bluetooth le keyboard 4. input the passcode display on GUI Expected result: After bluetooth-wizard telling user is okay the keyboard should work Actual result: Pairing mode stop on keyboard, but still not work. - More details about versions: Environment: xenial daily (20160307) bluez 5.37-0ubuntu5 gnome-bluetooth 3.18.2-1ubuntu2 blueman 2.0.3-1ubuntu1 bluetooth controller 0cf3:e005 Atheros Communications, Inc. (hci version: 4.1) Tested devices: Designer Mouse, bluetooth smart (pairable, work, re-pair work) Designer Keyboard, bluetooth smart (paired, not working) BT3.0 keyboard, bluetooth classic (pair and work) BT3.0 mouse, bluetooth classic (pair and work) - In control environment with the same hardware system and devices: trusty 14.04.1 + dist-upgrade (stay with 3.13 kernel) bluez5 5.35 (ppa: https://launchpad.net/~vidplace7/+archive/ubuntu/bluez5) It works with all above devices but can only be pairing through bluetoothctl manually, since the older bluetooth-wizard does not understand bluez 5.x. Everything seems works fine, although there are a lot more error messages, but since this bug is more about xenial, please let me know if we need more information about this, I'm able to reproduce this trusty scenario in anytime. - Additional note: A little clarification, since I'm not sure how far the Bluetooth SIG is going to use Bluetooth Smart(Low Energy, or even Smart-Ready) to cover the versioning, I decided to just use what ever I saw on the product box. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 15 11:40:12 2016 InstallationDate: Installed on 2016-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic.efi.signed root=UUID=1079eca4-4293-4e51-ba0e-84f7d681cb2c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0141B2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:71:CC:39:BD:22 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:862538 acl:39687 sco:0 events:2668 errors:0 TX bytes:26235 acl:904 sco:0 commands:1021 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-control-center/+bug/1557298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
Same issue here on Ubuntu 20.04 5.6.4 Kernel. Logitech MX3 Mouse works. Keyboard does pair difficult. When it pairs connection flickers on off. Same issue with Bose SoundSport headset and Samsung Q90R soundbar. If you need logs please provide commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
Same issue here on Ubuntu 20.04 5.6.4 Kernel. Logitech MX3 Mouse works. Keyboard does pair difficult. When it pairs connection flickers on off. Same issue with Bose SoundSport headset and Samsung Q90R soundbar. If you need logs please ask and provide commands. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
I guess this was merged to upstream kernels. I have no issues on 20.04 with 5.6.3 Kernel (actually since ~5.4.0 I do note experience this issue anymore). On another note, I see a similar tearing when playing high res videos on youtube (I have 2x4k monitors connected to my XPS 13 7390 / no fractional scaling enabled). Can someone confirm this? -- 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/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake Status in linux package in Ubuntu: Confirmed Bug description: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Is https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869481 possibly connected to this too? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: Fix Released Status in alsa-lib package in Ubuntu: Invalid Status in alsa-lib source package in Bionic: Fix Released Status in alsa-lib source package in Eoan: Fix Released Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859287] Re: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04
This issue reappeared on kernel 5.6.0 for me :/ The wifi networks are shown but connections cannot be build, they timeout. I am back on 5.5.13 now with 20.04. -- 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/1859287 Title: iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04 Status in linux package in Ubuntu: Fix Released Bug description: Hi there, Laptop: Dell XPS 13 7390 2-in-1 Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04. Firmware crashes after loading and interface doesn't show up. This is with: linux-image-5.4.0-9-generic 5.4.0-9.12 linux-firmware 1.184 I've noticed the driver was trying to load a more recent firmware: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 I've downloaded this file from upstream iwlwifi firmware git and tried unloading/reloading iwlwifi. Driver crashes as well, but with a different error code. Best, - LM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lool 1579 F pulseaudio /dev/snd/pcmC0D0p: lool 1579 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 15:02:08 2020 InstallationDate: Installed on 2019-12-02 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off plymouth.force-scale=3 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago) dmi.bios.date: 11/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
