[Kernel-packages] [Bug 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
I attached snoop/logs where the PC initiated the connection, for comparison. There, the issue doesn't happen, the headset calmly allows the PC to establish all the profiles since the PC connected the ACL. One can also see the difference in flow: Aug 29 01:57:02 RhoPC bluetoothd[4053589]: src/device.c:connect_profiles() /org/bluez/hci0/dev_FC_58_FA_7F_E5_18 (all), client :1.160 Aug 29 01:57:02 RhoPC bluetoothd[4053589]: src/service.c:btd_service_ref() 0x556620ba9bb0: ref=2 Aug 29 01:57:02 RhoPC bluetoothd[4053589]: src/service.c:change_state() 0x556620ba9bb0: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: disconnected -> connecting (0) Aug 29 01:57:05 RhoPC bluetoothd[4053589]: src/adapter.c:connected_callback() hci0 device FC:58:FA:7F:E5:18 connected eir_len 9 Aug 29 01:57:05 RhoPC bluetoothd[4053589]: src/profile.c:ext_connect() Headset Voice gateway connected to FC:58:FA:7F:E5:18 Aug 29 01:57:05 RhoPC bluetoothd[4053589]: src/service.c:change_state() 0x556620ba9bb0: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: connecting -> connected (0) THe HFP service entered state CONNECTING pretty much as soon as I tapped "Connect" in Blueman, even before the ACL was established. Then 3s later, it entered CONNECTED once the HFP SLC was established, courtesy of ext_connect(). I did a basic search and couldn't find anything that would be hurt by removing that CONNECTING transition -- pretty much every spot that checks for state CONNECTING during transitions, expects it to mean "this service connection was locally initiated". So we just need to make sure it means just that, especially since I see no other indicator accessible to listeners. Since a bunch of guesswork was done to get here, it would be neat if someone experienced with the stack can confirm how much of this is even correct, and if the proposed solution makes sense :-) -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez
[Kernel-packages] [Bug 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
That one's clear enough from the earlier log snippet and source: Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_connect() Headset Voice gateway connected to FC:58:FA:7F:E5:18 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state() 0x562f6441d710: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: disconnected -> connecting (0) Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state() 0x562f6441d710: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: connecting -> connected (0) This ext_connect() seems to be called whenever a profile connection is completed, whether successfully or not, whether locally or remotely initiated. Above, we see the state changes it orchestrated -- it first transitions the HFP "service" to CONNECTING and then to CONNECTED pretty quickly: if (conn->service && service_set_connecting(conn->service) < 0) goto drop; ... if (conn->service) btd_service_connecting_complete(conn->service, err ? -err->code : -EIO); Each of these state changes gets propagated to a bunch of listeners -- one of which is policy.c. = I think that first transition (to CONNECTING) should not have happened, because it takes away the ability of any listeners to judge whether a connection was locally or remotely initiated, and act accordingly. The HFP service should've simply gone from DISCONNECTED to CONNECTED -- that first IF block should be removed entirely. = If a connection were indeed locally initiated, the service's state would've been set to CONNECTING way back, by btd_service_connect() probably since it looks to be the one that kicks off the connection. ext_connect() only has enough info to make that final jump to CONNECTED. -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+sub
[Kernel-packages] [Bug 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
So why did Bluez initiate A2DP even when the headset was the one that established the ACL? The bluetoothd logs help out here: Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/adapter.c:connected_callback() hci0 device FC:58:FA:7F:E5:18 connected eir_len 5 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_confirm() incoming connect from FC:58:FA:7F:E5:18 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:btd_service_ref() 0x562f6441d710: ref=2 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_confirm() Headset Voice gateway authorizing connection from FC:58:FA:7F:E5:18 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_auth() FC:58:FA:7F:E5:18 authorized to connect to Headset Voice gateway Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/profile.c:ext_connect() Headset Voice gateway connected to FC:58:FA:7F:E5:18 Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state() 0x562f6441d710: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: disconnected -> connecting (0) Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/service.c:change_state() 0x562f6441d710: device FC:58:FA:7F:E5:18 profile Headset Voice gateway state changed: connecting -> connected (0) Aug 29 00:54:47 RhoPC bluetoothd[4046739]: src/device.c:device_profile_connected() Headset Voice gateway Success (0) Aug 29 00:54:47 RhoPC bluetoothd[4046739]: plugins/policy.c:policy_connect() /org/bluez/hci0/dev_FC_58_FA_7F_E5_18 profile a2dp-sink Aug 29 00:54:47 RhoPC bluetoothd[4046739]: profiles/audio/a2dp.c:a2dp_sink_connect() path /org/bluez/hci0/dev_FC_58_FA_7F_E5_18 One can easily see at the end there, where something in plugins/policy.c kicks off A2DP connection, apparently as soon as it got word that HFP had connected. Checking that file, the offending code seems to be this in hs_cb(): case BTD_SERVICE_STATE_CONNECTED: /* Check if service initiate the connection then proceed * immediately otherwise set timer */ if (old_state == BTD_SERVICE_STATE_CONNECTING) policy_connect(data, sink); else if (btd_service_get_state(sink) != BTD_SERVICE_STATE_CONNECTED) policy_set_sink_timer(data); break; The reasoning is sound though -- if the HFP connection was locally initiated i.e. previously in STATE_CONNECTING, then go ahead and connect A2DP right now. Otherwise, respect right-of-way and set a timer to connect it in around 2s, in case the headset somehow fails to do so. The problem is, this HFP connection was NOT locally initiated. So why was policy.c informed that it is? -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1
[Kernel-packages] [Bug 1941972] Re: Several bugs of file descriptor leak in bcc
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1941972 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941972 Title: Several bugs of file descriptor leak in bcc Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. step 1 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : Select the false branch at this point (fp!=stdin is false) but did not close it step 1 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 805 : Select the true branch at this point (headstr!=null is true) step 4 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 809 : Select the true branch at this point (lp!=null is true) step 5 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 811 : Select the false branch at this point (fp!=stdout is false) but did not close it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941972/+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 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
I've spent a while studying the snoop/syslogs and Bluez source, and I believe I've narrowed down the issue. * From the Headset-Initiated snoop, we can see where the headset connected the ACL (23:54:47 UTC), followed shortly by connecting HFP (successfully). * Very soon after the headset connected HFP, the PC/bluez initiated an AVDTP connection, a bid to connect A2DP -- this is unfriendly behaviour, since the general convention is: whomever created the ACL gets to create the profiles. Or at least is given enough time to connect them, before the other end starts its own attempt. The result of this behaviour is that the headset, probably getting ready to connect A2DP itself, now gets confused by this incoming PC connection, its firmware apparently not strong or flexible enough to handle this A2DP crossover scenario, manifesting as follows: That AVDTP channel (for A2DP signalling) does get established, but then strange behaviour is seen while setting up the media-channel -- the headset takes 3s to respond to the AVDTP_DISCOVER command. These 3s end up being costly because... * The PC creates a SCO connection to the headset around this time -- I believe this is because the PC must route my current audio stream somewhere, and since A2DP media isn't setup yet after all this time, it (PulseAudio?) will settle for HFP/SCO. (Even this SCO connection takes 5s to complete, headset still not out of the woods.) -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+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 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
** Attachment added: "Syslog taken when the PC initiates the connection" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521418/+files/syslog_PCInitiated -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+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 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
** Attachment added: "HCI snoop taken when the PC initiates the connection" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521417/+files/PCInitiated.snoop -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+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 1941977] Re: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
** Attachment added: "Syslog taken when the headset initiates the connection" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+attachment/5521416/+files/syslog_HeadsetInitiated -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941977/+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 1941977] [NEW] PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP
Public bug reported: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/14/2020:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:99:1D:20 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:3313120 acl:776 sco:26275 events:305102 errors:0 TX bytes:255208317 acl:298108 sco:22053 commands:6779 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-04-27T23:21:52.866445 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "HCI snoop taken when the headset initiates the connection" https://bugs.launchpad.net/bugs/1941977/+attachment/5521398/+files/HeadsetInitiated.snoop -- 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/1941977 Title: PC streams music over low-quality HFP/SCO connection, instead of A2DP/AVDTP Status in bluez package in Ubuntu: New Bug description: This issue was first discovered when I got this headset 2 years back: https://www.amazon.co.uk/gp/product/B01C2QCPYI. STEPS * Enable Bluetooth on the PC * Have music or some video playing on the PC * Power on the (already-paired) headset. It automatically connects to the PC. EXPECTED RESULT The PC's audio should now be streamed to the headset, over high-quality A2DP ACTUAL RESULT The PC's audio gets streamed over the low-quality HFP/SCO connection instead. Stopping and resuming the stream changes nothing. I have to manually open Blueman and right-click on the device and select "High-quality A2DP profile", for it to switch to the expected high-quality A2DP transport. HCI snoop logs and verbose bluetoothd-syslogs taken in both headset- initiated and PC-initiated connections are attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.3 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 5.4.0-74.83-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 29 03:49:08 2021 InstallationDate: Installed on 2019-06-08 (812 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9380 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-74-generic root=UUID=93dae559-0f0d-4e36-9318-ee7154840a9f ro resume=UUID=01c18f00-e0eb-4891-9bf1-3110416d9b39 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: bluez UpgradeStatus
[Kernel-packages] [Bug 1941937] Re: kubuntu focal.3 no wallpaper on one display, right-click not working on that display
another QA-test install today on same box. kubuntu wasn't touched in install, but to validate the new install the system was booted & logged int to ensure it was untouched... Logging in today was flawless; backgrounds on both displays & quick exploration of system (to ensure un-impacted by install on other partition on disk) was flawless... -- 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/1941937 Title: kubuntu focal.3 no wallpaper on one display, right-click not working on that display Status in linux package in Ubuntu: Confirmed Bug description: ** Background Performing a QA-test install (Lubuntu impish) to - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) testcase: install using existing partition (sda1) On the box existed - Lubuntu focal.3 (system selected for replacing with impish) - Xubuntu focal.3 (an install-alongside or auto-resize QA-test) - Kubuntu focal.3 (another install-alongside/auto-resize QA-test) I'm booting the Kubuntu focal.3 expecting no changes.. The QA-test done days ago was good and I passed it without issues. This will be it's first login after that initial-post-install checks where I noticed nothing wrong. ** What I see My displays are setup to match my config (one display set above the other), however wallpaper on my.bottom display is present & looks normal NO WALLPAPER appears on my.top display right-click on my.bottom display is pulling up menu allowing me Create.New..Configure.Desktop as expected. right-click on my.TOP display however does nothing Moving windows around is perfect.. ** ACTUAL BEHAVIOR Wallpaper on both monitors, not just my.bottom display Right click of background pulls up menu on both displays, not just my.bottom ** EXPECTED BEHAVIOR Wallpaper on both monitors, and right-click works both displays. (It did this in the initial boot after QA-test install; this is now 2nd boot of system which is first time I've noted this behavior) ** Note (LXQt has exhibited same behavior in focal) This thought is likely red herring - it reminded me of https://bugs.launchpad.net/openbox/+bug/1845756 which is tagged against openbox thus doesn't apply here. Originally I said "I've had this behavior before with LXQt & I can't recall if this was put down to an issue in Qt 5.12.8 (fixed in later releases), or openbox (which won't apply here of course).." -- I'll complete this QA-test and aim to return and add more later. This box is only used for QA-test installs, so system may not exist for very long. It's likely more useful if I repeated this with Kubuntu impish... but vanvugt's comment on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945 implies that's of limited value This bug MAYBE should be filed against linux/nouveau ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plasma-workspace 4:5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Aug 28 13:32:25 2021 InstallationDate: Installed on 2021-08-26 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: plasma-workspace UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guiverc 804 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-08-26 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor Package: linux (not installed) ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.m
[Kernel-packages] [Bug 1941974] Re: A potential bug of Use of Uninitialized Variable
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1941974 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941974 Title: A potential bug of Use of Uninitialized Variable Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found a bug in bcc , would you help me to check if this bug is true?thanks for your patience. == step 1 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : buf is defined here but not initialized step 2 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941974/+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 1941973] Re: Several potential bugs of memory leak
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1941973 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941973 Title: Several potential bugs of memory leak Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. == step 1 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2088 : Allocate memory to result step 2 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2090 : Select the false branch at this point (result==null is false) step 3 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1756 : Function xmalloc executes and stores the return value to strings step 4 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1760 : Select the true branch at this point (read(indesc,strings,strs_size)!=strs_size is true), the allocated memory is leaked step 1 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1239 : Allocate memory to p step 2 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1240 : Select the true branch at this point (p!=null is true) step 3 : In file build/bcc/bcc.c(build is directory generated by configure) , function catstr line 284 : Function xalloc executes and returns step 4 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 762 : Function catstr executes and stores the return value to p step 5 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 763 : Select the true branch at this point (opt_v>1 is true) step 6 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 765 : Select the true branch at this point (opt_v>2 is true) step 7 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 753 : Select the false branch at this point (ihttps://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941973/+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 1941972] Re: Several bugs of file descriptor leak in bcc
** Description changed: Ubuntu version: 18.04 bcc version:0.16.17 + I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. + + + step 1 : + In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : + Function fopen executes and stores the return value to fp + + step 2 : + In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : + Select the false branch at this point (fp==null is false) + + step 3 : + In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : + Select the false branch at this point (fp!=stdin is false) but did not close it - step 1 : -In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : -Function fopen executes and stores the return value to fp + step 1 : + In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : + Function fopen executes and stores the return value to fp - step 2 : -In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : -Select the false branch at this point (fp==null is false) + step 2 : + In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : + Select the false branch at this point (fp==null is false) - step 3 : -In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : -Select the false branch at this point (fp!=stdin is false) but did not close it + step 3 : + In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 805 : + Select the true branch at this point (headstr!=null is true) - - - - step 1 : -In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : -Function fopen executes and stores the return value to fp - - step 2 : -In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : -Select the false branch at this point (fp==null is false) - - step 3 : -In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 805 : -Select the true branch at this point (headstr!=null is true) - - step 4 : -In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 809 : -Select the true branch at this point (lp!=null is true) - step 5 : -In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 811 : -Select the false branch at this point (fp!=stdout is false) but did not close it + step 4 : + In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 809 : + Select the true branch at this point (lp!=null is true) + step 5 : + In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 811 : + Select the false branch at this point (fp!=stdout is false) but did not close it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941972 Title: Several bugs of file descriptor leak in bcc Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. step 1 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : Select the false branch at this point (fp!=stdin is false) but did not close it ===
[Kernel-packages] [Bug 1941974] [NEW] A potential bug of Use of Uninitialized Variable
Public bug reported: Ubuntu version: 18.04 bcc version:0.16.17 I found a bug in bcc , would you help me to check if this bug is true?thanks for your patience. == step 1 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : buf is defined here but not initialized step 2 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) ** Affects: linux86 (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu version: 18.04 bcc version:0.16.17 - == - step 1 : -In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : - buf is defined here but not initialized + step 1 : + In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : + buf is defined here but not initialized - step 2 : -In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : -buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) - - there are several potential bugs of Unchecked Return Value to NULL - Pointer Dereference : + step 2 : + In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : + buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) ** Description changed: Ubuntu version: 18.04 bcc version:0.16.17 + I found a bug in bcc , would you help me to check if this bug is true?thanks for your patience. == step 1 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : buf is defined here but not initialized step 2 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941974 Title: A potential bug of Use of Uninitialized Variable Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found a bug in bcc , would you help me to check if this bug is true?thanks for your patience. == step 1 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 668 : buf is defined here but not initialized step 2 : In file build/as/genobj.c(build is directory generated by configure) , function putobjword line 672 : buf[1] is used as the 1st parameter in function putobj1 (buf[1] is uninitialized) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941974/+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 1941973] Re: Several potential bugs of memory leak
** Description changed: Ubuntu version: 18.04 bcc version:0.16.17 - + I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. == - step 1 : -In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2088 : -Allocate memory to result + step 1 : + In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2088 : + Allocate memory to result - step 2 : -In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2090 : -Select the false branch at this point (result==null is false) + step 2 : + In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2090 : + Select the false branch at this point (result==null is false) - step 3 : -In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1756 : -Function xmalloc executes and stores the return value to strings + step 3 : + In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1756 : + Function xmalloc executes and stores the return value to strings - step 4 : -In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1760 : -Select the true branch at this point (read(indesc,strings,strs_size)!=strs_size is true), the allocated memory is leaked + step 4 : + In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1760 : + Select the true branch at this point (read(indesc,strings,strs_size)!=strs_size is true), the allocated memory is leaked - step 1 : -In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1239 : -Allocate memory to p + step 1 : + In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1239 : + Allocate memory to p - step 2 : -In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1240 : -Select the true branch at this point (p!=null is true) + step 2 : + In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1240 : + Select the true branch at this point (p!=null is true) - step 3 : -In file build/bcc/bcc.c(build is directory generated by configure) , function catstr line 284 : -Function xalloc executes and returns + step 3 : + In file build/bcc/bcc.c(build is directory generated by configure) , function catstr line 284 : + Function xalloc executes and returns - step 4 : -In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 762 : -Function catstr executes and stores the return value to p + step 4 : + In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 762 : + Function catstr executes and stores the return value to p - step 5 : -In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 763 : -Select the true branch at this point (opt_v>1 is true) + step 5 : + In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 763 : + Select the true branch at this point (opt_v>1 is true) - step 6 : -In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 765 : -Select the true branch at this point (opt_v>2 is true) + step 6 : + In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 765 : + Select the true branch at this point (opt_v>2 is true) - step 7 : -In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 753 : -Select the false branch at this point (ihttps://bugs.launchpad.net/bugs/1941973 Title: Several potential bugs of memory leak Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. == step 1 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc l
[Kernel-packages] [Bug 1941975] [NEW] Several bugs of Null Pointer Dereference/Unchecked Return Value to NULL Pointer Dereference
Public bug reported: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. = step 1 : In file build/ar/ar.c(build is directory generated by configure) , function prev_mapelt line 775 : Select the false branch at this point (tail->next!=null is false) step 2 : In file build/ar/ar.c(build is directory generated by configure) , function prev_mapelt line 777 : Return null to caller step 3 : In file build/ar/ar.c(build is directory generated by configure) , function move_in_map line 1332 : Function prev_mapelt executes and stores the return value to prev (prev can be null) step 4 : In file build/ar/ar.c(build is directory generated by configure) , function move_in_map line 1333 : Store this->next to prev->next == step 1 : In file build/cpp/cpp.c(build is directory generated by configure) , function insert_substrings line 1403 : Allocate memory to rv (lacking failure check, 7 out of 19 memory allocations checked failures) step 2 : In file build/cpp/cpp.c(build is directory generated by configure) , function insert_substrings line 1403 : Store 0 to rv = step 1 : In file build/cpp/cpp.c(build is directory generated by configure) , function insert_substrings line 1403 : Allocate memory to rv (lacking failure check, 7 out of 19 memory allocations checked failures) step 2 : In file build/cpp/cpp.c(build is directory generated by configure) , function insert_substrings line 1457 : Select the false branch at this point ((cc.0.ph.lcssa25+2)>len.0.ph.ph is false) step 3 : In file build/cpp/cpp.c(build is directory generated by configure) , function insert_substrings line 1458 : Store *(data_str) to rv[cc] === step 1 : In file build/cpp/cpp.c(build is directory generated by configure) , function gen_substrings line 1271 : Allocate memory to arg_list (lacking failure check, 7 out of 19 memory allocations checked failures) step 2 : In file build/cpp/cpp.c(build is directory generated by configure) , function gen_substrings line 1272 : arg_list is used as the 1st parameter in function memset (arg_list can be null) === step 1 : In file build/cpp/cpp.c(build is directory generated by configure) , function gen_substrings line 1271 : Allocate memory to arg_list (lacking failure check, 7 out of 19 memory allocations checked failures) step 2 : In file build/cpp/cpp.c(build is directory generated by configure) , function gen_substrings line 1277 : Load value from arg_list[ac.0].name = ** Affects: linux86 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941975 Title: Several bugs of Null Pointer Dereference/Unchecked Return Value to NULL Pointer Dereference Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. = step 1 : In file build/ar/ar.c(build is directory generated by configure) , function prev_mapelt line 775 : Select the false branch at this point (tail->next!=null is false) step 2 : In file build/ar/ar.c(build is directory generated by configure) , function prev_mapelt line 777 : Return null to caller step 3 : In file build/ar/ar.c(build is directory generated by configure) , function move_in_map line 1332 : Function prev_mapelt executes and stores the return value to prev (prev can be null) step 4 : In file build/ar/ar.c(build is directory generated by configure) , function move_in_map line 1333 : Store this->next to prev->next =
[Kernel-packages] [Bug 1941972] [NEW] Several bugs of file descriptor leak in bcc
Public bug reported: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. step 1 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : Select the false branch at this point (fp!=stdin is false) but did not close it step 1 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 805 : Select the true branch at this point (headstr!=null is true) step 4 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 809 : Select the true branch at this point (lp!=null is true) step 5 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 811 : Select the false branch at this point (fp!=stdout is false) but did not close it ** Affects: linux86 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux86 in Ubuntu. https://bugs.launchpad.net/bugs/1941972 Title: Several bugs of file descriptor leak in bcc Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. step 1 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 315 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function readinfile line 320 : Select the false branch at this point (fp!=stdin is false) but did not close it step 1 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Function fopen executes and stores the return value to fp step 2 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 801 : Select the false branch at this point (fp==null is false) step 3 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 805 : Select the true branch at this point (headstr!=null is true) step 4 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 809 : Select the true branch at this point (lp!=null is true) step 5 : In file build/copt/copt.c(build is directory generated by configure) , function writeoutf line 811 : Select the false branch at this point (fp!=stdout is false) but did not close it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941972/+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 1941973] [NEW] Several potential bugs of memory leak
Public bug reported: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. == step 1 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2088 : Allocate memory to result step 2 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2090 : Select the false branch at this point (result==null is false) step 3 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1756 : Function xmalloc executes and stores the return value to strings step 4 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1760 : Select the true branch at this point (read(indesc,strings,strs_size)!=strs_size is true), the allocated memory is leaked step 1 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1239 : Allocate memory to p step 2 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1240 : Select the true branch at this point (p!=null is true) step 3 : In file build/bcc/bcc.c(build is directory generated by configure) , function catstr line 284 : Function xalloc executes and returns step 4 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 762 : Function catstr executes and stores the return value to p step 5 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 763 : Select the true branch at this point (opt_v>1 is true) step 6 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 765 : Select the true branch at this point (opt_v>2 is true) step 7 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 753 : Select the false branch at this point (ihttps://bugs.launchpad.net/bugs/1941973 Title: Several potential bugs of memory leak Status in linux86 package in Ubuntu: New Bug description: Ubuntu version: 18.04 bcc version:0.16.17 I found several bugs in bcc , would you help me to check if these bugs are true?thanks for your patience. == step 1 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2088 : Allocate memory to result step 2 : In file build/ar/ar.c(build is directory generated by configure) , function xmalloc line 2090 : Select the false branch at this point (result==null is false) step 3 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1756 : Function xmalloc executes and stores the return value to strings step 4 : In file build/ar/ar.c(build is directory generated by configure) , function make_new_symdefs line 1760 : Select the true branch at this point (read(indesc,strings,strs_size)!=strs_size is true), the allocated memory is leaked step 1 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1239 : Allocate memory to p step 2 : In file build/bcc/bcc.c(build is directory generated by configure) , function xalloc line 1240 : Select the true branch at this point (p!=null is true) step 3 : In file build/bcc/bcc.c(build is directory generated by configure) , function catstr line 284 : Function xalloc executes and returns step 4 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 762 : Function catstr executes and stores the return value to p step 5 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 763 : Select the true branch at this point (opt_v>1 is true) step 6 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 765 : Select the true branch at this point (opt_v>2 is true) step 7 : In file build/bcc/bcc.c(build is directory generated by configure) , function run_unlink line 753 : Select the false branch at this point (ihttps://bugs.launchpad.net/ubuntu/+source/linux86/+bug/1941973/+subscriptions -- Mailing list: https://launchpad.net/~ke
[Kernel-packages] [Bug 1941967] [NEW] touchpad does not appear in devices and is not working after installing ubuntu 'Lenovo ideapad S340'
Public bug reported: After installing Ubuntu, the touchpad stopped responding and its not appearing in the devices list, tried installing and removing xserver- xorg-input-libinput and xserver-xorg-input-synaptics with no success ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 28 17:44:10 2021 InstallationDate: Installed on 2021-08-28 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "list of devices" https://bugs.launchpad.net/bugs/1941967/+attachment/5521371/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941967 Title: touchpad does not appear in devices and is not working after installing ubuntu 'Lenovo ideapad S340' Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: After installing Ubuntu, the touchpad stopped responding and its not appearing in the devices list, tried installing and removing xserver- xorg-input-libinput and xserver-xorg-input-synaptics with no success ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 28 17:44:10 2021 InstallationDate: Installed on 2021-08-28 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1941967/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
@72 opening salvo of " Ignorance doesn't mean knowledge, it is quite the opposite..." ...nd then completely misreading a simple line of text. k. where have I said it's something to do w/ the headerz??? I've only meant that the whole frigging exercise is to get the modules to work on my site while you offer a roundabout way (complete with the obligatory 0.05% increase in gowd knows what) and then admitting it'll break the darn modules... the rest of the stuff is... I'd best leave it be)) -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1941955] [NEW] New upstream release 2021.08.28
Public bug reported: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Hirsute) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: Confirmed ** Affects: wireless-regdb (Ubuntu Impish) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Impish) Importance: Undecided Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: wireless-regdb (Ubuntu Bionic) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Focal) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: wireless-regdb (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: wireless-regdb (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1941955 Title: New upstream release 2021.08.28 Status in wireless-regdb package in Ubuntu: In Progress Status in wireless-regdb source package in Bionic: Confirmed Status in wireless-regdb source package in Focal: Confirmed Status in wireless-regdb source package in Hirsute: Confirmed Status in wireless-regdb source package in Impish: In Progress Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1941955/+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 1909814] Re: Keyboard not working
Hi people, unfortunately I can't add information regarding the server systems' problems as I'm not affected. In fact I only have the few information that came in the bugzilla thread (https://bugzilla.kernel.org/show_bug.cgi?id=213031) and the fix patch stayed in kernel for only such a short period of time that I doubt anyone to be able to fix either this or "the other" issue. Atm. I can't see a clear plan on how to go on, so feel free to add your expertise, knowledge and opinion (here or there). TIA, Manuel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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 1941950] [NEW] linux-riscv: missing kernel signature
Public bug reported: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New ** Tags: riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1941950 Title: linux-riscv: missing kernel signature Status in linux-riscv package in Ubuntu: New Bug description: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1941950/+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 1941876] Re: Touchpad Sometimes Doesn't Work at Boot
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1941876 Title: Touchpad Sometimes Doesn't Work at Boot Status in linux package in Ubuntu: Confirmed Bug description: # Information cat /proc/version_signature: Ubuntu 5.4.0-81.91-generic 5.4.128 sudo lspci -vnvn: https://termbin.com/q7jt # Annoying Fix -In order to get the touchpad to work, you'll have to restart it one time (or more). # Kernel Boot Messages (When the touchpad is not working) [2.907747] i2c_designware i2c_designware.1: i2c_dw_handle: lost arbitration [3.915122] i2c_designware i2c_designware.1: controller timed out [3.915128] i2c_hid i2c-SYNA2B5A:00: failed to retrieve report from device [6.235034] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: knj6344 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 EcryptfsInUse: Yes InstallationDate: Installed on 2021-08-16 (11 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=bf191557-7167-4211-a91d-d9ef3b7412f1 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 Tags: uma Uname: Linux 5.4.0-81-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 01/14/2021 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941876/+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 1937897] Re: GPIO error logs in start and dmesg after update of kernel
These two error messages display when booting and closing live disk media using 'safe graphics' gpio gpiochip: (gpio_aaeon): tried to insert a GPIO chip with zero lines gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 they do not seem to upset the processes of the media this occurs with Kubunt Impish daily builds and also with Kubuntu 2004.3 daily build -- 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/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] After upgrade kernel to 5.11.0-25 which introduce some ODM patches from AAEON, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. Which fixes the issue introduced by Hirsute: 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices Impish: 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+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
