[Touch-packages] [Bug 2047314] Autopkgtest regression report (tzdata/2023d-0ubuntu0.23.04)
All autopkgtests for the newly accepted tzdata (2023d-0ubuntu0.23.04) for lunar have finished running. The following regressions have been reported in tests triggered by the package: chrony/4.3-1ubuntu4 (armhf) mtail/3.0.0~rc50-1 (arm64) 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
I installed tzdata_2023d-0ubuntu0.23.10_all.deb on a 22.04.3 LTS system
with these messages logged.
ntpd[2389941]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'):
good hash signature
ntpd[2389941]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'):
loaded, expire=2024-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Looks good to me! Thanks!
--
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/2047314
Title:
tzdata 2023d release (leap-second.list expiring this week)
Status in tzdata package in Ubuntu:
Fix Released
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Lunar:
Fix Committed
Status in tzdata source package in Mantic:
Fix Committed
Bug description:
[ Impact ]
leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.
The 2023d release contains the following changes:
Briefly:
Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
Vostok, Antarctica changed time zones on 2023-12-18.
Casey, Antarctica changed time zones five times since 2020.
Code and data fixes for Palestine timestamps starting in 2072.
A new data file zonenow.tab for timestamps starting now.
Changes to future timestamps
Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
the rest of Greenland's timekeeping practice on 2024-03-31, by
changing its time zone from -01/+00 to -02/-01 at the same moment
as the spring-forward transition. Its clocks will therefore not
spring forward as previously scheduled. The time zone change
reverts to its common practice before 1981.
Fix predictions for DST transitions in Palestine in 2072-2075,
correcting a typo introduced in 2023a.
Changes to past and future timestamps
Vostok, Antarctica changed to +05 on 2023-12-18. It had been at
+07 (not +06) for years. (Thanks to Zakhary V. Akulov.)
Change data for Casey, Antarctica to agree with timeanddate.com,
by adding five time zone changes since 2020. Casey is now at +08
instead of +11.
Changes to past tm_isdst flags
Much of Greenland, represented by America/Nuuk, changed its
standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
This does not affect UTC offsets, only the tm_isdst flag.
(Thanks to Thomas M. Steenholdt.)
New data file
A new data file zonenow.tab helps configure applications that use
timestamps dated from now on. This simplifies configuration,
since users choose from a smaller Zone set. The file's format is
experimental and subject to change.
[ Test Plan ]
Test cases were added to autopkgtest to cover the testing:
* python: test_2023d
So the test plan is to check that all autopkgtest succeeds.
[ Other Info ]
The autopkgtest for chrony is flaky on jammy and newer (see bug
#2002910).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2045621] Re: Improve power consumption on Framework systems
Appreciate this everyone. I have multiple people beginning to test this today. I will be joining them next week. I have asked each to report back here. -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2047008] Re: [SRU] Add Telit FN990 compositions
Hello Laider, or anyone else affected, Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.3 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: modemmanager (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
``` aplay -l ... card 2: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` According to laptop's specs: https://psref.lenovo.com/Product/Legion_Slim_7_16APH8?tab=spec Audio Chip High Definition (HD) Audio, Realtek® ALC3306 codec It seems like Linux reports ALC287 instead of ALC3306. According to a reddit post, ALC3306 is just a name change of ALC287. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Same no audio problem on this laptop: Legion Slim 7 16APH8 https://psref.lenovo.com/Detail/Legion/Legion_Slim_7_16APH8?M=82Y4001UMZ OS: Fedora 39 Kernel: 6.6.9-200.fc39.x86_64 alsa-info.sh http://alsa-project.org/db/?f=dc0275d1836faea7ddf81a990b07e4a86313bf9a Bios: Version: M1CN36WW Release Date: 09/21/2023 cat /sys/class/sound/hwC1D0/subsystem_id 0xaa0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045621] Please test proposed package
Hello Artur, or anyone else affected, Accepted systemd-hwe into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd- hwe/249.11.5 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. -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Re: Improve power consumption on Framework systems
Hello Artur, or anyone else affected, Accepted systemd-hwe into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd- hwe/253.5.3 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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: systemd-hwe (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: systemd-hwe (Ubuntu Jammy) Status: In Progress => 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
This fixes a build failure but has no user-facing impact, it does not need to be released to -updates. Setting block-proposed tag. ** Tags added: block-proposed-mantic ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: Fix Released Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build the heimdal package successfully. It's also important to be able to apply security fixes in the future (if needed). [ Test plan ] Build the package in a ppa to check that the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal # lxc shell Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of aftools against the new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check that the command is not broken (you don't get a aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:heimdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that is the case, when executing, the affected binary will no run and a message like this could appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2036253] Please test proposed package
Hello Andreas, or anyone else affected, Accepted heimdal into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/heimdal/7.8.git20221117.28daf24+dfsg-3ubuntu1.23.10.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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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 heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: Fix Released Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build the heimdal package successfully. It's also important to be able to apply security fixes in the future (if needed). [ Test plan ] Build the package in a ppa to check that the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal # lxc shell Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of aftools against the new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check that the command is not broken (you don't get a aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:heimdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that is the case, when executing, the affected binary will no run and a message like this could appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING
[Touch-packages] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting
> * Begin midi playback in any midi player using fluidsynth from the terminal This is not a reproducible test case that can be actioned by someone just reading the bug. Please provide a specific test case showing how to reproduce the failure. If possible, it would be best to also provide a reference midi file to use. ** Changed in: fluidsynth (Ubuntu Mantic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/2047656 Title: [SRU] Players terminate after stopping and restarting Status in fluidsynth package in Ubuntu: Fix Released Status in fluidsynth source package in Mantic: Incomplete Status in fluidsynth source package in Noble: Fix Released Bug description: [ Impact ] Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of playback of a midi song, causing issues for a multitude of players including EasyABC. This will cause said player to be unable to playback again and perhaps even crash. See https://github.com/FluidSynth/fluidsynth/issues/1272, fix in https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055. This is the included patch with the upload of 2.3.3-2.1ubuntu-0.23.10.1 [ Test Case ] * Begin midi playback in any midi player using fluidsynth from the terminal * Stop midi playback * Attempt start again * Error in terminal: fluidsynth: error: The maximum playback duration has been reached. Terminating player! [ What could go wrong ] This is actually a fix for a regression that was found in version 2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble. I think the only thing that can go wrong here is that this patch is not the actual fix and we need to find more solutions within. I have tested this in my PPA and it *seems* to fix it, but it would be nice if the original reporter could verify once this lands in proposed. [ Other information ] Included below is the original report, in which case the reporter deduces that the problem is the binary being spat-out is the 2.3.2 version from the 2.3.3 sources. This is not the case, as it appears to be confusion due to the -2.1 Debian revision number. I assure, this is definitely the 2.3.3, and the bug, per the github link in the Impact section, is pertinent to this version. --- The latest package of fluidsynth should include the sources from version 2.3.3 but the binary includes only version 2.3.2 This version has a bug (see https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to problems in EasyABC. Please include the latest version 2.3.3 from upstream in the ubuntu package. -- Description: Ubuntu 23.10 Release: 23.10 Codename: mantic $ apt-cache policy libfluidsynth3 libfluidsynth3: Installiert: 2.3.3-2.1 Installationskandidat: 2.3.3-2.1 Versionstabelle: *** 2.3.3-2.1 500 500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.20.04 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.22.04 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Please test proposed package
Hello Bill, or anyone else affected, Accepted tzdata into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.23.04 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 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)
Hello Bill, or anyone else affected, Accepted tzdata into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tzdata/2023d-0ubuntu0.23.10 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- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. 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 Mantic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: tzdata (Ubuntu Lunar) Status: New => Fix Committed ** Tags added: verification-needed-lunar -- 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/2047314 Title: tzdata 2023d release (leap-second.list expiring this week) Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Lunar: Fix Committed Status in tzdata source package in Mantic: Fix Committed Bug description: [ Impact ] leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023. The 2023d release contains the following changes: Briefly: Ittoqqortoormiit, Greenland changes time zones on 2024-03-31. Vostok, Antarctica changed time zones on 2023-12-18. Casey, Antarctica changed time zones five times since 2020. Code and data fixes for Palestine timestamps starting in 2072. A new data file zonenow.tab for timestamps starting now. Changes to future timestamps Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of the rest of Greenland's timekeeping practice on 2024-03-31, by changing its time zone from -01/+00 to -02/-01 at the same moment as the spring-forward transition. Its clocks will therefore not spring forward as previously scheduled. The time zone change reverts to its common practice before 1981. Fix predictions for DST transitions in Palestine in 2072-2075, correcting a typo introduced in 2023a. Changes to past and future timestamps Vostok, Antarctica changed to +05 on 2023-12-18. It had been at +07 (not +06) for years. (Thanks to Zakhary V. Akulov.) Change data for Casey, Antarctica to agree with timeanddate.com, by adding five time zone changes since 2020. Casey is now at +08 instead of +11. Changes to past tm_isdst flags Much of Greenland, represented by America/Nuuk, changed its standard time from -03 to -02 on 2023-03-25, not on 2023-10-28. This does not affect UTC offsets, only the tm_isdst flag. (Thanks to Thomas M. Steenholdt.) New data file A new data file zonenow.tab helps configure applications that use timestamps dated from now on. This simplifies configuration, since users choose from a smaller Zone set. The file's format is experimental and subject to change. [ Test Plan ] Test cases were added to autopkgtest to cover the testing: * python: test_2023d So the test plan is to check that all autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
With community support on Libera IRC's #ubuntu Andi and I were able to determine the root cause of this issue was apparently a read-only /usr file system (caused by a user-initiated system configuration change). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: Invalid Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
** Changed in: sqlite3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: Invalid Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
Please close this bug. The filesystem was indeed read-only and it was due to "user error". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: Invalid Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
I rebooted and ran Software Updater again. I now get this message every time with no further details shown. ** Attachment added: "Screenshot from 2024-01-05 17-36-23.png" https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+attachment/5736905/+files/Screenshot%20from%202024-01-05%2017-36-23.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: New Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
Sorry, This is not a bug with sqlite. It is a bug with the software updater. I tried to search for the "software updater" package but the package- search feature in the bug reporter gave me this error: ** Attachment added: "search.png" https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+attachment/5736904/+files/search.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: New Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2048405] [NEW] multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gn
Public bug reported: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sqlite3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: New Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:1
[Touch-packages] [Bug 2048081] Re: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openss
In the terminal I see dpkg-deb (sub-processo): ZSTD_decompressStream error : Corrupted block detected which makes me think the package was corrupted in transport. Try sudo apt-get clean sudo apt-get update ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2048081 Title: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh- pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado Status in openssh package in Ubuntu: Incomplete Bug description: Do not upgrade dpkg-deb: erro: o subprocesso retornou erro do status de saída 2 dpkg: erro ao processar o arquivo /var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb (--unpack): não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou s tream inesperado Erros foram encontrados durante o processamento de: /var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: libsqlite3-0:i386: Install libsqlite3-0:amd64: Install openssh-client:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 4 09:23:18 2024 ErrorMessage: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2023-12-30 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.5, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh Title: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2048081/+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 2024009] Re: [PATCH] systemd-resolved can't follow more than 8 CNAMEs
Hello Vincent, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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. ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/2024009 Title: [PATCH] systemd-resolved can't follow more than 8 CNAMEs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [Impact] Using systemd-resolved to resolve a hostname which has more than 8 CNAME redirects will fail because of the hard-coded limit. While this case is somewhat rare, the original reporter demonstrated a real-world scenario where this happened (although that particular hostname seems to be fixed now). [Test Plan] This test plan uses a LXC container to test systemd-resolved on Focal. If LXD has not been configured on your system, start with: $ lxd init --auto Then, create a Focal container with: $ lxc launch ubuntu-daily:focal focal Install dnsmasq-base if needed: $ apt install dnsmasq-base Stop other DNS servers: $ systemctl stop systemd-resolved $ kill -9 $(pgrep dnsmasq) Now, on the host start a new DNS server that listens on lxdbr0, and sets up an A record, and many CNAME records which ultimately redirect to the A record: $ dnsmasq \ --cname=test10.lan,test9.lan \ --cname=test9.lan,test8.lan \ --cname=test8.lan,test7.lan \ --cname=test7.lan,test6.lan \ --cname=test6.lan,test5.lan \ --cname=test5.lan,test4.lan \ --cname=test4.lan,test3.lan \ --cname=test3.lan,test2.lan \ --cname=test2.lan,test1.lan \ --cname=test1.lan,test0.lan \ -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP where $IP is any host on your network. Now, obtain a shell in the Focal container: $ lxc exec focal bash Attempt to resolve test10.lan: $ resolvectl query test10.lan test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'test2.lan' On an affected system, the above error will be seen. On a patched system, the hostname should be resolved. [Where problems could occur] The patch simply increases the maximum CNAME redirects that are allowed from 8 to 16, so a reasonable limit is still imposed. If an application specifically relied on systemd-resolved's limit being at 8, then that application would potentially see new behavior. [Original Description] On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only follows 8 CNAME redirections maximum. So when using a service like Azure Virtual Desktop that has between 9 and 12 redirections, name resolution fails. $ host client.wvd.microsoft.com Host client.wvd.microsoft.com not found: 2(SERVFAIL) $ resolvectl query client.wvd.microsoft.com client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net' On the other hand it's working fine on Ubuntu 20.04 because CNAME loop limit has been raised from 8 to 16. $ host client.wvd.microsoft.com client.wvd.microsoft.com is an alias for client.privatelink-global.wvd.microsoft.com. client.privatelink-global.wvd.microsoft.com is an alias for client.privatelink.wvd.microsoft.com. client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com. rdweb.wvd.microsoft.com is an alias for rdweb.privatelink-global.wvd.microsoft.com. rdweb.privatelink-global.wvd.microsoft.com is an alias for rdweb.privatelink.wvd.microsoft.com. rdweb.privatelink.wvd.microsoft.com is an alias for rdweb-prod-geo.trafficmanager.net.
[Touch-packages] [Bug 1969365] Re: focal: backport kexec fallback patch
Hello Dan, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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. ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1969365 Title: focal: backport kexec fallback patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: It would be great if focal's systemd could have https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3 backported to it. [Impact] We have observed that kexec'ing to another kernel will fail as the drive containing the `kexec` binary has been unmounted by the time systemd attempts to do so, indicated in the console: Starting Reboot via kexec... [ 163.960938] shutdown[1]: (sd-kexec) failed with exit status 1. [ 163.963463] reboot: Restarting system [Test Plan] 1) Launch a 20.04 instance 2) `apt-get install kexec-tools` 3) In `/boot`, filling in whatever needed in your environment: kexec -l vmlinuz --initrd initrd.img --append '' 4) `reboot` (I have reproduced this in a single-disk VM, so I assume it reproduces ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot` could be used to emulate the unmounting.) [Where problems could occur] Users could inadvertently be relying on the current behaviour: if they have configured their systems to kexec, they currently will be rebooting normally, and this patch would cause them to start actually kexec'ing. [Other info] We're currently maintaining a systemd tree with only this patch added to focal's tree: this patch has received a bunch of testing from us in focal. This patch landed in v246, so it's already present in supported releases later than focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173
Hello Roxana, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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. ** Changed in: systemd (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/2029352 Title: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173 Status in systemd package in Ubuntu: Invalid Status in systemd source package in Focal: Fix Committed Bug description: [Impact] The armhf autopkgtest fails for focal and ultimately leads to less test coverage because other packages now won't block on these failures, and may not notice new regressions. [Test Plan] The test-execute test within root-unittests should pass. [Where problems could occur] The patch only changes a service file in the test tree of systemd, so this is not a change that will be seen on real Ubuntu systems. Hence any further problems would be seen only in the test-execute test. [Original Description] This is a scripted bug report about ADT failures while running systemd tests for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. root-unittests fails. Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
Hello Guillaume, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packag
[Touch-packages] [Bug 2037281] Re: Shutdown when triggering daemon-reload early in boot
Hello Valentin, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 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. ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037281 Title: Shutdown when triggering daemon-reload early in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Jammy: Fix Committed Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
While the test plan now has information about changing the locale there is nothing which covers the keyboard changes. I'm going to accept this today but please update the test case to include testing the keyboard changes and ensure that is also tested. ** Changed in: systemd (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Bug description: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core or Ubuntu Core Desktop admin terminal must change the locale to the specified one, which can be checked by reading the */etc/default/locale* file. Also, *localectl* must return the new locale. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so only those applications that modify by themselves the */etc/default/keyboard* and/or */etc/default/locale* would present a problem, in which case they would require specific patches. Anyway, those applications neither would work with the current state (with those files in a read-only filesystem). [Other info] For Noble, this will be addressed when we merge systemd v255 from Debian. This is only needed on core, so we don't need to fix for Mantic or Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2037281] Re: Shutdown when triggering daemon-reload early in boot
Hello Valentin, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.12 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: systemd (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2037281 Title: Shutdown when triggering daemon-reload early in boot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Jammy: Fix Committed Bug description: In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue where if a service, started earlier than devices are processed by udev, does `systemctl daemon-reload`, the system shuts down. This is due to devices for mounted filesystem temporarily taken dead, which pulls most units down. This was fixed by upstream in https://github.com/systemd/systemd/pull/23218. But this was not backported to the versions used by Ubuntu packages for focal and jammy. The needed commit from that PR is the one with message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`. This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed. And I suppose it does also for jammy. I have manually tested the fix with Ubuntu Core 20, and this fixes our issue. We would like this patch to be backported to focal-updates and jammy- updates. Thank you in advance. [ Impact ] If a user adds a service that calls `systemctl daemon-reload`, and if this service is started before systemd-udevd. And if the initrd is systemd (the case of Ubuntu Core), then most service will be stopped or cancel, and the machine will mostly shutdown everything and hang. The fix has been backported down to 250 upstream. It is already on kinetic and later. The fix only affects systems where systemd is used in initrd. [ Test Plan ] On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any system that uses systemd in initrd. Add a systemd service that calls `systemctl daemon-reload`. The service should have `DefaultDependencies=no` in order to start as soon as possible and be enabled. Restart the machine. If fix is not applied, after the service is started, most of units with be shutdown, and the system will be unusable. [ Where problems could occur ] This should affect systems with systemd in initrd. There are risks on systems that have an udev rule in initrd not present in the main system. There are risks on systems that use db_persist in initrd where the device can potentially get dead state. Though this does not seem to happen on Ubuntu Core 22, even though we use db_persist for dev mapper devices. Regression is upstream bug #23429. Commits named "core/device: device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not downgrade device state if it is already enumerated" could be applied as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2035122] Please test proposed package
Hello Sergio, or anyone else affected, Accepted systemd into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.12 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. -- 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/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Bug description: [Impact] When working with ubuntu core or ubuntu core desktop, neither */etc/default/locale* nor */etc/default/keyboard* are modifiable, so it's not possible to set the global keyboard or the global language. This is required to allow to set the GDM language, and the default one during installation. The first half of the solution is to create the folder */etc/writable/default*, and make soft-links from */etc/default/locale* to */etc/writable/default/locale* and from */etc/default/keyboard* to */etc/writable/default/keyboard*, just like it is already being done with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and , */etc/timezone*. This solution, unfortunately, isn't complete. Although any application that just reads the files will work, not all of the applications that write to them will; specifically the systemd utilities that set the contents for those files, because they don't open the file directly; instead, they create first the new file in the same folder than the old one, fill its contents, and only then delete the old one and rename the new one. To solve this, systemd in Ubuntu already has several patches that detect if a file is a soft-link, in which case it replaces the old path with the destination one. Currently I have in place a patch for Ubuntu Core Desktop that implements both changes for both */etc/default/locale* and */etc/default/keyboard*. [Test plan] Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core or Ubuntu Core Desktop admin terminal must change the locale to the specified one, which can be checked by reading the */etc/default/locale* file. Also, *localectl* must return the new locale. [Where problems could occur] In general, applications just read the content of the file and use the DBus interface to set the locale, so only those applications that modify by themselves the */etc/default/keyboard* and/or */etc/default/locale* would present a problem, in which case they would require specific patches. Anyway, those applications neither would work with the current state (with those files in a read-only filesystem). [Other info] For Noble, this will be addressed when we merge systemd v255 from Debian. This is only needed on core, so we don't need to fix for Mantic or Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2044159] Re: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data
@ Simon #3 Im also able to file bugs, with that cloud-init warning as described by you only when the package is 'linux' apport seems to abort saying its not a valid package but i suspect this is due another bug; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2044159 Title: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu-desktop 24.04 development branch @ 21/11/2023 When filing individual bugs from terminal using ubuntu-bug package i'm getting an error: cloud-init run data not found on system. Unable to add cloud-specific data wich in some cases prevents me to file the bug ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.27.0-0ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportLog: ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:06:19 2023 InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044159/+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 2045621] Re: Improve power consumption on Framework systems
I have uploaded this change for jammy and mantic, and it is already in systemd in noble-proposed. Given lunar is EOL on January 25, I think we can skip lunar, so I marked that won't fix. ** Changed in: systemd-hwe (Ubuntu Lunar) Status: Confirmed => Won't Fix ** Changed in: systemd-hwe (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: systemd-hwe (Ubuntu Mantic) Status: Confirmed => 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: In Progress Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Won't Fix Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: In Progress Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 1746419] Re: bond parameters are not changed by 'netplan apply'
I'm also affected by this issue. Makes experimenting with settings very tedious. -- 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/1746419 Title: bond parameters are not changed by 'netplan apply' Status in netplan: Triaged Status in nplan package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I have a yaml file as follows: network: version: 2 ethernets: bonddevs: match: name: ens[78] bonds: bond0: interfaces: [bonddevs] parameters: mode: active-backup mii-monitor-interval: 1 addresses: - 10.10.10.1/24 Say I decide that 1s is too frequent for the MII interval, and I want to change the interval to 2s. If I change that in the yaml, then run # netplan generate # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 In other words, the change has not been applied. Running netplan --debug apply prints: DEBUG:device bond0 operstate is up, not replugging So I wondered if bringing the bond down would help. It does not: # ip link set dev bond0 down # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 However, deleting the link works: # ip link del dev bond0 # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 2000 This is counter-intuitive behaviour. Ideally, I would like a regular netplan apply to work without deleting the bond. However, a changed to the docs to make this clear would be OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nplan 0.32~17.10.1 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Jan 31 05:47:42 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+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 1746419] Re: bond parameters are not changed by 'netplan apply'
** Tags added: foundations-todo -- 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/1746419 Title: bond parameters are not changed by 'netplan apply' Status in netplan: Triaged Status in nplan package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I have a yaml file as follows: network: version: 2 ethernets: bonddevs: match: name: ens[78] bonds: bond0: interfaces: [bonddevs] parameters: mode: active-backup mii-monitor-interval: 1 addresses: - 10.10.10.1/24 Say I decide that 1s is too frequent for the MII interval, and I want to change the interval to 2s. If I change that in the yaml, then run # netplan generate # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 In other words, the change has not been applied. Running netplan --debug apply prints: DEBUG:device bond0 operstate is up, not replugging So I wondered if bringing the bond down would help. It does not: # ip link set dev bond0 down # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 However, deleting the link works: # ip link del dev bond0 # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 2000 This is counter-intuitive behaviour. Ideally, I would like a regular netplan apply to work without deleting the bond. However, a changed to the docs to make this clear would be OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nplan 0.32~17.10.1 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Jan 31 05:47:42 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
Thank you for your incredibly thorough analysis of this. Since finding this via bug 2046470, I have tried, without success, to create a test to show any difference in performance or power or whatever between irqbalance enabled/disabled on my Ubuntu 20.04 test server. While my vote carries little weight here, I give it anyhow: A) Change it from an opt-out to an opt-in and remove the dependency from ubuntu-standard Mainly because, and from my own investigation, I agree with: > To me this seems to be a perfect case for a few special images/deployments > known to match the workload profile that needs this to enable it. > It is also more likely that a professional admin of such a large scale machine > (or cluster thereof) can make the opt-in decision and evaluation better than > expecting every user of Ubuntu to think about an opt-out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1007924] Re: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep)
** Changed in: pm-utils (Debian) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1007924 Title: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep) Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Triaged Status in pm-utils package in Debian: Confirmed Bug description: While looking at /var/log/pm-suspend.log I have noticed that the NetworkManager hooks fail: Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend_hybrid: Having NetworkManager put all interaces to sleep...Failed. Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend_hybrid: Having NetworkManager wake interfaces back up...Failed. Looking at the script is uses org.freedesktop.NetworkManager.sleep and org.freedesktop.NetworkManager.wake. Calling this results in errors like this: % sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.sleep Error org.freedesktop.DBus.Error.UnknownMethod: Method "sleep" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist According to the documentation [1], the interface is different / has changed. The correct usage would be to call org.freedesktop.NetworkManager.Sleep with a boolean value, like: sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Sleep boolean:true 1: http://projects.gnome.org/NetworkManager/developers/api/09/spec.htmlorg.freedesktop.NetworkManager.Sleep ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pm-utils 1.4.1-9 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 2 21:36:40 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/1007924/+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 2046356] Re: Update URL for Support information in MOTD message
I have performed the SRU verification with the following script:
--
#!/bin/bash
set -e
series=$1
name=$series-dev
function cleanup {
lxc delete $name --force
}
function on_err {
echo -e "Test Failed"
cleanup
exit 1
}
trap on_err ERR
lxc launch ubuntu-daily:$series $name
sleep 5
# Install latest base-files
lxc exec $name -- apt-get update > /dev/null
lxc exec $name -- apt-get install -y base-files > /dev/null
echo -e "\n* Latest base-files is installed"
echo "###"
lxc exec $name -- apt-cache policy base-files
echo -e "###\n"
echo -e "\n* Installing update-motd"
lxc exec $name -- apt-get install -y update-motd > /dev/null
echo -e "###\n"
echo -e "\n* Check current MOTD message for Support URL"
echo "###"
lxc exec $name -- update-motd
echo -e "###\n"
echo -e "\n* base-files is installed from proposed"
echo "###"
lxc exec $name -- sh -c "echo \"deb http://archive.ubuntu.com/ubuntu
$series-proposed main\" | tee /etc/apt/sources.list.d/proposed.list"
lxc exec $name -- apt-get update > /dev/null
lxc exec $name -- apt-get -t $series-proposed install base-files -y > /dev/null
lxc exec $name -- apt-cache policy base-files
echo -e "###\n"
echo -e "\n* Check updated MOTD message fro Support URL"
echo "###"
lxc exec $name -- update-motd
echo -e "###\n"
cleanup
--
I can confirm that URL has been successfully updated for the MOTD message.
I am also attaching the test results for all the releases target by this change
** Attachment added: "base-files-test-result.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+attachment/5736850/+files/base-files-test-result.tar.xz
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy verification-needed-lunar
verification-needed-mantic verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-jammy verification-done-lunar
verification-done-mantic verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2046356
Title:
Update URL for Support information in MOTD message
Status in base-files package in Ubuntu:
Fix Released
Status in base-files source package in Xenial:
Fix Committed
Status in base-files source package in Bionic:
Fix Committed
Status in base-files source package in Focal:
Fix Committed
Status in base-files source package in Jammy:
Fix Committed
Status in base-files source package in Lunar:
Fix Committed
Status in base-files source package in Mantic:
Fix Committed
Status in base-files source package in Noble:
Fix Released
Bug description:
[Impact]
When users see the MOTD message, they are currently seeing an outdated url
under the support information.
Even though the outdated url redirects to new Ubuntu Pro webpage, we believe
the users should still see
the correct url from the start
[Test Case]
- Launch a LXD container for any of the affected releases
- Install the package with this fix applied
- Install `update-motd` package
- Run `update-motd` and confirm the Support url is now the correct one
[Regression Potential]
If users are parsing MOTD for some reason, the url change might break that
logic now. However, parsing MOTD messages is not a supported flow, so we
believe regression potential is low here.
[Discussion]
Since we want users to be aware of what Ubuntu Pro is, we should highlight
the right product name on any place that is still using the old "advantage"
name. Updating the support URL here is a step into this direction
[Original Bug Description]
On the file 10-help-text, we are printing the following line on MOTD:
* Support: https://ubuntu.com/advantage
We should update the url to https://ubuntu.com/pro instead, as this
will the default url for support information now
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2048136] Re: Please support systemd-coredump as core dump handler
First step: support reading report from systemd-coredump: https://github.com/canonical/apport/pull/281 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2048136 Title: Please support systemd-coredump as core dump handler Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: There can only be one system core dump handler on a Linux system and Apport is the Ubuntu default core dump handler. Besides Apport other tools offer coredump handler, in particular systemd-coredump. Due to Apport being installed on all Ubuntu system by default none of these alternate system can be installed. There has been some user request for this integration to work. Proper integration between Apport and systemd-coredump would offer a better experience to developers who want to use systemd-coredump. systemd- coredump and coredumpctl provide more documentation and have more users upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2048136/+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 1834780] Re: apport should have python3-launchpadlib in required dependencies
As of Ubuntu 23.10, python3-apport depends on python3-launchpadlib. So this bug was addressed. ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1834780 Title: apport should have python3-launchpadlib in required dependencies Status in apport package in Ubuntu: Fix Released Bug description: When asked to report apt-collect , apport is not installed on my system and I was told "apt install apport", so I did and the installation went ok. Problem: apport then fails on missing dependency python3-launchpadlib Workaround: manually install it through apt. Solution: apport should have python3-launchpadlib in required dependencies. --- ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: apport 2.20.9-0ubuntu7.6 [origin: Ubuntu] PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-20.21~18.04.1-generic 5.0.8 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-20-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1834780/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same problem Razer Blade 16 2023 -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2046356] Re: Update URL for Support information in MOTD message
The update-motd armhf failure is unrelated (migration-reference also fails): https://autopkgtest.ubuntu.com/packages/u/update- motd/mantic/armhf The macaulay2 ppc64el was a flaky test (OOM) and passed with a re- trigger: https://autopkgtest.ubuntu.com/packages/m/macaulay2/jammy/ppc64el -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in base-files source package in Jammy: Fix Committed Status in base-files source package in Lunar: Fix Committed Status in base-files source package in Mantic: Fix Committed Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
After all the history I was looking at where we are right now: - irqbalance already is not in ubuntu-cloud-minimal images - irqbalance is in normal cloud images and installed systems via the dep from ubuntu-server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
I subscribed a few people directly to get their input. @Steve I've subscribed you after trying to find, refer and summarize all of the past to allow you and anyone else to read into this in one go. I think I'll need your input as Architect and as participant of these discussions right from when they started 14 years ago. @Phil/@John Some past discussions, especially the backpedaling of Debian referred to virtual environments and/or large cloud providers. Is irqbalance anything you got asked to disable (or keep) for their environment? No need to share names, but reasoning or data points would be helpful :-) @Dimitri Is there a more clear "this is what userspace should do in regard to this in 2024" form the kernel? I couldn#t find it, but maybe you know or know who'd know ... @Sebastien Since most problems reported have been around Desktops (to be fair, that could be an coincidence because that is where people do more experiments and have more diverse special cases). But I think it is fair to ask you if requests or discussion like the above have come up towards Desktop that are worth to refer here? Maybe one of you has more details that help to make the decision more clear and easy. Or a gut feeling that is even stronger than mine, strong enough even to pick one of the options? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
# Summary This discussion was seeminly easier to make the more dedicated to a singluar use case you are - as then you have less "but what if" cases to consider. That wide usage is great for Ubuntu but sometimes delays decisions. List of reasons to remove it from the default dependencies: - Seems to cause issues more often on Desktop environments - cpufreq, thermald and similar struggle to save energy - Impacts due to unepexcted throttling - Conflicts with enabling/disabling threads/cores - Problematic in virtual environments - It is mostly an x86 thing but we pull it in everywhere - It conflicts with manually fine tuned IRQ affinity e.g. in ultra low latency setups - It is less useful on cpus with large and wide shared caches as well as in virtual environments without fix pinning List of reasons to keep it in the set of default dependencies: - Benefits seem mostly for large scale servers - lacking irqbalance can be a performance degradation in some large scale high traffic cases I think from all I've found - old and new - it seems it still has its purpose in some scenarios, but the HW/SW world evolved and it is nowadays less often useful and more often harmful than it was in the past. On the other hand there is almost no clear cut "it is bad and that is why", most issues were individual issues and special cases, nothing that would apply to everyone. And irqbalance still has is purpose, so we should surely keep it around. In a perfect worlds this would have half a year of time or more and two people to run all kinds of workloads on all kinds of HW to compare. But let us be honest that will not happen and that would then also be not be worth the effort. We'll have to decide with what we have. Have the others that switched have more time to evaluate in depth, I do not know. But usually once a significant amount of the ecosystems changed and you lack better data it is better to also follow or common hints and optimizations will no more apply due to being the one outlier in regard to behavior. To me this seems to be a perfect case for a few special images/deployments known to match the workload profile that needs this to enable it. It is also more likely that a professional admin of such a large scale machine (or cluster thereof) can make the opt-in decision and evaluation better than expectint every user of Ubuntu to think about an opt-out. --- Options IMHO: A) Change it from an opt-out to an opt-in and remove the dependency from ubuntu-standard B) Remove it from ubuntu-standard to get rid of it in Desktops and images used in virtual environments. But try to keep it in a place that is mostly used for bare metal which tend to be closer to the kind that benefits more C) Do nothing, keep it as is D) Any of the above, but let us not touch Noble more than half way through the cycle, but do that early in 24.10 to have enough exposure before a release in an LTS. My gut feeling (and it can't be much more without much more time for much deeper investigations) would be (A). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior:
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Actions by Others Times have changes, as mentioned above the kernel learned many new tricks. More new I/O hardware virtual or physical appeared that tries to be smart and thereby sometimes conflict with what irqbalance does. Some are mostly based on the links referred above, the Debian disucssion was more about it being harmful (or at least not helpful) in virtual environments and hence removed from cloud images (we close in on workload specific again). Indeed many projects already removed it from the default - https://github.com/pop-os/iso/pull/288 - https://github.com/ValveSoftware/Proton/issues/3243 - https://lists.debian.org/debian-cloud/2019/04/msg00040.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi, this was overlooked for too long but came up in bug 2046470 again which made me see this for the first time. I'd wish we'd have had that even a bit earlier e.g. to release it with mantic and not half way through noble, but still now is the time to still change the next LTS. I needed to make up my mind on this to come to a conclusion and so I wrote a summary mostly for myself, but also for others that I want to ack to the decision as well as for anyone to later be able to understand what changed and why. I must admit that I'm slightly biased, having looked at it ages ago, even before I was more active in Ubuntu development and already wondering if that should be used by default. And yes, some people had a stronger wish to get it out of the default. So as already reported, many have already asked to remove it. I'll try to break up my answers to be more easily referable. ** Also affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
# Referred Arguments An argument that might not have been so strong more than a decade ago but is much more today is power savings and that is an aspect that comes up over and over. It also had reports of conflicts with power saving [10] and e.g. dynamically disabling/enabling cores which is much more a thing nowadays as long ago this was only reliably working on mainframes anyway. I don't buy the "games need 100%" as even games need their I/O to happen, but OTOH irqbalance just doesn't help much nowadays either as the kernel learned many more tricks to do well - like to name just one all the traffic aware and potentially offloaded rps/xps [2]. And irqbalance is not mutually exclusive with most of those technologies not with RSS [18] nor with kernel policies [15]. Some report about conflicting with their custom tweaking of IRQs [8][16]. It is actually a common conflict between irqbalance being smart [9] and other things like a particular device firmware being smart leading to a conflict of interest. => But TBH that is why it is removable for such rare cases. On one hand it clearly has some impact and various cases of bad impacts by it have come up as well for frame rates [11], stuttering [14] or even network traffic [12]. But on the other hand, there have been reports and cases where a broken irqbalance led to impacted high-performance network traffic [7], so it is not that it is clearly always bad [13]. While we never know how outdated any such source might be, it proves that it is most likely workload and system dependent. Many documentations also sitll refer to it only older RH, Arch [19], ... you'll find it everywhere. It is an interesting case, and the workload dependency leads many discussions to even be contradicting - in one case it saves cpu power in the other it makes it worse. In one it helps traffic in the other is degrades it. That is all a consqeuence of it being workload and system dependent. This back and forther is perfectly encapsulated in this phornix thread [15]. Which quotes interesting other POVs like kernel solutions often being "driver centric" optimizing throughput, but maybe not always the best as policy for the full system as irqbalance pilicies and tunables are configurable. An interim summary might be: """ It could cause rare issues or conflicts, especially on Desktop, but might be still wanted on Servers especially those with a high rate of I/O """ Which is interestingly quite close to the arguments floating around when it was added more than a decade ago (see further below). [2]: https://www.kernel.org/doc/html/latest/networking/scaling.html [7]: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2038573 [8]: https://groups.google.com/g/gce-discussion/c/Ns8hgOUW9GY [9]: https://docs.xilinx.com/r/en-US/ug1523-x3522-user/Interrupt-Affinity [10]: https://konkor.github.io/cpufreq/faq/#irqbalance-detected [11]: https://askubuntu.com/questions/1067866/ubuntu-18-04-steam-games-frame-rate-drop [12]: https://serverfault.com/questions/410928/irqbalance-on-linux-and-dropped-packets [13]: https://bookofzeus.com/harden-ubuntu/server-setup/disable-irqbalance/ [14]: https://www.reddit.com/r/linux_gaming/comments/emnu3k/removing_irqbalance_fixed_major_stuttering_in/ [15]: https://www.phoronix.com/forums/forum/hardware/processors-memory/1335986-amd-zen-1-linux-performance-hit-from-retbleed-accumulated-cpu-mitigation-impact/page4 [16]: https://documentation.suse.com/sbp/server-linux/pdf/SBP-performance-tuning_en.pdf [18]: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/performance_tuning_guide/network-rss [19]: https://wiki.archlinux.org/title/Improving_performance#irqbalance ** Bug watch added: Debian Bug tracker #577788 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577788 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
# Integration and maintenance Despite some saying it is for the past only, it is regularly updated and has multiple releases per year throughout all the time [4]. Those updates flow well into Debian and Ubuntu - so it is not a classic "old and outdated" case. And while not much changes in those updates, it means it still learns like about thermal events in 1.9.1 or about isolcpus in 1.0.9. I'm not saying it is super modern doing it all, but it gets updates. Currently this is seeded in ubuntu-standard [1], which is what makes it default installed everywhere. But it is intentionally only a recommends, so the set of people that want to remove it can do so. It was added a long time ago [3] back when multi-core was a rare thing at least for Desktop systems. This was based on a discussion [5] and was related to the kernel [6] actively delegating this to userspace. Debian did a similar change a bit later [17] for the same reasons. But again this was the time of single-core being common. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/tree/standard?h=noble#n19 [3]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/commit/?h=noble&id=dcd02266953547e11221979eb17eb740a76a62b5 [4]: https://github.com/Irqbalance/irqbalance/tags [5]: https://lists.ubuntu.com/archives/ubuntu-devel/2010-January/029939.html [6]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b8e8c1bf7275eca859fe551dfa484134eaf013b [17]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577788 ** Bug watch added: github.com/ValveSoftware/Proton/issues #3243 https://github.com/ValveSoftware/Proton/issues/3243 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems
** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2043393 Title: Report.get_logind_session fails to determine session on cgroup2 systems Status in Apport: In Progress Status in apport package in Ubuntu: Triaged Bug description: Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu 18.04 only cgroup version 1). Report.get_logind_session will fail to determine the logind session and always return None if only cgroup2 is used. get_logind_session searches for cgroup lines with "name=systemd:" and then extracts the session from "/session-". This worked in Ubuntu 16.04 but started failing in 18.04. Content of /proc/self/cgroup when printed from a terminal inside a Ubuntu desktop session: Ubuntu 16.04 (xenial) - ``` 12:cpuset:/ 11:perf_event:/ 10:pids:/user.slice/user-1000.slice 9:blkio:/ 8:hugetlb:/ 7:net_cls,net_prio:/ 6:cpu,cpuacct:/ 5:devices:/user.slice 4:freezer:/ 3:rdma:/ 2:memory:/ 1:name=systemd:/user.slice/user-1000.slice/session-c1.scope ``` Ubuntu 18.04 (bionic) - ``` 12:freezer:/ 11:net_cls,net_prio:/ 10:memory:/ 9:rdma:/ 8:cpu,cpuacct:/ 7:devices:/user.slice 6:perf_event:/ 5:cpuset:/ 4:pids:/user.slice/user-1000.slice/user@1000.service 3:hugetlb:/ 2:blkio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service 0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service ``` Ubuntu 20.04 (focal) - ``` 13:memory:/user.slice/user-1000.slice/user@1000.service 12:perf_event:/ 11:misc:/ 10:pids:/user.slice/user-1000.slice/user@1000.service 9:hugetlb:/ 8:cpuset:/ 7:blkio:/ 6:devices:/user.slice 5:cpu,cpuacct:/ 4:freezer:/ 3:rdma:/ 2:net_cls,net_prio:/ 1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope 0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope ``` Ubuntu 22.04 (jammy) - ``` 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope ``` To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2043393/+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 1899628] Re: ubuntu-bug fails just after installing apt update has never been done
** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1899628 Title: ubuntu-bug fails just after installing apt update has never been done Status in apport package in Ubuntu: Triaged Bug description: Doing the ISO testing in a machine, that I did it staying offline. After installing, I connected and noticed a bug I wanted to report in ubuntu-drivers-common, but doing `ubuntu-bug` on it failed: This does not seem to be an official Ubuntu Package. Please retry after updating the indexes of available packages... https://i.imgur.com/fnDz6vf.png This is true as per: $ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.5.4 Candidate: 1:0.8.5.4 Version table: *** 1:0.8.5.4 100 100 /var/lib/dpkg/status However, apport should probably trigger an apt-update in such case first instead of failing, or adding a button to do this easily and then proceed with the report. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu49 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 13 14:19:30 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1899628/+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 1838372] Re: 'ubuntu-bug -w' doesn't work under wayland
The latest 'ubuntu-bug -w' shows an error message: ``` $ LANGUAGE=C apport-cli -w *** Error: Cannot create report The window option cannot be used on Wayland. Please find the window's process ID and then run 'ubuntu-bug '. The process ID can be found by running the System Monitor application. In the Processes tab, scroll until you find the correct application. The process ID is the number listed in the ID column. ``` But since Wayland is the default, we should implement Wayland support. ** Changed in: apport (Ubuntu) Status: Confirmed => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Wishlist ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1838372 Title: 'ubuntu-bug -w' doesn't work under wayland Status in apport package in Ubuntu: Triaged Bug description: 'ubuntu-bug -w' doesn't work for most applications such nautilus, gedit, settings, etc. under wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1838372/+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 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description
Thank you for taking the time to report this bug and contributing to Ubuntu. I can reproduce your steps and Apport behaves poorly for that use case. Following steps should be implemented to address this bug: 1. Improve the message "You need to specific the pakacge or PID" to state that it should be on the command line and it also should mention the --window option. 2. Fix --window option to work also on Wayland. (bug #1838372) 3. Instead of printing the error message, guide the user in the UI. To anwser your other question and help your initial task: ubuntu-bug and apport-bug are the same (one is a symlink to the other). The program name of "Ubuntu Software" is snap-store. ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Low ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Importance: Undecided => Low ** Changed in: apport Status: New => Triaged ** Changed in: apport Milestone: None => 2.28.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2044129 Title: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: the man page of ubuntu-bug/apport-bug (what is the difference? why am I shown the manpage of apport-bug when typing man ubuntu-bug?) says running apport-bug without arguments results in showing me a list of symptoms. When I try to report a bug in some general program that is not related to the other 9 categories - which is most of the 1 apps in Ubuntu - I must chose "Other Problem" - but in contrary to the man page that tells me I am asked about further things, I only get "You need to specific the pakacge or PID". I currently try to report a bug in the things that identifies itself as "Ubuntu Software" in the Dock, but I have no idea what its correct program or package name is, and have no idea how to find that. In PS there is no process with "ubuntu" or "software" in its name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apport 2.27.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16 Uname: Linux 6.2.0-1015-lowlatency x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 14:38:42 2023 InstallationDate: Installed on 2023-08-21 (92 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: apport UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2044129/+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 2044159] Re: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data
Hi! Thank you for filing a bug and contributing to Ubuntu. We're able to partially confirm this bug by simply having cloud-init installed on our system and running `ubuntu-bug libc6`, which will start off by printing 'cloud-init run data not found on system. Unable to add cloud-specific data.' on stderr. However, this didn't prevent us from filing bugs, either on a GUI environment or in a terminal-only chroot. Could you give us more details about the cases where it prevented you from filing a bug? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2044159 Title: Ubuntu-bug triggers an error cloud-init run data not found on system. Unable to add cloud-specific data Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu-desktop 24.04 development branch @ 21/11/2023 When filing individual bugs from terminal using ubuntu-bug package i'm getting an error: cloud-init run data not found on system. Unable to add cloud-specific data wich in some cases prevents me to file the bug ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: apport 2.27.0-0ubuntu6 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportLog: ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:06:19 2023 InstallationDate: Installed on 2023-11-09 (12 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=nl_NL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: apport UpgradeStatus: Upgraded to noble on 2023-11-09 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2044159/+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 2006981] Re: apport-gtk crashed with signal 5 in g_log_writer_default()
Little bit of data here. For some reason glib2.0 is thinking we're in a GDB context and so is spitting out a SIGTRAP rather than the expected SIGABRT, see https://sources.debian.org/src/glib2.0/2.78.3-1/glib/gmessages.c/#L556 Now, why is it aborting I'm not too sure. The stack trace gives us a hint, as it seems it's failing to detect a graphical environment. Did the crash appear spontaneously on the desktop, or were you trying to report another bug? ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2006981 Title: apport-gtk crashed with signal 5 in g_log_writer_default() Status in apport package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I can´t provide any other information other than what was collected. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: apport-gtk 2.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:9017369:2023-02-10 20:09:56.662793636 -0300:2023-02-10 20:09:57.662793636 -0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash 640:1000:124:1463707:2023-02-10 20:09:58.698746919 -0300:2023-02-10 20:09:59.698746919 -0300:/var/crash/_usr_bin_kwin_x11.1000.crash 640:1000:124:633811:2023-02-10 20:09:59.986718177 -0300:2023-02-10 20:10:00.986718177 -0300:/var/crash/_usr_bin_xembedsniproxy.1000.crash 640:1000:124:653094:2023-02-10 20:10:01.258690357 -0300:2023-02-10 20:10:02.258690357 -0300:/var/crash/_usr_bin_gmenudbusmenuproxy.1000.crash 640:1000:124:990:2023-02-10 20:10:05.770595073 -0300:2023-02-10 20:10:06.770595073 -0300:/var/crash/_usr_share_apport_apport-gtk.1000.crash CurrentDesktop: KDE Date: Fri Feb 10 20:10:04 2023 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A Signal: 5 SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2006981/+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 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10
Same here, I was using Ubuntu 23.10 for a while, and on day my headset started behaving weirdly, I didn't installed anything. When trying to troubleshoot, I noticed that I had audio working when choosing Handsfree mode, that's mono audio with mic input for my Senheiser HD BT40, but it doesn't work when choosing other configurations with stereo high fidelity aptX or anything else. Moving forward, I noticed that even the laptop audio isn't working (Comet Lake PCH cAVS) from my hinkPad X1 Extreme Gen 3 Intel (15"). I think I broke my system even harder trying to fix it trying pipewire, wireplumber and such, now when I go to Sound Configuration I don't even see other previously available configurations when selecting the Headset. Is there some steps so I can restore default configurations =/? http://alsa-project.org/db/?f=b74c74303071e17f6d87fe940f59d89132eecc53 -- 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/2043524 Title: audio disappeared after upgrade to Ubuntu 23.10 Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except there is no audio output on streaming functions. The external bluetooth speaker is connected and detected. It is charged and responds to testing. Just no sound when playing videos or podcasts. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: owner 975 F wireplumber /dev/snd/seq:owner 971 F pipewire CasperMD5CheckResult: fail CurrentDesktop: KDE Date: Tue Nov 14 17:50:17 2023 InstallationDate: Installed on 2023-04-15 (213 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago) dmi.bios.date: 07/04/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2046474] Re: Ubuntu-bug in terminal few errors
Hi again!
Thanks for filing the multiple detailed bugs, this is greatly
appreciated as it makes triaging much easier!
In this instance, I'm closing this as Invalid since this output isn't
directly apport/ubuntu-bug related, it's the output of some tools we're
invoking under the hood, and/or GTK being its verbose self. There isn't
much we can do about it.
Cheers!
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2046474
Title:
Ubuntu-bug in terminal few errors
Status in apport package in Ubuntu:
Invalid
Bug description:
Ubuntu-bug in terminal few errors
ubuntu-bug -w
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0):
cannot open directory "/var/lib": permission denied
update.go:85: cannot change mount namespace according to change mount
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none
bind,ro 0 0): cannot open directory "/var/lib": permission denied
Gtk-Message: 18:43:25.874: Failed to load module
"window-decorations-gtk-module"
Gtk-Message: 18:43:25.874: Failed to load module "colorreload-gtk-module"
kng@kng-300E5EV-300E4EV-270E5EV-270E4EV:~$ ATTENTION: default value of option
mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF
while parsing a value", line: 1, column: 0))
ALSA lib conf.c:4120:(snd_config_update_r) Cannot access file
/usr/share/alsa/alsa.conf
ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ default
[Parent 10803, IPC I/O Parent] WARNING: process 11194 exited on signal 9:
file
/build/firefox/parts/firefox/build/ipc/chromium/src/base/process_util_posix.cc:266
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
640:1000:125:10103500:2023-12-14 16:45:11.104133895 +0200:2023-12-14
16:45:07.048100891 +0200:/var/crash/_usr_bin_kwin_x11.1000.crash
640:1000:125:7629821:2023-12-14 15:37:52.752158527 +0200:2023-12-14
15:37:50.912875521 +0200:/var/crash/_usr_bin_dolphin.1000.crash
CurrentDesktop: KDE
Date: Thu Dec 14 19:16:42 2023
InstallationDate: Installed on 2021-03-10 (1009 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2023-05-08 (220 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2046474/+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 2048112] Re: Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first
Hi, thanks for taking the time to report this issue and contributing to Ubuntu :) I confirmed this issue (along with the one with firefox snap vs deb). This is a bit bigger of an issue, as it means some non-privileged users won't be able to report issues (or at least would give up as soon as the prompt comes up), thus marking as Medium. ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Summary changed: - Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first + Ubuntu-bug prompts for admin password before selecting the target package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2048112 Title: Ubuntu-bug prompts for admin password before selecting the target package Status in apport package in Ubuntu: Triaged Bug description: Ubuntu-bug ask for password to find out that bug is for snap app and gives info where to report. Instead it should save resources and check that first and password not needed to give just info of another bug reporting location ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jan 4 21:15:17 2024 InstallationDate: Installed on 2024-01-04 (0 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048112/+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 2045621] Re: Improve power consumption on Framework systems
Got it, thanks. The merge proposals were created. -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2047999] Re: Ubuntu-bug thinks i have 2 firefox installed
Hi, thanks for taking the time to report this issue and contributing to Ubuntu :) I just confirmed on my system. Since the number of transitional packages is fairly small, I think we should just maintain a hardcoded list in Apport and hide the .deb by default (with maybe a way to override this?) Marking as Low priority, since this is IMHO something of a papercut (still annoying, though!) ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Low ** Summary changed: - Ubuntu-bug thinks i have 2 firefox installed + ubuntu-bug shows both the snap and the transitional deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2047999 Title: ubuntu-bug shows both the snap and the transitional deb Status in apport package in Ubuntu: Triaged Bug description: Make 22.04.3 usb live make ubuntu-bug firefox it says cant- its snap app learn how to update snap sudo snap refresh sudo snap refresh ubuntu-bug firefox see screenshot- asks about 2 different snaps why previous is not removed? why before it said that snap cant be reported? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82.5 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportLog: ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: called for pid 1362, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: executable: /usr/lib/systemd/systemd-journald (command line "/lib/systemd/systemd-journald") ERROR: apport (pid 7549) Thu Jan 4 03:01:09 2024: wrote report /var/crash/_usr_lib_systemd_systemd-journald.0.crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CrashReports: 640:0:124:308838:2024-01-04 03:01:09.572926187 +:2024-01-04 03:01:09.480938425 +:/var/crash/_usr_lib_systemd_systemd-journald.0.crash CurrentDesktop: KDE Date: Thu Jan 4 03:59:27 2024 LiveMediaBuild: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2047999/+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 2045621] Re: Improve power consumption on Framework systems
** Merge proposal linked: https://code.launchpad.net/~artur-at-work/+git/systemd-hwe/+merge/458064 ** Merge proposal linked: https://code.launchpad.net/~artur-at-work/+git/systemd-hwe/+merge/458066 ** Merge proposal linked: https://code.launchpad.net/~artur-at-work/+git/systemd-hwe/+merge/458067 -- 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/2045621 Title: Improve power consumption on Framework systems Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: Fix Committed Status in systemd-hwe package in Ubuntu: Invalid Status in systemd source package in Jammy: Won't Fix Status in systemd-hwe source package in Jammy: Confirmed Status in systemd source package in Lunar: Won't Fix Status in systemd-hwe source package in Lunar: Confirmed Status in systemd source package in Mantic: Won't Fix Status in systemd-hwe source package in Mantic: Confirmed Status in systemd source package in Noble: Fix Committed Status in systemd-hwe source package in Noble: Invalid Bug description: [ Impact ] * Framework systems that have DP or HDMI cards connected will have increased power consumption even when nothing is connected to DP or HDMI ports since the cards don't default to autosuspend. * Backporting upstream patch that adds rules in hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions. [ Test Plan ] * DUT: Framework with DP and HDMI: $ lsusb | grep Framework Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card 1. Autosuspend is not enabled before patch. Set to "on" in power/control $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control on $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer Framework $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control on 2. Install patch 3. Autosuspend is enabled for both extensions. Set to "auto" in power/control $ cat power/control auto [ Where problems could occur ] * During testing verified that both DP+HDMI display show good output after hot-plug, system suspend, and reboot. There might be some differences when hibernate and hotplug. [ Other Info ] * https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2036253] Re: FTBFS: missing strl* symbols fail the build
Uploaded on mantic queue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2036253 Title: FTBFS: missing strl* symbols fail the build Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Mantic: Fix Committed Status in heimdal source package in Noble: Fix Released Status in heimdal package in Debian: Fix Released Bug description: [ Impact ] Currently, the build of the heimdal package against glibc 2.38 is not possible due to the fact that strlcat and strlcpy were added to glibc in version 2.38 and heimdal no longer defines its internal version. We need this fix to build the heimdal package successfully. It's also important to be able to apply security fixes in the future (if needed). [ Test plan ] Build the package in a ppa to check that the error is gone and that the package builds successfully. # Install the package and check it works ok #0.Prepare a VM or Container. i.e: # lxc launch ubuntu-daily:mantic Mheimdal # lxc shell Mheimdal #1. Install heimtools from heimdal-clients # apt update && apt upgrade -y # apt install -y heimdal-clients #1.1 Check the libraries are installed well # dpkg -l libroken19-heimdal | grep ii # dpkg -l libkafs0-heimdal | grep ii #1.2 Check that the command is not broken (you get a Usage: : heimtools [--version] [--help] command ..) # heimtools --help #2. Install aklog from src:aftools, openafs-krb5 binary package. A rebuild of aftools against the new heimdal package is needed for this to be successfull. # apt install -y openafs-krb5 #2.1 Check that the command is not broken (you don't get a aklog: symbol lookup error: aklog: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0) # aklog --help [ Where problems could occur ] I tried to get a complete list of libraries and binaries that use the symbols affected in this fix (inside and outside the ones provided by src:heimdal itself), but, I don't know if there are other third-party pieces of software outside the archive that depends on these libraries. If that is the case, when executing, the affected binary will no run and a message like this could appear: undefined symbol: rk_strlcat, version HEIMDAL_ROKEN_1.0 Could be a disruption in the way the heimdal suite works? Unlikely, but there is always room for it. It should be fine since the symbols, in this case, are available to all heimdal-dependants libraries in the build. This case could arise if a mix of heimdal libraries (provided by two different versions of src:heimdal) are installed, but this is what the 'Breaks:' that was added in the d/control wants to avoid. [ Other Info ] A rebuild of the openafs package against this new version of the libraries provided by this heimdal package is needed. (bug 2046441). [ Original Description ] See ubuntu-devel thread[1] and mantic rebuild report[2]. dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkafs0-heimdal/DEBIAN/symbols doesn't match completely debian/libkafs0-heimdal.symbols --- debian/libkafs0-heimdal.symbols (libkafs0-heimdal_7.8.git20221117.28daf24+dfsg-3ubuntu1_amd64) +++ dpkg-gensymbolshoPgEa 2023-09-05 02:37:15.654111977 + @@ -12,7 +12,7 @@ _kafs_get_cred@Base 1.4.0+git20110226 _kafs_realm_of_cell@Base 1.4.0+git20110226 _kafs_resolve_debug@Base 1.4.0+git20110226 - _kafs_strlcpy@Base 1.4.0+git20110226 +#MISSING: 7.8.git20221117.28daf24+dfsg-3ubuntu1# _kafs_strlcpy@Base 1.4.0+git20110226 k_afs_cell_of_file@Base 1.4.0+git20110226 k_hasafs@Base 1.4.0+git20110226 k_hasafs_recheck@Base 1.4.0+git20110226 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:18: override_dh_makeshlibs] Error 25 This one might need a fix similar to the krb5 one[3]. 1. https://lists.ubuntu.com/archives/ubuntu-devel/2023-September/042784.html 2. https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html#ubuntu-server-team 3. https://launchpad.net/ubuntu/+source/krb5/1.20.1-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2036253/+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 2047780] Re: BlueZ release 5.71
Turns out it's not as simple as the above comments suggest.
> https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721
> https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3
udev changes are not relevant to the failures in
https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1 AFAICT
> https://salsa.debian.org/bluetooth-team/bluez/-/commit/f4d76255cdfa
Our dh doesn't seem to understand "${env:" in *.install, so using the
same approach as Debian doesn't seem to work. It always treats
"${env:..." as a literal path. And yes I did remember to export the
variable from debian/rules.
Just hard coding the service file paths to /usr would probably work for
Launchpad builds, but is not something I'm willing to do right now since
the path change hasn't graduated from proposed yet and I can't test it
locally. I'm only willing to upload changes I have tested locally so it
can wait till systemd has migrated... In the meantime, can anyone tell
me why "${env:..." isn't understood? Is it the compatibility level?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
Status in bluez package in Ubuntu:
Fix Committed
Bug description:
Release BlueZ 5.71 to noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2048192] Re: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré
janv. 05 08:36:19 machineubuntu sshd[5752]: /etc/ssh/sshd_config.d/port.conf: line 4: Bad configuration option: CleintAliveCountMax janv. 05 08:36:19 machineubuntu sshd[5752]: /etc/ssh/sshd_config.d/port.conf: terminating, 1 bad configuration options You have an invalid configuration option in your config file, because it is misspelled. You will need to correct this configuration to be able to start sshd. At which point 'sudo dpkg --configure -a' should resolve the package install issue. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2048192 Title: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in openssh package in Ubuntu: Invalid Bug description: seems I won't be able to upgrade the system to the next LTS untill this package is updated ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ssh 1:8.2p1-4ubuntu0.10 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: openssh-sftp-server:amd64: Install openssh-server:amd64: Install openssh-client:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 5 08:36:19 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2022-08-18 (504 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: openssh Title: package ssh 1:8.2p1-4ubuntu0.10 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2048192/+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
