[Touch-packages] [Bug 1973610] Re: Bluetooth will not stay on or connect to devices when on
We haven't had any bug reports like this that weren't hardware-specific. Maybe to avoid confusion here we should choose just one Bluetooth chip. Either the USB dongle (Broadcom Corp. BCM20702A0) or the internal chip (Intel AX210/AX211/AX411). -- 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/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+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 1973610] Re: Bluetooth will not stay on or connect to devices when on
For the USB dongle there are kernel messages: [ 34.065571] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 34.065744] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0a5c-21e8.hcd' [ 34.065757] Bluetooth: hci0: BCM: 'brcm/BCM-0a5c-21e8.hcd' ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973610/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I just installed the -proposed package and still no dice. Could someone post (here or elsewhere) a instructions for getting this working from scratch as of today? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks
The attachment "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- 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/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+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 1973654] [NEW] Using debian-installer on a server with a Let's Encrypt cert dies
Public bug reported: While using debian-installer to install Ubuntu Focal, I get the following error: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] There was an issue in 2021, where the "DST_Root_CA_X3.crt" certificate used by Let's Encrypt expired. https://letsencrypt.org/docs/dst-root-ca-x3-expiration- september-2021/ The problem is that the certificate is still included in the "ca- certificates_20190110ubuntu1_all.deb" that debian-installer fetches during install. May 16 22:02:17 debootstrap: Preparing to unpack .../ca-certificates_20190110ubuntu1_all.deb ... May 16 22:02:17 debootstrap: Unpacking ca-certificates (20190110ubuntu1) ... May 16 22:02:31 debootstrap: Setting up ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Processing triggers for ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Running hooks in /etc/ca-certificates/update.d... Because the certificate is expired, debian-installer dies with: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] te is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] Can Ubuntu update the ca-certificate .deb pulled during install to one that does not have DST_Root_CA_X3.crt? Thanks. ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1973654 Title: Using debian-installer on a server with a Let's Encrypt cert dies Status in ca-certificates package in Ubuntu: New Bug description: While using debian-installer to install Ubuntu Focal, I get the following error: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] There was an issue in 2021, where the "DST_Root_CA_X3.crt" certificate used by Let's Encrypt expired. https://letsencrypt.org/docs/dst-root-ca-x3-expiration- september-2021/ The problem is that the certificate is still included in the "ca- certificates_20190110ubuntu1_all.deb" that debian-installer fetches during install. May 16 22:02:17 debootstrap: Preparing to unpack .../ca-certificates_20190110ubuntu1_all.deb ... May 16 22:02:17 debootstrap: Unpacking ca-certificates (20190110ubuntu1) ... May 16 22:02:31 debootstrap: Setting up ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Processing triggers for ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Running hooks in /etc/ca-certificates/update.d... Because the certificate is expired, debian-installer dies with: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] te is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] Can Ubuntu update the ca-certificate .deb pulled during install to one that does not have DST_Root_CA_X3.crt? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1973654/+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 1966886] Re: ssh-copy-id and Dropbear Server
Just to add a voice to this: we see the same things migrating from 18.04 to 22.04 while controlling some embedded ARM/Debian devices running dropbear. The key are indeed appearing in the wrong place as stated above and the log in does not proceed as expected. We can work around this for production systems, but the behaviour is confusing (and obviously not consistent between 18.04 and 22.04). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1966886 Title: ssh-copy-id and Dropbear Server Status in openssh package in Ubuntu: Triaged Bug description: on Dropbear SSH Servers ssh-copy-id installs the key in /etc/dropbear/authorized_keys only the openwrt dropbear server uses that path https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch the upstream dropbear server uses the normal path ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+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 1973642] Re: [REGRESSION] Unable to connect to EAP-TLS networks
** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+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 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
but can connect to Ubuntu 20.4
Status in openssh package in Ubuntu:
Expired
Bug description:
Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a
Windows 10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
"boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
],
The user-data file was:
#cloud-config
autoinstall:
version: 1
identity:
realname: mclibre
hostname: ubuntu
password:
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
locale: es_ES.UTF-8
keyboard:
layout: es
network:
network:
version: 2
ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
ssh:
install-server: true
late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/'
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/"
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using
packer 1.5.6 but Packer can't create the image because once the installation is
done, after rebooting the SSH server does not answer (the packer log error
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+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 1901752] Re: Can’t connect to a specific Wi-Fi network with wpa_supplicant
[Expired for wpa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: wpa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1901752 Title: Can’t connect to a specific Wi-Fi network with wpa_supplicant Status in wpa package in Ubuntu: Expired Bug description: This is the error I get if I try to connect to a specific Wi-Fi network on Ubuntu 20.10 with wpa_supplicant: Error: Connection activation failed: (7) Secrets were required, but not provided. If I use iwd instead, everything works fine. I also can connect to other networks with wpa_supplicant. I had the same issue with the Live USB. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wpasupplicant 2:2.9-1ubuntu8 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 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 Date: Tue Oct 27 20:55:39 2020 InstallationDate: Installed on 2020-10-26 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1901752/+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 1973654] Re: Using debian-installer on a server with a Let's Encrypt cert dies
I believe this is caused by debootstrap - it only uses packages from the release pocket (and this is frozen from the time Ubuntu 20.04 LTS was originally released). This is a known issue https://askubuntu.com/questions/744684/latest-security-updates-with- debootstrap but I am not sure if there is much you can do to get debian- installer to say use multistrap instead of debootstrap. ** Package changed: ca-certificates (Ubuntu) => debian-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1973654 Title: Using debian-installer on a server with a Let's Encrypt cert dies Status in debian-installer package in Ubuntu: New Bug description: While using debian-installer to install Ubuntu Focal, I get the following error: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] There was an issue in 2021, where the "DST_Root_CA_X3.crt" certificate used by Let's Encrypt expired. https://letsencrypt.org/docs/dst-root-ca-x3-expiration- september-2021/ The problem is that the certificate is still included in the "ca- certificates_20190110ubuntu1_all.deb" that debian-installer fetches during install. May 16 22:02:17 debootstrap: Preparing to unpack .../ca-certificates_20190110ubuntu1_all.deb ... May 16 22:02:17 debootstrap: Unpacking ca-certificates (20190110ubuntu1) ... May 16 22:02:31 debootstrap: Setting up ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Processing triggers for ca-certificates (20190110ubuntu1) ... May 16 22:02:40 debootstrap: Running hooks in /etc/ca-certificates/update.d... Because the certificate is expired, debian-installer dies with: May 16 22:02:41 base-installer: Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] te is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 129.59.59.10 443] Can Ubuntu update the ca-certificate .deb pulled during install to one that does not have DST_Root_CA_X3.crt? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1973654/+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 1973477] Re: unable to upgrade to xubuntu
the missing firmware warning is not the reason, it's erroring because of klibc-utils ** Package changed: linux-firmware (Ubuntu) => klibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1973477 Title: unable to upgrade to xubuntu Status in klibc package in Ubuntu: Incomplete Bug description: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 Errors were encountered while processing: klibc-utils E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 15 16:59:41 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2022-04-20 (24 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1973477/+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 1871148] Re: services start before apparmor profiles are loaded
@eurbah hi, also for the service in question, can you attach the output of `systemctl list-dependencies --after snap..service` AFAICT, all services are to be started after snapd.apparmor.d, which in turn is started after apparmor.service, which should ensure that apparmor profiles are loaded before service startup is attempted. -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1973405] Re: Ubuntu 22.04/Wayland Session: Crash when resizing snapped windows
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1973405 Title: Ubuntu 22.04/Wayland Session: Crash when resizing snapped windows Status in Ubuntu: Incomplete Bug description: 1. Login: Wayland Session 2. Started Firefox snap via terminal: MOZ_ENABLE_WAYLAND=1 snap run firefox & disown 3. Started Visual Studio Code snap 4. Started File 5. Snapped the three windows to left and right (Firefox to the left and the other two windows to the right) 6. Dragged the windows border to resize the windows - repeat this a few times, adjust the third window to snap again (VSCode) Observed: - Poor performance while resizing - The desktop freezes for a few seconds sometimes - Crash to login screen. I have a hybrid system. I had disabled the internal screen and I was playing around on the external monitor connected HDMI. I think the HDMI in my laptop is connected to the discreet NVIDIA card. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 14 14:02:59 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
Hi Etienne, can you be a bit more explicit about what is the issue that you are seeing? What are the services which are not starting? Also please attach the SVG file generated by "sudo systemd-analyze plot", it might help us. -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+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 1973467] Re: [nvidia] Screen Blank: External screen is not turned off
** Summary changed: - Screen Blank: External screen is not turned off + [nvidia] Screen Blank: External screen is not turned off ** Tags added: nvidia nvidia-wayland wayland ** Tags added: hybrid multimonitor -- 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/1973467 Title: [nvidia] Screen Blank: External screen is not turned off Status in xorg package in Ubuntu: New Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1973467/+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 1973477] [NEW] unable to upgrade to xubuntu
You have been subscribed to a public bug: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125b-2.fw for module r8169 Errors were encountered while processing: klibc-utils E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 15 16:59:41 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2022-04-20 (24 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: klibc (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 -- unable to upgrade to xubuntu https://bugs.launchpad.net/bugs/1973477 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc 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 1973575] [NEW] [HP Laptop 15-bs0xx, Realtek ALC3227, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: The sound is not comming and when I try to turn up the volume,it is saying 'dummy output' instead of volume. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 13:06:33 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Laptop 15-bs0xx, Realtek ALC3227, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973575 Title: [HP Laptop 15-bs0xx, Realtek ALC3227, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: The sound is not comming and when I try to turn up the volume,it is saying 'dummy output' instead of volume. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 13:06:33 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP Laptop 15-bs0xx, Realtek ALC3227, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973575/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1973467] Re: [nvidia] Screen Blank: External screen is not turned off
Does the same bug occur if you choose a Xorg session (or just non- Wayland) on the login screen? -- 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/1973467 Title: [nvidia] Screen Blank: External screen is not turned off Status in xorg package in Ubuntu: New Bug description: In Power -> Power Saving Options -> Screen Blank - the option states that the screen will be turned off after some period, which is what I'd expect from a sleep mode. I have a hybrid system. I have disabled the internal display and I use the external connected via HDMI (and I believe it is connected to the NVIDIA GPU). When the screen goes blank the external monitor is not turned off really. It goes blank but it is still turned on and glows, so no power is saved. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:16:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2022-05-01 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 065C71 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1973467/+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 1973473] Re: Cannot enable LivePatch
*** This bug is a duplicate of bug 1972809 *** https://bugs.launchpad.net/bugs/1972809 Thank you for your bug report, that's already reported as bug #1972809 which has a candidate fix available for testing ** This bug has been marked a duplicate of bug 1972809 Cant enable ua from GUI, works from CLI -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973473 Title: Cannot enable LivePatch Status in software-properties package in Ubuntu: New Bug description: When I click enable live patch, I see: "Could not enable Livepatch. Try again." Trying again does not help. See also the screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun May 15 22:54:53 2022 InstallationDate: Installed on 2022-01-18 (117 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2022-04-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973473/+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 1973589] [NEW] Restart loop when using PathExistsGlob
Public bug reported: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1973589 Title: Restart loop when using PathExistsGlob Status in systemd package in Ubuntu: Confirmed Bug description: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973589/+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 1973589] Re: Restart loop when using PathExistsGlob
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1973589 Title: Restart loop when using PathExistsGlob Status in systemd package in Ubuntu: Confirmed Bug description: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973589/+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 1973237] Re: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade
After update to 4.15.0-177 I have a frequent issues with detecting my Wi-Fi card on boot (Ubuntu 18.04, Lenovo P51), have to switch back to 4.15.0-176 for work. description: Wireless interface product: Wireless 8265 / 8275 vendor: Intel Corporation physical id: 0 bus info: pci@:04:00.0 logical name: wlp4s0 version: 78 serial: ac:ed:5c:62:8e:41 width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.15.0-176-generic firmware=34.0.1 ip=192.168.0.125 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:144 memory:ecd0-ecd01fff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1973237 Title: WiFi adapter, system speakers and brightness regulation stopped working after package upgrade Status in unattended-upgrades package in Ubuntu: New Bug description: After an unattended upgrade (the packages upgraded listed at the end), at least following things crashed: - WiFi adapter - not seen by the system - system speakers - not seen - cannot regulate the brightness of my laptop screen Used system: Ubuntu 18.04.6 LTS Release: 18.04 version.log and lspci-vnvn.log in attachment --- upgraded and installed packages --- Start-Date: 2022-05-12 20:09:41 Commandline: /usr/bin/unattended-upgrade Upgrade: cron:amd64 (3.0pl1-128.1ubuntu1.1, 3.0pl1-128.1ubuntu1.2) End-Date: 2022-05-12 20:09:49 Start-Date: 2022-05-12 20:09:53 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq-base:amd64 (2.79-1ubuntu0.5, 2.79-1ubuntu0.6) End-Date: 2022-05-12 20:09:55 Start-Date: 2022-05-12 20:09:58 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:11 Start-Date: 2022-05-12 20:10:15 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-en:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:16 Start-Date: 2022-05-12 20:10:19 Commandline: /usr/bin/unattended-upgrade Upgrade: firefox-locale-pl:amd64 (99.0+build2-0ubuntu0.18.04.2, 100.0+build2-0ubuntu0.18.04.1) End-Date: 2022-05-12 20:10:20 Start-Date: 2022-05-12 20:10:24 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:25 Start-Date: 2022-05-12 20:10:29 Commandline: /usr/bin/unattended-upgrade Upgrade: libnss3:amd64 (2:3.35-2ubuntu2.13, 2:3.35-2ubuntu2.14) End-Date: 2022-05-12 20:10:30 Start-Date: 2022-05-12 20:10:33 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-libc-dev:amd64 (4.15.0-176.185, 4.15.0-177.186) End-Date: 2022-05-12 20:10:34 Start-Date: 2022-05-12 20:10:38 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-signed-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:10:38 Start-Date: 2022-05-12 20:10:42 Commandline: /usr/bin/unattended-upgrade Upgrade: libcurl4:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18), curl:amd64 (7.58.0-2ubuntu3.17, 7.58.0-2ubuntu3.18) End-Date: 2022-05-12 20:10:43 Start-Date: 2022-05-12 20:10:47 Commandline: /usr/bin/unattended-upgrade Install: linux-headers-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-image-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-headers-4.15.0-177:amd64 (4.15.0-177.186, automatic), linux-modules-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic), linux-modules-extra-4.15.0-177-generic:amd64 (4.15.0-177.186, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-image-generic:amd64 (4.15.0.176.165, 4.15.0.177.166), linux-generic:amd64 (4.15.0.176.165, 4.15.0.177.166) End-Date: 2022-05-12 20:12:20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1973237/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
Thank you for your bug report. Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system? It would also be worth trying if https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 makes a difference for you, could be the same issue with legacy server ** Changed in: wpa (Ubuntu) Status: New => Incomplete -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-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: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1973476] Re: Startup Applications desktop file untranslated on Ubuntu 22.04
Thank you for your bug report. The string was translated after the current language packs were generated so is missing from the curent version https://translations.launchpad.net/ubuntu/jammy/+source/gnome- session/+pots/gnome-session-42/fr/29/+translate it should be fixed in the next langpacks refresh before .1 ** Package changed: gnome-session (Ubuntu) => language-pack-gnome-fr (Ubuntu) ** Changed in: language-pack-gnome-fr (Ubuntu) Importance: Medium => Low ** Changed in: language-pack-gnome-fr (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr in Ubuntu. https://bugs.launchpad.net/bugs/1973476 Title: Startup Applications desktop file untranslated on Ubuntu 22.04 Status in language-pack-gnome-fr package in Ubuntu: Fix Committed Bug description: The desktop entry for Startup Applications is untranslated under Ubuntu 22.04 in my native french language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-fr/+bug/1973476/+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 1961427] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2022-05-16 06:17 EDT---
With the new combination, bedtools testsuite is green and zlib passes all of my
tests too. So it looks good, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on IBM z Systems:
Incomplete
Status in bedtools package in Ubuntu:
New
Status in zlib package in Ubuntu:
Incomplete
Status in bedtools source package in Focal:
New
Status in zlib source package in Focal:
New
Status in bedtools source package in Impish:
New
Status in zlib source package in Impish:
New
Status in bedtools source package in Jammy:
New
Status in zlib source package in Jammy:
Incomplete
Bug description:
SRU Justification:
==
[Impact]
* zlib: compressBound() returns an incorrect result on IBM z15
hardware.
* Passing the result of compressBound() to compress() results
in an error code.
* This is because compressBound() is not adjusted for DFLTCC.
[Fix]
* Adjust compressBound() for DFLTCC like it's already done
for deflateBound().
* Since zlib project does not accept patches at the moment,
the fix has been integrated into the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
* The fix extracted out of the above is:
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff
[Test Plan]
* An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
with Ubuntu Server 21.10 (or 22.04).
* A test can be done based on the following C test program:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
* The test needs to be done by IBM, due to the requirements
for the special z15 hardware.
* A successful test was just completed, based on the version in jammy-
proposed, which is at the same code level that the impish version this
SRU is targeted for.
[Where problems could occur]
* If the adjustment of compressBound() for DFLTCC is done
erroneously the issue can still be present or in worst case
even affect Z systems other than z15 only.
* The compression can become errorneous with the new changes,
e.g. in compressBound.
* Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
(incl. the bit definitions), may cause various and unforseen defects.
* Any build time issues that might have been introduced by this patch
can be identified by a test build; this was done and is available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427
[Other Info]
* Ubuntu jammy, impish and focal are affected.
__
Description: zlib: compressBound() returns an incorrect result on z15
Symptom: Passing the result of compressBound() to compress()
results in an error code.
Problem: compressBound() is not adjusted for DFLTCC.
Solution: Adjust compressBound() for DFLTCC like it's already done
for deflateBound(). Since zlib project does not accept
patches at the moment, the fix has been integrated into
the DFLTCC pull request:
https://github.com/madler/zlib/pull/410
The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.
Reproduction: z15 only:
#include
#include
#include
int main() {
Bytef in_buf[128], out_buf[1024];
for (size_t i = 0; i < sizeof(in_buf); i++)
in_buf[i] = rand();
uLongf dest_len = compressBound(sizeof(in_buf));
assert(dest_len <= sizeof(out_buf));
int ret = compress(out_buf, _len,
in_buf, sizeof(in_buf));
assert(ret == Z_OK);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Changed in: wpa (Ubuntu Jammy) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04
the update on https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 which allows legacy renegociation by default might fix some of the issues reported on this bug -- 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/1960268 Title: SSL handshake failed - VPN SSL broken in 22.04 Status in openssl package in Ubuntu: Incomplete Bug description: I'm trying to connect with global protect VPN but fails at login with: SSL handshake failed Failed to load URL https://... QtNetwork Error 6 Another VPN client does work but the rdp connection to a remote server fails with: transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session impish Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-19 (325 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: openssl 3.0.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: wayland-session jammy Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago) UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare sudo uinput _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy
Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562, CVE-2022-0865 and CVE-2022-0891 are now released and available. (https://ubuntu.com/security/notices/USN-5421-1). Jammy is currently at version 4.3.0-6 which includes the patch for CVE-2022-0865 as it was introduced in 4.3.0-5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy Status in tiff package in Ubuntu: In Progress Bug description: The versions in Trusty, Xenial, Bionic, Focal and Impish may be vulnerable to all CVEs below. The version in Jammy is vulnerable to CVE-2022-0865. Debian released an advisory on March 24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsc-lite (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
We're seeing this same issue. The postinst script in the 22.04 package seems to be missing a few lines that were still there in 21.10, one of which would be the one that executes systemctl enable pcscd.socket. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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]
Lenovo Legion S7 15IMH5 Has anyone managed to get their sound working on it? Would appreciate a tutorial or some tips (the more specific, the better, as this thread is full of other devices as well and it'd take a long time to try everything) -- 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]
Looking at the model number, there's a chance it's compatible with the verbs of the 15IMHG05, or another model from around that time. Do you know how to build and run your own kernel? Also, please provide a URL to your alsa-info. On 5/15/2022 12:12 PM, bugzilla-dae...@kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=208555 > > --- Comment #599 from Andrei Miculita (andreimiculita+k...@gmail.com) --- > Lenovo Legion S7 15IMH5 > > Has anyone managed to get their sound working on it? Would appreciate a > tutorial or some tips (the more specific, the better, as this thread is full > of > other devices as well and it'd take a long time to try everything) > -- 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 1973607] [NEW] Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Public bug reported: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1747499] Re: 98-reboot-required and Interaction with livepatch
The package FTBFS against -proposed but builds successfully against the -release pocket. Based on the error, it seems related to recent changes in how apt determines kernels that can be autoremoved. apt (2.0.7) focal; urgency=medium * Revert "Protect currently running kernel at run-time" * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of 2.4.5; including the change to only protect two kernels, not last installed one (LP: #1968154) -- Julian Andres Klode Mon, 25 Apr 2022 15:58:46 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1747499 Title: 98-reboot-required and Interaction with livepatch Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Focal: Fix Committed Status in update-notifier source package in Focal: Fix Committed Bug description: [Impact] * If a system is using canonical livepatch, has it enabled, and patches are applied, it could be confusing for a user to receive a "system restart required" messages in the MOTD when logging in. * Livepatch is available on LTS releases. Thus, the users can be confused following a kernel update on 20.04. * The upload prevents update-notifier and unattended-ugprades hooks from adding "system restart"-related messages to motd when Livepatch is enabled. Livepatch, when enabled, already contributes to the motd message so there is no need to have duplicate (and sometimes contradictory) information. [Test Plan] * how to reproduce the bug: 1. Install and boot a 20.04 server VM 2. Make sure it runs a generic kernel (or another flavour that supports Livepatch) 3. Enable Livepatch using the following command: $ ua attach # replace by an actual contract token 4. Upgrade the kernel (if you are already running the latest available kernel update, you can install a different flavour) 5. Upon logging in again, the motd will show ***System restart required***. * other testing appropriate to perform before landing this update: * Making sure that the patch has no impact when livepatch is not enabled. * The motd should show ***System restart required*** after upgrading the kernel if livepatch is not enabled. [Where problems could occur] * The change updates a hook script in /etc/kernel/postinst.d/. Scripts in this directory are executing when upgrading / installing a kernel. If somehow the script is broken, it can prevent dpkg for succeeding when upgrading / installing the kernel. * If the implementation is wrong, we might end up "losing" the ***System restart required*** message when livepatch is disabled [Original bug description] If a system is using canonical livepatch, has it enabled, and patches are applied, it could be confusing for a user to receive a "system restart required" messages in the MOTD when logging in. That message, when present, is printed by 98-reboot-required which essentially just cats /var/run/reboot-required to stdout. That file is placed by packages that require a reboot so that they are properly used in their updated versions. Examples that come to mind are libc and the kernel. There is a secondary file that can be created which says which packages requested the reboot. That would be /var/run/reboot- required.pkgs Ideally that script should not print out the reboot required message if a) livepatch is installed and enabled; b) the only trigger for the reboot is a kernel update. For (a), one can use the command "ubuntu-advantage is-livepatch- enabled" and check $?. That is in the ubuntu-advantage-tools package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic
Thanks you for you bug report, does that cmd work for you? $ xdg-open http://www.ubuntu.com -- 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/1973470 Title: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic Status in apport package in Ubuntu: New Bug description: Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD. While reporting Bug #1973469, I discovered that ubuntu-bug was unable to open Firefox at the very end of the process. Sadly, I closed the terminal window that contained the initial error, but I was able to easily reproduce it reporting this bug. The full console output of "ubuntu-bug apport" on Lubuntu Kinetic is: *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 94% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?' I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this is due to the Snap version of Firefox, but I don't know for sure. Since ubuntu-bug is what gave me the error, I'm filing this against Apport. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: LXQt Date: Sun May 15 11:41:07 2022 LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1973470/+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 1973610] [NEW] Bluetooth will not stay on or connect to devices when on
Public bug reported: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:A8:66:B1 ACL MTU: 1021:8 SCO MTU: 64:1 DOWN INIT RUNNING RX bytes:175353 acl:52 sco:0 events:6887 errors:0 TX bytes:18571 acl:52 sco:0 commands:1087 errors:2 mtime.conffile..etc.bluetooth.main.conf: 2022-05-16T09:39:58.915340 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1973610 Title: Bluetooth will not stay on or connect to devices when on Status in bluez package in Ubuntu: New Bug description: Since upgrading from Ubuntu 20.10, my internal bluetooth card as well as an external usb dongle will not work. Bluetooth starts as off, and cannot be turned on. If I use systemctl to turn it on, it is on but doesn't find any devices through bluez. Blueman finds devices but cannot connect to them. The hardware on this machine has remained identical; the only difference is the new version of Ubuntu. Hence the problem has to be software. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 09:45:02 2022 InstallationDate: Installed on 2021-10-22 (205 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=710f912e-cc80-4456-915a-90de1169d201 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-05-03 (12 days ago) dmi.bios.date: 08/04/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.50 dmi.board.name: N7 B550 dmi.board.vendor: NZXT dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.50:bd08/04/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnNZXT:rnN7B550:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M.
[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
We haven't got new reports since the fix landed nor visible regression so let's say the fix is working as intended. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Committed Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1971272] Re: Merge cyrus-sasl2 from Debian unstable for kinetic
This became a sync, after debian accepted my DEP8 tests. https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1971272 Title: Merge cyrus-sasl2 from Debian unstable for kinetic Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: Upstream: tbd Debian: 2.1.28+dfsg-4 Ubuntu: 2.1.27+dfsg2-3ubuntu1 Debian does new releases regularly, so it's likely there will be newer versions available before FF that we can pick up if this merge is done later in the cycle. ### New Debian Changes ### cyrus-sasl2 (2.1.28+dfsg-4) unstable; urgency=medium * d/copyright: java/* files were removed upstream * d/copyright: Reformat the default license's margin * d/copyright: Add project's license to include/makemd5.c * Move SCRAM to libsasl2-modules (Closes: #977360) * Install additional GS2 module for Heimdal * Remove Roberto from the Uploaders * Drop 0005-Fixes-in-library-mutexes.patch * Drop 0021-Fix-keytab-option-for-MIT-Kerberos.patch * Remove former logcheck conffile (Closes: #1009851) * lintian: Fix excessive-priority-for-library-package * lintian: Fix package-contains-empty-directory -- Bastian Germann Wed, 20 Apr 2022 01:01:01 +0200 cyrus-sasl2 (2.1.28+dfsg-3) unstable; urgency=high * Set MIT/Heimdal CFLAGS instead of CPPFLAGS * Drop unnecessary 0027-properly-create-libsasl2.pc.patch * Prevent installing outdated ChangeLog (Closes: #1009681) * Remove debug log message and its logcheck rule (Closes: #805310) * Self-reference pluginviewer man as saslpluginviewer (Closes: #1009380) * Get rid of broken README.configure-options * Add sasldbconverter2.8 manpage * d/copyright: Add missing KTH license * Install libsasl.5 manpage [ Debian Janitor ] * Remove constraints unnecessary since buster -- Bastian Germann Fri, 15 Apr 2022 12:02:13 +0200 cyrus-sasl2 (2.1.28+dfsg-2) unstable; urgency=medium * Remove cruft -- Bastian Germann Fri, 25 Feb 2022 18:58:54 +0100 cyrus-sasl2 (2.1.28+dfsg-1) experimental; urgency=medium * Drop upstream patches * Import new release signing key * Reset repacksuffix * New upstream version 2.1.28+dfsg (CVE-2022-24407) * Rebase 0027-properly-create-libsasl2.pc.patch -- Bastian Germann Tue, 22 Feb 2022 23:40:47 +0100 cyrus-sasl2 (2.1.27+dfsg2-3) unstable; urgency=medium [ Andreas Hasenack ] * Fix configure.ac for autoconf 2.70 (Closes: #1003355, #1000152) -- Bastian Germann Tue, 11 Jan 2022 11:25:37 +0100 cyrus-sasl2 (2.1.27+dfsg2-2) unstable; urgency=medium [ Helmut Grohne ] * Fix FTCBFS: (Closes: #928512) + cross.patch: Support caching SPNEGO support test. + Provide SPNEGO support test result. [ Vagrant Cascadian ] * Set date in man pages (Closes: #995145) -- Bastian Germann Wed, 17 Nov 2021 01:23:49 +0100 cyrus-sasl2 (2.1.27+dfsg2-1) unstable; urgency=medium * Add bage to uploaders (Closes: #799864) * Use upstream patches where possible * Amend off-by-one in _sasl_add_string function * Replace some patches by upstream equivalents * Apply the patches in order of to their prefixes * Add missing caret (^) in logcheck rule (Closes: #830764) * Remove unnecessary GPL copy * Add missing copyright/licenses * Repack, getting rid of more problematic files * Build html documentation * Make the package rebuildable * Remove outdated README.Debian info * Disable autostart via debhelper * Drop unnecessary patch * Remove alternative, old build dep libmysqlclient-dev Annotate documentation Build-Depends with :native [ Frédéric Brière ] * Make logcheck snippet compatible with systemd journal -- Bastian Germann Sun, 14 Nov 2021 14:11:18 +0100 cyrus-sasl2 (2.1.27+dfsg-2.3) unstable; urgency=medium * Non-maintainer upload. * d/watch: Check the github releases page * Get rid of a patch's patch * Recover upstream-compatible patch license (Closes: #996866) + Relicense libobj patch * Fix lintian: unused-override ### Old Ubuntu Delta ### cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1) jammy; urgency=medium * SECURITY UPDATE: SQL injection in SQL plugin - debian/patches/CVE-2022-24407.patch: escape password for SQL insert/update commands in plugins/sql.c. - CVE-2022-24407 -- Marc Deslauriers Tue, 22 Feb 2022 14:17:18 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1971272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1973608] Re: udev TAG-="uaccess" does not work on ubuntu 22.04
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1973608
Title:
udev TAG-="uaccess" does not work on ubuntu 22.04
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess",
RUN:="/bin/setfacl -m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
Udev info:
udevadm info -q all -n /dev/bus/usb/001/007
P: /devices/pci:00/:00:14.0/usb1/1-1
N: bus/usb/001/007
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/007
E: DEVTYPE=usb_device
E: DRIVER=apple-mfi-fastcharge
E: PRODUCT=5ac/12a8/1302
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=007
E: MAJOR=189
E: MINOR=6
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2331114479
E: USBMUX_SUPPORTED=1
E: SYSTEMD_WANTS=usbmuxd.service
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=05ac
E: ID_MODEL=iPhone
E: ID_MODEL_ENC=iPhone
E: ID_MODEL_ID=12a8
E: ID_REVISION=1302
E: ID_SERIAL=Apple_Inc._iPhone_8101000A2DD826B8001E
E: ID_SERIAL_SHORT=8101000A2DD826B8001E
E: ID_BUS=usb
E: ID_USB_INTERFACES=:060101:010100:010200:03:fffe02:fffd01:
E: ID_VENDOR_FROM_DATABASE=Apple, Inc.
E: GPHOTO2_DRIVER=PTP
E: ID_GPHOTO2=1
E: ID_MODEL_FROM_DATABASE=iPhone 5/5C/5S/6/SE
E: ID_PATH=pci-:00:14.0-usb-0:1
E: ID_PATH_TAG=pci-_00_14_0-usb-0_1
E: ID_FOR_SEAT=usb-pci-_00_14_0-usb-0_1
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: TAGS=:uaccess:seat:systemd:
E: CURRENT_TAGS=:seat:systemd:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973608/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1747499] Re: 98-reboot-required and Interaction with livepatch
Trying to validate this upload but unattended-upgrades failed to build
with:
Applying pinning: PkgFilePin(id=0, priority=-32768)
Applying pin -32768 to package_file: >/test/root.unused-deps/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages'
a=lucid-updates,c=main,v=10.04,o=Ubuntu,l=Ubuntu arch='amd64'
site='archive.ubuntu.com' IndexType='Debian Package Index' Size=106 ID:0>
Using
(^linux-image-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^.*-modules-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$|^linux-headers-[1-9][0-9]*\.[0-9]+\.[0-9]+-[0-9]+(-.+)?$)
regexp to find kernel packages
Using
(^linux-image-5\.4\.0\-109\-generic$|^linux-image-5\.4\.0\-109$|^.*-modules-5\.4\.0\-109\-generic$|^.*-modules-5\.4\.0\-109$|^linux-headers-5\.4\.0\-109\-generic$|^linux-headers-5\.4\.0\-109$)
regexp to find running kernel packages
{'old-unused-dependency', 'any-old-unused-modules'}
Keeping auto-removable test-package-dependency package(s) because it would also
remove the following packages which should be kept in this step:
old-unused-dependency
The following packages are marked for installation or upgrade which is not
allowed when performing autoremovals: forbidden-dependency
.
==
FAIL: test_remove_unused_dependencies_new_unused_only
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
File "./test_remove_unused.py", line 164, in
test_remove_unused_dependencies_new_unused_only
self.assertTrue(needle_kernel_good in haystack,
AssertionError: False is not true : Can not find 'Removing unused kernel
packages: linux-image-4.05.0-1021-kvm
' in '2022-05-10 20:56:21,336 INFO Starting unattended upgrades script
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in update-notifier package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Focal:
Fix Committed
Status in update-notifier source package in Focal:
Fix Committed
Bug description:
[Impact]
* If a system is using canonical livepatch, has it enabled, and
patches are applied, it could be confusing for a user to receive a
"system restart required" messages in the MOTD when logging in.
* Livepatch is available on LTS releases. Thus, the users can be
confused following a kernel update on 20.04.
* The upload prevents update-notifier and unattended-ugprades hooks from
adding "system restart"-related messages to motd when Livepatch is enabled.
Livepatch, when enabled, already contributes to the motd message so there is
no need to have duplicate (and sometimes contradictory) information.
[Test Plan]
* how to reproduce the bug:
1. Install and boot a 20.04 server VM
2. Make sure it runs a generic kernel (or another flavour that supports
Livepatch)
3. Enable Livepatch using the following command:
$ ua attach # replace by an actual contract token
4. Upgrade the kernel (if you are already running the latest available
kernel update, you can install a different flavour)
5. Upon logging in again, the motd will show ***System restart required***.
* other testing appropriate to perform before landing this update:
* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the
kernel if livepatch is not enabled.
[Where problems could occur]
* The change updates a hook script in /etc/kernel/postinst.d/.
Scripts in this directory are executing when upgrading / installing a
kernel. If somehow the script is broken, it can prevent dpkg for
succeeding when upgrading / installing the kernel.
* If the implementation is wrong, we might end up "losing" the
***System restart required*** message when livepatch is disabled
[Original bug description]
If a system is using canonical livepatch, has it enabled, and patches
are applied, it could be confusing for a user to receive a "system
restart required" messages in the MOTD when logging in.
That message, when present, is printed by 98-reboot-required which
essentially just cats /var/run/reboot-required to stdout. That file is
placed by packages that require a reboot so that they are properly
used in their updated versions. Examples that come to mind are libc
and the kernel.
There is a secondary file that can be created which says which
packages requested the reboot. That would be /var/run/reboot-
required.pkgs
Ideally that script should not print out the reboot required message
if a) livepatch is installed and enabled; b) the only trigger
[Touch-packages] [Bug 1677781] Re: Missing dep8 tests
Sent new dep8 tests to debian, and then synced the package back into ubuntu: https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1677781 Title: Missing dep8 tests Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source cyrus-sasl2 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/cyrus-sasl2 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1 3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe 4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5 WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5 Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G WY9JzBOc6MUi46Hh9ZN5 =szTz -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between debian package and the ubuntu one. ** Patch added: "debdiff_debian_ubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590044/+files/debdiff_debian_ubuntu.debdiff ** Tags added: fr-2388 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
Please find attached the debdiff between old ubuntu version and the new one. ** Patch added: "debdiff_oldubuntu_newubuntu.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+attachment/5590043/+files/debdiff_oldubuntu_newubuntu.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973608] [NEW] udev TAG-="uaccess" does not work on ubuntu 22.04
Public bug reported:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
Udev info:
udevadm info -q all -n /dev/bus/usb/001/007
P: /devices/pci:00/:00:14.0/usb1/1-1
N: bus/usb/001/007
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/007
E: DEVTYPE=usb_device
E: DRIVER=apple-mfi-fastcharge
E: PRODUCT=5ac/12a8/1302
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=007
E: MAJOR=189
E: MINOR=6
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2331114479
E: USBMUX_SUPPORTED=1
E: SYSTEMD_WANTS=usbmuxd.service
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=05ac
E: ID_MODEL=iPhone
E: ID_MODEL_ENC=iPhone
E: ID_MODEL_ID=12a8
E: ID_REVISION=1302
E: ID_SERIAL=Apple_Inc._iPhone_8101000A2DD826B8001E
E: ID_SERIAL_SHORT=8101000A2DD826B8001E
E: ID_BUS=usb
E: ID_USB_INTERFACES=:060101:010100:010200:03:fffe02:fffd01:
E: ID_VENDOR_FROM_DATABASE=Apple, Inc.
E: GPHOTO2_DRIVER=PTP
E: ID_GPHOTO2=1
E: ID_MODEL_FROM_DATABASE=iPhone 5/5C/5S/6/SE
E: ID_PATH=pci-:00:14.0-usb-0:1
E: ID_PATH_TAG=pci-_00_14_0-usb-0_1
E: ID_FOR_SEAT=usb-pci-_00_14_0-usb-0_1
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: TAGS=:uaccess:seat:systemd:
E: CURRENT_TAGS=:seat:systemd:
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Confirmed
** Description changed:
+ Ubuntu 22.04.
+ Udev version 249.11-0ubuntu3.1.
+
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
- -m g:sudo:rw -m g:plugdev:rw -m g:2046:rw -m g:2027:rw $env{DEVNAME}"
+ -m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
** Description changed:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess", RUN:="/bin/setfacl
-m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
+
+ Udev info:
+ udevadm info -q all -n /dev/bus/usb/001/007
+ P: /devices/pci:00/:00:14.0/usb1/1-1
+ N: bus/usb/001/007
+ L: 0
+ E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
+ E: DEVNAME=/dev/bus/usb/001/007
+ E: DEVTYPE=usb_device
+ E: DRIVER=apple-mfi-fastcharge
[Touch-packages] [Bug 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
Thank you for your bug report, could you include the output of $ ubuntu-drivers debug ? ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1973379 Title: "additional drivers" says we are using nvidia drivers but its not true Status in software-properties package in Ubuntu: Incomplete Bug description: after selecting the recommended, tested nvidia driver, and restarting the system as suggested, no nvidia modules are loaded at all, instead just nouveau kernel modules are loaded and all the nvidia tools confirm that no nvidia drivers are being used and running. But starting the software properties and opening the "additional drivers" tab again, I'm being told the nvidia drivers are in selected and "1 proprietary driver in use". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 13 23:20:12 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-12 (760 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 SourcePackage: software-properties UpgradeStatus: Upgraded to jammy on 2022-04-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973379/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1973476] [NEW] Startup Applications desktop file untranslated on Ubuntu 22.04
You have been subscribed to a public bug: The desktop entry for Startup Applications is untranslated under Ubuntu 22.04 in my native french language. ** Affects: language-pack-gnome-fr (Ubuntu) Importance: Low Status: Fix Committed ** Tags: i18n jammy l10n -- Startup Applications desktop file untranslated on Ubuntu 22.04 https://bugs.launchpad.net/bugs/1973476 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-fr 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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
** Changed in: wpa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Released Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1892825] Autopkgtest regression report (glibc/2.27-3ubuntu1.6)
All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: docker.io/20.10.7-0ubuntu5~18.04.3 (i386, amd64, s390x, arm64, ppc64el) sbd/1.3.1-2 (amd64) chromium-browser/100.0.4896.127-0ubuntu0.18.04.1 (armhf) pymol/1.8.4.0+dfsg-1build1 (s390x, ppc64el) nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386) pgbouncer/1.8.1-1build1 (amd64) r-cran-urltools/1.7.0-1ubuntu1 (arm64, ppc64el) firefox/100.0+build2-0ubuntu0.18.04.1 (arm64) python-llfuse/1.3.3+dfsg-3 (arm64) c-icap/1:0.4.4-1 (ppc64el) givaro/4.0.2-8ubuntu1 (armhf) apport/2.20.9-0ubuntu7.27 (amd64) threadweaver/5.44.0-0ubuntu1 (i386) apt/1.6.14 (arm64) containerd/1.5.5-0ubuntu3~18.04.2 (amd64, arm64) glibc/2.27-3ubuntu1.6 (armhf) cura-engine/1:3.1.0-2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#glibc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: Fix Released Status in pam package in Ubuntu: New Status in glibc source package in Bionic: Fix Committed Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Released Status in pam source package in Focal: New Status in glibc source package in Hirsute: Won't Fix Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8 The LANGUAGE=en_US.UTF-8 line should have been replaced by LANGUAGE=en_GB.UTF-8. $ update-locale --locale-file /tmp/locale LANGUAGE The LANGUAGE setting is now commented out. [regression potential] Apart from the general concerns about a glibc rebuild, this is a simple change to a simple script. Performing the test as in the test case section is enough to ensure it still works. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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
Re: [Touch-packages] [Bug 1973217] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit sta
On 5/16/22 09:42, Lena Voytek wrote: > You noted that this may be due to update-manager having two instances > running. Were you able to try again with one running to get it updated? > If not, does updating with: > > sudo apt update > sudo apt upgrade > > cause any errors? Yes, errors persist: apt install openssh-server Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfwupdplugin1 Use 'sudo apt autoremove' to remove it. Suggested packages: molly-guard monkeysphere ssh-askpass The following NEW packages will be installed: openssh-server 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 0 B/377 kB of archives. After this operation, 1,527 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package openssh-server. (Reading database ... 298345 files and directories currently installed.) Preparing to unpack .../openssh-server_1%3a8.2p1-4ubuntu0.5_amd64.deb ... Unpacking openssh-server (1:8.2p1-4ubuntu0.5) ... Setting up openssh-server (1:8.2p1-4ubuntu0.5) ... rescue-ssh.target is a disabled or a static unit, not starting it. Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: en abled) Active: activating (auto-restart) (Result: exit-code) since Fri 2022-05-13 06:47:48 PDT; 3ms ago Docs: man:sshd(8) man:sshd_config(5) Process: 6402 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255/EXCEPT ION) dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned e rror exit status 1 Processing triggers for systemd (245.4-4ubuntu3.17) ... and then: systemctl status ssh.service ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2022-05-16 06:26:11 PDT; 4h 48min ago Docs: man:sshd(8) man:sshd_config(5) Process: 140702 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255/EXCEPTION) May 16 06:26:11 paradise systemd[1]: ssh.service: Scheduled restart job, restart counter is at 5. May 16 06:26:11 paradise systemd[1]: Stopped OpenBSD Secure Shell server. May 16 06:26:11 paradise systemd[1]: ssh.service: Start request repeated too quickly. May 16 06:26:11 paradise systemd[1]: ssh.service: Failed with result 'exit-code'. May 16 06:26:11 paradise systemd[1]: Failed to start OpenBSD Secure Shell server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1973217 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: It might be that two instances of update-manager seemed to be running at the same time. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 12 08:50:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1973217/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Good news for Belgians who connect tot the government site with there id card. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
see also https://sourceware.org/bugzilla/show_bug.cgi?id=29045#c3 where the gdb list recommends updating to a stable version of gdb ** Bug watch added: Sourceware.org Bugzilla #29045 https://sourceware.org/bugzilla/show_bug.cgi?id=29045 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: Confirmed Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1971932] Re: error in rsync protocol data stream
I attempted to reproduce by running the command through localhost over ssh and it succeeded using a 3GB file. This may be due to the transfer between Ubuntu and Debian then. Here is my test case: # lxc launch images:ubuntu/jammy test-rsync # lxc exec test-rsync bash # apt update && apt dist-upgrade -y # apt install rsync openssh-server # passwd ubuntu # su ubuntu # cd # mkdir dest # head -c 3GB /dev/urandom > test # rsync -avz --stats -e ssh test localhost:~/dest/ @jmbaudach can you try to transfer your over 2GB file locally with ssh to see if it fails there. That will help us narrow down the issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Incomplete Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1973589] Re: Restart loop when using PathExistsGlob
** Description changed: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target + + - + www-data@josi-test-jammy03:~ $ systemctl --user status test.path + × test.path - Test + Loaded: loaded (/home/www-data/.config/systemd/user/test.path; disabled; vendor preset: enabled) + Active: failed (Result: unit-start-limit-hit) since Mon 2022-05-16 17:08:08 CEST; 121ms ago +Triggers: ● test.service + + May 16 17:08:04 josi-test-jammy03 systemd[24979]: Started Test + May 16 17:08:08 josi-test-jammy03 systemd[24979]: test.path: Failed with result 'unit-start-limit-hit'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1973589 Title: Restart loop when using PathExistsGlob Status in systemd package in Ubuntu: Confirmed Bug description: When using PathExistsGlob in a path unit, systemd starts the corresponding service unit in an infinite loop. We have observed this problem only under Jammy. -- [Unit] Description=Test [Path] PathExistsGlob=/home/www-data/test/*.so Unit=test.service [Install] WantedBy=multi-user.target -- [Unit] Description=Test [Service] Type=simple ExecStart=echo test StartLimitBurst=1000 [Install] WantedBy=multi-user.target - www-data@josi-test-jammy03:~ $ systemctl --user status test.path × test.path - Test Loaded: loaded (/home/www-data/.config/systemd/user/test.path; disabled; vendor preset: enabled) Active: failed (Result: unit-start-limit-hit) since Mon 2022-05-16 17:08:08 CEST; 121ms ago Triggers: ● test.service May 16 17:08:04 josi-test-jammy03 systemd[24979]: Started Test May 16 17:08:08 josi-test-jammy03 systemd[24979]: test.path: Failed with result 'unit-start-limit-hit'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973589/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
Hello Thomas, Since the issue can't be reproduced in impish or jammy, is this an error you found in Focal, or has this been fixed for you? If it's an error in an earlier supported version then we can backport the fix to it. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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
Re: [Touch-packages] [Bug 1973379] Re: "additional drivers" says we are using nvidia drivers but its not true
Thanks, but I am not sure if that can still be helpful for the analysis, because in the meantime I got the nvidia drivers running properly. What finally got me there was these commands: ubuntu-drivers devices ubuntu-drivers autoinstall apt install nvidia-dkms-510 update-initramfs -k all -u and a reboot. it could be that the first two are not needed when properly selecting the nvidia drivers in the GUI drivers tool, but it appears to me the dkms part is missing in the GUI tool just as in the CLI version, and without that the drivers are not running for me. here's the debug output: $ ubuntu-drivers debug === log messages from detection === DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:_get_db_name: output ID_PCI_CLASS_FROM_DATABASE=Display controller ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller ID_PCI_INTERFACE_FROM_DATABASE=VGA controller ID_VENDOR_FROM_DATABASE=NVIDIA Corporation ID_MODEL_FROM_DATABASE=TU117M [GeForce GTX 1650 Mobile / Max-Q] DEBUG:root:_get_db_name(/sys/devices/pci:00/:00:01.0/:01:00.0, pci:v10DEd1F91sv17AAsd22A8bc03sc00i00): vendor "NVIDIA Corporation", model "TU117M [GeForce GTX 1650 Mobile / Max-Q]" DEBUG:root:Skipping check for rtl8812au-dkms since it does not depend on video abi DEBUG:root:Skipping check for open-vm-tools-desktop since it does not depend on video abi DEBUG:root:Skipping check for rtl8821ce-dkms since it does not depend on video abi DEBUG:root:Skipping check for bcmwl-kernel-source since it does not depend on video abi DEBUG:root:Skipping check for oem-qemu-meta since it does not depend on video abi DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/arm-gles.py return value: None DEBUG:root:Loading custom detection plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py DEBUG:root:plugin /usr/share/ubuntu-drivers-common/detect/sl-modem.py return value: None === modaliases in the system === acpi:PNP0C14: wmi:86CCFD48-205E-4A77-9C48-2021CBEDE341 acpi:PNP0C0D: platform:thinkpad_hwmon platform:eisa
[Touch-packages] [Bug 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)
The attachment "debdiff_oldubuntu_newubuntu.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1973607 Title: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) Status in logrotate package in Ubuntu: New Bug description: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973608] Re: udev TAG-="uaccess" does not work on ubuntu 22.04
This was a deliberate change in systemd [1] to address the kernel's
bind/unbind uevent issue [2]. In short, it is an intentional change in
udev's behavior, and unfortunately breaks the assumptions that your
custom udev rules rely on.
[1]
https://github.com/systemd/systemd/commit/e77b146f825ef1bb63c297cc713962b94422d2c6
[2] https://lwn.net/Articles/837033/
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1973608
Title:
udev TAG-="uaccess" does not work on ubuntu 22.04
Status in systemd package in Ubuntu:
Invalid
Bug description:
Ubuntu 22.04.
Udev version 249.11-0ubuntu3.1.
I have 72-my-rule.rules
ACTION=="add|bind", SUBSYSTEM=="usb",
ENV{ID_USB_INTERFACES}=="*:060101:*", TAG-="uaccess",
RUN:="/bin/setfacl -m g:sudo:rw -m g:plugdev:rw $env{DEVNAME}"
It removes TAG uaccess for my usb device. On my ubuntu 18.04 and 20.04
it works fine, but on 22.04 does not. It causes next rule 73-seat-
late.rules to run builtin uaccess, which does not need to run.
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
ACTION=="remove", GOTO="seat_late_end"
ENV{ID_SEAT}=="", ENV{ID_AUTOSEAT}=="1", ENV{ID_FOR_SEAT}!="",
ENV{ID_SEAT}="seat-$env{ID_FOR_SEAT}"
ENV{ID_SEAT}=="", IMPORT{parent}="ID_SEAT"
ENV{ID_SEAT}!="", TAG+="$env{ID_SEAT}"
TAG=="uaccess", ENV{MAJOR}!="", RUN{builtin}+="uaccess"
LABEL="seat_late_end"
Udev info:
udevadm info -q all -n /dev/bus/usb/001/007
P: /devices/pci:00/:00:14.0/usb1/1-1
N: bus/usb/001/007
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-1
E: DEVNAME=/dev/bus/usb/001/007
E: DEVTYPE=usb_device
E: DRIVER=apple-mfi-fastcharge
E: PRODUCT=5ac/12a8/1302
E: TYPE=0/0/0
E: BUSNUM=001
E: DEVNUM=007
E: MAJOR=189
E: MINOR=6
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=2331114479
E: USBMUX_SUPPORTED=1
E: SYSTEMD_WANTS=usbmuxd.service
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=05ac
E: ID_MODEL=iPhone
E: ID_MODEL_ENC=iPhone
E: ID_MODEL_ID=12a8
E: ID_REVISION=1302
E: ID_SERIAL=Apple_Inc._iPhone_8101000A2DD826B8001E
E: ID_SERIAL_SHORT=8101000A2DD826B8001E
E: ID_BUS=usb
E: ID_USB_INTERFACES=:060101:010100:010200:03:fffe02:fffd01:
E: ID_VENDOR_FROM_DATABASE=Apple, Inc.
E: GPHOTO2_DRIVER=PTP
E: ID_GPHOTO2=1
E: ID_MODEL_FROM_DATABASE=iPhone 5/5C/5S/6/SE
E: ID_PATH=pci-:00:14.0-usb-0:1
E: ID_PATH_TAG=pci-_00_14_0-usb-0_1
E: ID_FOR_SEAT=usb-pci-_00_14_0-usb-0_1
E: COLORD_DEVICE=1
E: COLORD_KIND=camera
E: TAGS=:uaccess:seat:systemd:
E: CURRENT_TAGS=:seat:systemd:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1973608/+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 1968074] Re: moc fails to parse include inside enum
** Changed in: gudhi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1968074 Title: moc fails to parse include inside enum Status in gudhi package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: Seen while trying to rebuild gudhi against qtbase5-dev/ 5.15.3+dfsg-1 : AutoMoc subprocess error The moc process failed to compile "SRC:/src/GudhUI/gui/MainWindow.cpp" into "SRC:/build/userversion/src/GudhUI/GudhUI_autogen/include/MainWindow.moc" included by "SRC:/src/GudhUI/gui/MainWindow.cpp" ... Output -- usr/include/tbb/tbb_profiling.:29: Parse error at "/usr/include/tbb/internal/_tbb_strings.h" Previous builds against qtbase5-dev/5.15.2+dfsg-15 were successful [1]. I found an upstream bug [2] with the same error, although the versions differ. I also found similar bug [3] that is reported to be fixed in 5.15.6. [1] https://launchpad.net/ubuntu/+source/gudhi/3.5.0+dfsg-1ubuntu1 [2] https://bugreports.qt.io/browse/QTBUG-94790 [3] https://bugreports.qt.io/browse/QTBUG-80990 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gudhi/+bug/1968074/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Hi @Sebastien, no problem at all. I will create a new bug report once I'm sure I've tried everything on my side. Have a lovely day. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Bug description: * Impact Connecting to some PEAP wifi doesn't work anymore since the openssl3 transition Details on the issue can be found on http://lists.infradead.org/pipermail/hostap/2022-May/040511.html * Test case Try using a PEAP wifi not implementing RFC5746, it should be able to connect * Regression potential The change allows to connect to less secure WiFis the same way that wpa allowed before openssl3, lower security enforcement isn't ideal but still better than non working hardware. WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+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 1973217] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
Hello Frank, You noted that this may be due to update-manager having two instances running. Were you able to try again with one running to get it updated? If not, does updating with: sudo apt update sudo apt upgrade cause any errors? Thanks! ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1973217 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: It might be that two instances of update-manager seemed to be running at the same time. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 12 08:50:07 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-10-06 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 125: Bad configuration option: Host /etc/ssh/sshd_config: line 126: Bad configuration option: ForwardX11 /etc/ssh/sshd_config: terminating, 2 bad configuration options SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-09-29 (225 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1973217/+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 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdb (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971474 Title: SRU: Update gdb to the final 12.1 release in 22.04 LTS Status in gdb package in Ubuntu: Confirmed Bug description: Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes up to the final release are: - updated gnulib library - Fix for PR mi/29002 (Windows only) - gdb: fix 'remote show FOO-packet' aliases - various testsuite fixes - fixing compiler warnings - Fix bug in Ada number lexing - Remove "Ada Settings" node from the manual - Handle TLS variable lookups when using separate debug files. - PR 28980: gdb: don't copy entirely optimized out values in value_copy - gdb/mi: fix use after free of frame_info causing spurious notifications Comparing the test results between the two builds doesn't show any regression on any architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971474/+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 1973137] Re: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed
Hello Sebastian, Thank you for taking the time to make this bug report. The error you are encountering shows up through openldap, so marking the bug under openldap is fine. It may be due to multiple sources attempting to free a request. Does this error show up every time you attempt to log in? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1973137 Title: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed Status in openldap package in Ubuntu: New Bug description: I dont know it is openldap related: Operation System: Ubuntu 22.04 Packages: sssd-ldap 2.6.3-1ubuntu3 libldap-2.5-0:amd64 2.5.11+dfsg-1~exp1ubuntu3 libldap-common2.5.11+dfsg-1~exp1ubuntu3 I have configured sssd to use LDAPS over HAPROXY. With the latest Debian Version and Ubuntu 20.04 i have no error. But with Ubuntu 22.04 i randomly cant login. Syslog show this error: May 12 06:57:55 ingress2 sssd[870590]: sssd_be: ../../../../libraries/libldap/request.c:970: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed. If i configured SSSD to use directly our LDAP Server, its working. Regards Sebastian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1973137/+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 1973137] Re: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed
Hi Lena, i found the Problem after some time: I dont know why but Ubuntu 22.04 needs longer to take the LDAP Request. This is also the answer, why ldap without HAPROXY is working. Now i have set HAPROXY timeout to 5sec and it is working now. With Ubuntu 20.04 (same configuration) ldap Login with timeout of "1sec" is possible. Regards Sebastian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1973137 Title: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed Status in openldap package in Ubuntu: New Bug description: I dont know it is openldap related: Operation System: Ubuntu 22.04 Packages: sssd-ldap 2.6.3-1ubuntu3 libldap-2.5-0:amd64 2.5.11+dfsg-1~exp1ubuntu3 libldap-common2.5.11+dfsg-1~exp1ubuntu3 I have configured sssd to use LDAPS over HAPROXY. With the latest Debian Version and Ubuntu 20.04 i have no error. But with Ubuntu 22.04 i randomly cant login. Syslog show this error: May 12 06:57:55 ingress2 sssd[870590]: sssd_be: ../../../../libraries/libldap/request.c:970: ldap_do_free_request: Assertion `lr->lr_refcnt == 1' failed. If i configured SSSD to use directly our LDAP Server, its working. Regards Sebastian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1973137/+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 1869979] Re: liborc-0.4.so doesn't exist after install
In accordance with Debian Policy, the unversioned .so is available in the liborc-0.4-dev package. https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#development- files ** Changed in: orc (Ubuntu) Status: New => Invalid -- 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/1869979 Title: liborc-0.4.so doesn't exist after install Status in orc package in Ubuntu: Invalid Bug description: If you apt install liborc-0.4-0, there is no liborc-0.4.so file in /usr/lib/x86_64-linux-gnu/ There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but there is no link with name liborc-0.4.so pointing to that same file. I don't know if this is a bug or expected behavior, but it does trigger issues with other packages, such as out-of-tree modules for GNURadio: https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453 Those can be fixed with a simple symlink. If this is a problem with the build system of the other project (i.e., it should have picked up the so.0 file), my apologies and please close the issue. Thanks. System details: Description: Ubuntu 18.04.4 LTS Release: 18.04 Version: liborc-0.4-0 Installed: 1:0.4.28-1 Summary: I expect there to be a .so file by the name of the library somewhere on the system after installing. There is not one, but instead, the name I expect with a .so.0 extension exists, but there is no symlink with the expected name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1869979/+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 1973642] [NEW] [REGRESSION] Unable to connect to EAP-TLS networks
Public bug reported: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: jammy patch ** Patch added: "8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch" https://bugs.launchpad.net/bugs/1973642/+attachment/5590156/+files/8df79f60d616e183257ae1a2c2b48beaf29e5eec.patch ** Tags added: patch -- 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/1973642 Title: [REGRESSION] Unable to connect to EAP-TLS networks Status in network-manager package in Ubuntu: New Bug description: Fresh install of Xubuntu 22.04, currently with network-manager 1.36.4-2ubuntu1 Attempting to connect to an EAP-TLS network fails with: NetworkManager[703]: [1652732829.9142] device (wlp0s12f0): Activation: (wifi) connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager[703]: [1652732829.9143] Config: added 'ssid' value 'AP' NetworkManager[703]: [1652732829.9143] Config: added 'scan_ssid' value '1' NetworkManager[703]: [1652732829.9144] Config: added 'bgscan' value 'simple:30:-65:300' NetworkManager[703]: [1652732829.9144] Config: added 'key_mgmt' value 'WPA-EAP FT-EAP FT-EAP-SHA384 WPA-EAP-SHA256' NetworkManager[703]: [1652732829.9144] Config: added 'eap' value 'TLS' NetworkManager[703]: [1652732829.9144] Config: added 'fragment_size' value '1266' NetworkManager[703]: [1652732829.9144] Config: added 'ca_cert' value '' NetworkManager[703]: [1652732829.9144] Config: added 'domain_suffix_match' value '' NetworkManager[703]: [1652732829.9145] Config: added 'private_key' value '.key' NetworkManager[703]: [1652732829.9145] Config: added 'private_key_passwd' value '' NetworkManager[703]: [1652732829.9145] Config: added 'client_cert' value '.crt' NetworkManager[703]: [1652732829.9145] Config: added 'identity' value '' NetworkManager[703]: [1652732829.9146] Config: added 'proactive_key_caching' value '1' NetworkManager[703]: [1652732829.9178] sup-iface[c392e32eb812390f,0,wlp0s12f0]: assoc[473f0d33ad3574e9]: failure to add network: invalid message format NetworkManager[703]: [1652732829.9179] device (wlp0s12f0): state change: config -> failed (reason 'supplicant-failed', sys-iface-state: 'managed') Caused by NM providing an empty domain_suffix_match option Upstream commit fixing this (also attached): https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/8df79f60d616e183257ae1a2c2b48beaf29e5eec Upstream bug report: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
here is the result of the journalctl ** Attachment added: "result of the journalctl command" https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5590157/+files/journalctl.odt -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-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: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
I already tried to apply https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834 but this doesn't help. I also tried https://ubuntuforums.org/showthread.php?t=2474436 but doesn't help neither -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-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: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04
for https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 i'm a bit lost! What do I have to do with the 3 available files? -- 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/1970799 Title: wifi connection on hotspot with wpa enterprise on 22.04 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Status in wpa package in Ubuntu: Incomplete Bug description: With 20.04 I used a wifi connection with a hotspot Telenet with following parametres: security : WPA2 entreprise authentification : tunneled TLS no AC certificat drequired inner authentication : MSCHAPV2(non EAP) user name: my id password : my pswd with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200) This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK in appendice some infos --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michelvlt 1725 F pulseaudio /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2022-04-21 (7 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600 MachineType: Apple Inc. MacBookPro8,1 NonfreeKernelModules: wl Package: wpa PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-25-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: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 87.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245B3640C91C81 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245B3640C91C81 dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro8,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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
