[Touch-packages] [Bug 2017999] Autopkgtest regression report (tzdata/2023c-0ubuntu0.20.04.2)
All autopkgtests for the newly accepted tzdata (2023c-0ubuntu0.20.04.2) for focal have finished running. The following regressions have been reported in tests triggered by the package: postgresql-12/12.14-0ubuntu0.20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Autopkgtest regression report (tzdata/2023c-2exp1ubuntu1.1)
All autopkgtests for the newly accepted tzdata (2023c-2exp1ubuntu1.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: chrony/4.3-1ubuntu4 (armhf) python-tz/2022.7.1-3 (amd64, arm64, armhf, ppc64el, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/lunar/update_excuses.html#tzdata [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Description changed: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output - mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): + mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" - Fri Apr 28 05:49:00 PST 2023 + Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" - Fri Apr 28 12:49:00 -01 2023 + Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" - Fri Apr 28 16:49:00 MSK 2023 + Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.0): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 06:49:00 PDT 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 15:49:00 CEST 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 EEST 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Please test proposed package
Hello Daniel, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Please test proposed package
Hello Daniel, or anyone else affected, Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Hello Daniel, or anyone else affected, Accepted tzdata into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023c-0ubuntu0.22.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed-kinetic ** Changed in: tzdata (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: Fix Committed Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: Fix Committed Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: Fix Committed Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2015071] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/2015071 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Invalid Bug description: broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 15:39:13 2023 InstallationDate: Installed on 2023-03-12 (21 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2015071/+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 2015075] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2015075 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: Invalid Bug description: pulse audio broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 16:04:49 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2015075/+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 2020229] Re: settings doesn't show all sound devices
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/2020229 Title: settings doesn't show all sound devices Status in alsa-driver package in Ubuntu: New Bug description: After upgrading to 23.04, the settings -> sound -> output device and input device menus no longer show a class-compliant usb audio interface. aplay -l shows the audio device is present (see attached screenshot). This was working correctly before upgrading. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 19 16:58:53 2023 InstallationDate: Installed on 2022-07-29 (294 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-04-22 (27 days ago) dmi.bios.date: 04/10/2022 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E155LAMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-155L dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE155LAMS.112:bd04/10/2022:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnModern15A5M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-155L:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku155L.1: dmi.product.family: Modern dmi.product.name: Modern 15 A5M dmi.product.sku: 155L.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020229/+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 1535840] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1535840 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535840/+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 2015071] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem
** Changed in: alsa-driver (Ubuntu) Status: Invalid => New -- 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/2015071 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: Invalid Bug description: broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 15:39:13 2023 InstallationDate: Installed on 2023-03-12 (21 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2015071/+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 2015075] Re: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
** Changed in: pulseaudio (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2015075 Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all Status in pulseaudio package in Ubuntu: Invalid Bug description: pulse audio broken pipe error 32 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 3 16:04:49 2023 InstallationDate: Installed on 2023-03-12 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Sisäinen äänentoisto - HDA Intel HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvar 1649 F pulseaudio /dev/snd/controlC0: alvar 1649 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7817, Intel Haswell HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:br4.6:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2015075/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
** Merge proposal linked:
https://code.launchpad.net/~alexsander-souza/maas/+git/maas/+merge/443301
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
In Progress
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
New
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
New
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Patch added: "tzdata_2023c-0ubuntu0.20.04.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/python-tz/+bug/2017999/+attachment/5674253/+files/tzdata_2023c-0ubuntu0.20.04.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1535840/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Patch added: "tzdata_2023c-0ubuntu0.22.04.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/python-tz/+bug/2017999/+attachment/5674252/+files/tzdata_2023c-0ubuntu0.22.04.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
Confirmed this still exists in 22.04 (Jammy Jellyfish), with symptoms being SystemD booting always into "degraded" state because wdmd.service (Watchdog Multiplexing Daemon) will always fail due to missing watchdog kernel module(s). Check this is the case with: sudo systemctl status sudo systemctl list-units --failed The solution suggested by @ishworgurung works to allow iTCO_wdt (and other watchdogs) to be loaded by the kernel during boot appropriately. Then, wdmd.service starts up successfully and SystemD enters successful "running" state (assuming all other SystemD services are working properly). However, every kernel package update will place another blacklist file in /lib/modprobe.d/blacklist_linux_$(uname -r).conf. So this is only a temporary workaround until these modules are not blacklisted by default. The blacklist files are part of linux-modules-$(uname -r) package(s). Therefore, this bug should be listed as also affecting Linux kernel source packages for Ubuntu. $ dpkg -S /lib/modprobe.d/blacklist_linux_*.conf linux-modules-5.15.0-74-generic: /lib/modprobe.d/blacklist_linux_5.15.0-74-generic.conf linux-modules-5.4.0-149-generic: /lib/modprobe.d/blacklist_linux_5.4.0-149-generic.conf # ^^ These packages own /lib/modprobe.d/blacklist_linux*.conf files $ apt-cache show linux-modules-$(uname -r) | grep -C5 Source: | sed -e 's/^//' Package: linux-modules-5.15.0-74-generic Architecture: amd64 Version: 5.15.0-74.81 Priority: optional Section: kernel Source: linux Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 123864 Depends: linux-image-5.15.0-74-generic | linux-image-unsigned-5.15.0-74-generic ## ^^ Part of Linux APT package(s) in Ubuntu -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Patch added: "tzdata_2023c-0ubuntu0.22.10.2_v2.debdiff" https://bugs.launchpad.net/ubuntu/focal/+source/python-tz/+bug/2017999/+attachment/5674251/+files/tzdata_2023c-0ubuntu0.22.10.2_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2016439] Autopkgtest regression report (curl/7.88.1-8ubuntu2)
All autopkgtests for the newly accepted curl (7.88.1-8ubuntu2) for lunar have
finished running.
The following regressions have been reported in tests triggered by the package:
curl/7.88.1-8ubuntu2 (ppc64el)
dgit/10.7 (amd64, ppc64el, s390x)
glance/2:26.0.0-0ubuntu1 (armhf)
gnocchi/4.5.0-0ubuntu1 (armhf)
ironic/1:21.4.0-0ubuntu1 (armhf)
libsoup3/3.4.0-1 (amd64, arm64)
lighttpd/1.4.67-1ubuntu2 (ppc64el)
mailman3/3.3.8-1ubuntu1 (arm64, ppc64el)
mediawiki/1:1.39.2-1 (armhf)
mediawiki-extension-codemirror/4.0.0~git20221204.b897975-1 (armhf)
mediawiki-extension-youtube/1.9.3~git20221020.e005c0b-1 (armhf)
mediawiki-skin-greystuff/1.2.5~git20220922.60bda8c-2 (armhf)
redmine/5.0.4-5 (armhf)
rsyslog/8.2302.0-1ubuntu3 (armhf)
rust-curl-sys/0.4.58-1 (arm64)
sahara/2:18.0.0-0ubuntu1 (armhf)
senlin/1:15.0.0-0ubuntu1 (armhf)
systemd/252.5-2ubuntu3 (amd64, arm64, s390x)
tang/11-2 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#curl
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2016439
Title:
Regression finding system certificates
Status in curl package in Ubuntu:
Fix Released
Status in curl source package in Lunar:
Fix Committed
Status in curl source package in Mantic:
Fix Released
Status in curl package in Debian:
Fix Released
Bug description:
[ Impact ]
Users of applications that link against libcurl's NSS flavour might
experience issues when trying to contact HTTPS servers. This can lead
to scenarios where the application is unable to connect.
[ Test Plan ]
First, let's verify that the GNUTLS flavour of libcurl does the right
thing:
$ lxc launch ubuntu-daily:lunar curl-bug2016439
$ lxc shell curl-bug2016439
# apt update && apt install -y libcurl4-gnutls-dev gcc
# cat > curl-test.c << __EOF__
#include
#include
int main(void)
{
CURL *curl;
CURLcode res;
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com;);
/* example.com is redirected, so we tell libcurl to follow redirection */
curl_easy_setopt(curl, CURLOPT_FOLLOWLOCATION, 1L);
/* Perform the request, res will get the return code */
res = curl_easy_perform(curl);
/* Check for errors */
if(res != CURLE_OK)
fprintf(stderr, "curl_easy_perform() failed: %s\n",
curl_easy_strerror(res));
/* always cleanup */
curl_easy_cleanup(curl);
}
return 0;
}
__EOF__
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
Example Domain
...
#
You should see the HTML dump of example.com. Now, let's install the
NSS flavour of libcurl and recompile the test program against it:
# apt install -y libcurl4-nss-dev
# gcc curl-test.c -o curl-test -lcurl
# ./curl-test
curl_easy_perform() failed: SSL peer certificate or SSH remote key was not OK
As we can see, there was an error when validating the TLS certificate.
[ Where problems could occur ]
The adjustment needed to the downstream patch is pretty simple and has
been tested extensively. The original reporter mentioned that the
issue did not happen before this patch was applied, so in the unlikely
event of a regression the best route would be to revert the patch
entirely.
[ More Info ]
This happens because of an error in one of our patches (authored by
me) to teach libcurl where to properly find libnsspem.so and
libnssckbi.so. The problem is that libnsspem.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/nss/, while libnssckbi.so is installed under
/usr/lib/$(DEB_HOST_ARCH)/, but I mistakenly pointed libcurl to look
under the "/nss/" directory for both libraries. As it turns out,
libnssckbi.so is necessary in order to use the Mozilla's root
certificate.
[ Original Description ]
[ Clone of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034359 ]
Between 7.88.1-2 and 7.88.1-5, there was a change to where curl with
nss looks for loadable libraries:
curl (7.88.1-4) unstable; urgency=medium
* d/p/Use-correct-path-when-loading-libnss-pem-ckbi-.so.patch:
Prepend "/nss/" before the library name.
Before the change to the load path, curl could find
/lib/x86_64-linux-gnu/libnssckbi.so but not
/lib/x86_64-linux-gnu/nss/libnsspem.so, after the change it's the
reverse.
libnssckbi.so is enough to get a trust root (the mozilla certificate
store is compiled inside that library), whereas libnsspem.so
(1.0.8+1-1) isn't.
This
[Touch-packages] [Bug 2017999] Proposed package upload rejected
An upload of tzdata to kinetic-proposed has been rejected from the upload queue for the following reason: "missing the fix for debconf preseed handling". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Proposed package upload rejected
An upload of tzdata to jammy-proposed has been rejected from the upload queue for the following reason: "missing the fix for debconf preseed handling". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Hello Daniel, or anyone else affected, Accepted tzdata into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023c-2exp1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: tzdata (Ubuntu Lunar) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Fix Committed Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 1260172] Re: translation in Italian
** Changed in: gnupg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1260172 Title: translation in Italian Status in gnupg package in Ubuntu: Incomplete Bug description: Translation in Italian is complete but I don't know how I can send it upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1260172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket - Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) - Active: inactive (dead) -Triggers: ● pcscd.service - Listen: /run/pcscd/pcscd.comm (Stream) + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) + Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. + + As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: + - jammy + - kinetic + - lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the
[Touch-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Also affects: pcsc-lite (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034209 Importance: Unknown Status: Unknown ** Also affects: pcsc-lite (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: pcsc-lite (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: pcsc-lite (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: pcsc-lite (Ubuntu Jammy) Status: New => Triaged ** Changed in: pcsc-lite (Ubuntu Kinetic) Status: New => Triaged ** Changed in: pcsc-lite (Ubuntu Lunar) Status: New => Triaged ** Changed in: pcsc-lite (Ubuntu Jammy) Importance: Undecided => High ** Changed in: pcsc-lite (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: pcsc-lite (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: - Ubuntu Mate 22.04 with the latest updates. - Problem is present with internal smart-card reader and also external usb smart-card reader. + [ Impact ] - eid-viewer sees no card reader,but When i do: + The pscc-lite package provides an open source implementation of PC/SC, + the de-facto standard to interface Personal Computers with Smart + Cards/Readers. - sudo pcscd -f + This bug is in the upstream debian packaging, and results in the + pcscd.socket being disabled after installation. This prevents automatic + startup of the associated pcscd.service, thus preventing automatic + handling of Smart Cards/Readers w/out manual intervention to enable the + socket (which doesn't persist across reboots). - it is working, also following the tips of Ludovic: - https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html + This is especially painful for users that require Smart Authentication + for login. - sudo systemctl stop pcscd.socket - sudo systemctl start pcscd.socket + [ Test Plan ] - It is working until next restart. + Steps to reproduce: - libacsccid1 version: 1.1.8-1 - libccid version: 1.5.0-2 - pcscd version: 1.9.5-3 - eid-archive version: 2022.3 - eid-mw version: 5.0.28v5.0.28-0u2204-1 - eid-viewer version: 5.0.28v5.0.28-0u2204-1 + 1. If installed, remove and do a fresh install of the package pcscd + (the sole version released for jammy is 1.9.5-3). - In Firefox, my eid card is then also recognized, but only in the ESR - version, but this is a know Mozilla bug. + 2. Verify that the pcscd.socket is disabled: + + $ systemctl status pcscd.socket + ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) +Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) + + 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or + Nitrokey) that's known to work on Ubuntu and verify that it fails to + work. + + Repeating the same steps with a package built with the patch attached to + comment #27 should ensure that the socket is enabled, and that + interaction with a Smart Card or Crypto Token should work w/out manual + intervention. + + [ Where problems could occur ] + + This is a back-ported change from upstream and is a result of a bug in + dh_installsystemd (see comment #26). As such the risk is minimal. + + The only potential risk of failure I can come up with is a snap that + stages the old version of the client library, as it would be looking in + the wrong place for the socket. + + [ Other Info ] + + This bug was originally reported against Ubuntu Mate 22.04, however it + applies to all derivatives of Ubuntu Desktop 22.04 LTS. + + Note - while there's some disagreement as to whether this bug occurs + 100% of the time across all 22.04 installations, it's pretty clear from + the upstream Debian bug and subsequent packaging fix that we should land + this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal.
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
fixed header for patch ** Patch added: "lp-2019856v3-jammy-add-arm-core-support.debdiff" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5674198/+files/lp-2019856v3-jammy-add-arm-core-support.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: In Progress Status in util-linux source package in Lunar: In Progress Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Summary changed: - pcscd 1.9.5-3 do not start automatically, only manual + pcscd.socket is disabled after installation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
** Changed in: maas
Status: Triaged => In Progress
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
In Progress
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
New
Status in linux package in Ubuntu:
Fix Committed
Status in systemd package in Ubuntu:
Invalid
Status in apparmor source package in Lunar:
New
Status in linux source package in Lunar:
Fix Committed
Status in systemd source package in Lunar:
New
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2020183] Re: Xorg crash
All the time the displays got relocked again, right after I unlocked it with my password. Some parts of the desktop can be seen for a moment in the meanwhile. Right after that, it shows the "This screen is locked" message with a padlock and turns into black and shows me the errors. So for the first time, I can't unlock the display successfully, but for the 2nd time it works. Apart from that it also happens, that I won't get back the login screen after the session has been locked. Super strange. -- 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/2020183 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: I'm using a Docking station with two displays (1 HDMI + 1 DP) and one HDMI to the machine's port. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Thu May 18 15:11:56 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8846] InstallationDate: Installed on 2022-08-05 (286 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-72-generic root=/dev/mapper/elx_vg-root ro mem_sleep_default=deep noaudit noquiet nosplash sysrq_always_enabled i915.enable_guc=1 intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-08-05T12:33:01.637811 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020183/+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 2020183] [NEW] Xorg crash
Public bug reported: I'm using a Docking station with two displays (1 HDMI + 1 DP) and one HDMI to the machine's port. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Thu May 18 15:11:56 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8846] InstallationDate: Installed on 2022-08-05 (286 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-72-generic root=/dev/mapper/elx_vg-root ro mem_sleep_default=deep noaudit noquiet nosplash sysrq_always_enabled i915.enable_guc=1 intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-08-05T12:33:01.637811 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal ubuntu -- 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/2020183 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: I'm using a Docking station with two displays (1 HDMI + 1 DP) and one HDMI to the machine's port. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98 Uname: Linux 5.15.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Thu May 18 15:11:56 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8846] InstallationDate: Installed on 2022-08-05 (286 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-72-generic root=/dev/mapper/elx_vg-root ro mem_sleep_default=deep noaudit noquiet nosplash sysrq_always_enabled i915.enable_guc=1 intel_idle.max_cstate=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2021 dmi.bios.release: 6.2 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.06.02 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.51 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.06.02:bd08/12/2021:br6.2:efr48.51:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.33.00:cvnHP:ct10:cvr:sku4T9G0EC#ABB: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4T9G0EC#ABB dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with
[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
** Patch added: "tzdata_2023c-2exp1ubuntu1.1_v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5674128/+files/tzdata_2023c-2exp1ubuntu1.1_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Incomplete Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency
Thanks for the review. I tested what happens if a debconf answer is provided that will be removed by the update: ``` $ printf "tzdata tzdata/Areas select Europe\ntzdata tzdata/Zones/Europe select Uzhgorod\n" | debconf-set-selections $ DEBIAN_FRONTEND=noninteractive apt install ./tzdata_2023c-0ubuntu0.20.04.2_all.deb [...] Current default time zone: 'Europe/Amsterdam' ``` So it will select the first entry of that area instead. So we need to keep all debconf options. I'll prepare a new set of debdiffs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: Invalid Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: Invalid Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: Invalid Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: Incomplete Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2020177] [NEW] Leaking sessions in pam_systemd
Public bug reported: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago Leader: 2637625 Remote: 92.42.15.122 Service: sshd; type tty; class user State: closing Unit: session-302548700.scope # ps axf|wc -l 72 The only way I could figure to fix this is to reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 Uname: Linux 4.15.0 x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDmesg: Date: Fri May 19 12:58:47 2023 Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 TERM=xterm-256color PATH=(custom, no user) ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts' ProcKernelCmdLine: quiet SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago) acpidump: mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/2020177 Title: Leaking sessions in pam_systemd Status in systemd package in Ubuntu: New Bug description: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago Leader: 2637625 Remote: 92.42.15.122 Service: sshd; type tty; class user State: closing Unit: session-302548700.scope # ps axf|wc -l 72 The only way I could figure to fix this is to reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 Uname: Linux 4.15.0 x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDmesg: Date: Fri May 19 12:58:47 2023 Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 TERM=xterm-256color PATH=(custom, no user) ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts' ProcKernelCmdLine: quiet SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago) acpidump: mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+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 1951018] Re: No ability to discern IPv4 vs IPv6 rules through Python
This bug was fixed in the package ufw - 0.36.2-1 --- ufw (0.36.2-1) unstable; urgency=medium * New upstream release (LP: #1946804, LP: #1927737, LP: #1927734, LP: #2015645, LP: #1996636, LP: #1965462, LP: #1951018, Closes: 1034568, Closes: 1034119). Drop the following (included upstream): - 0002-fix-copyright.patch - 0003-python3-versions.patch - 0004-set-default-policy-after-load.patch * Remaining changes: - 0001-optimize-boot.patch * add new debian/po/ro.po. Thanks Remus-Gabriel Chelu (Closes: 1033758) * debian/control: - Breaks with iptables-persistent and netfilter-persistent. When ufw is installed, it is not enabled by default, so it doesn't interfere with other firewall software (until it is enabled). In contrast, iptables-persistent and netfilter-persistent install enabled, which interferes with ufw. Add a breaks on these to avoid them being co-installed with ufw (and causing problems for users). - use Python-Version instead of XB-Python-Version - remove Depends on obsolete lsb-base * ufw.lintian-overrides: - update for breaks-without-version iptables-persistent and netfilter-persistent - update for newer lintian -- Jamie Strandboge Thu, 18 May 2023 14:03:07 + ** Changed in: ufw (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1951018 Title: No ability to discern IPv4 vs IPv6 rules through Python Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Bug description: Version: ufw 0.36 Ubuntu Version: 20.04.3 LTS There doesn't appear to be a Python method for accessing IPv4 and IPv6 rules in a distinguishable manner. In the source code (root/src/backend.py) there is an object that stores IPv4 and IPv6 rules in separate lists. Those lists are then accessed with the following method: def get_rules(self): '''Return list of all rules''' return self.rules + self.rules6 The issue with this is that the returned list doesn't contain an indication of what IP version each item corresponds to and would display something like the following. 1 allow 22/tcp 2 allow 80 3 allow 443 4 allow 22/tcp 5 allow 80 6 allow 443 I don't currently see a way to distinguish between IPv4 and IPv6 rules other than accessing the lists in the backend object directly (but I don't think this is best practice). E.g.: rules_ipv4 = backend.rules rules_ipv6 = backend.rules6 One possible fix would be to add functions that return only the IPv4 or IPv6 rules. E.g.: def get_rules_ipv4(self): '''Return list of all ipv4 rules''' return self.rules def get_rules_ipv6(self): '''Return list of all ipv6 rules''' return self.rules6 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1951018/+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 2015645] Re: ufw crashes in wsl2
This bug was fixed in the package ufw - 0.36.2-1
---
ufw (0.36.2-1) unstable; urgency=medium
* New upstream release (LP: #1946804, LP: #1927737, LP: #1927734,
LP: #2015645, LP: #1996636, LP: #1965462, LP: #1951018, Closes: 1034568,
Closes: 1034119). Drop the following (included upstream):
- 0002-fix-copyright.patch
- 0003-python3-versions.patch
- 0004-set-default-policy-after-load.patch
* Remaining changes:
- 0001-optimize-boot.patch
* add new debian/po/ro.po. Thanks Remus-Gabriel Chelu (Closes: 1033758)
* debian/control:
- Breaks with iptables-persistent and netfilter-persistent. When ufw is
installed, it is not enabled by default, so it doesn't interfere with
other firewall software (until it is enabled). In contrast,
iptables-persistent and netfilter-persistent install enabled, which
interferes with ufw. Add a breaks on these to avoid them being
co-installed with ufw (and causing problems for users).
- use Python-Version instead of XB-Python-Version
- remove Depends on obsolete lsb-base
* ufw.lintian-overrides:
- update for breaks-without-version iptables-persistent and
netfilter-persistent
- update for newer lintian
-- Jamie Strandboge Thu, 18 May 2023 14:03:07
+
** Changed in: ufw (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/2015645
Title:
ufw crashes in wsl2
Status in ufw:
Fix Released
Status in ufw package in Ubuntu:
Fix Released
Status in ufw source package in Focal:
Triaged
Status in ufw source package in Jammy:
Triaged
Status in ufw source package in Mantic:
Fix Released
Bug description:
When I enable systemd in WSL2 (it became supported recently), install
ufw, and run sudo ufw enable, I get the error detailed in
https://superuser.com/questions/1775776/enabling-ufw-failed-with-
ubuntu-from-wsl2. You may already be aware of this error, I'm not sure
if "NotTheDr01ds" has talked to you about this yet. Note that the WSL2
/proc/[pid]/stat format, although weird, does comply with the spec:
https://man7.org/linux/man-pages/man5/proc.5.html
I verified that you can fix this issue by replacing the first split in
line 427 with rsplit(')', 1) so it splits based on the last
parenthesis instead of the all parenthesis.
Before:
ppid = open(name).readlines()[0].split(')')[1].split()[1]
After:
ppid = open(name).readlines()[0].rsplit(')',1)[1].split()[1]
C:\Users\caleb>wsl --version
WSL version: 1.1.6.0
Kernel version: 5.15.90.1
WSLg version: 1.0.50
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2728
➜ ufw git:(master) ufw --version
ufw 0.36
Copyright 2008-2015 Canonical Ltd.
➜ ufw git:(master) cat /proc/229/stat | cut -c -23
229 (Relay(230)) S 228
To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/2015645/+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 2020127] Re: x apps fail to launch from terminal shell
Brilliant! grep XAUTHORITY ~/.* found /home/dave/.bashrc: export XAUTHORITY=~/.Xauthority and commenting the line out in .bashrc fixed the problem I don't know how the export got into my .bashrc Possibly to do with me recently upgrading to 23.04 from 22.04 via 22.10, without checking 22.10 in any detail. Or, it took two attempts to download 23.04 due to slow network and repositories timing out and something glitched. More likely it could have been me fiddling with X in the past. Whatever the cause, many thanks for your help Cheers, Dave On 19/05/2023 02:59, Daniel van Vugt wrote: > Thanks for the bug report. > > I can't seem to reproduce the issue here. Perhaps you just need to > delete ~/.Xauthority or perhaps there's something in your local config > setting it? Try: > >grep XAUTHORITY ~/.* > -- 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/2020127 Title: x apps fail to launch from terminal shell Status in xorg package in Ubuntu: New Bug description: New upgrade to 23.04 In terminal typing xeyes, idle or other X app including ubuntu-bug fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot open display: :0 Desktop and remote access from another machine to a shell on this host with ssh -X work correctly echo $XAUTHORITY is /home/dave/.Xauthority File exists and contains 2 cookies Clue: export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug links to a working per session cookie, and I'm able to type this. Expected behaviour: display just works when an X application is started from a shell. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 18 18:44:46 2023 DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 GHz Edition] [1787:2321] InstallationDate: Installed on 2021-03-06 (802 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago) dmi.bios.date: 08/28/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z490 AORUS ELITE AC dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Z490 MB dmi.product.name: Z490 AORUS ELITE AC dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2020127/+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 2020163] [NEW] only = and != equations work for auid field
Public bug reported: lsb_release -rc Release:22.04 Codename: jammy dpkg -l|grep audi ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing work for = and != $ sudo auditctl -a always,exit -F auid=1000 $ sudo auditctl -a always,exit -F auid!=1000 $ sudo auditctl -D No rules Do not work for < > <= >= $ sudo auditctl -a always,exit -F auid<1000 -bash: 1000: No such file or directory $ sudo auditctl -a always,exit -F auid>1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid<=1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid>=1000 -F missing operation for auid sudo auditctl -a always,exit -F auidubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid<=ubuntu bash: =ubuntu: No such file or directory sudo auditctl -a always,exit -F auid>=ubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid>'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<='ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid>='ubuntu' -F missing operation for auid ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/2020163 Title: only = and != equations work for auid field Status in audit package in Ubuntu: New Bug description: lsb_release -rc Release: 22.04 Codename: jammy dpkg -l|grep audi ii auditd 1:3.0.7-1build1 amd64User space tools for security auditing ii libaudit-common 1:3.0.7-1build1 all Dynamic library for security auditing - common files ii libaudit1:amd64 1:3.0.7-1build1 amd64Dynamic library for security auditing ii libauparse0:amd64 1:3.0.7-1build1 amd64Dynamic library for parsing security auditing work for = and != $ sudo auditctl -a always,exit -F auid=1000 $ sudo auditctl -a always,exit -F auid!=1000 $ sudo auditctl -D No rules Do not work for < > <= >= $ sudo auditctl -a always,exit -F auid<1000 -bash: 1000: No such file or directory $ sudo auditctl -a always,exit -F auid>1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid<=1000 -F missing operation for auid $ sudo auditctl -a always,exit -F auid>=1000 -F missing operation for auid sudo auditctl -a always,exit -F auidubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid<=ubuntu bash: =ubuntu: No such file or directory sudo auditctl -a always,exit -F auid>=ubuntu -F missing operation for auid sudo auditctl -a always,exit -F auid>'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<'ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid<='ubuntu' -F missing operation for auid sudo auditctl -a always,exit -F auid>='ubuntu' -F missing operation for auid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2020163/+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 2020161] Re: Printing Job is processed but failed to be printed using driverless
I can recreate this all time on 4 Ubuntu 23.04 machines. I dont have a 22.10 or 22.04 to test here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2020161 Title: Printing Job is processed but failed to be printed using driverless Status in cups package in Ubuntu: New Bug description: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2020161/+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 2020161] [NEW] Printing Job is processed but failed to be printed using driverless
Public bug reported: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2020161 Title: Printing Job is processed but failed to be printed using driverless Status in cups package in Ubuntu: New Bug description: Since about a week, all my Ubuntu 23.04 failed to print driverless. I have installed an IPP connection that works, but the default driverless stops with Idle - "job processing failed". I use a HP MFP280nmw. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups 2.4.2-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri May 19 08:16:21 2023 InstallationDate: Installed on 2023-04-04 (44 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lpstat: device for HP_Color_LaserJet_MFP_M280nw_83DB46: implicitclass://HP_Color_LaserJet_MFP_M280nw_83DB46/ MachineType: TUXEDO TUXEDO InfinityBook Pro Gen7 (MK1) Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M280nw_83DB46.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=d0cb7813-e17a-4964-afed-4ff96fbb89a4 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to lunar on 2023-04-04 (44 days ago) dmi.bios.date: 01/16/2023 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: N.1.05A08 dmi.board.asset.tag: Standard dmi.board.name: PHxARX1_PHxAQF1 dmi.board.vendor: NB02 dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: Standard dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrN.1.05A08:bd01/16/2023:br5.25:efr1.37:svnTUXEDO:pnTUXEDOInfinityBookProGen7(MK1):pvrStandard:rvnNB02:rnPHxARX1_PHxAQF1:rvrStandard:cvnTUXEDO:ct10:cvrStandard:skuIBP1XI07MK1: dmi.product.name: TUXEDO InfinityBook Pro Gen7 (MK1) dmi.product.sku: IBP1XI07MK1 dmi.product.version: Standard dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2020161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
