[Touch-packages] [Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)
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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: Switch to "unified" cgroup hierarchy (cgroupv2) Status in lxc: Fix Released Status in lxd: Fix Released Status in snapd: Confirmed Status in docker.io package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Fix Released Status in snapd package in Ubuntu: In Progress Status in systemd package in Ubuntu: Confirmed Status in lxc package in Debian: Fix Released Status in systemd package in Debian: Fix Released Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Please test with generic kernel, and set both DAC1 and DAC2 to maximum, download the attached set-verb.sh, chmod a+x set-verb.sh, sudo ./set- verb.sh. Check if the bass spk could output sound? thx. ** Attachment added: "set-verb.sh" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5498623/+files/set-verb.sh -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4 --- openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0 to validate, as it is common on self-signed leaf certificates. (LP: #1926254) - d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch - d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch - d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch * Split d/p/pr12272.patch into multiple patchfiles to fix dpkg-source error when attempting to build a source package, due to pr12272.patch patching files multiple times within the same patch. (LP: #1927161) - d/p/lp-1927161-1-x86-Add-endbranch-to-indirect-branch-targets-fo.patch - d/p/lp-1927161-2-Use-swapcontext-for-Intel-CET.patch - d/p/lp-1927161-3-x86-Always-generate-note-gnu-property-section-f.patch - d/p/lp-1927161-4-x86_64-Always-generate-note-gnu-property-sectio.patch - d/p/lp-1927161-5-x86_64-Add-endbranch-at-function-entries-for-In.patch -- Matthew Ruffell Wed, 05 May 2021 12:13:30 +1200 -- 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/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Released Status in openssl source package in Groovy: Fix Released Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config
[Touch-packages] [Bug 1926254] Re: x509 Certificate verification fails when basicConstraints=CA:FALSE, pathlen:0 on self-signed leaf certs
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.4 --- openssl (1.1.1f-1ubuntu2.4) focal; urgency=medium * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0 to validate, as it is common on self-signed leaf certificates. (LP: #1926254) - d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch - d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch - d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch -- Matthew Ruffell Wed, 28 Apr 2021 12:37:28 +1200 ** Changed in: openssl (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: openssl (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Released Status in openssl source package in Groovy: Fix Released Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ c_rehash CA $ openssl genpkey
[Touch-packages] [Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
This bug was fixed in the package openssl - 1.1.1f-1ubuntu4.4 --- openssl (1.1.1f-1ubuntu4.4) groovy; urgency=medium * Allow x509 certificates which set basicConstraints=CA:FALSE,pathlen:0 to validate, as it is common on self-signed leaf certificates. (LP: #1926254) - d/p/lp-1926254-1-Allow-certificates-with-Basic-Constraints-CA-fa.patch - d/p/lp-1926254-2-Set-X509_V_ERR_INVALID_EXTENSION-error-for-inva.patch - d/p/lp-1926254-3-Add-test-cases-for-the-non-CA-certificate-with-.patch * Split d/p/pr12272.patch into multiple patchfiles to fix dpkg-source error when attempting to build a source package, due to pr12272.patch patching files multiple times within the same patch. (LP: #1927161) - d/p/lp-1927161-1-x86-Add-endbranch-to-indirect-branch-targets-fo.patch - d/p/lp-1927161-2-Use-swapcontext-for-Intel-CET.patch - d/p/lp-1927161-3-x86-Always-generate-note-gnu-property-section-f.patch - d/p/lp-1927161-4-x86_64-Always-generate-note-gnu-property-sectio.patch - d/p/lp-1927161-5-x86_64-Add-endbranch-at-function-entries-for-In.patch -- Matthew Ruffell Wed, 05 May 2021 12:13:30 +1200 ** Changed in: openssl (Ubuntu Groovy) Status: Fix Committed => Fix Released -- 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/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Groovy: Fix Released Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1926254] Update Released
The verification of the Stable Release Update for openssl has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1926254 Title: x509 Certificate verification fails when basicConstraints=CA:FALSE,pathlen:0 on self-signed leaf certs Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Released Bug description: [Impact] In openssl 1.1.1f, the below commit was merged: commit ba4356ae4002a04e28642da60c551877eea804f7 Author: Bernd Edlinger Date: Sat Jan 4 15:54:53 2020 +0100 Subject: Fix error handling in x509v3_cache_extensions and related functions Link: https://github.com/openssl/openssl/commit/ba4356ae4002a04e28642da60c551877eea804f7 This introduced a regression which caused certificate validation to fail when certificates violate RFC 5280 [1], namely, when a certificate has "basicConstraints=CA:FALSE,pathlen:0". This combination is commonly seen by self-signed leaf certificates with an intermediate CA before the root CA. Because of this, openssl 1.1.1f rejects these certificates and they cannot be used in the system certificate store, and ssl connections fail when you try to use them to connect to a ssl endpoint. The error you see when you try verify is: $ openssl verify -CAfile CA/rootCA_cert.pem -untrusted CA/subCA_cert.pem user1_cert.pem error 20 at 0 depth lookup: unable to get local issuer certificate error user1_cert.pem: verification failed The exact same certificates work fine on Xenial, Bionic and Hirsute. [1] https://tools.ietf.org/html/rfc5280.html [Testcase] We will create our own root CA, intermediate CA and leaf server certificate. Create necessary directories: $ mkdir reproducer $ cd reproducer $ mkdir CA Write openssl configuration files to disk for each CA and cert: $ cat << EOF >> rootCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Root-CA [ usr_cert ] basicConstraints= critical,CA:TRUE keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> subCA.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test RSA PSS Sub-CA [ usr_cert ] basicConstraints= critical,CA:TRUE,pathlen:0 keyUsage= critical,keyCertSign,cRLSign subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF $ cat << EOF >> user.cnf [ req ] prompt = no distinguished_name = req_distinguished_name x509_extensions = usr_cert [ req_distinguished_name ] C = DE O = Test Org CN = Test User [ usr_cert ] basicConstraints= critical,CA:FALSE,pathlen:0 keyUsage= critical,digitalSignature,keyAgreement extendedKeyUsage= clientAuth,serverAuth subjectKeyIdentifier= hash authorityKeyIdentifier = keyid:always EOF Then generate the necessary RSA keys and form certificates: $ openssl genpkey -algorithm RSA-PSS -out rootCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config rootCA.cnf -set_serial 01 -new -batch -sha256 -nodes -x509 -days 9125 -out CA/rootCA_cert.pem -key rootCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl genpkey -algorithm RSA-PSS -out subCA_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config subCA.cnf -new -out subCA_req.pem -key subCA_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in subCA_req.pem -CA CA/rootCA_cert.pem -CAkey rootCA_key.pem -out CA/subCA_cert.pem -CAserial rootCA_serial.txt -CAcreateserial -extfile subCA.cnf -extensions usr_cert -days 4380 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ c_rehash CA $ openssl genpkey -algorithm RSA-PSS -out user1_key.pem -pkeyopt rsa_keygen_bits:2048 $ openssl req -config user.cnf -new -out user1_req.pem -key user1_key.pem -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 $ openssl x509 -req -sha256 -in user1_req.pem -CA CA/subCA_cert.pem -CAkey
[Touch-packages] [Bug 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
Hi Dan, thanks for that. Interestingly it was much harder to reproduce the problem with debugging enabled, but we got it on about the 15th try. The log is attached. ** Attachment added: "systemd-networkd-1.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+attachment/5498612/+files/systemd-networkd-1.log -- 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/1928733 Title: Starting systemd Network Service fails with "Invalid argument" Status in systemd package in Ubuntu: Incomplete Bug description: This server has a new install of Ubuntu 18.04 server. Sometimes (around 50% of the time) when it boots systemd-networkd.service initially fails to start with an error as below. It then tries again and succeeds, however other services which depend on systemd-networkd have already failed on the dependency by then. From the output of "journalctl -u systemd-networkd": -- Reboot -- May 17 19:44:28 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. May 17 19:44:30 server1 systemd[1]: Failed to start Network Service. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. May 17 19:44:30 server1 systemd[1]: Stopped Network Service. May 17 19:44:30 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed May 17 19:44:30 server1 systemd[1]: Started Network Service. May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon May 17 19:53:11 2021 InstallationDate: Installed on 2021-03-18 (60 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.3 dmi.board.name: 04JN2K dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R440 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Touch-packages] [Bug 1927161] Update Released
The verification of the Stable Release Update for openssl has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Groovy: Fix Committed Status in openssl source package in Hirsute: Fix Committed Status in openssl source package in Impish: Fix Released Bug description: [impact] openssl doesn't build source properly because of a badly-constructed patch [test case] $ pull-lp-source openssl groovy ... $ cd openssl-1.1.1f/ $ quilt pop -a ... $ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.3 dpkg-buildpackage: info: source distribution groovy-security dpkg-buildpackage: info: source changed by Marc Deslauriers dpkg-source --before-build . dpkg-source: warning: can't parse dependency perl:native dpkg-source: error: diff 'openssl-1.1.1f/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 25 Test builds are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1927161-test [regression potential] any regression would likely cause a failed build or would affect the functionality that patch pr12272 was added for, which is adding support for Intel CET [scope] this is needed only for g and later this is caused by the bad patch 'pr12272.patch' which is only included in g/h/i, so this does not apply to f or earlier [other info] note that if the patches are applied, this bug is bypassed; i.e. if 'quilt pop -a' is removed from the test case above, the bug doesn't reproduce. this is only a problem when the patches aren't already applied and dpkg-buildpackage needs to call dpkg-source to apply the patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.9 --- zfs-linux (0.8.3-1ubuntu12.9) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:45 +0100 -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Update Released
The verification of the Stable Release Update for rtl8812au has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package virtualbox - 6.1.16-dfsg-6~ubuntu1.20.04.2 --- virtualbox (6.1.16-dfsg-6~ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:42:15 +0100 ** Changed in: virtualbox-hwe (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package r8168 - 8.048.00-1ubuntu0.20.04.2 --- r8168 (8.048.00-1ubuntu0.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:42 +0100 ** Changed in: rtl8812au (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.4 --- v4l2loopback (0.12.3-1ubuntu0.4) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:12 +0100 ** Changed in: virtualbox (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package lttng-modules - 2.12.2-1ubuntu1~20.04.2 --- lttng-modules (2.12.2-1ubuntu1~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:09 +0100 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package virtualbox-hwe - 6.1.16-dfsg- 6ubuntu1.20.04.2 --- virtualbox-hwe (6.1.16-dfsg-6ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:25 +0100 ** Changed in: zfs-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package iptables-netflow - 2.4-2ubuntu0.4 --- iptables-netflow (2.4-2ubuntu0.4) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:51 +0100 ** Changed in: liblzf (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package rtl8812au - 4.3.8.12175.20140902+dfsg- 0ubuntu13~20.04.2 --- rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:52 +0100 ** Changed in: sysdig (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package sysdig - 0.26.4-1ubuntu0.3 --- sysdig (0.26.4-1ubuntu0.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:09:03 +0100 ** Changed in: v4l2loopback (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package bcmwl - 6.30.223.271+bdcom- 0ubuntu7~20.04.2 --- bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:27 +0100 ** Changed in: dahdi-linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package oss4 - 4.2-build2010-5ubuntu6~20.04.2 --- oss4 (4.2-build2010-5ubuntu6~20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:32 +0100 ** Changed in: r8168 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package nvidia-graphics-drivers-340 - 340.108-0ubuntu5.20.04.2 --- nvidia-graphics-drivers-340 (340.108-0ubuntu5.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:05:47 +0100 ** Changed in: oss4 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package liblzf - 3.6-2~ubuntu1.20.04.2 --- liblzf (3.6-2~ubuntu1.20.04.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 17:11:50 +0100 ** Changed in: lime-forensics (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package evdi - 1.7.0+dfsg-1ubuntu1~20.04.3 --- evdi (1.7.0+dfsg-1ubuntu1~20.04.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:32 +0100 ** Changed in: gost-crypto (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package dm-writeboost - 2.2.9-1ubuntu1.2 --- dm-writeboost (2.2.9-1ubuntu1.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:23 +0100 ** Changed in: evdi (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package lime-forensics - 1.9-1ubuntu0.2 --- lime-forensics (1.9-1ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:08:00 +0100 ** Changed in: lttng-modules (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package gost-crypto - 0.3.2-2ubuntu0.2 --- gost-crypto (0.3.2-2ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:41 +0100 ** Changed in: iptables-netflow (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu6.2 --- dahdi-linux (1:2.11.1~dfsg-1ubuntu6.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:14 +0100 ** Changed in: dm-writeboost (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package backport-iwlwifi-dkms - 8324-0ubuntu3~20.04.3 --- backport-iwlwifi-dkms (8324-0ubuntu3~20.04.3) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:07:04 +0100 ** Changed in: bcmwl (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1914279] Re: linux from security may force reboots without complete dkms modules
This bug was fixed in the package acpi-call - 1.1.0-5ubuntu0.2 --- acpi-call (1.1.0-5ubuntu0.2) focal; urgency=medium * No change rebuild in security pocket. LP: #1914279. -- Dimitri John Ledkov Thu, 29 Apr 2021 16:06:55 +0100 ** Changed in: acpi-call (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: backport-iwlwifi-dkms (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Released Status in backport-iwlwifi-dkms source package in Focal: Fix Released Status in bcmwl source package in Focal: Fix Released Status in dahdi-linux source package in Focal: Fix Released Status in dm-writeboost source package in Focal: Fix Released Status in evdi source package in Focal: Fix Released Status in gost-crypto source package in Focal: Fix Released Status in iptables-netflow source package in Focal: Fix Released Status in liblzf source package in Focal: Fix Released Status in lime-forensics source package in Focal: Fix Released Status in lttng-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in oss4 source package in Focal: Fix Released Status in r8168 source package in Focal: Fix Released Status in rtl8812au source package in Focal: Fix Released Status in sysdig source package in Focal: Fix Released Status in v4l2loopback source package in Focal: Fix Released Status in virtualbox source package in Focal: Fix Released Status in virtualbox-hwe source package in Focal: Fix Released Status in zfs-linux source package in Focal: Fix Released Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
OK, wrote an email to realtek codec expert to ask for help. -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Performing verification for Groovy I enabled -proposed and installed libpam-modules libpam-modules-bin libpam-runtime libpam0g version 1.3.1-5ubuntu6.20.10.1 >From there, I set the pam_faillock configuration in: /etc/security/faillock.conf: deny = 3 unlock_time = 120 and also: /etc/pam.d/common-auth: # here are the per-package modules (the "Primary" block) authrequisite pam_faillock.so preauth auth[success=1 default=ignore] pam_unix.so nullok_secure auth[default=die] pam_faillock.so authfail authsufficient pam_faillock.so authsucc # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the "Additional" block) authoptionalpam_cap.so # end of pam-auth-update config >From there, I created a new user "dave", and rebooted the system. I connected via ssh with the "dave" user and used the wrong password 5 times. I then tried with the correct password and found the account to be locked. I waited 2 minutes, and tried again with the correct password, and I was logged in. When the account was locked, I logged in as the "ubuntu" user and ran: $ sudo faillock --user dave dave: WhenType Source Valid 2021-05-19 02:08:53 RHOST 192.168.122.1V 2021-05-19 02:08:58 RHOST 192.168.122.1V 2021-05-19 02:09:02 RHOST 192.168.122.1V And I could see the times that "dave" was locked. I also tested resetting via: $ sudo faillock --user dave --reset and "dave" was allowed to log in again. My tests agree with what Richard sees. Marking as verified for Groovy. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Performing verification for Hirsute I enabled -proposed and installed libpam-modules libpam-modules-bin libpam-runtime libpam0g version 1.3.1-5ubuntu6.21.04.1 >From there, I set the pam_faillock configuration in: /etc/security/faillock.conf: deny = 3 unlock_time = 120 and also: /etc/pam.d/common-auth: # here are the per-package modules (the "Primary" block) authrequisite pam_faillock.so preauth auth[success=1 default=ignore] pam_unix.so nullok_secure auth[default=die] pam_faillock.so authfail authsufficient pam_faillock.so authsucc # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the "Additional" block) authoptionalpam_cap.so # end of pam-auth-update config >From there, I created a new user "dave", and rebooted the system. I connected via ssh with the "dave" user and used the wrong password 5 times. I then tried with the correct password and found the account to be locked. I waited 2 minutes, and tried again with the correct password, and I was logged in. When the account was locked, I logged in as the "ubuntu" user and ran: $ sudo faillock --user dave dave: WhenType Source Valid 2021-05-19 01:50:25 RHOST 192.168.122.1V 2021-05-19 01:50:28 RHOST 192.168.122.1V 2021-05-19 01:50:31 RHOST 192.168.122.1V And I could see the times that "dave" was locked. I also tested resetting via: $ sudo faillock --user dave --reset and "dave" was allowed to log in again. My tests agree with what Richard sees. Marking as verified for Hirsute. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to:
[Touch-packages] [Bug 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12 --- initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) * hook-functions: - include firmware from /lib/firmware/updates (LP: #1571506) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [Impact] * Firmware files under /lib/firmware/updates would not be processed when running update-initramfs * The kernel org specifies that this is a location where firmware can be stored, so we should search there [Test Case] * Stage some firmware under /lib/firmware/updates * Run update-initramfs and ensure that the firmware in /lib/firmware/updates is found and included in the initramfs [Where problems could occur] * Since dpkg places no files in /lib/firmware/updates, we could end up picking up firmware changes that we did not intend [Other info] * This change already exists in groovy and beyond. It was pulled in when initramfs-tools version 0.137 was merged from Debian according to the kernel doc http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README Linux kernel will search firmware from "/lib/firmware/updates/" UTS_RELEASE, "/lib/firmware/updates", "/lib/firmware/" UTS_RELEASE, "/lib/firmware" But the add module function in initramfs-tools won't search the "/lib/firmware/updates". This problem applies to all Ubuntu releases. Attach patch to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Mon Apr 18 14:24:29 2016 InstallationDate: Installed on 2014-04-23 (725 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1571506/+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 1876570] Re: Could not resume from hibernation when swap is specified as device
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12 --- initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) * hook-functions: - include firmware from /lib/firmware/updates (LP: #1571506) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: initramfs-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+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 1876570] Re: Could not resume from hibernation when swap is specified as device
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1 --- initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+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 1876570] Re: Could not resume from hibernation when swap is specified as device
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5 --- initramfs-tools (0.136ubuntu6.5) focal; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5 --- initramfs-tools (0.136ubuntu6.5) focal; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1 --- initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.12 --- initramfs-tools (0.130ubuntu3.12) bionic; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) * hook-functions: - include firmware from /lib/firmware/updates (LP: #1571506) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: initramfs-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1927779] Re: MODULES=list results in error
This bug was fixed in the package initramfs-tools - 0.137ubuntu12.1 --- initramfs-tools (0.137ubuntu12.1) groovy; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1927779] Re: MODULES=list results in error
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.5 --- initramfs-tools (0.136ubuntu6.5) focal; urgency=medium * scripts/local-premount/resume: - Use readlink -f to correctly handle non-symlink $resume (LP: #1876570) * hook-functions: - when MODULES=list there will be no 'kernel' dir, so don't try to find anything there, as it will log an error (LP: #1927779) * hooks/fsck: - don't check PASSNO, always include fsck (LP: #1917780) -- Dan Streetman Thu, 18 Mar 2021 14:48:17 -0400 ** Changed in: initramfs-tools (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: initramfs-tools (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1917780] Update Released
The verification of the Stable Release Update for initramfs-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Released Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1927779] Update Released
The verification of the Stable Release Update for initramfs-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1927779 Title: MODULES=list results in error Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Invalid Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [impact] setting MODULES=list in /etc/initramfs-tools/initramfs.conf results in an error/warning when running update-initramfs [test case] edit initramfs.conf to change MODULES=list and run update-initramfs: $ grep MODULES /etc/initramfs-tools/initramfs.conf # MODULES: [ most | netboot | dep | list ] MODULES=list $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.8.0-48-generic find: ‘/var/tmp/mkinitramfs_Yr04uh/lib/modules/5.8.0-48-generic/kernel’: No such file or directory [regression potential] any regression would likely result in an initramfs that did not include the correct/required modules, and/or failure to build a new initramfs [scope] this is needed for f and g. this is not fixed in debian, but is fixed in h and i. the code in b is different and doesn't include this bug, so this doesn't apply to b. for debian, MR open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/48 [other info] this caused some of the 'amd64-*' autopkgtests to fail in h until it was fixed. those autopkgtests don't exist in g and earlier so this was not noticed until now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1927779/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Performing verification for Focal I enabled -proposed and installed libpam-modules libpam-modules-bin libpam-runtime libpam0g version 1.3.1-5ubuntu4.2 >From there, I set the pam_faillock configuration in: /etc/security/faillock.conf: deny = 3 unlock_time = 120 and also: /etc/pam.d/common-auth: # here are the per-package modules (the "Primary" block) authrequisite pam_faillock.so preauth auth[success=1 default=ignore] pam_unix.so nullok_secure auth[default=die] pam_faillock.so authfail authsufficient pam_faillock.so authsucc # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the "Additional" block) authoptionalpam_cap.so # end of pam-auth-update config >From there, I created a new user "dave", and rebooted the system. I connected via ssh with the "dave" user and used the wrong password 5 times. I then tried with the correct password and found the account to be locked. I waited 2 minutes, and tried again with the correct password, and I was logged in. When the account was locked, I logged in as the "ubuntu" user and ran: $ sudo faillock --user dave dave: WhenType Source Valid 2021-05-19 00:31:08 RHOST 192.168.122.1V 2021-05-19 00:31:13 RHOST 192.168.122.1V 2021-05-19 00:31:17 RHOST 192.168.122.1V And I could see the times that "dave" was locked. I also tested resetting via: $ sudo faillock --user dave --reset and "dave" was allowed to log in again. My tests agree with what Richard sees. Marking as verified for Focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to:
[Touch-packages] [Bug 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Performing verification for Bionic I enabled -proposed and installed libpam-modules libpam-modules-bin libpam-runtime libpam0g version 1.1.8-3.6ubuntu2.18.04.3 >From there, I set the pam_faillock configuration in: /etc/security/faillock.conf: deny = 3 unlock_time = 120 and also: /etc/pam.d/common-auth: # here are the per-package modules (the "Primary" block) authrequisite pam_faillock.so preauth auth[success=1 default=ignore] pam_unix.so nullok_secure auth[default=die] pam_faillock.so authfail authsufficient pam_faillock.so authsucc # here's the fallback if no module succeeds authrequisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around authrequiredpam_permit.so # and here are more per-package modules (the "Additional" block) authoptionalpam_cap.so # end of pam-auth-update config >From there, I created a new user "dave", and rebooted the system. I connected via ssh with the "dave" user and used the wrong password 5 times. I then tried with the correct password and found the account to be locked. I waited 2 minutes, and tried again with the correct password, and I was logged in. When the account was locked, I logged in as the "ubuntu" user and ran: $ sudo faillock --user dave dave: WhenType Source Valid 2021-05-19 00:57:10 RHOST 192.168.122.1V 2021-05-19 00:57:12 RHOST 192.168.122.1V 2021-05-19 00:57:16 RHOST 192.168.122.1V And I could see the times that "dave" was locked. I also tested resetting via: $ sudo faillock --user dave --reset and "dave" was allowed to log in again. My tests agree with what Richard sees. Marking as verified for Bionic. ** Tags removed: verification-needed-bionic ** Tags added: sts verification-done-bionic -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go
[Touch-packages] [Bug 1876570] Update Released
The verification of the Stable Release Update for initramfs-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1876570 Title: Could not resume from hibernation when swap is specified as device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Status in initramfs-tools source package in Hirsute: Fix Released Bug description: [impact] unable to resume from hibernation when resume= boot param is specified as device path [test case] set up device/partition for swap, e.g. /dev/vda2 add 'resume=/dev/vda2' kernel boot parameter hibernate power system back on; it should resume from /dev/vda2 instead of coldboot [regression potential] any regression would likely result in failure to correctly resume from hibernation, incorrectly attempting to resume from hibernation, or failing to resume from hibernation. [scope] this is needed in b/f/g/h this bug was introduced, ironically, by bug 1644975, which was added in bionic, so this bug doesn't exist in xenial. this code that introduced this bug isn't included in Debian, so no change is needed there. [original description] I originally experienced this on Pop!_OS but I have reproduced it on a freshly installed Ubuntu. 1. Ubuntu 20.04 LTS 2. initramfs-tools-core 0.136ubuntu6 3. I expect the system to resume from hibernation when running pm_hibernate 4. The system starts up anew when I try to resume I have setup a swap partition on /dev/vda2 in /etc/fstab. To enable hibernate I added the kernel parameter "resume=/dev/vda2" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. From debugging initramfs it tries to follow a symbolic link DEV=$(readlink "$resume") (see /usr/share/initramfs-tools/scripts/local-premount/resume, line 35) which works well when swap is specified with uuid. When swap is specified as a device directly the readlink returns an empty string and the system does not resume from hibernation. To verify this I added the parameter -f to readlink and run "update- initramfs -u". The system now hibernates successfully. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 13:26:02 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570/+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 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt
The focal and groovy autopkgtest failures in apt-clone look suspiciously
like real regressions. Do we have an analysis of those?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
[SRU] Backport zstd support, fix bug in python-apt
Status in apt package in Ubuntu:
Fix Released
Status in python-apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in python-apt source package in Xenial:
Fix Committed
Status in python-apt source package in Bionic:
Fix Committed
Status in python-apt source package in Focal:
Fix Committed
Status in python-apt source package in Groovy:
Fix Committed
Status in python-apt source package in Hirsute:
Fix Released
Status in python-apt source package in Impish:
Fix Released
Bug description:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if
/usr/bin/zstd does not exist, it will pass "false" as the compressor,
and then ExtractTar fails (same for other compressors).
On hirsute, the python-apt upload also includes some new
annotations for build-dependencies, as it's a straight upload of the 2.2
stable series.
[Test plan]
The apt regression tests cover the compression methods extensively, including
even stored compressed lists in /var/lib/apt and fetching Packages files
compressed with such methods, for all compression methods.
The final test is to make apt_inst.DebFile("glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
1923845 work in python3-apt.
For hirsute, the build dependency changes will verify themselves
during the build ;)
[Where problems could occur]
APT:
The changes to APT are adding the zstd compression backend to FileFd
and then linking it into the configuration. The former is adding new
code, triggered only on zstd files, and should not be able to cause
regressions.
The latter is a bunch of small lines here and there, and it caused
issues during backporting in the test suite because it expected
compressors in a specific order. However, chances are that nothing
else has as stringent requirements as the test suite, so I don't
believe that is a problem for existing users.
Bugs can of course be in the code dealing with zstd, and that might
open you up to security vulnerabilities in the zstd code if you pass
APT zstd compressed files.
A regression can be if clients used apt-helper cat-file to cat a zstd-
compressed file ending in .zst - they'll now get uncompressed content,
rather than compressed.
python-apt:
The change just replaces Binary with Name, aligning the code with APT
itself, so it's so trivial, we don't expect regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+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 1919255] Re: tracker-store crashed with signal 5
Mine still happens every day about 5 minutes after starting up On Tue, May 18, 2021, 15:10 Merlin <1919...@bugs.launchpad.net> wrote: > I saw this for a few days after a fresh install of Hirsute. It would > happen shortly after boot, but it seems to have stopped. It could be > because tracker has now scanned everything. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1919255 > > Title: > tracker-store crashed with signal 5 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
By following the same test procedure done in #18 and #19, the Hirsute build of pam_faillock was successfully validated. -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
@gjolly There were networking-related changes in systemd which could have
caused this but I also see that the kernel packages also changed between the
Azure images:
-ii linux-image-azure 5.8.0.1017.19+21.04.14
...
+ii linux-image-5.8.0-1022-azure 5.8.0-1022.24+21.04.2
Could you please prepare an image that has the older kernel and newer
systemd to rule out kernel changes causing the issue?
Also do you still observe the issue in Impish? It has systemd 248 now.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1919255] Re: tracker-store crashed with signal 5
I saw this for a few days after a fresh install of Hirsute. It would happen shortly after boot, but it seems to have stopped. It could be because tracker has now scanned everything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1919255 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: Confirmed Bug description: This just happened... ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Mon Mar 15 17:47:12 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-02-28 (15 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227) ProcCmdline: /usr/libexec/tracker-store Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1919255/+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 1928360] Re: Switch to Fcitx 5 for Chinese
Sure, Seth, attached please find the output from cat /var/log/audit/audit.log | grep DENIED ** Attachment added: "apparmor_denied-lines_chromium.txt" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1928360/+attachment/5498578/+files/apparmor_denied-lines_chromium.txt -- 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/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
By following the same test procedure done in #18 and #19, the Groovy build of pam_faillock was successfully validated. -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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] [apparmor] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
On Tue, May 18, 2021 at 07:39:48PM -, Gunnar Hjalmarsson wrote: > On 2021-05-16 22:23, Gunnar Hjalmarsson wrote: > > As regards apparmor it's possible that no change is needed. > > Well, I simply tested with the Chromium snap. fcitx5 does not work in > Chromium, while fcitx4 does. So something needs to be done. Excellent, can you paste the DENIED lines from your test into the bug report? Thanks -- 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/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
By following the same test procedure done in #18 and #19, the Focal build of pam_faillock was successfully validated. -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Additional tests done on bionic: after changing the parameters set in /etc/security/faillock.conf to: deny=2 unlock_time=20 By trying to authenticate with the wrong password 2 times, it was verified that the account was locked for the amount of time set to the unlock_time parameter (20s). -- 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/1927796 Title: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix Status in pam package in Ubuntu: Fix Committed Status in pam source package in Bionic: Fix Committed Status in pam source package in Focal: Fix Committed Status in pam source package in Groovy: Fix Committed Status in pam source package in Hirsute: Fix Committed Status in pam source package in Impish: Fix Committed Bug description: [IMPACT] There is a known issue in pam_tally2 which may cause an account to be lock down even with correct password, in a busy node environment where simultaneous logins takes place (https://github.com/linux-pam/linux-pam/issues/71). There are already two customer cases from Canonical clients complaining about this behavior (00297697 and 00303806). Also, potentially, this will cause further problems in the future, since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to lock accounts when wrong passwords are used. And both benchmarks - but specially STIG - requires use of a lot of audit rules, which can lead to the busy node environment. The issue impacts all pam_tally2 versions distributed in all currently supported Ubuntu versions and also the next unreleased one. Note that, according to https://github.com/linux-pam/linux-pam/issues/71, there is no plan to fix this issue! [FIX] This fix proposes to add pam_faillock module to the PAM package, so users of pam_tally2 having issues can migrate to pam_faillock. We also plan to modify the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but in order to do so, we need the pam_faillock module to be available. Note that we don't propose to remove pam_tally2, since not every user of this module is affected. [TEST] Tested on a VM installed with Focal server iso and on another with Bionic server iso. Enabled pam_faillock module as recommeded by its man page. Then tried to log over ssh with an incorrect password, until the account got locked. Waited for the configured grace time to unlock and logged in using the correct password. Note that, since the pam_tally2 issue is caused by a racing condition, with a hard to recreate environment (we could not even reproduce it with pam_tally2), we could not reproduce the conditions to test pam_faillock with. [REGRESSION POTENTIAL] The regression potential for this is small, since we're not removing the old pam_tally2 module, just adding another one. So anyone still using pam_tally2 will be able to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1928360] Re: Switch to Fcitx 5 for Chinese
On 2021-05-16 22:23, Gunnar Hjalmarsson wrote: > As regards apparmor it's possible that no change is needed. Well, I simply tested with the Chromium snap. fcitx5 does not work in Chromium, while fcitx4 does. So something needs to be done. -- 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/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: In Progress Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+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 1928604] Re: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases
Thanks for taking the time to file this bug and trying to make Ubuntu better. ubuntu-advantage-tools does not provide only a way to enable ESM, it also provides a bunch of other services (from the project README): "The Ubuntu Advantage client provides users with a simple mechanism to view, enable, and disable offerings from Canonical on their system. The following entitlements are supported: Common Criteria EAL2 certification artifacts provisioning Canonical CIS Benchmark Audit Tool Ubuntu Extended Security Maintenance FIPS 140-2 Certified Modules FIPS 140-2 Non-Certified Module Updates Livepatch Service " Those other services might be useful in non-EOL releases. Due to that, the package is installed by default in all supported releases. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1928604 Title: ubuntu-advantage-tools should not be auto-installed on supported Ubuntu releases Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Bug description: I understand that Canonical thinks about financial profit. It is business and it is good. But please do not install ubuntu-advantage-tools to supported releases like 18.04 LTS, 20.04 LTS and 21.04. It may confuse users. Users do not expect ESM existence on supported systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1928604/+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 1927796] Re: [SRU]pam_tally2 can cause accounts to be locked by correct password. pam_faillock use is the recommended fix
Tested pam_faillock module for pam on bionic.
Test consisted on setting up pam_faillock with the following
configuration, as described in the man page:
/etc/security/faillock.conf file example:
deny=4
unlock_time=1200
silent
/etc/pam.d/config file example:
auth required pam_faillock.so preauth
# optionally use requisite above if you do not want to prompt for the password
# on locked accounts
auth sufficient pam_unix.so
auth [default=die] pam_faillock.so authfail
auth required pam_deny.so
account required pam_faillock.so
# if you drop the above call to pam_faillock.so the lock will be done also
# on non-consecutive authentication failures
account required pam_unix.so
A new user 'joas' was created and its password set. Then, initially, 4
logins were made through ssh and terminal, using the correct password.
All were successful.
User 'joas' was, then, logged out and 4 attempts to login with incorrect
password were made. Since pam_faillock module was set to lock on the 4th
incorrect attempt, another try was done, this time with the correct
password.
After confirming that the 'joas' account was locked, by trying, with the
correct password, additional times, the superuser account was used to
display the account stats ('faillock --user joas') and then used to
unlock the 'joas' account ('faillock --user joas --reset').
Then, again 4 logins were made using the correct password, in order to
check it was successfully authenticating.
Another test consisted on typing the wrong password 3 times, then typing
the correct one, to make sure the PAM module was properly resetting the
counter.
--
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/1927796
Title:
[SRU]pam_tally2 can cause accounts to be locked by correct password.
pam_faillock use is the recommended fix
Status in pam package in Ubuntu:
Fix Committed
Status in pam source package in Bionic:
Fix Committed
Status in pam source package in Focal:
Fix Committed
Status in pam source package in Groovy:
Fix Committed
Status in pam source package in Hirsute:
Fix Committed
Status in pam source package in Impish:
Fix Committed
Bug description:
[IMPACT]
There is a known issue in pam_tally2 which may cause an account to be lock
down even with correct password, in a busy node environment where simultaneous
logins takes place (https://github.com/linux-pam/linux-pam/issues/71).
There are already two customer cases from Canonical clients
complaining about this behavior (00297697 and 00303806).
Also, potentially, this will cause further problems in the future,
since both STIG benchmarks and CIS benchmarks rely on pam_tally2 to
lock accounts when wrong passwords are used. And both benchmarks - but
specially STIG - requires use of a lot of audit rules, which can lead
to the busy node environment.
The issue impacts all pam_tally2 versions distributed in all currently
supported Ubuntu versions and also the next unreleased one. Note that,
according to https://github.com/linux-pam/linux-pam/issues/71, there
is no plan to fix this issue!
[FIX]
This fix proposes to add pam_faillock module to the PAM package, so users of
pam_tally2 having issues can migrate to pam_faillock. We also plan to modify
the current STIG benchmarks to rely on pam_faillock instead of pam_tally2, but
in order to do so, we need the pam_faillock module to be available.
Note that we don't propose to remove pam_tally2, since not every user
of this module is affected.
[TEST]
Tested on a VM installed with Focal server iso and on another with Bionic
server iso. Enabled pam_faillock module as recommeded by its man page. Then
tried to log over ssh with an incorrect password, until the account got locked.
Waited for the configured grace time to unlock and logged in using the correct
password.
Note that, since the pam_tally2 issue is caused by a racing condition,
with a hard to recreate environment (we could not even reproduce it
with pam_tally2), we could not reproduce the conditions to test
pam_faillock with.
[REGRESSION POTENTIAL]
The regression potential for this is small, since we're not removing the old
pam_tally2 module, just adding another one. So anyone still using pam_tally2
will be able to do so.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1927796/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
Thank you for the links!
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => In Progress
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Dmitry Shachnev (mitya57)
--
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/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in qtbase-opensource-src package in Ubuntu:
In Progress
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
Confirmed that patched [1][2] Qt fixes this bug.
[1] https://codereview.qt-project.org/c/qt/qtbase/+/328240
[2]
https://launchpadlibrarian.net/539330399/qtbase-opensource-src_5.15.2+dfsg-5+0.drop.0_5.15.2+dfsg-5+0.drop.1.diff.gz
--
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/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 273507] Re: No sound effects play when "play sound effects when buttons are clicked" is enabled
@Chris that linked comment seems like spam, I reported it now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/273507 Title: No sound effects play when "play sound effects when buttons are clicked" is enabled Status in libcanberra package in Ubuntu: Triaged Bug description: Binary package hint: libcanberra-gtk-module As initially detailed in some of the comments in #258703, selecting the "Play sound effects when buttons are clicked" has no effect. The instructions in this mailing list post (https://tango.0pointer.de/pipermail/libcanberra- discuss/2008-July/21.html) need to be followed to enable libcanberra gtk integration, which will properly enable gtk-sound effects. Quoted here: "...Packagers! If you package libcanberra, make sure to include a script like this one in your package: #!/bin/sh if [ -z "$GTK_MODULES" ] ; then GTK_MODULES="libcanberra-gtk-module" else GTK_MODULES="$GTK_MODULES:libcanberra-gtk-module" fi export GTK_MODULES This script should be sourced in each Gnome session and will enable the libcanberra gtk module for all gtk programs. In fedora we install it as "libcanberra-gtk-module.sh" in /etc/X11/xinit/xinitrc.d/. I assume other distributions have similar directories. ..." I think this is missing from the ubuntu libcanberra packages, which is preventing the gtk sound effects from working properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/273507/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
DAC1 - no sound DAC2 - sound(only through the top speaker bar) -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
> 1st test: set the DAC1 volume to minimum, and set the DAC2 volume to maximum, could you still hear the music? Does the sound comes from front speaker or rear speaker? Music works, bass speakers are not enabled. > 2nd test: set the DAC1 voluem to maximum, and set the DAC2 volume to minimum, could you still hear the music? Does the sound comes from front speaker or rear speaker? There is no sound at all. -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1919177] Re: Azure: issues with accelerated networking on Hirsute
Hi there,
Is there any update on this issue? I would like to understand who owns
the investigation/debugging process? Please tell us if you need any help
from the CPC team.
--
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/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in cloud-init:
Incomplete
Status in cloud-init package in Ubuntu:
Incomplete
Status in linux-azure package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not
applied.
Especially, in those cases, the public SSH key is not setup properly.
[how to reproduce]
Start a VM with AN enabled:
```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"
--image
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY"
--accelerated-networking
```
After a moment, try to SSH: if you succeed, delete and recreate a new
VM.
[troubleshooting]
To be able to connect into the VM, run:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```
In "/run/cloud-init/instance-data.json", I can see:
```
"publicKeys": [
{
"keyData": "",
"path": "/home/ubuntu/.ssh/authorized_keys"
}
],
```
as expected.
[workaround]
As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:
az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
This example uses "ssh-import-id" but it's also possible to just echo
a given public key into /home/ubuntu/.ssh/authorized_keys
NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1919177/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Not sure if it helps, but when i run speaker-test -c 5, all 5 channels get sent to the speaker bar up top. -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource- src/+bug/1857824/comments/12 ** Changed in: qtbase-opensource-src (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/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
shared-mime-info 2.0-1 Published in groovy-release on 2020-10-14 ** Changed in: shared-mime-info (Ubuntu) Status: Fix Committed => Fix Released -- 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/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: Invalid Status in shared-mime-info package in Ubuntu: Fix Released Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1928733] Re: Starting systemd Network Service fails with "Invalid argument"
can you turn on systemd debug (e.g. with systemd.log_level=debug boot parameter) and reproduce the error, then check the logs for additional messages indicating what the failure is ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1928733 Title: Starting systemd Network Service fails with "Invalid argument" Status in systemd package in Ubuntu: Incomplete Bug description: This server has a new install of Ubuntu 18.04 server. Sometimes (around 50% of the time) when it boots systemd-networkd.service initially fails to start with an error as below. It then tries again and succeeds, however other services which depend on systemd-networkd have already failed on the dependency by then. From the output of "journalctl -u systemd-networkd": -- Reboot -- May 17 19:44:28 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set up mount namespacing: Invalid argument May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=226/NAMESPACE May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with result 'exit-code'. May 17 19:44:30 server1 systemd[1]: Failed to start Network Service. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 1. May 17 19:44:30 server1 systemd[1]: Stopped Network Service. May 17 19:44:30 server1 systemd[1]: Starting Network Service... May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed May 17 19:44:30 server1 systemd[1]: Started Network Service. May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not managed by us May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.46 ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18 Uname: Linux 4.15.0-142-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 Date: Mon May 17 19:53:11 2021 InstallationDate: Installed on 2021-03-18 (60 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 transparent_hugepage=never SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.3 dmi.board.name: 04JN2K dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R440 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
specially:
"The spec hasn't changed, but I made the same mistake in xdgmime
(the reference implementation) and in Qt: when multiple globs match,
and the result from magic sniffing is unrelated to any of those globs,
then I used the magic result, but that's wrong, globs have priority
and one of them should be picked up."
and there is multiple glob matches:
--
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/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
Qt actually prefers system copy from shared-mime-info if it's available.
Here is the code for 5.12.8 (used in Ubuntu 20.04):
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/mimetypes/qmimedatabase.cpp?h=5.12.8#n99
The internal copy (":/qt-project.org/qmime") is only used when the
system one is missing (fdoIterator == mimeDirs.constEnd()).
Furthermore, in Ubuntu 20.10 and 21.04 we are building Qt with -no-
mimetype-database, which makes Qt use *only* the system copy:
https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/f0d53be16a31ea55
So I think it is a bug in shared-mime-info only, not in Qt. Do you
agree?
--
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/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
maybe fixed: https://codereview.qt-project.org/c/qt/qtbase/+/328240
** Package changed: kde-cli-tools (Ubuntu) => qtbase-opensource-src
(Ubuntu)
--
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/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in qtbase-opensource-src package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
** Package changed: kde-cli-tools (Ubuntu) => qtbase-opensource-src (Ubuntu) -- 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/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in qtbase-opensource-src package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+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 1857824] [NEW] kmimetypefinder5 misidentifies mimetype of python files containing certain strings
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd;>
http://www.w3.org/1999/xhtml;>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: qtbase-opensource-src (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
kmimetypefinder5 misidentifies mimetype of python files containing certain
strings
https://bugs.launchpad.net/bugs/1857824
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to qtbase-opensource-src 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 1770271] Re: VegaM support
** Changed in: amd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770271 Title: VegaM support Status in amd: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in mesa source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: VegaM is a new GPU. Please include support for VegaM in the next LTS (16.04.x and 18.04.x) and non-LTS releases. Kernel support starts here (32 patches): https://patchwork.freedesktop.org/patch/218839/ Mesa support: https://cgit.freedesktop.org/mesa/mesa/commit/?id=d6a66bc8dbcdeed8e87f649bc281de0d60d2f123 https://cgit.freedesktop.org/mesa/mesa/commit/?id=c6f1d360198c52d208645c0ccb5e988cded408e8 https://cgit.freedesktop.org/mesa/mesa/commit/?id=90de03708fa269ad54de881b467f4811e4eef87e To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1770271/+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 1928789] Re: bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1928789 Title: bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Warning from zsys that bpool only had 11% free space when manually running "apt upgrade". There were also several packages that could be "auto-removed". Once apt autoremove was run, the linux-firmware was installed OK. Perhaps apt (or package install) could: a) detect low disk space b) note that free space can be made with autoremove c) stop and raise an error, rather than crashing. $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-5.8.0-49-generic linux-hwe-5.8-headers-5.8.0-49 linux-image-5.8.0-49-generic linux-modules-5.8.0-49-generic linux-modules-extra-5.8.0-49-generic python3-appdirs python3-distlib python3-filelock python3-importlib-metadata python3-more-itertools python3-virtualenv python3-zipp 0 to upgrade, 0 to newly install, 12 to remove and 1 not to upgrade. 2 not fully installed or removed. After this operation, 391 MB disk space will be freed. Do you want to continue? [Y/n] y Requesting to save current system state ERROR couldn't save system state: Minimum free space to take a snapshot and preserve ZFS performance is 20%. Free space on pool "bpool" is 11%. Please remove some states manually to free up space. (Reading database ... 289639 files and directories currently installed.) Removing linux-headers-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-hwe-5.8-headers-5.8.0-49 (5.8.0-49.55~20.04.1) ... Removing linux-modules-extra-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-image-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... /etc/kernel/prerm.d/dkms: dkms: removing: virtualbox 6.1.16 (5.8.0-49-generic) (x86_64) Uninstall Beginning Module: virtualbox Version: 6.1.16 Kernel: 5.8.0-49-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.8.0-49-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image:
[Touch-packages] [Bug 1928789] [NEW] bpool free space low caused package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returne
Public bug reported: Warning from zsys that bpool only had 11% free space when manually running "apt upgrade". There were also several packages that could be "auto-removed". Once apt autoremove was run, the linux-firmware was installed OK. Perhaps apt (or package install) could: a) detect low disk space b) note that free space can be made with autoremove c) stop and raise an error, rather than crashing. $ sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED linux-headers-5.8.0-49-generic linux-hwe-5.8-headers-5.8.0-49 linux-image-5.8.0-49-generic linux-modules-5.8.0-49-generic linux-modules-extra-5.8.0-49-generic python3-appdirs python3-distlib python3-filelock python3-importlib-metadata python3-more-itertools python3-virtualenv python3-zipp 0 to upgrade, 0 to newly install, 12 to remove and 1 not to upgrade. 2 not fully installed or removed. After this operation, 391 MB disk space will be freed. Do you want to continue? [Y/n] y Requesting to save current system state ERROR couldn't save system state: Minimum free space to take a snapshot and preserve ZFS performance is 20%. Free space on pool "bpool" is 11%. Please remove some states manually to free up space. (Reading database ... 289639 files and directories currently installed.) Removing linux-headers-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-hwe-5.8-headers-5.8.0-49 (5.8.0-49.55~20.04.1) ... Removing linux-modules-extra-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... Removing linux-image-5.8.0-49-generic (5.8.0-49.55~20.04.1) ... /etc/kernel/prerm.d/dkms: dkms: removing: virtualbox 6.1.16 (5.8.0-49-generic) (x86_64) Uninstall Beginning Module: virtualbox Version: 6.1.16 Kernel: 5.8.0-49-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/5.8.0-49-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.8.0-49-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-53-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found initrd image: initrd.img-5.8.0-50-generic in rpool/ROOT/ubuntu_l3g9y7 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found initrd image: initrd.img-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_8mgn83 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found initrd image: initrd.img-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_z80dj8 Found linux image: vmlinuz-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found initrd image: initrd.img-5.4.0-58-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found linux image: vmlinuz-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found initrd image: initrd.img-5.4.0-56-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found linux image: vmlinuz-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found initrd image: initrd.img-5.4.0-53-generic in rpool/ROOT/ubuntu_l3g9y7@autozsys_izpa76 Found linux image:
[Touch-packages] [Bug 1921484] Re: libedit no longer reads editrc
Same here, mysql command line used to read bindings from .editrc in previous versions of Ubuntu Server, now fails to honor them in 20.04 LTS. Strace confirms that libedit is not opening the file .editrc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1921484 Title: libedit no longer reads editrc Status in libedit package in Ubuntu: Confirmed Bug description: strings /usr/lib/x86_64-linux-gnu/libedit.so.2.0.56 |grep editrc in Ubuntu 18.04 LTS returns /.editrc as expected but strings /usr/lib/x86_64-linux-gnu/libedit.so.2.0.63 |grep editrc in Ubuntu 20.04 LTS comes back empty. Verified with strace'ing the mysql client as well: editrc is no longer picked up, making mysql rather irritating to use. Peeking at the source code, the problematic commit is d253f567 which wraps the editrc code in an "#ifdef HAVE_ISSETUGID" which is BSD only. I am unable to find upstream in version control to help further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1921484/+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 1921484] Re: libedit no longer reads editrc
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1921484 Title: libedit no longer reads editrc Status in libedit package in Ubuntu: Confirmed Bug description: strings /usr/lib/x86_64-linux-gnu/libedit.so.2.0.56 |grep editrc in Ubuntu 18.04 LTS returns /.editrc as expected but strings /usr/lib/x86_64-linux-gnu/libedit.so.2.0.63 |grep editrc in Ubuntu 20.04 LTS comes back empty. Verified with strace'ing the mysql client as well: editrc is no longer picked up, making mysql rather irritating to use. Peeking at the source code, the problematic commit is d253f567 which wraps the editrc code in an "#ifdef HAVE_ISSETUGID" which is BSD only. I am unable to find upstream in version control to help further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1921484/+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 273507] Re: No sound effects play when "play sound effects when buttons are clicked" is enabled
Hi its a good weather with a good smoke from https://www.medicalmarijuanabudshop.com/ their service is amazing try them out -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/273507 Title: No sound effects play when "play sound effects when buttons are clicked" is enabled Status in libcanberra package in Ubuntu: Triaged Bug description: Binary package hint: libcanberra-gtk-module As initially detailed in some of the comments in #258703, selecting the "Play sound effects when buttons are clicked" has no effect. The instructions in this mailing list post (https://tango.0pointer.de/pipermail/libcanberra- discuss/2008-July/21.html) need to be followed to enable libcanberra gtk integration, which will properly enable gtk-sound effects. Quoted here: "...Packagers! If you package libcanberra, make sure to include a script like this one in your package: #!/bin/sh if [ -z "$GTK_MODULES" ] ; then GTK_MODULES="libcanberra-gtk-module" else GTK_MODULES="$GTK_MODULES:libcanberra-gtk-module" fi export GTK_MODULES This script should be sourced in each Gnome session and will enable the libcanberra gtk module for all gtk programs. In fedora we install it as "libcanberra-gtk-module.sh" in /etc/X11/xinit/xinitrc.d/. I assume other distributions have similar directories. ..." I think this is missing from the ubuntu libcanberra packages, which is preventing the gtk sound effects from working properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/273507/+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 1928001] Re: [SRU] New stable release 2.68.1
automake-1.16> same started happening in impish too - you could cherry- pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe? netplan.io> slyon told me this is known bad and is skipped in other releases already (upstream) and will be included in the next SRU to hirsute, if any. could be hinted too? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Committed Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+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 873072] Re: Postinst error: chown: invalid group: `root:messagebus'
Maybe you need to copy /etc/group as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/873072 Title: Postinst error: chown: invalid group: `root:messagebus' Status in dbus package in Ubuntu: Confirmed Bug description: In Ubuntu Core 11.10 daily in chroot environment with host's /etc/passwd and /etc/shadow copied in chroot I get the following error on installing dbus package: chown: invalid group: `root:messagebus' dpkg: error processing dbus (--configure): subprocess installed post-installation script returned error exit status 1 This error paralyzes any further attempts to install anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/873072/+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 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04
Ok the other machine I was having this issue with is a kvm-qemu virtual machine acting as a mail server. On it I remove xorg-xserver-video* and with those removed it no longer hangs. So it seems somehow xserver graphics/video are involved. My workstation is using intel internal graphics and it is an i7-9700k so I use the kernel based x-server on it and don't need the others. -- 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/1928564 Title: systemctl reboot hangs the machine under hirsute 21.04 Status in systemd package in Ubuntu: Incomplete Bug description: If you type "systemctl reboot" instead of rebooting the machine hangs hard, nothing except a hard power cycle seems to get it's attention. This is true of both physical hardware and virtual machines, it was NOT a problem under groovy. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 Uname: Linux 5.12.4 x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat May 15 19:12:59 2021 InstallationDate: Installed on 2020-08-10 (278 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.12.4 root=UUID=1065426b-f156-4c90-a98b-e7258e07a88f ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to hirsute on 2021-05-12 (3 days ago) dmi.bios.date: 06/04/2020 dmi.bios.release: 16.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd06/04/2020:br16.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.resolved.conf: 2020-12-17T10:04:04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+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 1664844] Re: No distinction between link-up and link-down interfaces
** Description changed: [Impact] + + Since very long, we had a feature request in netplan to determine the + activation mode of a given network interface. We got requests to enable + marking some interfaces as 'manual', meaning that networkd (or any other + backend) would not control its state in any way, requiring the + administrator to bring the interface up or down manually. The other + request was to mark a interface as 'off', that is: forcing the network + interface to always be down until the configuration option isn't + changed. + + This was mainly requested for the networkd backend and requires the new + feature of specifying ActivationPolicy= for interfaces, alongside the + required netplan changes. + + This feature is present in systemd 248 - for netplan supported stable + series we have decided to cherry-pick and backport this feature on top + of current systemd. The networkd feature basically adds the following 5 + ActivationPolicy modes: always-down, down, manual, up, always-up. For + netplan purposes we only use 'always-down' and 'manual'. + + The netplan feature, hopefully landing as part of 0.103, is called + 'activation-mode' and supports two values: 'manual' and 'off'. + + [Test Case] + + For the systemd part: + + * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. + * Upgrade systemd to the -proposed version + * For the target interface, create/modify the networkd configuration (for instance by adding /etc/systemd/network/20-.network) to include the ActivationPolicy= setting in [Link], for instance: + + [Match] + Name=dummy0 + + [Network] + Address=192.168.10.30/24 + Gateway=192.168.10.1 + + [Link] + ActivationPolicy=manual + + * Try all 5 combinations of ActivationPolicy values: always-down, down, + manual, up, always-up - doing `sudo networkctl reload` everytime and + checking if the interface behaves as expected. + + [Where problems could occur] + + The patchset modifies quite a lot of code in the networkd link handling + code paths, so regressions could appear in how networkd manages links - + maybe by suddenly certain interfaces not getting brought up as they were + before. + + --- + + + [Original Description] + + [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". - [Test case] + [Old Test case] Write a netplan configuration: network: - version: 2 - renderer: networkd - ethernets: - eth0: - optional: yes - dhcp4: yes + version: 2 + renderer: networkd + ethernets: + eth0: + optional: yes + dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. - [Regression potential] + [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that implies that not only its adminStatus is "disabled" by default, but also netplan will not be able to do anything "nice" for the interface, such as rename it to what the user specified in MAAS. If I include the interface but don't specify any addresses or DHCP, it isn't clear if it will be link up (my current assumption) or link down. There should be a way to allow an interface to be recognized by netplan (and even partially configured, waiting for the user to run something like 'ifup ' on a manual but not auto-started interface in ifupdown), but marked administratively disabled. (adminStatus down) ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released -- 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/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: In Progress Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in
[Touch-packages] [Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported
The GTK issue is known as https://gitlab.gnome.org/GNOME/gtk/-/issues/931 There is perhaps a cheese issue there as well though on what it's trying to render ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #931 https://gitlab.gnome.org/GNOME/gtk/-/issues/931 -- 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/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID
[Touch-packages] [Bug 1928763] Re: Ubuntu does not recognize the touchpad
*** This bug is a duplicate of bug 1881319 *** https://bugs.launchpad.net/bugs/1881319 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1881319, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1881319 Touchpad not recognized Lenovo IdeaPad 5 15ARE05 -- 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/1928763 Title: Ubuntu does not recognize the touchpad Status in linux package in Ubuntu: New Bug description: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928763/+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 1928763] [NEW] Ubuntu does not recognize the touchpad
Public bug reported: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- 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/1928763 Title: Ubuntu does not recognize the touchpad Status in xorg package in Ubuntu: New Bug description: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
[Touch-packages] [Bug 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported
** Package changed: cheese (Ubuntu) => gtk+3.0 (Ubuntu) -- 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/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to:
[Touch-packages] [Bug 1927827] [NEW] Error launching cheese: Native Windows taller than 65535 pixels are not supported
You have been subscribed to a public bug: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-04-28 (17 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 3.38.0-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 Tags: hirsute gstreamer-error Uname: Linux 5.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected gstreamer-error hirsute wayland-session -- Error launching cheese: Native Windows taller than 65535 pixels are not supported https://bugs.launchpad.net/bugs/1927827 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1928602] Re: Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout
GPU DRIVER: 4.6 Mesa 21.1.0 - kisak-mesa PPA we don't have that even in impish yet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1928602 Title: Cyberpunk 1.22 crashes with amdgpu ring gfx_0.0.0 timeout Status in mesa package in Ubuntu: New Bug description: Please see details in this link: https://gitlab.freedesktop.org/drm/amd/-/issues/934#note_916755 This happens when I try to play Cyberpunk 2077 1.22 in Proton. I use Proton-6.8-GE-1. The game launches, it plays fine but when I open the Inventory, it crashes. All other Proton versions crash the game immediately or very frequently with this graphics driver timeout. (Note this happened very rarely on Cyberpunk 1.21, other games seem to work fine and my system is otherwise stable) I was told to file a bug against mesa. OS: Ubuntu 20.04.2 LTS KERNEL: 5.12.3-xanmod1 CPU: AMD Ryzen 7 3700X 8-Core GPU: AMD AMD Radeon RX 5700 XT (NAVI10, DRM 3.40.0, 5.12.3-xanmod1, LLVM 12.0.0) GPU DRIVER: 4.6 Mesa 21.1.0 - kisak-mesa PPA RAM: 32 GB Kernel Arguments GRUB_CMDLINE_LINUX_DEFAULT="usbcore.autosuspend=-1 quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.noretry=0" Summary May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:36 hackintosh kernel: [ 257.280586] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.282283] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=21, emitted seq=23 May 13 12:17:36 hackintosh kernel: [ 262.282477] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Cyberpunk2077.e pid Full Log May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8b546e460 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8c13ca0a0 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: Fossilize WARN: Render pass handle 0x7fb8c13ca0a0 is not registered. May 13 12:17:26 hackintosh Cyberpunk 2077.desktop[8529]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize). May 13 12:17:36 hackintosh kernel: [ 257.280586] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.282283] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=21, emitted seq=23 May 13 12:17:36 hackintosh kernel: [ 262.282477] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Cyberpunk2077.e pid 8529 thread Cyberpunk2077.e pid 8529 May 13 12:17:36 hackintosh kernel: [ 262.282652] amdgpu :0c:00.0: amdgpu: GPU reset begin! May 13 12:17:36 hackintosh kernel: [ 262.400268] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! May 13 12:17:36 hackintosh kernel: [ 262.660931] amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) May 13 12:17:36 hackintosh kernel: [ 262.661006] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed May 13 12:17:36 hackintosh kernel: [ 262.904580] amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) May 13 12:17:36 hackintosh kernel: [ 262.904654] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed May 13 12:17:37 hackintosh kernel: [ 263.148241] [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx May 13 12:17:37 hackintosh kernel: [ 263.158091] [drm] free PSP TMR buffer May 13 12:17:37 hackintosh kernel: [ 263.197727] amdgpu :0c:00.0: amdgpu: BACO reset May 13 12:17:40 hackintosh kernel: [ 266.340490] amdgpu :0c:00.0: amdgpu: GPU reset succeeded, trying to resume May 13 12:17:40 hackintosh
[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Tim and Jussi, I tried to find the same machine as yours in our office, but there is no 9i, c930 or c940. Please do one more test, then I will ask for help from Realtek according to the test result. Boot with the standard kernel (not my testing kernel), play some music through the speaker, open a terminal, run alsamixer, 1st test: set the DAC1 volume to minimum, and set the DAC2 volume to maximum, could you still hear the music? Does the sound comes from front speaker or rear speaker? 2nd test: set the DAC1 voluem to maximum, and set the DAC2 volume to minimum, could you still hear the music? Does the sound comes from front speaker or rear speaker? thx. -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1928695] Re: unable to install libjsoncpp-1 on ubuntu 21.04
Thanks for the quick reply. will raise the bug in the relevant repository. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjsoncpp in Ubuntu. https://bugs.launchpad.net/bugs/1928695 Title: unable to install libjsoncpp-1 on ubuntu 21.04 Status in libjsoncpp package in Ubuntu: Invalid Bug description: Machine details: Hardware: Raspberrypi4B OS: ubuntu 21.04 Issue: when trying to install openthread as per the installation procedure in the path: https://openthread.io/codelabs/openthread-border-router#1 it fails to install libjsoncpp1. When tried to install via apt-get, it says package cannot be located. # apt-get install libjsoncpp1 Reading package list... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package libjsoncpp1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1928695/+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
