[Bug 2072677] Re: MOTD CVE warning being shown on already-patched package versions when running apt upgrades
Can you please attach /var/log/ubuntu-advantage.log and the output of "sudo dmesg -T | grep ubuntu_pro"? Alternatively, run: apport-collect 2072677 and that will attach the relevant logs to this bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072677 Title: MOTD CVE warning being shown on already-patched package versions when running apt upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2072677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073007] [NEW] Should ignore loop devices
Public bug reported: Because of snaps, an Ubuntu system usually has a ton of loop devices in use: $ losetup NAMESIZELIMIT OFFSET AUTOCLEAR RO BACK-FILE DIO LOG-SEC /dev/loop1 0 0 1 1 /var/lib/snapd/snaps/git-ubuntu_1506.snap 0 512 /dev/loop29 0 0 1 1 /var/lib/snapd/snaps/snapcraft_12136.snap 0 512 /dev/loop19 0 0 1 1 /var/lib/snapd/snaps/gnome-42-2204_172.snap 0 512 /dev/loop37 0 0 1 1 /var/lib/snapd/snaps/ustriage_214.snap0 512 /dev/loop27 0 0 1 1 /var/lib/snapd/snaps/snap-store_1147.snap 0 512 /dev/loop17 0 0 1 1 /var/lib/snapd/snaps/kubectl_3280.snap0 512 /dev/loop8 0 0 1 1 /var/lib/snapd/snaps/core22_1380.snap 0 512 /dev/loop35 0 0 1 1 /var/lib/snapd/snaps/testflinger-cli_179.snap 0 512 /dev/loop25 0 0 1 1 /var/lib/snapd/snaps/lxd_28463.snap 0 512 /dev/loop15 0 0 1 1 /var/lib/snapd/snaps/firmware-updater_121.snap0 512 /dev/loop6 0 0 1 1 /var/lib/snapd/snaps/core20_2318.snap 0 512 /dev/loop33 0 0 1 1 /var/lib/snapd/snaps/snapd-desktop-integration_83.snap0 512 /dev/loop23 0 0 1 1 /var/lib/snapd/snaps/kubectl_3281.snap0 512 /dev/loop13 0 0 1 1 /var/lib/snapd/snaps/firefox_4483.snap0 512 /dev/loop4 0 0 1 1 /var/lib/snapd/snaps/core18_2829.snap 0 512 /dev/loop31 0 0 1 1 /var/lib/snapd/snaps/snapd_21759.snap 0 512 /dev/loop21 0 0 1 1 /var/lib/snapd/snaps/gtk-common-themes_1535.snap 0 512 /dev/loop11 0 0 1 1 /var/lib/snapd/snaps/cups_1058.snap 0 512 /dev/loop2 0 0 1 1 /var/lib/snapd/snaps/chromium_2878.snap 0 512 /dev/loop38 0 0 1 1 /var/lib/snapd/snaps/chromium_2898.snap 0 512 /dev/loop0 0 0 1 1 /var/lib/snapd/snaps/bare_5.snap 0 512 /dev/loop28 0 0 1 1 /var/lib/snapd/snaps/snapcraft_12024.snap 0 512 /dev/loop18 0 0 1 1 /var/lib/snapd/snaps/git-ubuntu_1505.snap 0 512 /dev/loop9 0 0 1 1 /var/lib/snapd/snaps/core24_423.snap 0 512 /dev/loop36 0 0 1 1 /var/lib/snapd/snaps/ustriage_209.snap0 512 /dev/loop26 0 0 1 1 /var/lib/snapd/snaps/snap-store_1134.snap 0 512 /dev/loop16 0 0 1 1 /var/lib/snapd/snaps/firmware-updater_127.snap0 512 /dev/loop7 0 0 1 1 /var/lib/snapd/snaps/core22_1122.snap 0 512 /dev/loop34 0 0 1 1 /var/lib/snapd/snaps/testflinger-cli_178.snap 0 512 /dev/loop24 0 0 1 1 /var/lib/snapd/snaps/lxd_28322.snap 0 512 /dev/loop14 0 0 1 1 /var/lib/snapd/snaps/firefox_4539.snap0 512 /dev/loop5 0 0 1 1 /var/lib/snapd/snaps/core20_2264.snap 0 512 /dev/loop32 0 0 1 1 /var/lib/snapd/snaps/snapd-desktop-integration_157.snap 0 512 /dev/loop12 0 0 1 1 /var/lib/snapd/snaps/distrobuilder_1833.snap 0 512 /dev/loop40 0 0 1 1 /var/lib/snapd/snaps/gnome-46-2404_26.snap0 512 /dev/loop3 0 0 1 1 /var/lib/snapd/snaps/core18_2823.snap 0 512 /dev/loop30 0 0 1 1 /var/lib/snapd/snaps/snapd_21465.snap 0 512 /dev/loop20 0 0 1 1 /var/lib/snapd/snaps/gnome-42-2204_176.snap 0 512 /dev/loop10 0 0 1 1 /var/lib/snapd/snaps/cups_1052.snap 0 512 /dev/loop39 0 0 1 1 /var/lib/snapd/snaps/mesa-2404_44.snap0 512 When running tuned on such a system, there is a lot of noise in the logs about loop devices not supporting hdparm: 2024-07-12 17:38:51,438 INFO tuned.plugins.plugin_disk: Device 'nvme0n1' not supported by hdparm 2024-07-12 17:38:51,440 INFO tuned.plugins.plugin_disk: Device 'loop0' not supported by hdparm 2024-07-12
[Bug 2043281] Re: Update tuned package in Ubuntu 22.04 LTS
I wouldn't say it's a crash, it's just a conflict between services. If you install power-profiles-daemon and start it, and tuned is also installed and started, tuned will be stopped. If you start tuned, then power-profiles-daemon will be stopped. Can you elaborate a bit on the Ubuntu 22.04 scenario that is causing unexpected behavior? Maybe I missed something. ** Changed in: tuned (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043281 Title: Update tuned package in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2043281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072996] Re: Noisy and ugly postinst
** Changed in: tuned (Ubuntu Noble) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: tuned (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072996 Title: Noisy and ugly postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2072996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
What dependency could I add to src:tuned that would pull in the correct linux-tools-* package that has the python3 perf module? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613393] Re: Provide linux-perf package
Does the python perf module really need to depend on the exact running kernel? This makes it difficult to install in a container, because the OS of the container might not have the linux-tools- package matching the host kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613393 Title: Provide linux-perf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1613393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051290] Re: scheduler and irqbalance plugins do not work
This is fixed in noble with linux-tools-6.8.0-38: root@n-tuned:~# dpkg -S /usr/lib/python3/dist-packages/linux-tools-6.8.0-38/perf.cpython-312-x86_64-linux-gnu.so linux-tools-6.8.0-38: /usr/lib/python3/dist-packages/linux-tools-6.8.0-38/perf.cpython-312-x86_64-linux-gnu.so root@n-tuned:~# python3 -c "import perf" root@n-tuned:~# ** Also affects: tuned (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: tuned (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: tuned (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051290 Title: scheduler and irqbalance plugins do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051290] Re: scheduler and irqbalance plugins do not work
Oracular has the fix in the proposed kernel at the moment, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/comments/22 ** Changed in: tuned (Ubuntu Oracular) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051290 Title: scheduler and irqbalance plugins do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2051290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072996] [NEW] Noisy and ugly postinst
Public bug reported:
In noble, installing tuned-2.21.0-1ubuntu2 produces this ugly output:
Unpacking tuned (2.21.0-1ubuntu2) ...
Setting up tuned (2.21.0-1ubuntu2) ...
/usr/lib/python3/dist-packages/tuned/plugins/plugin_bootloader.py:376:
SyntaxWarning: invalid escape sequence '\s'
self._cmd.add_modify_option_in_file(f, {"set\s+" + consts.GRUB2_TUNED_VAR :
"", "set\s+" + consts.GRUB2_TUNED_INITRD_VAR : ""}, add = False)
/usr/lib/python3/dist-packages/tuned/plugins/plugin_bootloader.py:376:
SyntaxWarning: invalid escape sequence '\s'
self._cmd.add_modify_option_in_file(f, {"set\s+" + consts.GRUB2_TUNED_VAR :
"", "set\s+" + consts.GRUB2_TUNED_INITRD_VAR : ""}, add = False)
/usr/lib/python3/dist-packages/tuned/plugins/plugin_bootloader.py:406:
SyntaxWarning: invalid escape sequence '\s'
cfg = re.sub(r"^\s*set\s+" + consts.GRUB2_TUNED_VAR + "\s*=.*\n", "",
grub2_cfg, flags = re.MULTILINE)
/usr/lib/python3/dist-packages/tuned/plugins/plugin_bootloader.py:408:
SyntaxWarning: invalid escape sequence '\s'
cfg = re.sub(r"^\s*set\s+" + consts.GRUB2_TUNED_INITRD_VAR + "\s*=.*\n", "",
grub2_cfg, flags = re.MULTILINE)
/usr/lib/python3/dist-packages/tuned/plugins/plugin_bootloader.py:483:
SyntaxWarning: invalid escape sequence '\s'
(grub2_cfg_new, nsubs) = re.subn(r"\b(set\s+" + opt + "\s*=).*$", r"\1" +
"\"" + self._cmd.escape(d[opt]) + "\"", grub2_cfg_new, flags = re.MULTILINE)
/usr/lib/python3/dist-packages/tuned/plugins/plugin_net.py:352: SyntaxWarning:
invalid escape sequence '\s'
"\s+TX:": "\nadaptive-tx:",
/usr/lib/python3/dist-packages/tuned/plugins/plugin_net.py:371: SyntaxWarning:
invalid escape sequence '\['
vl = [v for v in value.split('\n') if len(str(v)) > 0 and not
re.search("\[fixed\]$", str(v))]
/usr/lib/python3/dist-packages/tuned/plugins/plugin_scheduler.py:138:
SyntaxWarning: invalid escape sequence '\;'
"""
/usr/lib/python3/dist-packages/tuned/profiles/functions/functions.py:49:
SyntaxWarning: invalid escape sequence '\:'
sl = [str(v).replace("\:", ":") for v in sl]
/usr/lib/python3/dist-packages/tuned/utils/commands.py:32: SyntaxWarning:
invalid escape sequence '\s'
return re.sub('\s+', ' ', str(s)).strip()
/usr/lib/python3/dist-packages/tuned/utils/commands.py:438: SyntaxWarning:
invalid escape sequence '\,'
return [str(v).replace("\,", ",") for v in l]
/usr/lib/python3/dist-packages/tuned/utils/config_parser.py:28: SyntaxWarning:
invalid escape sequence '\s'
r'(?P[^' + delims + '\s][^' + delims + ']*)'
/usr/lib/python3/dist-packages/tuned/utils/config_parser.py:29: SyntaxWarning:
invalid escape sequence '\s'
r'\s*(?P[' + delims + '])\s*'
/usr/lib/python3/dist-packages/tuned/utils/config_parser.py:33: SyntaxWarning:
invalid escape sequence '\s'
r'(?P[^' + delims + '\s][^' + delims + ']*)'
/usr/lib/python3/dist-packages/tuned/utils/config_parser.py:35: SyntaxWarning:
invalid escape sequence '\s'
r'(?P[' + delims + '])\s*'
/usr/lib/python3/dist-packages/tuned/utils/config_parser.py:40: SyntaxWarning:
invalid escape sequence '\s'
self._re = re.compile("\s+(%s).*" %
")|(".join(list(self._inline_comment_prefixes)))
/usr/lib/python3/dist-packages/tuned/utils/nettool.py:119: SyntaxWarning:
invalid escape sequence '\s'
p_filter = Popen(["sed", "s/^\s*//;s/:\s*/:\\n/g"], \
Created symlink /etc/systemd/system/multi-user.target.wants/tuned.service →
/usr/lib/systemd/system/tuned.service.
Processing triggers for dbus (1.14.10-4ubuntu4) ...
Processing triggers for man-db (2.12.0-4build2) ...
This is fixed in oracular.
** Affects: tuned (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: tuned (Ubuntu Noble)
Importance: Undecided
Status: New
** Affects: tuned (Ubuntu Oracular)
Importance: Undecided
Status: Fix Released
** Also affects: tuned (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: tuned (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: tuned (Ubuntu Oracular)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072996
Title:
Noisy and ugly postinst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tuned/+bug/2072996/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
I can see this is available in oracular-proposed's kernel and linux- tools package: ubuntu@o-dep8:~$ uname -r 6.10.0-15-generic ubuntu@o-dep8:~$ apt-cache policy linux-tools-$(uname -r) linux-tools-6.10.0-15-generic: Installed: 6.10.0-15.15 Candidate: 6.10.0-15.15 Version table: *** 6.10.0-15.15 100 100 http://br.archive.ubuntu.com/ubuntu oracular-proposed/main amd64 Packages 100 /var/lib/dpkg/status ubuntu@o-dep8:~$ python3 -c "import perf; [print(c) for c in perf.cpu_map()]" 0 (the python module can be imported and run some trivial code) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051560] Re: Provide python perf module
** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051560 Title: Provide python perf module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999814] Re: [SRU] Allow for specifying common baseline CPU model with disabled feature
Hello Paul, or anyone else affected, Accepted nova into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nova/3:25.2.1-0ubuntu2.4 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: nova (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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999814 Title: [SRU] Allow for specifying common baseline CPU model with disabled feature To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1999814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067632] Re: No logo in Horizon - 404 logo-canonical-openstack-splash.svg
Hello Nobuto, or anyone else affected, Accepted horizon into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/horizon/4:24.0.0-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: horizon (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067632 Title: No logo in Horizon - 404 logo-canonical-openstack-splash.svg To manage notifications about this bug go to: https://bugs.launchpad.net/snap-openstack/+bug/2067632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071939] Please test proposed package
Hello Alex, or anyone else affected, Accepted ceilometer into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ceilometer/2:22.0.0-0ubuntu1.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071939 Title: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2071939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071939] Re: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service
Can we also do a diff of the package listing with this patch, to be sure we are not including unwanted files all of a sudden? ** Changed in: ceilometer (Ubuntu Noble) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071939 Title: [caraca|2024.1] the 22.0 version of python3-ceilometer is missing files thus breaking the notification service To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2071939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy and noble
The jammy upload has this changelog in its changes file: cloud-init (24.2-0ubuntu1~22.04.1) jammy; urgency=medium . * d/apport-general-hook.py: Move apport hook to main branch * d/cloud-init.maintscript: remove /etc/cloud/clean.d/README * d/cloud-init.logrotate: add logrotate config for cloud-init * d/cloud-init.postinst: change priority of hotplug rules. Avoids LP #1946003 on upgraded systems. References: [0] https://github.com/canonical/cloud-init/pull/4799 [1] commit/b519d861aff8b44a0610c176cb34adcbe28df144 * d/cloud-init.templates: enable WSL datasource by default * d/control: remove netifaces * d/p/deprecation-version-boundary.patch: Pin deprecation version to 22.1 * drop d/p/do-not-block-user-login.patch: upstream 4981ea9 now orders cloud-init.service Before=systemd-user-sessions.service * refresh patches: - d/p/cli-retain-file-argument-as-main-cmd-arg.patch - d/p/keep-dhclient-as-priority-client.patch - d/p/status-do-not-remove-duplicated-data.patch - d/p/status-retain-recoverable-error-exit-code.patch - d/p/revert-551f560d-cloud-config-after-snap-seeding.patch - d/p/retain-ec2-default-net-update-events.patch - d/p/retain-old-groups.patch * Upstream snapshot based on 24.2. (LP: #2071762). List of changes from upstream can be found at https://raw.githubusercontent.com/canonical/cloud-init/24.2/ChangeLog . cloud-init (24.1.3-0ubuntu1~22.04.6) jammy; urgency=medium . * d/p/chad: cherry-pick snap refresh a) Changes listed in d/changelog but not found in the actual diff/package (i.e., no diff at all on those files when compared to the previous published cloud-init package): * d/apport-general-hook.py: Move apport hook to main branch * d/cloud-init.maintscript: remove /etc/cloud/clean.d/README * d/cloud-init.logrotate: add logrotate config for cloud-init * d/cloud-init.postinst: change priority of hotplug rules. * d/cloud-init.templates: enable WSL datasource by default * d/cloud-init.templates: enable WSL datasource by default Had a chat with James Falcon about these, and other issues we talked about, and they will upload again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071762 Title: sru cloud-init (24.2 update) to focal, jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2071762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064751] Re: [SRU] revert security-regression in Focal's libcrypto++
I spent a long time trying to understand what happened with this CVE. - upstream's first attempt at a fix, which misses fixing "leak on binary fields (EC2N class)": https://github.com/weidai11/cryptopp/issues/869 - it also introduced a regression, so besides an incomplete fix, it introduces a bug - three regressions were filed upstream: - https://github.com/weidai11/cryptopp/issues/994 - https://github.com/weidai11/cryptopp/issues/1269 (this last one specifically about the library on ubuntu) - https://github.com/weidai11/cryptopp/issues/878 - we also have 3 launchpad bugs about this: #2064751 (this one), #2060564, and #1893934. Shouldn't all of these be mentioned in the changelog? Then it gets confusing. I'm finding multiple references across all these bugs about either a revert, or a partial revert, or a revert plus a fix elsewhere (specially when they mention version 8.3.0). In https://github.com/weidai11/cryptopp/issues/878#issuecomment-753375057, there is a commit range: https://github.com/weidai11/cryptopp/compare/38cff9aa59f299f7d1e802e614edc205ee2965fb...5dfc7e1c27d2d3225257f1458f0a5b3e623d08e7 Is that the same as reverting the original CVE fix? Is there any option to actually fixing the CVE in 5.6.4? The proposal here is plainly reverting the patch added in 5.6.4-9, which will reintroduce the CVE, correct? ** Bug watch added: github.com/weidai11/cryptopp/issues #869 https://github.com/weidai11/cryptopp/issues/869 ** Bug watch added: github.com/weidai11/cryptopp/issues #994 https://github.com/weidai11/cryptopp/issues/994 ** Bug watch added: github.com/weidai11/cryptopp/issues #1269 https://github.com/weidai11/cryptopp/issues/1269 ** Bug watch added: github.com/weidai11/cryptopp/issues #878 https://github.com/weidai11/cryptopp/issues/878 ** Changed in: libcrypto++ (Ubuntu Focal) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064751 Title: [SRU] revert security-regression in Focal's libcrypto++ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcrypto++/+bug/2064751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024019] Re: Add GCC atomic support (-moutline-atomics) for arm64 on Focal
nginx is full of autopkgtest errors in the excuses report[1]. For some reason they were not reported here, perhaps they happened during one of the past outages we had. They also all have a reported version number of "unknown", which usually indicates an infrastructure problem. I retriggered them all. 1. https://ubuntu-archive-team.ubuntu.com/proposed-migration/focal/update_excuses.html#nginx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024019 Title: Add GCC atomic support (-moutline-atomics) for arm64 on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/2024019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067745] Update Released
The verification of the Stable Release Update for openldap has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067745 Title: New upstream microrelease 2.5.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2067745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071785] Re: OpenLDAP (slapd) is broken in Ubuntu 22.04 after upgrade to version 2.5.17+dfsg-0ubuntu0.22.04.1
This was fixed in https://launchpad.net/ubuntu/+source/openldap/2.5.18+dfsg-0ubuntu0.22.04.1 which I just released into updates. Marking as "fix released" for jammy. ** Changed in: openldap (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071785 Title: OpenLDAP (slapd) is broken in Ubuntu 22.04 after upgrade to version 2.5.17+dfsg-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2071785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062394] Update Released
The verification of the Stable Release Update for xdg-desktop-portal has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062394 Title: Update xdg-desktop-portal to 1.18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2062394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061955] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061955 Title: Add support for Arrow Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068918] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068918 Title: New bugfix release 24.0.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2068918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072702] Re: AppArmor profile prevents use of TLS keys and certificates
Note also the README.apparmor[1] explanation. Packages can also install apparmor profile snippets in /etc/apparmor.d/rsyslog.d. If the default of the freeipa package (or whatever produced /etc/ipa/ca.crt) is to place certificate and keys in /etc/ipa, maybe it could ship such a profile snippet. 1. https://git.launchpad.net/ubuntu/+source/rsyslog/tree/debian/README.apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072702 Title: AppArmor profile prevents use of TLS keys and certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2072702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
Adding a task for gdm3, since it seems affected by dropping user_readenv=1 from its pam configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
Regarding the LC_* variables in openssh's config, I understand it's not a direct replacement for ~/.pam_environment, because that is on the *server*, and we would be sending the *client* vars. ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
> Is it just the "user_readenv=1" that needs dropped or would the entire line need to drop? Just user_readenv=1 needs to go. Bug LP: #952185 stated that ~/.pam_environment should be read, and the example they gave was locale settings. It's as if back then, the per- user locale variables were set via ~/.pam_environment, or so I understood. For openssh, the fix back then was two-fold: a) move pam_env to the end(ish) of session stack, so that if encrypted home directories were used, by then the home directory would be unlocked already. It's now just before pam_selinux, which is the last one, and way after @common-session, which is where the unlocking of the encrypted home directory would occur. b) add user_readenv=1, which was missing I just checked in noble, and logging in as a non-admin user, switched my language settings to english UK. Logged out, then back in, and indeed, something created ~/.pam_environment. Which tells me other parts of the system STILL, in 2024, expect that file to be read. Specifically, something in the desktop (gnome/mutter). For ssh, that might be irrelevant because at least nowadays we have this setting in the sshd_config: # Allow client to pass locale environment variables AcceptEnv LANG LC_* And this on the ssh_config (client) one: Host * (...) SendEnv LANG LC_* But even if we can drop user_readenv=1 from sshd's config (and I think we can), the same cannot be said for other login components of the system. A quick grep on my mantic desktop shows that gdm is the other big app that relies on user_readenv=1. And indeed, logging in on mantic, I get this deprecation warning in the logs from gdm's usage of pam_env: 2024-07-10T10:54:54.270057-03:00 nsnx2 gdm-launch-environment]: pam_env(gdm-launch-environment:session): deprecated reading of user environment enabled ... 2024-07-10T10:55:05.512619-03:00 nsnx2 gdm-password]: pam_env(gdm-password:session): deprecated reading of user environment enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072654] [NEW] RED ERROR bluetoothd[863]: profiles/sap/server.c:sap_server_register() Sap driver initialization f
Public bug reported: Apparently SAP stands for SIM Access Profile, to disable it I tried adding --noplugin=sap to the end of theExecStart=/usr/lib/bluetooth/bluetoothd line in/usr/lib/systemd/system/bluetooth.service. That didn't solve it. adding --noplugin=sap to the end of the ExecStart=/usr/lib/bluetooth/bluetoothd line in /etc/systemd/system/bluetooth.target.wants/bluetooth.service did clear the error. sudo nano /etc/systemd/system/bluetooth.target.wants/bluetooth.service ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap CTL-XY Enterreboot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Jul 10 08:51:58 2024 InstallationDate: Installed on 2024-07-08 (2 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 90FB0001US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=d770e3ae-826c-4dd3-a83f-1f904368d61c ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.release: 1.158 dmi.bios.vendor: LENOVO dmi.bios.version: FWKT9EA dmi.board.name: 3642 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258058241053 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Default string dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrFWKT9EA:bd04/22/2019:br1.158:efr1.21:svnLENOVO:pn90FB0001US:pvrideacentre710-25ISH:rvnLENOVO:rn3642:rvrSDK0J40700WIN3258058241053:cvnLENOVO:ct3:cvrDefaultstring:skuLENOVO_MT_90FB_BU_LENOVO_FM_ideacentre710-25ISH: dmi.product.family: ideacentre 710-25ISH dmi.product.name: 90FB0001US dmi.product.sku: LENOVO_MT_90FB_BU_LENOVO_FM_ideacentre 710-25ISH dmi.product.version: ideacentre 710-25ISH dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:66:C2:EE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:836 acl:0 sco:0 events:68 errors:0 TX bytes:5396 acl:0 sco:0 commands:68 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072654 Title: RED ERROR bluetoothd[863]: profiles/sap/server.c:sap_server_register() Sap driver initialization f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2072654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072651] [NEW] RED ERROR profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
Public bug reported: journalctl -p 3 -xb Jul 09 16:26:27 idea-90fb0001us kernel: Jul 09 16:26:27 idea-90fb0001us bluetoothd[910]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Jul 09 16:26:27 idea-90fb0001us bluetoothd[910]: sap-server: Operation not permitted (1) sudo hciconfig hci0 up Can't init device hci0: Operation not possible due to RF-kill (132) I believe there is a bluetoothd flag to disable SAP, I am going to try adding this flag to the ExecStart= line in bluetooth.service: sudo nano /usr/lib/systemd/system/bluetooth.service change line ExecStart=/usr/libexec/bluetooth/bluetoothd to ExecStart=/usr/libexec/bluetooth/bluetoothd --noplugin=sap CTL x Y to save ENTER reboot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Wed Jul 10 08:24:51 2024 InstallationDate: Installed on 2024-07-08 (2 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 90FB0001US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=d770e3ae-826c-4dd3-a83f-1f904368d61c ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.release: 1.158 dmi.bios.vendor: LENOVO dmi.bios.version: FWKT9EA dmi.board.name: 3642 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258058241053 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Default string dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrFWKT9EA:bd04/22/2019:br1.158:efr1.21:svnLENOVO:pn90FB0001US:pvrideacentre710-25ISH:rvnLENOVO:rn3642:rvrSDK0J40700WIN3258058241053:cvnLENOVO:ct3:cvrDefaultstring:skuLENOVO_MT_90FB_BU_LENOVO_FM_ideacentre710-25ISH: dmi.product.family: ideacentre 710-25ISH dmi.product.name: 90FB0001US dmi.product.sku: LENOVO_MT_90FB_BU_LENOVO_FM_ideacentre 710-25ISH dmi.product.version: ideacentre 710-25ISH dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:66:C2:EE ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:842 acl:0 sco:0 events:69 errors:0 TX bytes:5399 acl:0 sco:0 commands:69 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072651 Title: RED ERROR profiles/sap/server.c:sap_server_register() Sap driver initialization failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2072651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072605] [NEW] Red error bluetoothd[910]: profiles/sap/server.c:sap_server_register() Sap drive>
Public bug reported: boot error bluetoothd[910]: profiles/sap/server.c:sap_server_register() Sap drive> bluetoothd[910]: sap-server: Operation not permitted (1) Jul 09 16:26:27 idea-90fb0001us bluetoothd[910]: Failed to load LTKs for hci0: Invalid Parameters (0x0> Jul 09 16:26:27 idea-90fb0001us bluetoothd[910]: Failed to load IRKs for hci0: Invalid Parameters (0x0 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Jul 9 18:59:11 2024 InstallationDate: Installed on 2024-07-08 (1 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 90FB0001US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=d770e3ae-826c-4dd3-a83f-1f904368d61c ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.release: 1.158 dmi.bios.vendor: LENOVO dmi.bios.version: FWKT9EA dmi.board.name: 3642 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258058241053 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Default string dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrFWKT9EA:bd04/22/2019:br1.158:efr1.21:svnLENOVO:pn90FB0001US:pvrideacentre710-25ISH:rvnLENOVO:rn3642:rvrSDK0J40700WIN3258058241053:cvnLENOVO:ct3:cvrDefaultstring:skuLENOVO_MT_90FB_BU_LENOVO_FM_ideacentre710-25ISH: dmi.product.family: ideacentre 710-25ISH dmi.product.name: 90FB0001US dmi.product.sku: LENOVO_MT_90FB_BU_LENOVO_FM_ideacentre 710-25ISH dmi.product.version: ideacentre 710-25ISH dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: E4:A7:A0:66:C2:EE ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:842 acl:0 sco:0 events:69 errors:0 TX bytes:5399 acl:0 sco:0 commands:69 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072605 Title: Red error bluetoothd[910]: profiles/sap/server.c:sap_server_register() Sap drive> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2072605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072607] [NEW] red error colrd-sane
Public bug reported: colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied Jul 09 16:26:29 idea-90fb0001us colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied Jul 09 16:26:29 idea-90fb0001us colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied Jul 09 16:26:29 idea-90fb0001us colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied Jul 09 16:26:32 idea-90fb0001us hpfax[1401]: [1401]: error: Failed to create /var/spool/cups/tmp/.hplip ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: sane (not installed) ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Jul 9 19:01:38 2024 InstallationDate: Installed on 2024-07-08 (1 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-frontends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072607 Title: red error colrd-sane To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-frontends/+bug/2072607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072604] [NEW] Red error colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied
Public bug reported: the output ofsystemctl status colord colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static) Active: active (running) since Tue 2024-07-09 13:47:43 CDT; 1h 6min ago Main PID: 1059 (colord) Tasks: 4 (limit: 9370) Memory: 26.9M (peak: 33.2M) CPU: 579ms CGroup: /system.slice/colord.service └─1059 /usr/libexec/colord Jul 09 13:47:43 idea-90fb0001us systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles... Jul 09 13:47:43 idea-90fb0001us colord[1059]: failed to get edid data: EDID length is too small nvidia-470 graphics ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: colord 1.4.7-1build2 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Jul 9 18:53:40 2024 InstallationDate: Installed on 2024-07-08 (1 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) SourcePackage: colord UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072604 Title: Red error colord-sane[1076]: io/hpmud/musb.c 2102: Invalid usb_open: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2072604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072600] [NEW] nvidia-470 driver black screen on boot
Public bug reported: lubuntu 24.04.1 install to get working nvidia driver: 1) install lubuntu 2) sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa 3) sudo apt update 4) sudo ubuntu-drivers autoinstall ---installed nvidia-470 driver three times i got black screen on reboot- 5)sudo nano /etc/default/grubremove "quiet splash" but leave the "" 6) sudo update-grub 7) rebooted into nvidia graphics nvidia-smi all good ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.256.02 Thu May 2 14:37:44 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Tue Jul 9 17:46:56 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. GK208B [GeForce GT 730] [1642:3e56] InstallationDate: Installed on 2024-07-08 (1 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) MachineType: LENOVO 90FB0001US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=d770e3ae-826c-4dd3-a83f-1f904368d61c ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.release: 1.158 dmi.bios.vendor: LENOVO dmi.bios.version: FWKT9EA dmi.board.name: 3642 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258058241053 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Default string dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrFWKT9EA:bd04/22/2019:br1.158:efr1.21:svnLENOVO:pn90FB0001US:pvrideacentre710-25ISH:rvnLENOVO:rn3642:rvrSDK0J40700WIN3258058241053:cvnLENOVO:ct3:cvrDefaultstring:skuLENOVO_MT_90FB_BU_LENOVO_FM_ideacentre710-25ISH: dmi.product.family: ideacentre 710-25ISH dmi.product.name: 90FB0001US dmi.product.sku: LENOVO_MT_90FB_BU_LENOVO_FM_ideacentre 710-25ISH dmi.product.version: ideacentre 710-25ISH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072600 Title: nvidia-470 driver black screen on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2072600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
The discussion is continuing in the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
The heimdal changes are merged in debian now, just not yet in a package upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072504] [NEW] Merge samba 4.20.2+dfsg-6 or later
Public bug reported: Another merge from Debian for Oracular. At the moment, we have 4.20.2+dfsg-6 available. ** Affects: samba (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: Triaged ** Tags: needs-merge ** Changed in: samba (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072504 Title: Merge samba 4.20.2+dfsg-6 or later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2072504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072489] Re: AppArmor denied errors for ubuntu_pro_apt_news profile
Filed upstream issue: https://github.com/canonical/ubuntu-pro- client/issues/3193 ** Bug watch added: github.com/canonical/ubuntu-pro-client/issues #3193 https://github.com/canonical/ubuntu-pro-client/issues/3193 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072489 Title: AppArmor denied errors for ubuntu_pro_apt_news profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2072489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072489] Re: AppArmor denied errors for ubuntu_pro_apt_news profile
Thanks for this report, I just saw that too. Unsure what changed, because we didn't see these "before", but we can address this. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072489 Title: AppArmor denied errors for ubuntu_pro_apt_news profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2072489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
That PR was accepted and merged. For some reason, in salsa CI the new test failed, and I proposed https://salsa.debian.org/debian/heimdal/-/merge_requests/4 to fix that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Test packages for noble and oracular uploaded to https://launchpad.net/~ahasenack/+archive/ubuntu/plusone/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677863] Re: Missing dep8 tests
** Changed in: heimdal (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: heimdal (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677863 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1677863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
PR proposed in salsa for debian heimdal: https://salsa.debian.org/debian/heimdal/-/merge_requests/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2048232] Re: [SRU] Backport to 22.04 LTS
> * To leverage the functionality of the package, a recent enough ADSys > version must be used (at least >0.11.0, not currently in Jammy but there are approved plans to backport > ADSys 0.13.2). Jammy-updates currently has 0.9.2~22.04.2, and jammy-proposed has 0.14.1~22.04. Given the above, I understand that ubuntu-proxy-manager cannot be released yet, correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2048232 Title: [SRU] Backport to 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-proxy-manager/+bug/2048232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043098] Update Released
The verification of the Stable Release Update for mstflint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043098 Title: mstflint-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2043098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] Update Released
The verification of the Stable Release Update for mstflint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061182 Title: mstflint-dkms no longer exists in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061185] Update Released
The verification of the Stable Release Update for mstflint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061185 Title: mstflint-dkms module bug causes UBSAN errors in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061186] Update Released
The verification of the Stable Release Update for mstflint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061186 Title: mstflint_access kernel module licensing is inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.2
> boto3 is only main in noble and oracular and in universe for the others. > Hence we thought it didn't make > sense to have it in f,j and m and to depend or recommend from the universe > pocket You are correct, I mistakenly checked python3-boto, not python3-boto3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] Re: mstflint-dkms no longer exists in mantic
I repeated these tests with the mstflint-dkms package from mantic-proposed (4.26.0+1-1ubuntu0.1): - mstflint-dkms installs in mantic and builds against the mantic kernel. - mstflint-dkms/mantic upgrades cleanly from jammy. - mstflint-dkms/mantic upgrades cleanly to noble. The module built and loaded in all cases, and the upgrades also happened without issues. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061182 Title: mstflint-dkms no longer exists in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
The package built in jammy-proposed, therefore marking verification done. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949314] Update Released
The verification of the Stable Release Update for intel-gpu-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Re: Upstream microrelease of squid 5.9
Marking devel release task as invalid, since this is a jammy only MRE. ** Changed in: squid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040470] Update Released
The verification of the Stable Release Update for squid has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040470 Title: Upstream microrelease of squid 5.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/2040470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058286] Update Released
The verification of the Stable Release Update for octavia has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058286 Title: Requesting SRU for Octavia 10.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2058286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Please test proposed package
Hello Arif, or anyone else affected, Accepted sosreport into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/4.7.2-0ubuntu1~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. ** Changed in: sosreport (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Please test proposed package
Hello Arif, or anyone else affected, Accepted sosreport into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/4.7.2-0ubuntu1~20.04.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- 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Please test proposed package
Hello Arif, or anyone else affected, Accepted sosreport into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/4.7.2-0ubuntu1~22.04.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- 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: sosreport (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Please test proposed package
Hello Arif, or anyone else affected, Accepted sosreport into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sosreport/4.7.2-0ubuntu1~24.04.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- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. 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: sosreport (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.2
I noted that only noble has the python3-boto recommends, but since this is a new upstream version being updated in all ubuntu releases, it would make sense that the boto requirement would apply similarly everywhere else. I won't block on accepting it, but if you believe the "Recommends: python3-boto" was missed in mantic and earlier, a new upload on top of this one can still be made, with the change, and the -v option set correctly for the changes file. ** Changed in: sosreport (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055718] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055718 Title: timezone changed unexpectedly from EST to America/Adak or America/Indiana/Indianapolis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2055718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024377] Re: Adsys can't fetch GPOs
Hello Juarez, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024377 Title: Adsys can't fetch GPOs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2024377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049061] Re: adsysctl update with a domain user fails if KRB5CCNAME is not set
Hello Fabio, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049061 Title: adsysctl update with a domain user fails if KRB5CCNAME is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2049061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2044112] Re: Add dependency on nfs-common
Hello Gabriel, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2044112 Title: Add dependency on nfs-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2044112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051363] Re: Cannot perform certificate auto-enroll without NDES installed
Hello Gabriel, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051363 Title: Cannot perform certificate auto-enroll without NDES installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2051363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054445] Re: Regresion in sssd backend configuration
Hello Gabriel, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Changed in: adsys (Ubuntu Mantic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054445 Title: Regresion in sssd backend configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2054445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
Hello Jean-Baptiste, or anyone else affected, Accepted adsys into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.14.1~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. ** Tags removed: verification-done verification-done-mantic ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059756] Re: [SRU] adsys 0.14.1
adsys is failing all autopkgtests on mantic in all architectures. The error is the same: 106s autopkgtest [12:17:38]: test command1: ./debian/tests/test no-sudo 106s autopkgtest [12:17:38]: test command1: [--- 106s Running non-root tests... 106s ./debian/tests/test: 36: go: not found 106s autopkgtest [12:17:38]: test command1: ---] Comment #19 states that adsys vesion 0.14.1~23.10.1 was uploaded to mantic-unapproved with a fix for that, and I see it wasn't accepted still. I'll try to get to it in my shift. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059756 Title: [SRU] adsys 0.14.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2059756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066908] Update Released
The verification of the Stable Release Update for ovn has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066908 Title: [SRU] ovn 24.03.2 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2066908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061329] Update Released
The verification of the Stable Release Update for displaycal-py3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061329 Title: [SRU] displaycal 3.9.11-2 needs patch to work with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/displaycal-py3/+bug/2061329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060666] Re: [SRU] Memory leak in krb5 version 1.17
Hello Ponnuvel, or anyone else affected, Accepted krb5 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/krb5/1.17-6ubuntu4.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- 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: krb5 (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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060666 Title: [SRU] Memory leak in krb5 version 1.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
I have a heimdal branch with the upstream patch for includedir support, plus a new autopkgtest that exercises it and verifies the inclusion is happening. Code is here: https://code.launchpad.net/~ahasenack/ubuntu/+source/heimdal/+git/heimdal/+ref/oracular- heimdal-add-include-support-2037321 I'll tidy it up a bit and proposed to debian. I found a couple of extra commits in the heimdal github repository that fixup some things in the includedir support that I want to analyze and possibly include. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064384] Re: Merge samba from Debian unstable for oracular
Uploaded ** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/468093 ** Changed in: samba (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064384 Title: Merge samba from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/2064384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064434] Re: Merge openldap from Debian unstable for oracular
In oracular-proposed already: https://launchpad.net/ubuntu/+source/openldap/2.6.8+dfsg-1~exp3ubuntu1 ** Changed in: openldap (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064434 Title: Merge openldap from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2064434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2037321] Re: missing includedir snippet in krb5.conf causes GSSAPI to fail
** Bug watch added: Debian Bug tracker #1074775 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074775 ** Also affects: heimdal (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074775 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037321 Title: missing includedir snippet in krb5.conf causes GSSAPI to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2037321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064393] Re: Merge chrony from Debian unstable for oracular
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/chrony/+git/chrony/+merge/468629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064393 Title: Merge chrony from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2064393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/chrony/+git/chrony/+merge/468629 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064393] Re: Merge chrony from Debian unstable for oracular
** Merge proposal linked: https://code.launchpad.net/~git-ubuntu-import/ubuntu/+source/chrony/+git/chrony/+merge/468625 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064393 Title: Merge chrony from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2064393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Description changed:
[ Impact ]
- * An explanation of the effects of the bug on users and
+ The chronyd apparmor profile was changed as a fix for bug #2032805 to
+ allow chronyd to read/write a linuxptp timemaster socket:
- * justification for backporting the fix to the stable release.
+ @{run}/timemaster/chrony.SOCK0 rw,
- * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ That works, but is limiting, as it allows only one PTP clock/interface
+ to be used. If another one is setup, the other socket will be blocked by
+ apparmor, because its name will be "chrony.SOCK1", and so on.
+
+ The fix is to simply expand the apparmor rule to allow for more socket
+ files:
+
+ @{run}/timemaster/chrony.SOCK[0-9]* rw,
[ Test Plan ]
- * detailed instructions how to reproduce the bug
+ * Launch a VM. For example:
- * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+ lxc launch ubuntu-daily:oracular o-ptp --vm
- * if other testing is appropriate to perform before landing this update,
-this should also be described here.
+ * Install chrony and linuxptp in the VM:
+
+ sudo apt update && sudo apt install chrony linuxptp -y
+
+ * stop chrony:
+
+ sudo systemctl stop chrony.service
+
+ * Create a config file for timemaster, replacing the interface name with
+ the one that exists in the VM:
+
+ /etc/linuxptp/minimal.conf:
+ [ptp_domain 0]
+ interfaces enp5s0
+
+ [ptp_domain 127]
+ interfaces enp5s0
+
+ * in one terminal, observe the output of "dmesg -wT | grep timemaster"
+
+ * in another terminal, run this command:
+
+ sudo timemaster -m -q -f /etc/linuxptp/minimal.conf
+
+
+ * In a system with the bug, the command will issue a "Fatal error" like this:
+
+ Fatal error : Could not open socket /var/run/timemaster/chrony.SOCK1
+
+ * At the same time, the system with the bug will also log this line in
+ the "dmesg -wT" terminal:
+
+ [Tue Jul 2 20:08:12 2024] audit: type=1400 audit(1719950892.125:129):
+ apparmor="DENIED" operation="mknod" class="file"
+ profile="/usr/sbin/chronyd" name="/run/timemaster/chrony.SOCK1" pid=1942
+ comm="chronyd" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
+
+ * In a fixed system, there will be no apparmor log in the "dmesg -wT"
+ terminal, and the "timemaster" command will run without errors, and
+ won't exit.
+
[ Where problems could occur ]
- * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+ * Think about what the upload changes in the software. Imagine the change is
+ wrong or breaks something else: how would this show up?
- * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+ * It is assumed that any SRU candidate patch is well-tested before
+ upload and has a low overall risk of regression, but it's important
+ to make the effort to think about what ''could'' happen in the
+ event of a regression.
- * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+ your upload is low risk.
- * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+ * This both shows the SRU team that the risks have been considered,
+ and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
-
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
- * and address these questions in advance
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
[ Original Description ]
-
- The fix for bug #2032805 allows chronyd to use one PTP clock/interface with
timemaster, but not more than one.
+ The fix for bug #2032805 allows chronyd to use one PTP clock/interface
+ with timemaster, but not more than one.
Steps to reproduce (config must contain valid network interface names):
$ cat > minimal_timemaster.conf
# List two separate interfaces, or two separate domains with the same
interface:
# [ptp_domain 0]
# interfaces ens1f0np0
[ptp_domain 127]
interfaces ens1f0np0 ens1f1np1
$ sudo timemaster -m -q -f minimal_timemaster.conf
timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
timemaster[533042.285]: process 2755520
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Description changed:
- The fix for bug #2032805 allows chronyd to use one PTP clock/interface
- with timemaster, but not more than one.
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [ Test Plan ]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+
+ * if other testing is appropriate to perform before landing this update,
+this should also be described here.
+
+ [ Where problems could occur ]
+
+ * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+
+ [ Other Info ]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
+
+ [ Original Description ]
+
+
+ The fix for bug #2032805 allows chronyd to use one PTP clock/interface with
timemaster, but not more than one.
Steps to reproduce (config must contain valid network interface names):
$ cat > minimal_timemaster.conf
# List two separate interfaces, or two separate domains with the same
interface:
# [ptp_domain 0]
# interfaces ens1f0np0
[ptp_domain 127]
interfaces ens1f0np0 ens1f1np1
-
- $ sudo timemaster -m -q -f minimal_timemaster.conf
- timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
- timemaster[533042.285]: process 2755520 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.0.socket -t [127:ens1f0np0] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK0
- timemaster[533042.286]: process 2755522 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.1.socket -t [127:ens1f1np1] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK1
+ $ sudo timemaster -m -q -f minimal_timemaster.conf
+ timemaster[533042.285]: process 2755518 started: chronyd -n -f
/var/run/timemaster/chrony.conf
+ timemaster[533042.285]: process 2755520 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.0.socket -t [127:ens1f0np0] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK0
+ timemaster[533042.286]: process 2755522 started: phc2sys -l 5 -a -r -R 1.00
-z /var/run/timemaster/ptp4l.1.socket -t [127:ens1f1np1] -n 127 -E
refclock_sock --refclock_sock_address /var/run/timemaster/chrony.SOCK1
Fatal error : Could not open socket /var/run/timemaster/chrony.SOCK1
...
-
Quickfix:
sudo sed -i 's|@{run}/timemaster/chrony.SOCK0
rw,|@{run}/timemaster/chrony.SOCK[0-9]* rw,|' /etc/apparmor.d/usr.sbin.chronyd
sudo systemctl reload apparmor
Expected output:
The timemaster command continues to run until pressing CTRL+C
-
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04 LTS
Release: 24.04
chrony:
- Installed: 4.5-1ubuntu4
- Candidate: 4.5-1ubuntu4
+ Installed: 4.5-1ubuntu4
+ Candidate: 4.5-1ubuntu4
linuxptp:
- Installed: 4.0-1ubuntu1
- Candidate: 4.0-1ubuntu1
+ Installed: 4.0-1ubuntu1
+ Candidate: 4.0-1ubuntu1
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linuxptp 4.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: tsoffload linkout
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jun 5 21:53:26 2024
Dependencies:
- gcc-14-base 14-20240412-0ubuntu1
- libc6 2.39-0ubuntu8.2
- libgcc-s1 14-20240412-0ubuntu1
- libidn2-0 2.3.7-2build1
- libunistring5 1.1-2build1
+ gcc-14-base 14-20240412-0ubuntu1
+ libc6 2.39-0ubuntu8.2
+ libgcc-s1 14-20240412-0ubuntu1
+ libidn2-0 2.3.7-2build1
+ libunistring5 1.1-2build1
InstallationDate: Installed on 2024-05-14 (22 days ago)
InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Release amd64
(20240423)
ProcEnviron:
- LANG=en_US.UTF-8
- PATH=(custom, no user)
- SHELL=/bin/bash
- TERM=xterm-256color
- XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
I don't think linuxptp is at fault here, so marking its task as invalid. ** Also affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linuxptp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Oracular) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: linuxptp (Ubuntu Oracular) Importance: Undecided Status: New ** Changed in: linuxptp (Ubuntu Noble) Status: New => Invalid ** Changed in: linuxptp (Ubuntu Oracular) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064393] Re: Merge chrony from Debian unstable for oracular
** Changed in: chrony (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064393 Title: Merge chrony from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2064393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068526] Re: apparmor blocks using more than one timemaster clock with chrony
** Changed in: chrony (Ubuntu) Status: Triaged => In Progress ** Changed in: chrony (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068526 Title: apparmor blocks using more than one timemaster clock with chrony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2068526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050017] Re: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider
This is the official PPA for this effort: https://launchpad.net/~canonical- server/+archive/ubuntu/lp-2050017-apache2-modssl-provider-support I just copied the packages over from my personal one, and they should be published in the next few hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050017 Title: [24.04 FEAT] [SEC2339] HSM protected signing support for Apache httpd for openSSL 3.0 with PKCS #11 provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2050017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071645] [NEW] resize.f2fs fails with "Error: Device size is not sufficient for F2FS volume, more segment needed"
Public bug reported: Terminal transcript of a simple reproduction: kuebi@twobuntu:/tmp$ truncate -s 512M testfs # create a (sparse) file to hold a test filesystem kuebi@twobuntu:/tmp$ mkfs.f2fs testfs F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 1048576 (512 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: [testfs] Discarding device Info: Overprovision ratio = 10.000% Info: Overprovision segments = 50 (GC reserved = 28) Info: format successful kuebi@twobuntu:/tmp$ truncate -s 1G testfs # grow the backing storage kuebi@twobuntu:/tmp$ resize.f2fs testfs # try to resize to fit Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 2097152 (1024 MB) Info: MKFS version "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: FSCK version from "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" to "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: superblock features = 0 : Info: superblock encrypt level = 0, salt = Info: total FS sectors = 1048576 (512 MB) Info: CKPT version = 420523bb Info: Duplicate valid checkpoint to mirror position 512 -> 1024 Info: Write valid nat_bits in checkpoint Error: Device size is not sufficient for F2FS volume, more segment needed =19508kuebi@twobuntu:/tmp$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: f2fs-tools 1.14.0-2build1 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 19:39:01 2024 InstallationDate: Installed on 2021-07-14 (1083 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: f2fs-tools UpgradeStatus: Upgraded to jammy on 2022-05-14 (779 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2021-03-24T15:58:15 ** Affects: f2fs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: - Ubuntu 22.04.4 LTS, f2fs-tools 1.14.0-2build1. - Terminal transcript of a simple reproduction: kuebi@twobuntu:/tmp$ truncate -s 512M testfs # create a (sparse) file to hold a test filesystem kuebi@twobuntu:/tmp$ mkfs.f2fs testfs - F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) + F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 1048576 (512 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with - "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" + "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: [testfs] Discarding device Info: Overprovision ratio = 10.000% Info: Overprovision segments = 50 (GC reserved = 28) Info: format successful kuebi@twobuntu:/tmp$ truncate -s 1G testfs # grow the backing storage kuebi@twobuntu:/tmp$ resize.f2fs testfs # try to resize to fit Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 2097152 (1024 MB) Info: MKFS version - "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" + "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04)
Re: Merge Opportunities Report - 2024-07-01
Hi, On Mon, Jul 1, 2024 at 5:01 AM Bryce Harrington wrote: > Merges last authored or uploaded by Server team member or alumnus (via > Merge-o-Matic) > -- > geopy 2.3.0-1ubuntu12.4.1-1 > Andreas Hasenack I synced this yesterday, and it migrated already. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 2064390] Re: Merge backuppc-rsync from Debian unstable for oracular
This is in sync at the moment, nothing to merge (4.4.0-8) ** Changed in: backuppc-rsync (Ubuntu) Milestone: ubuntu-24.06 => ubuntu-24.07 ** Changed in: backuppc-rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064390 Title: Merge backuppc-rsync from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2064390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064393] Re: Merge chrony from Debian unstable for oracular
** Changed in: chrony (Ubuntu) Milestone: ubuntu-24.06 => ubuntu-24.07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064393 Title: Merge chrony from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2064393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067810] Re: Apparmor denial on /var/lib/dpkg/arch
There were test failures[1] on the software-properties package in noble, when run with this updated version of uubntu-advantage-tools, that had to be resolved. I did that a few days ago and they are green now. 1. https://autopkgtest.ubuntu.com/packages/software-properties/noble/amd64 https://autopkgtest.ubuntu.com/packages/software-properties/noble/armhf https://autopkgtest.ubuntu.com/packages/software-properties/noble/arm64 https://autopkgtest.ubuntu.com/packages/software-properties/noble/ppc64el https://autopkgtest.ubuntu.com/packages/software-properties/noble/s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067810 Title: Apparmor denial on /var/lib/dpkg/arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
Here is a list of current DEP8 failures with the error message from this bug: $ ./retry-autopkgtest-regressions --log-regex "fatal error: environment variable ‘DEB_HOST_ARCH’ not defined" https://autopkgtest.ubuntu.com/request.cgi?release=oracular=amd64=asymptote=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=arm64=asymptote=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=ppc64el=asymptote=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=amd64=mosh=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=arm64=mosh=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=ppc64el=mosh=dpkg%2F1.22.6ubuntu14 https://autopkgtest.ubuntu.com/request.cgi?release=oracular=s390x=mosh=dpkg%2F1.22.6ubuntu14 asymptote and mosh (why it didn't pick up my mwrap run from the previous comment I don't know) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071468 Title: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2071468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
The mwrap tests[1] are failing with the error[2] reported in this bug. 1. https://autopkgtest.ubuntu.com/packages/mwrap/oracular/amd64 2. https://autopkgtest.ubuntu.com/results/autopkgtest-oracular/oracular/amd64/m/mwrap/20240629_173552_2116e@/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071468 Title: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2071468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071468 Title: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2071468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
+1 maintenance: June 24 - June 28
I focused on the NBS report, where I saw that a new poppler needed some reverse dependencies rebuilt. And they were not rebuilding. This is C++, and it takes a while to build, specially if the failing arch is armhf, which was the case of two packages. The common root issue was that poppler switched to std=c++20[1] because they started using std::string::starts_with, and that is only defined in C++20. So all reverse dependencies that needed a rebuild also had to switch, and this was the basic fix I applied. # dia FTBFS https://bugs.launchpad.net/ubuntu/+source/dia/+bug/2070284 fixed # gdcm FTBFS https://bugs.launchpad.net/ubuntu/+source/gdcm/+bug/2070303 fixed # inkscape FTBFS https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/2070367 Partial fix, but it fails to build elsewhere after that. Latest upstream version is 1.3.2, and ours (and debian's) is 1.2.2, maybe it's best to update it and see what happens. Debian experimental has 1.3. # calligra FTBFS https://bugs.launchpad.net/ubuntu/+source/calligra/+bug/2070399 fixed # openboard FTBFS https://bugs.launchpad.net/ubuntu/+source/openboard/+bug/2070403 fixed # rdma-core FTBFS on armhf https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/2070280 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073050 I troubleshooted and Benjamin Drung fixed it in a debian upload which was then synced. # gambas3 FTBFS on armhf https://bugs.launchpad.net/ubuntu/+source/gambas3/+bug/2012420 After many attempts by different people, Gianfranco fixed it in https://launchpad.net/ubuntu/+source/gambas3/3.19.1-1ubuntu3 On Thursday, I did my usual SRU shift instead of +1 maintenance. I went over all releasable packages in noble-proposed, and released, accepted, or dealt with, the following: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2070070 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069828 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2068739 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2063203 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064280 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2064175 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2061121 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2066905 https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2007419 https://bugs.launchpad.net/ubuntu/+source/gnome-builder/+bug/2068065 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067886 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067585 https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067071 https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2067785 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2067592 https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2067387 https://bugs.launchpad.net/ubuntu/+source/klayout/+bug/2066026 https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180 https://bugs.launchpad.net/ubuntu/+source/extruct/+bug/2064861 https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2064843 https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-18/+bug/2064187 https://bugs.launchpad.net/ubuntu/+source/rtl8812au/+bug/2063820 https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637 https://bugs.launchpad.net/horizon/+bug/1728031 https://bugs.launchpad.net/horizon/+bug/2055409 https://bugs.launchpad.net/horizon/+bug/2054799 https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2037015 https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2062146 https://bugs.launchpad.net/ubuntu/+source/fwbuilder/+bug/1957168 1. https://gitlab.freedesktop.org/poppler/poppler/-/commit/d8ae3ba#9a2aa4db38d3115ed60da621e012c0efc0172aae -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 2070280] Re: FTBFS: missing files
Fixed by https://launchpad.net/ubuntu/+source/rdma-core/52.0-2, closing. ** Changed in: rdma-core (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070280 Title: FTBFS: missing files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdma-core/+bug/2070280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012420] Re: armhf patch no longer necessary, causes FTBFS with new poppler
And migrated. https://launchpad.net/ubuntu/+source/gambas3/3.19.1-1ubuntu3 ** Changed in: gambas3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012420 Title: armhf patch no longer necessary, causes FTBFS with new poppler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gambas3/+bug/2012420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012420] Re: armhf patch no longer necessary, causes FTBFS with new poppler
This was uploaded, and it built \o/ ** Changed in: gambas3 (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012420 Title: armhf patch no longer necessary, causes FTBFS with new poppler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gambas3/+bug/2012420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957168] Update Released
The verification of the Stable Release Update for fwbuilder has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957168 Title: [SRU] fwbuilder crashes in Noble when trying to create almost any type of new object To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwbuilder/+bug/1957168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067387] Update Released
The verification of the Stable Release Update for file-roller has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067387 Title: [SRU] Backport file-roller 44.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2067387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061637] Update Released
The verification of the Stable Release Update for xxdiff has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061637 Title: [SRU] xx-svn-review crashed with ModuleNotFoundError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xxdiff/+bug/2061637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064187] Re: llvm-18-linker-tools does not include LLVMgold.so
The dep8 tests was stuck, and the details page showed a tmpfail. I retrigered it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064187 Title: llvm-18-linker-tools does not include LLVMgold.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-18/+bug/2064187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062929] Please test proposed package
Hello Ankush, or anyone else affected, Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.765.44 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062929 Title: AppArmor profile policy `unconfined_restrictions` missing for jammy and mantic 6.5 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2062929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
