[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
Hi Marius,
> What actually is the effect of the denial? Will qemu not use more than one
> CPU,
> or is it something less harmful?
Since the new interface is arch specific and new the code does fall back
tot he old way.
226 /* On some architectures it is possible to distinguish between configured
227and active cpus. */
228 int
229 __get_nprocs_conf (void)
230 {
231 int result = read_sysfs_file ("/sys/devices/system/cpu/possible");
232 if (result != 0)
233 return result;
234
235 /* Fall back to /proc/stat and sched_getaffinity. */
236 return get_nprocs_fallback ();
237 }
Due to that, even when denied it gets the right number (as it had
before).
Once with and without isolation blocking access.
ubuntu@k2:/tmp$ ./testsysconf
_SC_NPROCESSORS_CONF 3
ubuntu@k2:/tmp$ sudo aa-exec -p test -- ./testsysconf
_SC_NPROCESSORS_CONF 3
It only has a real difference on systems where the new code was needed in the
first place.
Those are usually rather massive systems which start at lower cpu counts but
might hot-plug them later - on those with the denial falling back you'd only
get a lower than the real potential max number.
The code that hits this in your case is libnuma on initialization, unless you
are very deep into numa control on very huge systems using cpu hotplug you
won't see any effect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1989073
Title:
AppArmor DENIES reading of /sys/devices/system/cpu/possible
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Kinetic:
Confirmed
Bug description:
libvirt 8.6.0-0ubuntu1
apparmor 3.0.7-1ubuntu1
Creating a VM with virt-install produces this AppAmore denial:
AVC apparmor="DENIED" operation="open"
profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc"
name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu-
system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
Creation of the VM is successful. This is with nested virtualization.
This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor
3.0.7-1ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
Thanks a lot everyone! What actually is the effect of the denial? Will qemu not use more than one CPU, or is it something less harmful? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989073 Title: AppArmor DENIES reading of /sys/devices/system/cpu/possible Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Kinetic: Confirmed Bug description: libvirt 8.6.0-0ubuntu1 apparmor 3.0.7-1ubuntu1 Creating a VM with virt-install produces this AppAmore denial: AVC apparmor="DENIED" operation="open" profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc" name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu- system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Creation of the VM is successful. This is with nested virtualization. This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor 3.0.7-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
This has now landed upstream, on the master branch as c159d0925 Allow access to possible cpus for glibc-2.36 and has been cherry-picked back to 3.1, 3.0, 2.13, and 2.12 branches. This schedules it for release in the 2.12.4 and 2.13.7, 3.0.8 releases this week. Unfortunately 3.1.2 was cut last week so it just misses that release. I will look at assigning resources to this, I am not sure which of us will pick it up yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989073 Title: AppArmor DENIES reading of /sys/devices/system/cpu/possible Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Kinetic: Confirmed Bug description: libvirt 8.6.0-0ubuntu1 apparmor 3.0.7-1ubuntu1 Creating a VM with virt-install produces this AppAmore denial: AVC apparmor="DENIED" operation="open" profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc" name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu- system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Creation of the VM is successful. This is with nested virtualization. This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor 3.0.7-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
Hi, This is a serious bug. CMS_final() finalises the structure cms. Its purpose is to perform any operations necessary on cms. CMS_final() call to SMIME_crlf_copy() and not checking the return value from SMIME_crlf_copy() so even SMIME_crlf_copy() fail, CMS_final() will return ok but with wrong CMS data. SMIME_crlf_copy() copies data from in_bio to out_bio and it's used at the final op on cms structure (for example before writing or sending cms object) SMIME_crlf_copy will fail if some data in cms is missing or wrong. Scenario to reproduce: Create cms signature structure without the signature value and send it to CMS_final(). CMS_final() will return ok even if the CMS_final() fails. This causes the software to continue with incorrect information and pass it on even though it is incorrect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Triaged Status in openssl source package in Jammy: Triaged Status in openssl source package in Kinetic: Triaged Bug description: https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993571] Re: After 5.19.0-15, intel wifi 6 no longer available
The 'unavailability' of the wifi interface is apparently a path- dependent bug in network manager or a related component. I was not able to fix it in place, but a scratch reinstall of Kinetic fixed it. So it can't be the kernel. ** Package changed: linux (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1993571 Title: After 5.19.0-15, intel wifi 6 no longer available Status in network-manager package in Ubuntu: Confirmed Bug description: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1993571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993571] [NEW] After 5.19.0-15, intel wifi 6 no longer available
You have been subscribed to a public bug: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kinetic -- After 5.19.0-15, intel wifi 6 no longer available https://bugs.launchpad.net/bugs/1993571 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996550] [NEW] Bionic: system update killed networking (sort of)
Public bug reported: Filing for a friend: I have several Ubuntu servers that all just quit working at the same time. By “quit working” I mean they take forever to boot and applications do not work on them correctly until after about 30 minutes (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help systemd[1]: Started Dispatcher daemon for systemd-networkd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Description changed: Filing for a friend: - I have several UBNT servers that all just quit working at the same time. - By “quitworking” I mean they take forever to boot and applications to do - not work on them correctly. + I have several Ubuntu servers that all just quit working at the same + time. By “quit working” I mean they take forever to boot and + applications do not work on them correctly until after about 30 minutes + (and the applications have been restarted). Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operati
[Touch-packages] [Bug 1996552] [NEW] The liborc-0.4-dev package contains binarys
Public bug reported: -dev is for header files only and this strews with multiarch ** Affects: orc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to orc in Ubuntu. https://bugs.launchpad.net/bugs/1996552 Title: The liborc-0.4-dev package contains binarys Status in orc package in Ubuntu: New Bug description: -dev is for header files only and this strews with multiarch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1996552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996550] [NEW] Bionic: system update killed networking (sort of)
You have been subscribed to a public bug: Filing for a friend: I have several UBNT servers that all just quit working at the same time. By “quitworking” I mean they take forever to boot and applications to do not work on them correctly. Nov 14 16:27:08 help systemd[1]: Started OpenBSD Secure Shell server. Nov 14 16:27:08 help whoopsie[775]: [16:27:08] Using lock path: /var/lock/whoopsie/lock Nov 14 16:27:09 help whoopsie[775]: [16:27:09] Could not get the Network Manager state: Nov 14 16:27:09 help whoopsie[775]: [16:27:09] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager has not provided by any .service files Nov 14 16:27:09 help networkd-dispatcher[684]: WARNING: systemd-networkd is not running, output will be incomplete. Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=1, name='lo', type='loopback', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help networkd-dispatcher[684]: ERROR:Unknown state for interface NetworkctlListState(idx=2, name='eth0', type='ether', operational='n/a', administrative='unmanaged'): n/a Nov 14 16:27:09 help networkd-dispatcher[684]: Traceback (most recent call last): Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 286, in trigger_all Nov 14 16:27:09 help networkd-dispatcher[684]: force=True) Nov 14 16:27:09 help networkd-dispatcher[684]: File "/usr/bin/networkd-dispatcher", line 338, in handle_state Nov 14 16:27:09 help networkd-dispatcher[684]: raise UnknownState(operational_state) Nov 14 16:27:09 help networkd-dispatcher[684]: UnknownState: n/a Nov 14 16:27:09 help systemd[1]: Started Dispatcher daemon for systemd-networkd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- Bionic: system update killed networking (sort of) https://bugs.launchpad.net/bugs/1996550 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982483]
Created attachment 303138 AlsaInfo.txt Perhaps this has even more contents. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: I have tried: options snd-hda-intel model=alc285-hp-amp-init options snd-hda-intel model=alc274-dell-aio and newer kernels up to 5.19-rc6. 21: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.2CriaNVEdN5 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x7ad0 SubVendor: pci 0x103c "Hewlett-Packard Company" SubDevice: pci 0x89e9 Revision: 0x11 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x6105238000-0x610523bfff (rw,non-prefetchable) Memory Range: 0x610500-0x61050f (rw,non-prefetchable) IRQ: 161 (1098 events) Module Alias: "pci:v8086d7AD0sv103Csd89E9bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=new, avail=yes, need=no, active=unknown <6>[3.582352] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC274: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker <6>[3.582359] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) <6>[3.582362] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) <6>[3.582364] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 <6>[3.582366] snd_hda_codec_realtek hdaudioC0D0:inputs: <6>[3.582367] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 <6>[3.582369] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 Alsa-info: https://alsa- project.org/db/?f=ed6190cfc9d9eb1c758c6c3106dd236b150f5b31 Here is a kernel bug report: https://bugzilla.kernel.org/show_bug.cgi?id=216139 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 1560 F pulseaudio /dev/snd/controlC0: ernst 1560 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (143 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1006-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.0.0-1006.6-oem 6.0.0 RelatedPackageVersions: linux-restricted-modules-6.0.0-1006-oem N/A linux-backports-modules-6.0.0-1006-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 Tags: jammy wayland-session Uname: Linux 6.0.0-1006-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940996]
The release/2.34/master branch has been updated by Florian Weimer : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=86a701a20479dfbc23540b3143fd5b28660a2447 commit 86a701a20479dfbc23540b3143fd5b28660a2447 Author: Paul Eggert Date: Tue Sep 21 07:47:45 2021 -0700 regex: copy back from Gnulib Copy regex-related files back from Gnulib, to fix a problem with static checking of regex calls noted by Martin Sebor. This merges the following changes: * New macro __attribute_nonnull__ in misc/sys/cdefs.h, for use later when copying other files back from Gnulib. * Use __GNULIB_CDEFS instead of __GLIBC__ when deciding whether to include bits/wordsize.h etc. * Avoid duplicate entries in epsilon closure table. * New regex.h macro _REGEX_NELTS to let regexec say that its pmatch arg should contain nmatch elts. Use that for regexec, instead of __attr_access (which is incorrect). * New regex.h macro _Attr_access_ which is like __attr_access except portable to non-glibc platforms. * Add some DEBUG_ASSERTs to pacify gcc -fanalyzer and to catch recently-fixed performance bugs if they recur. * Add Gnulib-specific stuff to port the dynarray- and lock-using parts of regex code to non-glibc platforms. * Fix glibc bug 11053. * Avoid some undefined behavior when popping an empty fail stack. (cherry picked from commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to david.renoux from comment #714) > Any news from Lenovo support ? No luck from my side, support stated that they don't support non Microsoft platforms for this model. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
None. Whenever I picked up their calls, it would hang up, so the ticket would close. I'm going to try their support chat when I have time... Whenever that will be. On 11/4/22 12:41, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #714 from david.ren...@protonmail.com --- > Any news from Lenovo support ? > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Any news from Lenovo support ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993403] Re: Merge heimdal from Debian unstable for lunar
** Summary changed: - Merge heimdal from Debian unstable for l-series + Merge heimdal from Debian unstable for lunar ** Changed in: heimdal (Ubuntu) Milestone: None => ubuntu-22.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1993403 Title: Merge heimdal from Debian unstable for lunar Status in heimdal package in Ubuntu: New Bug description: Scheduled-For: ubuntu-22.11 Upstream: tbd Debian: 7.7.0+dfsg-6 Ubuntu: 7.7.0+dfsg-4ubuntu1 ### New Debian Changes ### heimdal (7.7.0+dfsg-6) unstable; urgency=medium * Retry deleting dangling windc.so again. Closes: #577229. * Create /var/lib/heimdal-kdc/m-key not /var/lib/heimdal-kdc/heimdal.mkey. Closes: #964008. * Disable use of -rpath in krb5-config.heimdal. Closes: #868840. -- Brian May Mon, 05 Sep 2022 08:35:33 +1000 heimdal (7.7.0+dfsg-5) unstable; urgency=medium * Fix missing closefrom symbol. Closes: #1016884, #1017244. * Fix spelling of dependency in changelog. * Fix override_dh_fixperms typo, use 700 for /var/lib/heimdal-kdc/ * Remove default --parallel from dh call. * Remove unused debian/upstream/signing-key.asc key. * Fix Multi-Arch headers. heimdal-multidev is not co-installable, so heimdal-dev cannot be co-installable either. -- Brian May Fri, 02 Sep 2022 07:59:59 +1000 heimdal (7.7.0+dfsg-4) unstable; urgency=medium * Delete dependency on install-info. Closes: #1013735. * Non-maintainer upload. * Reduce Build-Depends: (Closes: #980531) + Drop unused libhesiod-dev. + Drop unused libperl4-corelibs-perl as cf/make-proto.pl no longer uses it. + Drop unused libx11-dev, libxau-dev, libxt-dev, ss-dev, and x11proto-core-dev. + Clean generated C tables to actually rebuild them using python3. -- Brian May Mon, 27 Jun 2022 10:36:10 +1000 heimdal (7.7.0+dfsg-3) unstable; urgency=high * Fix CVE-2021-3671: A null pointer de-reference was found in the way samba kerberos server handled missing sname in TGS-REQ. Closes: #996586. * Fix autoconf 2.7 issues. -- Brian May Wed, 17 Nov 2021 12:12:45 +1100 heimdal (7.7.0+dfsg-2) unstable; urgency=medium * Build using python3. Closes: #936695, #960032. -- Brian May Tue, 12 May 2020 06:56:04 +1000 heimdal (7.7.0+dfsg-1) unstable; urgency=medium * New upstream version. * Fix CVE-2019-14870: The DelegationNotAllowed Kerberos feature restriction was not being applied when processing protocol transition requests (S4U2Self), in the AD DC KDC. Closes: #946786. -- Brian May Tue, 17 Dec 2019 20:23:41 +1100 heimdal (7.5.0+dfsg-3) unstable; urgency=high * CVE-2018-16860: Samba AD DC S4U2Self/S4U2Proxy unkeyed checksum. Closes: #928966. * CVE-2019-12098: Always confirm PA-PKINIT-KX for anon PKINIT. Closes: #929064. * Update test certificates to pre 2038 expiry. Closes: #923930. -- Brian May Tue, 21 May 2019 18:04:35 +1000 heimdal (7.5.0+dfsg-2.1) unstable; urgency=medium * Non-maintainer upload * Add patch to create headers before building (Closes: 906623) -- Hilko Bengen Sun, 28 Oct 2018 15:10:44 +0100 heimdal (7.5.0+dfsg-2) unstable; urgency=medium * Replace 'MAXHOSTNAMELEN' with 'MaxHostNameLen' in kdc/kx509.c for The Hurd. Closes: #900079. -- Brian May Sat, 02 Jun 2018 10:01:46 +1000 heimdal (7.5.0+dfsg-1) unstable; urgency=high * New upstream version. (Closes: #850723) + CVE-2017-17439: Remote unauthenticated DoS in Heimdal-KDC 7.4 (Closes: #878144, #868157) + Refresh patches. * Bump Standards-Version to 4.1.2 and compat level to 10. + Remove explicit reference to dh-autoreconf. * Use uscan to get orig source. + Refrain from mangling some bundled RFC texts; just exclude the mas they are not installed into any binary anyway. + Update d/copyright to DEP-5. + Can now use standard uscan/gbp/pristine-tar workflow. * Fix some lintian errors/warnings. + Strip trailing whitespace from changelog. + Fix some duplicate long descriptions. + Use optional priority everywhere. + Update/remove some overrides. ### Old Ubuntu Delta ### heimdal (7.7.0+dfsg-4ubuntu1) kinetic; urgency=medium * Merge with Debian unstable (LP: #1971280). Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. (LP #1934936) - d/libroken18-heimdal.symbols: Remove symbol rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226 Applied verbatim debdiff from Heinrich Schuchardt (xypron). (LP #1945787) -- Bryce Harrington Wed, 20 Jul 2022 16:52:39 -0700 To manage notification
[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
Submitted upstream: https://lists.ubuntu.com/archives/apparmor/2022-November/012528.html Once discussed and accepted there I suggest a backport to Kinetic. I hope this debug and patch helps, but to manage expectations, I'd hope/expect that someone usually looking after apparmor does that follow on step then. Could someone please agree to take it over from here and comment on this bug? P.S. I mostly want to avoid stepping on someones toes, if you want me to upload it to kinetic I can do so, let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989073 Title: AppArmor DENIES reading of /sys/devices/system/cpu/possible Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Kinetic: Confirmed Bug description: libvirt 8.6.0-0ubuntu1 apparmor 3.0.7-1ubuntu1 Creating a VM with virt-install produces this AppAmore denial: AVC apparmor="DENIED" operation="open" profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc" name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu- system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Creation of the VM is successful. This is with nested virtualization. This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor 3.0.7-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996471] Re: launchpad's "report a bug" hangs in bug data processing
** Package changed: apport (Ubuntu) => launchpad -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1996471 Title: launchpad's "report a bug" hangs in bug data processing Status in Launchpad itself: New Bug description: I encountered a bug in nautilus and wanted to report it by running "ubuntu-bug nautilus". A browser window was opened with the message "Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete." being displayed for 10 minutes or so. I would expect it to complete processing within 10-30s: it looks like it got stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1996471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
Just for completeness, apt-cacher version 3.7.4-1build1 on a Ubuntu 22.04 system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
Hmm, I did find what was causing it. I had a proxy configured for apt pointing at apt-cacher-ng on a local system. When I removed the proxy from the configuration, apt had no issues downloading lists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1956039 Title: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) Status in apt package in Ubuntu: Confirmed Bug description: Updating Jammy fails with: Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
Reported upstream at https://gitlab.com/apparmor/apparmor/-/issues/283 ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #283 https://gitlab.com/apparmor/apparmor/-/issues/283 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1989073 Title: AppArmor DENIES reading of /sys/devices/system/cpu/possible Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Kinetic: Confirmed Bug description: libvirt 8.6.0-0ubuntu1 apparmor 3.0.7-1ubuntu1 Creating a VM with virt-install produces this AppAmore denial: AVC apparmor="DENIED" operation="open" profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc" name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu- system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Creation of the VM is successful. This is with nested virtualization. This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor 3.0.7-1ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989073] Re: AppArmor DENIES reading of /sys/devices/system/cpu/possible
That is the commit causing the change [1] in behavior.
That is pretty low level (in libc6) and will probably hit anything that
links against libnuma.
I think the fix should therefore go into
/etc/apparmor.d/abstractions/base
Today it has:
# glibc's sysconf(3) routine to determine free memory, etc
@{PROC}/meminfor,
@{PROC}/stat r,
@{PROC}/cpuinfor,
@{sys}/devices/system/cpu/ r,
@{sys}/devices/system/cpu/online r,
And due to [1] I think this needs to get:
@{sys}/devices/system/cpu/possible r,
That is still missing in upstreams [2] current base profile.
Gladly it isn't too fatal, but still bad.
Retargetting this to the apparmor package.
[1]: https://sourceware.org/git/?p=glibc.git;a=commit;h=97a912f7a832a6
[2]:
https://gitlab.com/apparmor/apparmor/-/blob/master/profiles/apparmor.d/abstractions/base#L98
** Package changed: libvirt (Ubuntu) => apparmor (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1989073
Title:
AppArmor DENIES reading of /sys/devices/system/cpu/possible
Status in apparmor package in Ubuntu:
Confirmed
Status in apparmor source package in Kinetic:
Confirmed
Bug description:
libvirt 8.6.0-0ubuntu1
apparmor 3.0.7-1ubuntu1
Creating a VM with virt-install produces this AppAmore denial:
AVC apparmor="DENIED" operation="open"
profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc"
name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu-
system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0
Creation of the VM is successful. This is with nested virtualization.
This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor
3.0.7-1ubuntu1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1989073/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1989073] [NEW] AppArmor DENIES reading of /sys/devices/system/cpu/possible
You have been subscribed to a public bug: libvirt 8.6.0-0ubuntu1 apparmor 3.0.7-1ubuntu1 Creating a VM with virt-install produces this AppAmore denial: AVC apparmor="DENIED" operation="open" profile="libvirt-974c9859-e682-4f5d-b0cb-dcf3d60185fc" name="/sys/devices/system/cpu/possible" pid=2522 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Creation of the VM is successful. This is with nested virtualization. This did not happen with libvirt 8.0.0-1ubuntu8 and apparmor 3.0.7-1ubuntu1. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: apparmor (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Tags: kinetic regression-release -- AppArmor DENIES reading of /sys/devices/system/cpu/possible https://bugs.launchpad.net/bugs/1989073 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
Hi Gil, Can you explain a bit the actual impact of this bug and/or a scenario to reproduce. The commit doesn't give us a lot of details and the issue appears to be possibly quite serious but without diving deep into the code and possibly writing a reproducer from scratch ourselves, it is hard to be sure we properly understand it. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Triaged Status in openssl source package in Jammy: Triaged Status in openssl source package in Kinetic: Triaged Bug description: https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1993037] Re: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course
My system was upgraded from 20.04 LTS installation, which in turn was upgraded from 18.04 and some number of LTS releases back (since probably 8.04 when it was upgraded from some older Debian). I don't have separate /usr FS on this system, and usrmerge was not pulled as a dependency during any of the upgrades. Is this package essential now to solve the problem with debianutils ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1993037 Title: Ubuntu 22.04, debianutils moved run-parts into /usr/bin, breaking systemd-cron in the course Status in debianutils package in Ubuntu: Incomplete Status in systemd-cron package in Ubuntu: New Bug description: (Found in Ubuntu 22.04 LTS) package debianutils keeps run-parts executable in /usr/bin/ while package systemd-cron tries to find it in /bin/ $ which run-parts /usr/bin/run-parts $ dpkg -S `which run-parts` debianutils: /usr/bin/run-parts $ grep =/bin/run /lib/systemd/system/cron* /lib/systemd/system/cron-daily.service:ExecStart=/bin/run-parts --report /etc/cron.daily /lib/systemd/system/cron-hourly.service:ExecStart=/bin/run-parts --report /etc/cron.hourly /lib/systemd/system/cron-monthly.service:ExecStart=/bin/run-parts --report /etc/cron.monthly /lib/systemd/system/cron-weekly.service:ExecStart=/bin/run-parts --report /etc/cron.weekly Because of that, cron-daily.serice gets info "failed" state soon after system reboot. Please resolve the problem to make systemd-cron more usable. Thanks in advance for your help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debianutils/+bug/1993037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996471] Re: launchpad's "report a bug" hangs in bug data processing
** Package changed: ubuntu => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1996471 Title: launchpad's "report a bug" hangs in bug data processing Status in apport package in Ubuntu: New Bug description: I encountered a bug in nautilus and wanted to report it by running "ubuntu-bug nautilus". A browser window was opened with the message "Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete." being displayed for 10 minutes or so. I would expect it to complete processing within 10-30s: it looks like it got stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1996471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996471] [NEW] launchpad's "report a bug" hangs in bug data processing
You have been subscribed to a public bug: I encountered a bug in nautilus and wanted to report it by running "ubuntu-bug nautilus". A browser window was opened with the message "Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete." being displayed for 10 minutes or so. I would expect it to complete processing within 10-30s: it looks like it got stuck. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- launchpad's "report a bug" hangs in bug data processing https://bugs.launchpad.net/bugs/1996471 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996494] Re: CVE-2022-2309: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash)
** Changed in: libxml2 (Ubuntu) Status: New => Confirmed ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1996494 Title: CVE-2022-2309: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash) Status in libxml2 package in Ubuntu: Confirmed Bug description: NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, given a vulnerable code sequence in the application. The vulnerability is caused by the iterwalk function (also used by the canonicalize function). Such code shouldn’t be in wide-spread use, given that parsing + iterwalk would usually be replaced with the more efficient iterparse function. However, an XML converter that serialises to C14N would also be vulnerable, for example, and there are legitimate use cases for this code sequence. If untrusted input is received (also remotely) and processed via iterwalk function, a crash can be triggered. Reference: https://ubuntu.com/security/CVE-2022-2309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1996494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1994027 Title: Can't move window by drag and drop by using touch screen Status in Mutter: New Status in OEM Priority Project: New Status in gtk+3.0 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: [Summary] For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed. [Steps to reproduce] 1. Install the 22.04 2. Boot and login 3. Open a folder 4. Drag-n-drop the folder with finger touch 5. Drag-n-drop the folder with the Wacom Pen [Expected result] Both finger touch and wacom pen work normally. [Actual result] Wacom Pen works normally, finger touch can not move the folder. [Failure rate] 100% [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop` output] [Other Information] xorg 1:7.7+23ubuntu2 mutter-common 42.2-0ubuntu1 gnome-shell 42.4-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1994027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996496] Re: Cannot connect to Ubuntu BLE servers
** Attachment added: "log of nRF-Connect"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1996496/+attachment/5630720/+files/nRF-Connect-Log%202022-11-11%2023_49_24.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1996496
Title:
Cannot connect to Ubuntu BLE servers
Status in bluez package in Ubuntu:
New
Bug description:
I'm on Ubuntu 22.04.1 LTS, using bluez 5.65 (built from sources by this
guide: https://docs.embeddedts.com/BLE_Examples), and doing the following steps:
1. Run `python3 /usr/local/lib/bluez/test/example-advertisement`
2. Run `/usr/local/lib/bluez/test/example-gatt-server`
3. Use nRF Connect app on Android 9 phone to connect to the
"TestAdvertisement" device
The outcome is that the phone app tries to connect, but fails, leaving
me with a view of the GATT services and characteristics, but with no
way of accessing (read/write/notify) it. I have tried many other BLE
server implementations, but for the bug reporting I focused on the
most trusted reference.
Full logs are attached. The relevant part of the btmon log is here:
@ MGMT Event: Device Connected (0x000b) plen 13 {0x0001} [hci0] 945.575247
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Flags: 0x
Data length: 0
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2 #32 [hci0]
945.575351
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
@ RAW Open: btmon (privileged) version 2.22 {0x0002} 945.575453
@ RAW Close: btmon {0x0002} 945.575462
> HCI Event: LE Meta Event (0x3e) plen 4 #33 [hci0] 945.575984
LE Channel Selection Algorithm (0x14)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Algorithm: #1 (0x00)
> HCI Event: LE Meta Event (0x3e) plen 6 #34 [hci0] 945.576990
LE Advertising Set Terminated (0x12)
Status: Success (0x00)
Handle: 1
Connection handle: 3585
Number of completed extended advertising events: 0
> HCI Event: Command Status (0x0f) plen 4 #35 [hci0] 945.578094
LE Read Remote Used Features (0x08|0x0016) ncmd 1
Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
< HCI Command: Disconnect (0x01|0x0006) plen 3 #36 [hci0] 945.578193
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Remote User Terminated Connection (0x13)
> HCI Event: Command Status (0x0f) plen 4 #37 [hci0] 945.579984
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4 #38 [hci0] 945.652123
Status: Success (0x00)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection Terminated By Local Host (0x16)
@ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 945.652224
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection terminated by local host (0x02)
The Additional information:
$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: BC:6E:E2:D0:B1:27 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:3074 acl:43 sco:0 events:194 errors:0
TX bytes:7295 acl:42 sco:0 commands:125 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'epitos'
Class: 0x6c010c
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Laptop
HCI Version: (0xc) Revision: 0x3484
LMP Version: (0xc) Subversion: 0x3484
Manufacturer: Intel Corp. (2)
$ bluetoothctl
Agent registered
[CHG] Controller BC:6E:E2:D0:B1:27 Pairable: yes
[bluetooth]# show
Controller BC:6E:E2:D0:B1:27 (public)
Name: epitos
Alias: epitos
Class: 0x006c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Vendor specific (12345678-1234-5678-1234-56789abcdef0)
UUID: Device Information (180a--1000-8000-00805f9b34fb)
UUID: Battery Service (180f--1000-8000-00805f9b34fb)
UUID: Heart Rate (180d--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0540
Discovering: no
Roles: central
Roles: peripheral
Advertising Fe
[Touch-packages] [Bug 1996496] [NEW] Cannot connect to Ubuntu BLE servers
Public bug reported:
I'm on Ubuntu 22.04.1 LTS, using bluez 5.65 (built from sources by this guide:
https://docs.embeddedts.com/BLE_Examples), and doing the following steps:
1. Run `python3 /usr/local/lib/bluez/test/example-advertisement`
2. Run `/usr/local/lib/bluez/test/example-gatt-server`
3. Use nRF Connect app on Android 9 phone to connect to the "TestAdvertisement"
device
The outcome is that the phone app tries to connect, but fails, leaving
me with a view of the GATT services and characteristics, but with no way
of accessing (read/write/notify) it. I have tried many other BLE server
implementations, but for the bug reporting I focused on the most trusted
reference.
Full logs are attached. The relevant part of the btmon log is here:
@ MGMT Event: Device Connected (0x000b) plen 13 {0x0001} [hci0] 945.575247
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Flags: 0x
Data length: 0
< HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2 #32 [hci0]
945.575351
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
@ RAW Open: btmon (privileged) version 2.22 {0x0002} 945.575453
@ RAW Close: btmon {0x0002} 945.575462
> HCI Event: LE Meta Event (0x3e) plen 4 #33 [hci0] 945.575984
LE Channel Selection Algorithm (0x14)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Algorithm: #1 (0x00)
> HCI Event: LE Meta Event (0x3e) plen 6 #34 [hci0] 945.576990
LE Advertising Set Terminated (0x12)
Status: Success (0x00)
Handle: 1
Connection handle: 3585
Number of completed extended advertising events: 0
> HCI Event: Command Status (0x0f) plen 4 #35 [hci0] 945.578094
LE Read Remote Used Features (0x08|0x0016) ncmd 1
Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
< HCI Command: Disconnect (0x01|0x0006) plen 3 #36 [hci0] 945.578193
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Remote User Terminated Connection (0x13)
> HCI Event: Command Status (0x0f) plen 4 #37 [hci0] 945.579984
Disconnect (0x01|0x0006) ncmd 1
Status: Success (0x00)
> HCI Event: Disconnect Complete (0x05) plen 4 #38 [hci0] 945.652123
Status: Success (0x00)
Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection Terminated By Local Host (0x16)
@ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 945.652224
LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
Reason: Connection terminated by local host (0x02)
The Additional information:
$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: BC:6E:E2:D0:B1:27 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING PSCAN
RX bytes:3074 acl:43 sco:0 events:194 errors:0
TX bytes:7295 acl:42 sco:0 commands:125 errors:0
Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: PERIPHERAL ACCEPT
Name: 'epitos'
Class: 0x6c010c
Service Classes: Rendering, Capturing, Audio, Telephony
Device Class: Computer, Laptop
HCI Version: (0xc) Revision: 0x3484
LMP Version: (0xc) Subversion: 0x3484
Manufacturer: Intel Corp. (2)
$ bluetoothctl
Agent registered
[CHG] Controller BC:6E:E2:D0:B1:27 Pairable: yes
[bluetooth]# show
Controller BC:6E:E2:D0:B1:27 (public)
Name: epitos
Alias: epitos
Class: 0x006c010c
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x00b4
Pairable: yes
UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb)
UUID: PnP Information (1200--1000-8000-00805f9b34fb)
UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
UUID: Headset (1108--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Vendor specific (12345678-1234-5678-1234-56789abcdef0)
UUID: Device Information (180a--1000-8000-00805f9b34fb)
UUID: Battery Service (180f--1000-8000-00805f9b34fb)
UUID: Heart Rate (180d--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0540
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x01 (1)
SupportedInstances: 0x07 (7)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# devices
Device 90:00:DB:0D:50:8C SM-G800F
[bluetooth]# info 90:00:DB:0D:50:8C
Device 90:00:DB:0D:50:8C (public)
Name: SM-G800F
Alias: SM-G800F
Class: 0x005a020c
Icon: phone
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb)
UUID: Audio Source (110a--1000-800
