[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
This was uploaded and is in noble-unapproved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
The configure check is failing due to a missing include: conftest.c: In function 'main': conftest.c:177:20: error: implicit declaration of function 'exit' [-Werror=implicit-function-declaration] 177 | struct timeval tv; exit(gettimeofday(, NULL)); |^~~~ conftest.c:174:1: note: include '' or provide a declaration of 'exit' 173 | #include 174 | int conftest.c:177:20: warning: incompatible implicit declaration of built-in function 'exit' [-Wbuiltin-declaration-mismatch] 177 | struct timeval tv; exit(gettimeofday(, NULL)); |^~~~ conftest.c:177:20: note: include '' or provide a declaration of 'exit' cc1: some warnings being treated as errors Since the failure is due to that missing include, instead of the gettimeofday() function, the check reaches the incorrect answer to the question "checking if gettimeofday takes tz argument ". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
** 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/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
Thanks for verifying it. This is up for review and as soon as it's approved I'll upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
This PPA has a patched version for noble, would you mind trying it out please? https://launchpad.net/~ahasenack/+archive/ubuntu/autofs-segfault-2061667 ** Changed in: autofs (Ubuntu) Status: Triaged => In Progress ** Also affects: autofs (Ubuntu Noble) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: 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/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
I managed to reproduce it finally after I added "strictexpire" to /etc/auto.master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
And your second reproducer, with /mp in auto.master, doesn't work here: # ls -la /mp/mumon/_. ls: cannot access '/mp/mumon/_.': No such file or directory handle_packet: type = 3 handle_packet_missing_indirect: token 43, name mumon, request pid 4242 attempting to mount entry /mp/mumon lookup_mount: lookup(file): looking up mumon key "mumon" not found in map source(s). dev_ioctl_send_fail: token = 43 failed to mount /mp/mumon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
Which kernel are you running? There are some kernel version checks in the code which affect a buffer size, and that's a buffer that make_options_string() writes to. I haven't been able to reproduce this yet, with any of your config files. I'm on noble's kernel: 6.8.0-22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
** Changed in: autofs (Ubuntu) Status: Incomplete => Triaged ** Changed in: autofs (Ubuntu) Importance: Undecided => High ** Changed in: autofs (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/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
Thanks for this, I know better where to look now. The config files or a minimal reproducer would still help, of course. In the meantime, you can also try debuginfod[1], which is a way for gdb to automatically fetcl all the symbols for you. TL;DR Something like this sudo -i (because automounter needs to run as root) export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com; gdb r -f 1. https://ubuntu.com/server/docs/service-debuginfod -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061667 Title: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061667] Re: Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
Tried direct and indirect nfs mounts, and the test suite also does nfs
and cifs mounts, no segfault:
root@server:~# automount -d3 -f
Starting automounter version 5.1.9, master map /etc/auto.master
using kernel protocol version 5.05
lookup_nss_read_master: reading master file /etc/auto.master
do_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry /mnt
lookup_read_master: lookup(file): read entry /-
master_do_mount: mounting /mnt
lookup_nss_read_map: reading map file /etc/auto.mnt
do_init: parse(sun): init gathered global options: (null)
mounted indirect on /mnt with timeout 300, freq 75 seconds
st_ready: st_ready(): state = 0 path /mnt
master_do_mount: mounting /-
lookup_nss_read_map: reading map file /etc/auto.direct
do_init: parse(sun): init gathered global options: (null)
mounted direct on /foo with timeout 300, freq 75 seconds
do_mount_autofs_direct: mounted trigger /foo
st_ready: st_ready(): state = 0 path /-
handle_packet: type = 5
handle_packet_missing_direct: token 43, name /foo, request pid 14188
attempting to mount entry /foo
lookup_mount: lookup(file): looking up /foo
lookup_mount: lookup(file): /foo -> localhost:/storage
parse_mount: parse(sun): expanded entry: localhost:/storage
parse_mount: parse(sun): gathered options:
parse_mount: parse(sun): dequote("localhost:/storage") -> localhost:/storage
parse_mount: parse(sun): core of entry: options=, loc=localhost:/storage
sun_mount: parse(sun): mounting root /foo, mountpoint /foo, what
localhost:/storage, fstype nfs, options (null)
mount(nfs): root=/foo name=/foo what=localhost:/storage, fstype=nfs,
options=(null)
mount_mount: mount(nfs): calling mkdir_path /foo
mount_mount: mount(nfs): /foo is local, attempt bind mount
mount_mount: mount(bind): calling mkdir_path /foo
mount(bind): calling mount --bind -o defaults /storage /foo
mount(bind): mounted /storage type bind on /foo
dev_ioctl_send_ready: token = 43
mounted /foo
handle_packet: type = 3
handle_packet_missing_indirect: token 44, name nfs, request pid 14191
attempting to mount entry /mnt/nfs
lookup_mount: lookup(file): looking up nfs
lookup_mount: lookup(file): nfs -> localhost:/storage
parse_mount: parse(sun): expanded entry: localhost:/storage
parse_mount: parse(sun): gathered options:
parse_mount: parse(sun): dequote("localhost:/storage") -> localhost:/storage
parse_mount: parse(sun): core of entry: options=, loc=localhost:/storage
sun_mount: parse(sun): mounting root /mnt, mountpoint nfs, what
localhost:/storage, fstype nfs, options (null)
mount(nfs): root=/mnt name=nfs what=localhost:/storage, fstype=nfs,
options=(null)
mount_mount: mount(nfs): calling mkdir_path /mnt/nfs
mount_mount: mount(nfs): nfs is local, attempt bind mount
mount_mount: mount(bind): calling mkdir_path /mnt/nfs
mount(bind): calling mount --bind -o defaults /storage /mnt/nfs
mount(bind): mounted /storage type bind on /mnt/nfs
dev_ioctl_send_ready: token = 44
mounted /mnt/nfs
# mount -t autofs
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=3020)
/etc/auto.mnt on /mnt type autofs
(rw,relatime,fd=6,pgrp=14168,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=47695)
/etc/auto.direct on /foo type autofs
(rw,relatime,fd=9,pgrp=14168,timeout=300,minproto=5,maxproto=5,direct,pipe_ino=47702)
It would definitely help to have a reproducer, or the core file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061667
Title:
Noble 'autofs' 5.1.9-1ubuntu3 buffer overflow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2061667/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Re: pro sometimes runs before cloud-config.service
Looks good, but please also include: - azure run (to at least show it's still working, if you cannot reproduce the bug there easily) - what a test failure looks like, according to this plan +1 to go ahead and update the bug description's [test plan]. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.3~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: ubuntu-advantage-tools (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.3~16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. 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/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.3~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.3~23.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: New => 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/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Please test proposed package
Hello Lucas, or anyone else affected, Accepted ubuntu-advantage-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.3~22.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: New => 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/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Re: pro sometimes runs before cloud-config.service
> However, CPC is already aware of this issue and will help us creating the test plan here. I understand CPC can hit this bug quite frequently in the affected cloud images, so releasing this SRU to updates is conditional on an actual test plan being better described by them, and followed. ** Also affects: ubuntu-advantage-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: New => Fix Committed ** 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/2059952 Title: pro sometimes runs before cloud-config.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2059952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061325] Re: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
This is in noble-proposed now. ** Changed in: sosreport (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/2061325 Title: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2061325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061325] Re: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
** Bug watch added: Debian Bug tracker #1058214 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058214 ** Also affects: sosreport (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058214 Importance: Unknown Status: Unknown ** Changed in: sosreport (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: sosreport (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/2061325 Title: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2061325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061325] Re: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
** Description changed: https://launchpad.net/ubuntu/+source/sosreport/4.5.6-0ubuntu3 is failing to build in noble. Lots of test failures like: ERROR: test_open_file (tests.unittests.utilities_tests.GrepTest.test_open_file) -- Traceback (most recent call last): - File "/<>/tests/unittests/utilities_tests.py", line 35, in test_open_file - self.assertEquals(matches, ['import unittest\n']) - ^ + File "/<>/tests/unittests/utilities_tests.py", line 35, in test_open_file + self.assertEquals(matches, ['import unittest\n']) + ^ AttributeError: 'GrepTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? + + + Update: + https://github.com/sosreport/sos/commit/769768aabcae3d0265332ee72e9df94d1001f14c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061325 Title: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2061325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061325] [NEW] FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?
Public bug reported: https://launchpad.net/ubuntu/+source/sosreport/4.5.6-0ubuntu3 is failing to build in noble. Lots of test failures like: ERROR: test_open_file (tests.unittests.utilities_tests.GrepTest.test_open_file) -- Traceback (most recent call last): File "/<>/tests/unittests/utilities_tests.py", line 35, in test_open_file self.assertEquals(matches, ['import unittest\n']) ^ AttributeError: 'GrepTest' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? ** Affects: sosreport (Ubuntu) Importance: High Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061325 Title: FTBFS in noble: test failures: object has no attribute 'assertEquals'. Did you mean: 'assertEqual'? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2061325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
Mantic verification succeeded. ** Attachment added: "mantic-verification.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+attachment/5765296/+files/mantic-verification.log ** 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/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
Jammy verification succeeded. ** Attachment added: "jammy-verification.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+attachment/5765295/+files/jammy-verification.log ** 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/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
Focal verification succeeded. ** Attachment added: "focal-verification.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+attachment/5765294/+files/focal-verification.log ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
Bionic verification succeeded. ** Attachment added: "bionic-verification.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+attachment/5765293/+files/bionic-verification.log ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
The remaining verifications were done with the attached script. ** Attachment added: "test-apparmor.sh" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+attachment/5765292/+files/test-apparmor.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
Xenial verification a) Reproducing the problem, and confirming the fix Starting with 31.2: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~16.04 all transitional dummy package for ubuntu-pro-client Removing apparmor: $ sudo apt remove apparmor -y (...) The following packages will be REMOVED: apparmor liblxc1 lxc-common lxd snapd ubuntu-core-launcher (...) Removing apparmor (2.10.95-0ubuntu2.12) ... (...) Rebooting... Logging back in, checking apt-news.service to see it fails to start due to apparmor: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xe" for details. $ systemctl status apt-news.service ● apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2024-04-14 15:41:47 UTC; 10s ago Process: 1486 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 1486 (code=exited, status=231/APPARMOR) Installing ubuntu-advantage-tools from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~16.04 Candidate: 31.2.2~16.04 Version table: *** 31.2.2~16.04 500 500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~16.04 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages $ pro version 31.2.2~16.04 Now the service starts: $ sudo systemctl start apt-news.service $ $ sudo systemctl status apt-news.service ● apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static; vendor preset: enabled) Active: inactive (dead) (...) Apr 14 15:43:40 x-vm systemd[1]: Starting Update APT News... Apr 14 15:43:40 x-vm systemd[1]: Started Update APT News. b) Confirming that apparmor, when available, is being applied Continuing from test (a), we already have the proposed package installed. Re-installing apparmor: $ sudo apt install apparmor -y (...) Setting up apparmor (2.10.95-0ubuntu2.12) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Rebooting Confirming profile is loaded and enforced: $ sudo grep ubuntu_pro_apt_news /sys/kernel/security/apparmor/profiles ubuntu_pro_apt_news (enforce) Starting apt-news, it does not fail: $ sudo systemctl start apt-news.service ; echo $? 0 Hacking the service unit file to force the service to stay running so we can inspect it: $ sudo systemctl start apt-news.service (it's sleeping) Checking process: # ps auxwZ|grep time\\.sleep ubuntu_pro_apt_news (enforce) root 1749 0.0 0.8 35296 8716 ? Ss 15:49 0:00 /usr/bin/python3 -c import time; time.sleep(500) We can see it's confined with ubuntu_pro_apt_news in enforce mode. Xenial verification succeeded. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2057937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Jammy verification With the package from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~22.04 Candidate: 31.2.2~22.04 Version table: *** 31.2.2~22.04 500 500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~22.04 500 500 http://br.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 27.7~22.04.1 500 500 http://br.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ pro version 31.2.2~22.04 $ dpkg -l ubuntu-advantage-tools | grep ^ii ii ubuntu-advantage-tools 31.2.2~22.04 all transitional dummy package for ubuntu-pro-client THe versions match. Verification succeeded. ** 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/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Xenial verification With the package from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~16.04 Candidate: 31.2.2~16.04 Version table: *** 31.2.2~16.04 500 500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~16.04 500 500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages $ pro version 31.2.2~16.04 $ dpkg -l ubuntu-advantage-tools | grep ^ii ii ubuntu-advantage-tools 31.2.2~16.04 all transitional dummy package for ubuntu-pro-client The versions match. Verification succeeded. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Bionic verification With the package from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~18.04 Candidate: 31.2.2~18.04 Version table: *** 31.2.2~18.04 500 500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~18.04 500 500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 17 500 500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages $ pro version 31.2.2~18.04 $ dpkg -l ubuntu-advantage-tools | grep ^ii ii ubuntu-advantage-tools 31.2.2~18.04 all transitional dummy package for ubuntu-pro-client The versions match. Verification succeeded. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Focal verification With the package from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~20.04 Candidate: 31.2.2~20.04 Version table: *** 31.2.2~20.04 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~20.04 500 500 http://br.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 20.3 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ pro version 31.2.2~20.04 $ dpkg -l ubuntu-advantage-tools | grep ^ii ii ubuntu-advantage-tools 31.2.2~20.04 all transitional dummy package for ubuntu-pro-client The versions match. Verification succeeded. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Mantic verification With the package from proposed: $ apt-cache policy ubuntu-advantage-tools ubuntu-advantage-tools: Installed: 31.2.2~23.10 Candidate: 31.2.2~23.10 Version table: *** 31.2.2~23.10 500 500 http://br.archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 31.2~23.10 500 500 http://br.archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 29.4 500 500 http://br.archive.ubuntu.com/ubuntu mantic/main amd64 Packages $ pro version 31.2.2~23.10 $ dpkg -l ubuntu-advantage-tools|grep ^ii ii ubuntu-advantage-tools 31.2.2~23.10 all transitional dummy package for ubuntu-pro-client The versions match. Verification succeeded. ** 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/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
This is fix released in noble via https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.2 (and noble has 31.2.3 already). ** Changed in: ubuntu-advantage-tools (Ubuntu Noble) 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/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060967] Re: noble/rsync buffer overflow detected
I'm surprised this wasn't caught by the DEP8 tests. Care to also perhaps add a simple smoke test, like (note it's not using ssh or any network): $ rsync -F --delete-after --archive /etc/os-release /tmp/ *** buffer overflow detected ***: terminated rsync: connection unexpectedly closed (34 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) [sender=3.2.7] ** Changed in: rsync (Ubuntu) Importance: Undecided => High ** Changed in: rsync (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060967 Title: noble/rsync buffer overflow detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060848] Re: minifycss fails to run in Noble
diff -Nru matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch
--- matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 1970-01-01
01:00:00.0 +0100
+++ matthiasmullie-minify-1.3.68/debian/patches/fix-path.patch 2024-04-10
18:48:17.0 +0100
@@ -0,0 +1,37 @@
+Description: Fix paths of the files minify required
+Author: Sudip Mukherjee
+Bug-Ubuntu: https://launchpad.net/bugs/2060848
+Forwarded: not-needed
+Last-Update: 2024-04-10
You could also add the debian bug to this header:
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068767
I wouldn't block the upload on this, though. But I have another
question.
Are there more fixes needed? I just quickly tried to run it with a
random css file that is in the same package, and it failed:
$ minifycss ./tests/css/sample/convert_relative_path/source/absolute.css
PHP Fatal error: Uncaught Error: Class
"MatthiasMullie\PathConverter\Converter" not found in
/usr/share/php/MatthiasMullie/Minify/CSS.php:788
Stack trace:
#0 /usr/share/php/MatthiasMullie/Minify/CSS.php(339):
MatthiasMullie\Minify\CSS->getPathConverter()
#1 /usr/share/php/MatthiasMullie/Minify/Minify.php(149):
MatthiasMullie\Minify\CSS->execute()
#2 /usr/bin/minifycss(41): MatthiasMullie\Minify\Minify->minify()
#3 {main}
thrown in /usr/share/php/MatthiasMullie/Minify/CSS.php on line 788
The DEP8 tests also seems to be failing, at least locally:
$ AUTOPKGTEST_TMP=$(mktemp -d) sh debian/tests/upstream
phpab %development% - Copyright (C) 2009 - 2024 by Arne Blankerts and
Contributors
Scanning directory ./tests
Autoload file ./vendor/autoload.php generated.
Proceeding without a composer.json file.PHPUnit 9.6.17 by Sebastian
Bergmann and contributors.
Warning: Incorrect filter configuration, code coverage will not be
processed
... 63 / 343 ( 18%)
... 126 / 343 ( 36%)
..FE... 189 / 343 ( 55%)
... 252 / 343 ( 73%)
... 315 / 343 ( 91%)
343 / 343 (100%)
Time: 00:00.091, Memory: 12.00 MB
There was 1 error:
1) MatthiasMullie\Minify\Test\AbstractTest::testCache
Error: Class "MatthiasMullie\Scrapbook\Adapters\MemoryStore" not found
/tmp/tmp.w3M8gzyBuN/tests/js/AbstractTest.php:218
--
There was 1 failure:
1) MatthiasMullie\Minify\Test\AbstractTest::testLoadOpenBaseDirRestricted
open_basedir restriction caused minifier to fail
Failed asserting that 0 matches expected 512.
/tmp/tmp.w3M8gzyBuN/tests/js/AbstractTest.php:157
ERRORS!
Tests: 343, Assertions: 352, Errors: 1, Failures: 1.
** Changed in: matthiasmullie-minify (Ubuntu Noble)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060848
Title:
minifycss fails to run in Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/matthiasmullie-minify/+bug/2060848/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060848] Re: minifycss fails to run in Noble
** Also affects: matthiasmullie-minify (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: matthiasmullie-minify (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060848 Title: minifycss fails to run in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matthiasmullie-minify/+bug/2060848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060692] Re: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git
https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu6 is in noble- proposed claiming to fix this bug. Comment #6 above says there is a missing patch still. In any case, doesn't look like there is anything to sponsor here, so unsubscribing ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060692 Title: cupsd 2.4.7-1.2ubuntu5 on noble crashes due to recently backported commits from 2.4.x git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2060692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
And unsubscribing sponsors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
At the moment, noble-proposed has https://launchpad.net/ubuntu/+source/upower/1.90.3-1, uploaded a few hours ago: upower (1.90.3-1) unstable; urgency=medium * New upstream version 1.90.3 * Drop patches, merged upstream * Bump Build-Depends on meson to (>= 0.60.0) and libglib2.0-dev to (>= 2.66) as per meson.build * Switch Build-Depends on pkg-config to pkgconf * Bump Standards-Version to 4.7.0 -- Michael Biebl Mon, 08 Apr 2024 09:42:45 +0200 According to https://autopkgtest.ubuntu.com/packages/u/upower/noble/arm64 arm64 tests with that version have passed already: (...) 905s Ran 67 tests in 174.527s 905s 905s OK 905s PASS: upower/upower-integration.test 905s SUMMARY: total=1; passed=1; skipped=0; failed=0; user=11.5s; system=4.9s; maxrss=33304 906s autopkgtest [06:17:15]: test installed-tests: ---] 907s installed-tests PASS Closing bug (fix committed, since it's not yet in the release pocket). ** Changed in: upower (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/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
*** This bug is a duplicate of bug 2056442 *** https://bugs.launchpad.net/bugs/2056442 ** This bug has been marked a duplicate of bug 2056442 Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053157] Re: Jammy: netplan permissions warnings
Hello Chad, or anyone else affected, Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-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: cloud-init (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/2053157 Title: Jammy: netplan permissions warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2053157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Please test proposed package
Hello Brett, or anyone else affected, Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-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: cloud-init (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/2056100 Title: sru cloud-init 23.4.4 to 24.1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Please test proposed package
Hello Brett, or anyone else affected, Accepted cloud-init into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-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/2056100 Title: sru cloud-init 23.4.4 to 24.1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Re: sru cloud-init 23.4.4 to 24.1.3
Hello Brett, or anyone else affected, Accepted cloud-init into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-0ubuntu1~23.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- 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: cloud-init (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: cloud-init (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/2056100 Title: sru cloud-init 23.4.4 to 24.1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Re: sru cloud-init 23.4.4 to 24.1.3
I was careful in checking that the debian/patches/status-retain- recoverable-error-exit-code.patch patch was kept for mantic and earlier, as to not reintroduce #2048522. And I know it was decided that in noble the decision is to not patch it, i.e., return 2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056100 Title: sru cloud-init 23.4.4 to 24.1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053157] Re: Jammy: netplan permissions warnings
This is missing the SRU template, or clarification whether the test plan of the main SRU bug at #2056100 covers this change here. Normally, called-out bugs in d/changelog need to have the SRU template filled in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053157 Title: Jammy: netplan permissions warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2053157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053157] Re: Jammy: netplan permissions warnings
Changing jammy status to "in progress", because it's still in unapproved. ** Changed in: cloud-init (Ubuntu Jammy) Status: Fix Committed => 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/2053157 Title: Jammy: netplan permissions warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2053157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
Adding a release notes task to put a note under "known issues". ** Also affects: ubuntu-release-notes 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/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052642] Re: opeanfs-modules-dkms FTBS with linux 6.5 on jammy
This update is still missing the mantic verification, which blocks a jammy release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052642 Title: opeanfs-modules-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/2052642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058133] Update Released
The verification of the Stable Release Update for update-manager 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/2058133 Title: [SRU] update-manager crashes when ua security-status response is an error To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2058133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058133] Re: [SRU] update-manager crashes when ua security-status response is an error
Focal still has an ubuntu-release-upgrader regression on armhf. I triggered that one again. Jammy is ok. Bionic is ok, but can't be released before focal. The xenial upload is still in unapproved, probably because there is another xenial SRU going on in xenial-proposed: 1:16.04.21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058133 Title: [SRU] update-manager crashes when ua security-status response is an error To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/2058133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
> # dpkg -l crun Markus, thanks for the verification, but crun can be installed together with runc, and it's not clear which one will end up being used. That's why it's best to also make sure runc is *not* installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
This is blocked on a mantic upload fixing the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054621] Update Released
The verification of the Stable Release Update for php8.1 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/2054621 Title: Fix PHP crashes due to accessing dangling pointers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php8.1/+bug/2054621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051166] Re: [SRU] lcov 2.0-1 FTBFS on Mantic
The changes file that was accepted didn't include version 0.1, which is the one that fixed this bug here. Marking it "fix released" manually, since I just released https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2029924 ** Changed in: lcov (Ubuntu Mantic) 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/2051166 Title: [SRU] lcov 2.0-1 FTBFS on Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2051166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029924] Update Released
The verification of the Stable Release Update for lcov 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/2029924 Title: [SRU] "Can't locate lcovutil.pm" after updating to 2.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2029924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Hello Jeff, or anyone else affected, Accepted qemu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:6.2+dfsg-2ubuntu6.19 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: qemu (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags removed: verification-done ** 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/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Update Released
The verification of the Stable Release Update for qemu 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/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2046439 was released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018449] Update Released
The verification of the Stable Release Update for xmms2 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/2018449 Title: [SRU] `xmms2 add --playlist ... ` causes a core dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xmms2/+bug/2018449/+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
New pam package uploaded to noble-proposed. It's in the unapproved queue. -- 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/openssh/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
Marking the userspace component (src:nfs-utils) task as invalid, since it's a bug in the kernel. ** Changed in: nfs-utils (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+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
We won't fix this in openssh for Ubuntu 24.04 due to the change in behavior that it introduces at this stage in the cycle, but it should be fixed in 24.10. As for 24.04, what we will attempt to do is suppress the pam_env warning in the src:pam package. ** Also affects: pam (Ubuntu) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Milestone: None => later ** Changed in: pam (Ubuntu) Status: New => In Progress ** Changed in: pam (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: pam (Ubuntu) Milestone: None => ubuntu-24.04 -- 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/openssh/+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
Commit that added the warning to pam_env.c: https://github.com/linux- pam/linux-pam/commit/ecd526743a27157c5210b0ce9867c43a2fa27784 -- 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/openssh/+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
Deprecation warning introduced here: https://github.com/linux-pam/linux- pam/releases/tag/v1.5.0 Release notes for all releases up to 1.6.1 don't mention this again, so it's still there: https://github.com/linux-pam/linux-pam/releases -- 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/openssh/+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
Fixing this in noble at this time will require a feature freeze exception, because we would be changing behavior. The default for user_readenv in pam_env is 0 (off). In the sshd config, ubuntu/debian ship a pam config that sets it to on (1), therefore ~/.pam_environment will be read if it exists. Upstream has flagged that this feature (of reading user-provided env var files) will be removed in the future, and is thus catching the setting of user_readenv=1 and showing the deprecation notice warning. To get rid of the warning, we have to stop setting user_readenv=1, which will *disable* the feature. Meaning, in noble, if we make this change, ~/.pam_environment (or the file specified by user_envfile) will NOT be read anymore. -- 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/openssh/+bug/2059859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
That would be https://github.com/torvalds/linux/commit/fce7913b13d0270bcf926f986b7ef329e2e56eec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
> Could I know the kernel version which use for below test? Search for "testbed running kernel". In the case of that test, it's: 859s autopkgtest [01:53:38]: testbed running kernel: Linux 6.6.0-14-generic #14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I have GuoqingJiang access to the s390x vm where this bug can be observed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
Perhaps try an older kernel, from when the test last passed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Mantic verification In all architectures, except i386, the new test passed. Here is a log from the amd64 run[1]: 4333s autopkgtest [16:47:27]: test ssh-gssapi: [--- 4333s ## Setting up test environment 4333s ## Creating Kerberos realm EXAMPLE.FAKE 4333s Initializing database '/var/lib/krb5kdc/principal' for realm 'EXAMPLE.FAKE', 4333s master key name 'K/m...@example.fake' 4333s ## Creating principals 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Principal "testuser1...@example.fake" created. 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Principal "host/sshd-gssapi.example.f...@example.fake" created. 4333s ## Extracting service principal host/sshd-gssapi.example.fake 4333s Authenticating as principal root/ad...@example.fake with password. 4333s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 4333s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 4333s ## Adjusting /etc/krb5.conf 4333s ## TESTS 4333s 4333s ## TEST test_gssapi_login 4333s ## Configuring sshd for gssapi-with-mic authentication 4333s ## Restarting ssh 4333s ## Obtaining TGT 4333s Password for testuser1...@example.fake: 4333s Ticket cache: FILE:/tmp/krb5cc_0 4333s Default principal: testuser1...@example.fake 4333s 4333s Valid starting ExpiresService principal 4333s 04/05/24 16:47:27 04/06/24 02:47:27 krbtgt/example.f...@example.fake 4333s renew until 04/06/24 16:47:27 4333s 4333s ## ssh'ing into localhost using gssapi-with-mic auth 4333s Warning: Permanently added 'sshd-gssapi.example.fake' (ED25519) to the list of known hosts. 4334s Fri Apr 5 16:47:27 UTC 2024 4334s 4334s ## checking that we got a service ticket for ssh (host/) 4334s 04/05/24 16:47:27 04/06/24 02:47:27 host/sshd-gssapi.example.fake@ 4334s Ticket server: host/sshd-gssapi.example.f...@example.fake 4334s 4334s ## Checking ssh logs to confirm gssapi-with-mic auth was used 4334s Apr 05 16:47:27 sshd-gssapi.example.fake sshd[1688]: Accepted gssapi-with-mic for testuser1620 from 127.0.0.1 port 44922 ssh2: testuser1...@example.fake 4334s ## PASS test_gssapi_login 4334s 4334s ## TEST test_gssapi_keyex_login 4334s ## Configuring sshd for gssapi-keyex authentication 4334s ## Restarting ssh 4334s ## Obtaining TGT 4334s Password for testuser1...@example.fake: 4334s Ticket cache: FILE:/tmp/krb5cc_0 4334s Default principal: testuser1...@example.fake 4334s 4334s Valid starting ExpiresService principal 4334s 04/05/24 16:47:28 04/06/24 02:47:28 krbtgt/example.f...@example.fake 4334s renew until 04/06/24 16:47:28 4334s 4334s ## ssh'ing into localhost using gssapi-keyex auth 4334s Fri Apr 5 16:47:28 UTC 2024 4334s 4334s ## checking that we got a service ticket for ssh (host/) 4334s 04/05/24 16:47:28 04/06/24 02:47:28 host/sshd-gssapi.example.fake@ 4334s Ticket server: host/sshd-gssapi.example.f...@example.fake 4334s 4334s ## Checking ssh logs to confirm gssapi-keyex auth was used 4334s Apr 05 16:47:28 sshd-gssapi.example.fake sshd[1758]: Accepted gssapi-keyex for testuser1620 from 127.0.0.1 port 44930 ssh2: testuser1...@example.fake 4334s ## PASS test_gssapi_keyex_login 4334s 4334s ## ALL TESTS PASSED 4334s ## Cleaning up 4334s autopkgtest [16:47:28]: test ssh-gssapi: ---] 4335s ssh-gssapi PASS 4335s autopkgtest [16:47:29]: test ssh-gssapi: - - - - - - - - - - results - - - - - - - - - - 4335s autopkgtest [16:47:29]: summary 4335s regress PASS 4335s systemd-socket-activation PASS 4335s ssh-gssapi PASS Mantic verification succeeded. 1. https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/o/openssh/20240405_164750_3a52b@/log.gz ** 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/2053146 Title: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
Jammy verification In all architectures (except i386, which is a known failure everywhere) the new ssh-gssapi test passed. Here is the run on amd64[1]: 3438s autopkgtest [16:33:21]: test ssh-gssapi: [--- 3438s ## Setting up test environment 3438s ## Creating Kerberos realm EXAMPLE.FAKE 3438s Loading random data 3438s Initializing database '/var/lib/krb5kdc/principal' for realm 'EXAMPLE.FAKE', 3438s master key name 'K/m...@example.fake' 3438s ## Creating principals 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Principal "testuser1...@example.fake" created. 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Principal "host/sshd-gssapi.example.f...@example.fake" created. 3438s ## Extracting service principal host/sshd-gssapi.example.fake 3438s Authenticating as principal root/ad...@example.fake with password. 3438s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 3438s Entry for principal host/sshd-gssapi.example.fake with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab WRFILE:/etc/krb5.keytab. 3438s ## Adjusting /etc/krb5.conf 3438s ## TESTS 3438s 3438s ## TEST test_gssapi_login 3438s ## Configuring sshd for gssapi-with-mic authentication 3438s ## Restarting ssh 3438s ## Obtaining TGT 3438s Password for testuser1...@example.fake: 3438s Ticket cache: FILE:/tmp/krb5cc_0 3438s Default principal: testuser1...@example.fake 3438s 3438s Valid starting ExpiresService principal 3438s 04/05/24 16:33:20 04/06/24 02:33:20 krbtgt/example.f...@example.fake 3438s renew until 04/06/24 16:33:20 3438s 3438s ## ssh'ing into localhost using gssapi-with-mic auth 3438s Warning: Permanently added 'sshd-gssapi.example.fake' (ED25519) to the list of known hosts. 3439s Fri Apr 5 16:33:21 UTC 2024 3439s 3439s ## checking that we got a service ticket for ssh (host/) 3439s 04/05/24 16:33:21 04/06/24 02:33:20 host/sshd-gssapi.example.fake@ 3439s Ticket server: host/sshd-gssapi.example.f...@example.fake 3439s 3439s ## Checking ssh logs to confirm gssapi-with-mic auth was used 3439s Apr 05 16:33:21 sshd-gssapi.example.fake sshd[1518]: Accepted gssapi-with-mic for testuser1457 from 127.0.0.1 port 50668 ssh2: testuser1...@example.fake 3439s ## PASS test_gssapi_login 3439s 3439s ## TEST test_gssapi_keyex_login 3439s ## Configuring sshd for gssapi-keyex authentication 3439s ## Restarting ssh 3439s ## Obtaining TGT 3439s Password for testuser1...@example.fake: 3439s Ticket cache: FILE:/tmp/krb5cc_0 3439s Default principal: testuser1...@example.fake 3439s 3439s Valid starting ExpiresService principal 3439s 04/05/24 16:33:21 04/06/24 02:33:21 krbtgt/example.f...@example.fake 3439s renew until 04/06/24 16:33:21 3439s 3439s ## ssh'ing into localhost using gssapi-keyex auth 3439s Fri Apr 5 16:33:21 UTC 2024 3439s 3439s ## checking that we got a service ticket for ssh (host/) 3439s 04/05/24 16:33:21 04/06/24 02:33:21 host/sshd-gssapi.example.fake@ 3439s Ticket server: host/sshd-gssapi.example.f...@example.fake 3439s 3439s ## Checking ssh logs to confirm gssapi-keyex auth was used 3439s Apr 05 16:33:21 sshd-gssapi.example.fake sshd[1558]: Accepted gssapi-keyex for testuser1457 from 127.0.0.1 port 50670 ssh2: testuser1...@example.fake 3439s ## PASS test_gssapi_keyex_login 3439s 3439s ## ALL TESTS PASSED 3439s ## Cleaning up 3439s autopkgtest [16:33:22]: test ssh-gssapi: ---] 3439s autopkgtest [16:33:22]: test ssh-gssapi: - - - - - - - - - - results - - - - - - - - - - 3439s ssh-gssapi PASS 3440s autopkgtest [16:33:23]: summary 3440s regress PASS 3440s ssh-gssapi PASS Jammy verification succeeded. 1. https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/o/openssh/20240405_163345_c46fa@/log.gz ** 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/2053146 Title: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060566] Re: Add esm-infra-legacy support for Trusty
** Description changed: [Impact] As Trusty is reaching EOL of ESM support, we are now creating a new service called esm-infra-legacy to extend ESM support for more time. Users who are entitled to that service, will need to run both of these commands to enable the service in their machine: $ ua refresh $ ua enable esm-infra-legacy - The first command will update the contract definitions on the machine, making it aware of the esm-infra-legacy service, and the second command enables it on the - machine. + The first command will update the contract definitions on the machine, + making it aware of the esm-infra-legacy service, and the second command + enables it on the machine. Additionally, we can see that esm-infra-legacy will be a standalone service, meaning that users won't need to have esm-infra already enabled before enabling that service. This also means that both esm-infra and esm-infra-legacy are completely independent of one another, in the sense that changes on esm-infra should not affect esm-infra-legacy and vice versa. However, there is one situation where esm-infra will impact esm- infra-legacy. We will better discuss that on the discussion section. Finally, users should now see esm-infra-legacy output on status from now on, when attached and unattached. Users will also see that service on the output of ua help as well. [Test cases] The Trusty version of the client only has a subset of the integration tests we have on the other releases that support the client. Due to that, we will need to perform several manual tests to guarantee that the support for esm-infra-legacy is working and we are not affecting existing customers. Therefore, besides running the current test for the Trusty package, we will run the following tests: * Enabling esm-infra-legacy - - User is attached to a subscription that is entitled to esm-infra-legacy - - User can see esm-infra-legacy on ua help - - User can enable esm-infra-legacy through ua enable esm-infra-legacy - - User see esm-infra-legacy as enabled on the output of ua status - - User can see esm-infra-legacy enabled on the output of apt-cache policy - - User can disable esm-infra-legacy - - User can see that esm-infra-legacy is disabled on the machine - - User enables esm-infra-legacy again - - User can detach with esm-infra-legacy enabled on the machine + - User is attached to a subscription that is entitled to esm-infra-legacy + - User can see esm-infra-legacy on ua help + - User can enable esm-infra-legacy through ua enable esm-infra-legacy + - User see esm-infra-legacy as enabled on the output of ua status + - User can see esm-infra-legacy enabled on the output of apt-cache policy + - User can disable esm-infra-legacy + - User can see that esm-infra-legacy is disabled on the machine + - User enables esm-infra-legacy again + - User can detach with esm-infra-legacy enabled on the machine * Interactions with esm-infra - - User is attached to a subscription that is entitled to both esm-infra and esm-infra-legacy - - User has esm-infra enabled - - User can enable esm-infra-legacy - - User can see both esm-infra and esm-infra-legacy as enabled on status - - User can disable esm-infra-legacy and not affect esm-infra + - User is attached to a subscription that is entitled to both esm-infra and esm-infra-legacy + - User has esm-infra enabled + - User can enable esm-infra-legacy + - User can see both esm-infra and esm-infra-legacy as enabled on status + - User can disable esm-infra-legacy and not affect esm-infra * User that is not entitled to esm-infra-legacy - - User is attached to a subscription - - User cannot enable esm-infra-legacy - - User can see the service on status, which will show the service as not entitled + - User is attached to a subscription + - User cannot enable esm-infra-legacy + - User can see the service on status, which will show the service as not entitled * User that buys access to esm-infra-legacy - - User is already attached to a subscription - - User runs ua refresh - - User enable esm-infra-legacy - - User can see that the service is enabled on ua status + - User is already attached to a subscription + - User runs ua refresh + - User enable esm-infra-legacy + - User can see that the service is enabled on ua status * User that is attaching a new subscription - - User subscription can be either entitled or not to esm-infra-legacy - - In both situations, when the user runs ua attach, they will verify that: - - esm-infra will be enabled by default - - esm-infra-legacy should not be enabled by default + - User subscription can be either entitled or not to esm-infra-legacy + - In both situations, when the user runs ua attach, they will verify that: + - esm-infra will be enabled by default + -
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
** 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/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I have a VM where this can be reproduced, if anyone is interested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
> Does running `mount -vvv ...` provide more information? Nope, same as single -v: root@nfs:~# mount /mnt/nfs_home -vvv mount.nfs: timeout set for Mon Apr 8 15:48:10 2024 mount.nfs: trying text-based options 'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed for /mnt/nfs_home -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
-
[ Test Plan ]
This update adds a new autopkgtest to the package, which tests both
gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
and gssapi-keyex, which, before this update, does not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
-
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that change
is already present in the upstream code, and we are just updating it in
the new gssapi-keyex code (introduced by the distro[1] patch, already
present). Therefore, mistakes here should manifest themselves just in
the gssapi-keyex code, which wasn't working anyway. Effectively, though,
we are enabling a new authentication mechanism in sshd, one that was not
supposed to have been removed, but was broken by mistake.
-
[ Other Info ]
The fact no-one noticed this problem for more than two years could be
telling that there are not many users of this authentication mechanism
out there. The same applies to debian: it has also been broken for a
while there. Maybe we should drop it for future ubuntu releases, since
upstream refuses to take it in.
+
+
+ 1.
https://git.launchpad.net/ubuntu/+source/openssh/tree/debian/patches/gssapi.patch
+
[ Original Description ]
The Authmethod struct now have 4 entries but the initialization of the
method_gsskeyex in the debian/patches/gssapi.patch only have 3 entries.
The struct was changed in upstream commit
dbb339f015c33d63484261d140c84ad875a9e548 as
===
@@ -104,7 +104,8 @@ struct Authctxt {
struct Authmethod {
char*name;
- int (*userauth)(struct ssh *);
+ char*synonym;
+ int (*userauth)(struct ssh *, const char *);
int *enabled;
};
===
The incorrect code does
===
+Authmethod method_gsskeyex = {
+ "gssapi-keyex",
+ userauth_gsskeyex,
+ _authentication
+};
===
but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex
This is now (change from Focal) causing gssapi-keyex to be disabled.
===
lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
===
apt-cache policy openssh-server
openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
*** 1:8.9p1-3ubuntu0.6 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-updates/main amd64 Packages
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu
jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
1:8.9p1-3 500
500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main
amd64 Packages
===
** Description changed:
[ Impact ]
The gssapi-keyex authentication mechanism has been inadvertently broken
in openssh. It comes from a distro patch[1], and while the patch still
applied, it was no longer correct.
Without the fix, sshd will fail to start if gssapi-keyex is listed in
the AuthenticationMethods of the server, and if not, sshd will still
start, but gssapi-keyex will not be available.
[ Test Plan ]
- This update adds a new autopkgtest to the package, which tests both
- gssapi-with-mic ("normal" gssapi, which is not affected by this bug),
- and gssapi-keyex, which, before this update, does not work.
+ This update, besides fixing the patch, also adds a new autopkgtest to
+ the package, which tests both gssapi-with-mic ("normal" gssapi, which is
+ not affected by this bug), and gssapi-keyex, which, before this update,
+ did not work.
The test plan is to run the new ssh-gssapi autopkgtest and verify it
succeeds.
[ Where problems could occur ]
ssh is a critical piece of infrastructure, and problems with it could
have catastrophic consequences. The service itself has a test command
before it starts up to verify the syntax of the config file, but that
test is not applied on shutdown, so a restart with an invalid config
file could still leave sshd dead.
The patch adds a change to an authentication structure, but that change
is already present in the upstream code, and we are
[Bug 2060538] [NEW] rpcdebug segfault in s390x
Public bug reported:
Just running rpcdebug in noble on s390x causes a segfault. In gdb we
see:
Breakpoint 1, main (argc=1, argv=0x3ffa498) at rpcdebug.c:57
57 cdename = malloc(strlen(basename(argv[0])));
(gdb) n
58 if (cdename == NULL) {
(gdb) n
62 strcpy(cdename, basename(argv[0]));
(gdb) n
*** buffer overflow detected ***: terminated
It's the _FORTIFY_SOURCE=3 that is catching it, but only on s390x. Looks like
an off-by-one.
From the strcpy() manpage:
strcpy()
These functions copy the string pointed to by src, into a string at the buffer
pointed to by dst. The programmer is responsible for allocating a destination
buffer large enough, that is, strlen(src) + 1. For the difference between the
two functions, see RETURN VALUE.
Patch:
--- a/tools/rpcdebug/rpcdebug.c
+++ b/tools/rpcdebug/rpcdebug.c
@@ -54,7 +54,7 @@ main(int argc, char **argv)
char * module = NULL;
int c;
- cdename = malloc(strlen(basename(argv[0])));
+ cdename = malloc(strlen(basename(argv[0])) + 1);
if (cdename == NULL) {
fprintf(stderr, "failed in malloc\n");
exit(1);
** Affects: nfs-utils (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/2060538
Title:
rpcdebug segfault in s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060538/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060536] [NEW] DEP8 failures in noble, all arches
Public bug reported:
https://autopkgtest.ubuntu.com/packages/c/crmsh/noble/amd64
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/c/crmsh/20240407_073428_9de69@/log.gz
Only test failing in testsuite.sh:
2859s __ TestUtils.test_findln_by_timestamp
__
2859s
2859s self =
2859s
2859s def test_findln_by_timestamp(self):
2859s target_time = "Apr 03 13:10"
2859s target_time_stamp = crmutils.parse_to_timestamp(target_time+'
2023')
2859s with open('pacemaker.log') as f:
2859s data = f.read()
2859s constants.STAMP_TYPE = utils.determin_log_format(data)
2859s pacemaker_file_path = "pacemaker.log"
2859s result_line = utils.findln_by_timestamp(data, target_time_stamp,
pacemaker_file_path)
2859s > result_line_stamp =
utils.get_timestamp(data.split('\n')[result_line-1], pacemaker_file_path)
2859s E TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'
2859s
2859s test_report_utils.py:825: TypeError
** Affects: crmsh (Ubuntu)
Importance: Undecided
Status: New
** Affects: crmsh (Debian)
Importance: Unknown
Status: Unknown
** Tags: update-excuse
** Bug watch added: Debian Bug tracker #1068562
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068562
** Also affects: crmsh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068562
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/2060536
Title:
DEP8 failures in noble, all arches
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/2060536/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - Just filing the bug now to keep track of it. No troubleshooting done - yet. - https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x Looks like it has been failing for a long time already. Log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz 339s autopkgtest [14:41:04]: test local-server-client: [--- 340s Killed 340s autopkgtest [14:41:05]: test process requested reboot with marker boot1 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 372s FAIL: nfs_home not mounted 373s autopkgtest [14:41:38]: test local-server-client: ---] 373s local-server-client FAIL non-zero exit status 1 - and - 934s autopkgtest [14:50:59]: test kerberos-mount: [--- 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', 935s master key name 'K/M@DEP8' 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "nfs/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "host/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 936s exporting *:/storage 938s mount.nfs: mount system call failed for /mnt 938s umount: /mnt: not mounted. 938s autopkgtest [14:51:02]: test kerberos-mount: ---] 939s kerberos-mount FAIL non-zero exit status 32 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I don't think it's Kerberos related. The manual reproducer is a plain mount localhost, without Kerberos. The same simple localhost setup was working in mantic. I then dist upgraded the VM to noble, and it started failing. On Sun, 7 Apr 2024, 18:10 Bryce Harrington, <2060...@bugs.launchpad.net> wrote: > Does running `mount -vvv ...` provide more information? > > I notice of the 3 test cases in the dep8 that it's the 2 NFSv4 w/ > kerberos ones failing, and the simple nfsv3 one passes. Could it be > something to do with kerberos or its configuration? Like, could it be > authorizing a network IP other than 127.0.0.1? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2060217 > > Title: > NFSv4 fails to mount in noble/s390x > > Status in nfs-utils package in Ubuntu: > Triaged > > Bug description: > Just filing the bug now to keep track of it. No troubleshooting done > yet. > > https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x > > Looks like it has been failing for a long time already. > > Log: https://autopkgtest.ubuntu.com/results/autopkgtest- > noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz > > 339s autopkgtest [14:41:04]: test local-server-client: > [--- > 340s Killed > 340s autopkgtest [14:41:05]: test process requested reboot with marker > boot1 > 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 > seconds... > 372s FAIL: nfs_home not mounted > 373s autopkgtest [14:41:38]: test local-server-client: > ---] > 373s local-server-client FAIL non-zero exit status 1 > > > and > > > 934s autopkgtest [14:50:59]: test kerberos-mount: > [--- > 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', > 935s master key name 'K/M@DEP8' > 935s Authenticating as principal root/admin@DEP8 with password. > 935s Principal "nfs/nfs-server.dep8@DEP8" created. > 935s Authenticating as principal root/admin@DEP8 with password. > 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption > type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. > 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption > type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. > 935s Authenticating as principal root/admin@DEP8 with password. > 935s Principal "host/nfs-server.dep8@DEP8" created. > 935s Authenticating as principal root/admin@DEP8 with password. > 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption > type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. > 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption > type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. > 936s exporting *:/storage > 938s mount.nfs: mount system call failed for /mnt > 938s umount: /mnt: not mounted. > 938s autopkgtest [14:51:02]: test kerberos-mount: > ---] > 939s kerberos-mount FAIL non-zero exit status 32 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=nfs-utils; > component=main; status=Triaged; importance=High; assignee=None; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ahasenack bryce > Launchpad-Bug-Reporter: Andreas Hasenack (ahasenack) > Launchpad-Bug-Modifier: Bryce Harrington (bryce) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: ahasenack > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
I enabled rpc debugging with rpcdebug (after fixing an off-by-one strcpy error), but the logs don't mean much to me. ** Attachment added: "rpcdebug.log" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+attachment/5761997/+files/rpcdebug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: NFSv4 fails to mount in noble/s390x
Verbose mount: # mount localhost:/home /mnt/nfs_home -v mount.nfs: timeout set for Sun Apr 7 19:09:07 2024 mount.nfs: trying text-based options 'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1' mount.nfs: mount(2): Input/output error mount.nfs: mount system call failed for /mnt/nfs_home -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060217 Title: NFSv4 fails to mount in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: DEP8 failures in noble/s390x
The tests are correct, I can reproduce it in s390x. Any v4.* mount
fails, but v3 works:
root@nfs:~# mount localhost:/home /mnt/nfs_home -o vers=4.2
mount.nfs: mount system call failed for /mnt/nfs_home
root@nfs:~# mount localhost:/home /mnt/nfs_home -o vers=4.1
mount.nfs: mount system call failed for /mnt/nfs_home
root@nfs:~# mount localhost:/home /mnt/nfs_home -o vers=4.0
mount.nfs: mount system call failed for /mnt/nfs_home
root@nfs:~# mount localhost:/home /mnt/nfs_home -o vers=4
mount.nfs: mount system call failed for /mnt/nfs_home
root@nfs:~# mount localhost:/home /mnt/nfs_home -o vers=3
root@nfs:~#
And no version at all also fails:
root@nfs:~# mount localhost:/home /mnt/nfs_home
mount.nfs: mount system call failed for /mnt/nfs_home
dmesg is clean.
Strace shows, for that last attempt with no version specified:
1998 mount("localhost:/home", "/mnt/nfs_home", "nfs", 0,
"vers=4.2,addr=127.0.0.1,clientad"...) = -1 EIO (Input/output error)
** Summary changed:
- DEP8 failures in noble/s390x
+ NFSv4 fails to mount in 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/2060217
Title:
NFSv4 fails to mount in noble/s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046439] Update Released
The verification of the Stable Release Update for qemu 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/2046439 Title: Wrong code execution of s390x code with qemu TCG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2046439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Launchpad is/was sick... 504 Gateway Time-out\\nThe server didn\'t respond in time.\ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058576] Re: FTBFS: armhf: build-time test failures
Uploaded to noble, it's built in proposed \o/ ** Changed in: sssd (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/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
** Description changed: + [ Impact ] + + The "pro" command-line tool has a "version" parameter that needs to be + kept in sync with the package version from d/changelog. This has been + forgotten in 31.2.1, and we decided to release 31.2.2 with that fix. + + [ Test Plan ] + + Install ubuntu-advantage-tools and run the command: + + pro version + + Its output must match the package version from: + + dpkg -l ubuntu-advantage-tools + + + [ Where problems could occur ] + + The most common problem here is to rebuild the package with a new + version, or new suffix, and forgetting to update version.py again. + + Another problem is that the version.py update could be the wrong + version, but the test plan is looking for that exactly. + + + [ Other Info ] + + Not at this time. + + + [ Original Description ] + https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.1 missed a corresponding uaclient/version.py version update to match d/changelog. It was fixed in https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/31.2.2 without a changelog reference, and we should use this bug for the same change for the upcoming SRU in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2057937 Version 31.2.1 was not technically released as an SRU yet, it briefly existed in the unapproved queues without the uaclient/version.py fix, but was rejected in time. Technically we could add the corresponding version.py fix and use 31.2.1 in the SRUs, but we prefer to keep the stable releases using the same version everywhere, including devel. So let's make a 31.2.2 for the SRU, matching noble, and use this bug to track that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
The software-properties autopkgtests are failing on adding a ppa. I can reproduce this locally every now and then (not always, but soon enough), with this command, on noble: sudo rm /etc/apt/sources.list.d/ubuntu-support-team-ubuntu-software- properties-autopkgtest-mantic.sources ; sudo add-apt-repository ppa:ubuntu-support-team/software-properties-autopkgtest -y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058934] Re: Missing version.py update
Thank you, I'll add a test case to run "pro --version" and compare with the package's version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] Re: DEP8 failures in noble/s390x
** Changed in: nfs-utils (Ubuntu) Status: New => Triaged ** Changed in: nfs-utils (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/2060217 Title: DEP8 failures in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058964] Re: proposed-migration for autofs 5.1.9-1ubuntu2
After the fix for sssd[1] landed, I triggered a rebuild for autofs[2], and that worked. Closing this bug. 1. https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 2. https://launchpad.net/ubuntu/+source/autofs/5.1.9-1ubuntu3 ** Changed in: autofs (Ubuntu) Status: In Progress => 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/2058964 Title: proposed-migration for autofs 5.1.9-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/2058964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059078] Re: proposed-migration for faketime 0.9.10-2.1ubuntu1
I added an sssd task due to the workaround we had to add to it in https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576 (we don't install faketime). Should faketime be fixed, then we can revert that change in sssd. ** Also affects: sssd (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/2059078 Title: proposed-migration for faketime 0.9.10-2.1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2059078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059952] Re: pro sometimes runs before cloud-config.service
** Description changed: [ Impact ] Currently, the Pro client support a daemon named ubuntu-advantage.service that performs two actions: * Actively look for Pro licenses on Azure and GCP images to perform an auto-attach * Retry auto-attach on Pro images if that command fails on boot Therefore, this daemon is only being activated on generic Azure and GCP images and all Pro cloud images. This daemon was originally setup to run after the cloud-config.service. However, due to a race condition, this is no longer happening. Right now, we manually check in the daemon code to see if the cloud-config service has finished. Unfortunately, this new logic now breaks the current Pro setup through cloud-init userdata in both GCP and Azure Pro cloud images. That is because our daemon is now running before cloud-init has even started running. This means that the daemon will perform the attach and not cloud-init itself. This will be clearer, in the following example: Let's imagine this situation where a user is launching a Pro GCP image: 1) User provides the following cloud-init userdata to the cloud image before booting it: #cloud-config ubuntu_advantage: enable: [] This means that the user wants no services to be enabled, but still want to attach to the Pro license. - 2) Our daemon starts running before cloud-init has even started + 2) Our daemon starts running before cloud-config has even started 3) Our daemon see the cloud-config.service as inactive and proceeds normally 4) Our daemon identifies that the user is running on a GCP instance and there is a valid Pro license for it. 5) Due to that, our daemon auto-attach the machine completely ignoring the cloud-init directives. Therefore, to fix that issue we need to guarantee that we will only execute the daemon, if and only if, cloud-init has already started. That is because, on this situation, the cloud-config.service will already perform the attach operation following the user directives. When the daemon starts running, it will see that the image is already attached and do nothing. Finally, given this scenario, this bug is only affecting GCP/Azure Pro images, as these are the only ones that will be able to reach the flow described here. [Discussion] To address that issue, we are now also checking if the cloud-init service has already started if we detect that cloud-config service is inactive. If it isn't, the daemon will sleep for an specific amount of time before trying again. [ Test Plan ] Since this is a first boot issue, we will need to create a custom image with the package in proposed. Then, we need to guarantee that Pro configuration delivered through cloud-init is being honored when we launch the image. Additionally, it is worth noting that we cannot reproduce this issue on a VM easily. That is because, we would need "mock" the VM to pass as one of the affected clouds and also add a valid Pro license to it. However, CPC is already aware of this issue and will help us creating the test plan here. [ Where problems could occur ] We are updating the cloud-init wait logic on the daemon. This could potentially make our daemon to not start. However, since we are just now waiting on the base cloud-init.service to start and we have already tested this solution in a custom image, we believe this is a low risk for this fix. [ Original Description ] We have recently updated the Pro to not strictly run after cloud-config.service. If cloud-config.service has not been started when pro runs, it can complete before cloud-config.service begins and thus the user-specificed pro configuration will be ignored since the instance is already attached. When cloud-config.service has yet to run, ubuntu-advantage.service should wait until it's finished before running. ** Description changed: [ Impact ] Currently, the Pro client support a daemon named ubuntu-advantage.service that performs two actions: * Actively look for Pro licenses on Azure and GCP images to perform an auto-attach * Retry auto-attach on Pro images if that command fails on boot Therefore, this daemon is only being activated on generic Azure and GCP images and all Pro cloud images. This daemon was originally setup to run after the cloud-config.service. However, due to a race condition, this is no longer happening. Right now, we manually check in the daemon code to see if the cloud-config service has finished. Unfortunately, this new logic now breaks the current Pro setup through cloud-init userdata in both GCP and Azure Pro cloud images. That is because our daemon is now running before cloud-init has even started running. This means that the daemon will perform the attach and not cloud-init itself. This will be clearer, in the following example: Let's imagine this situation where a user is
[Bug 2058576] Re: FTBFS: armhf: build-time test failures
** Bug watch added: Debian Bug tracker #1068063 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063 ** Also affects: sssd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068063 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/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060217] [NEW] DEP8 failures in noble/s390x
Public bug reported: Just filing the bug now to keep track of it. No troubleshooting done yet. https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x Looks like it has been failing for a long time already. Log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/s390x/n/nfs-utils/20240404_145924_ef255@/log.gz 339s autopkgtest [14:41:04]: test local-server-client: [--- 340s Killed 340s autopkgtest [14:41:05]: test process requested reboot with marker boot1 364s autopkgtest-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds... 372s FAIL: nfs_home not mounted 373s autopkgtest [14:41:38]: test local-server-client: ---] 373s local-server-client FAIL non-zero exit status 1 and 934s autopkgtest [14:50:59]: test kerberos-mount: [--- 935s Initializing database '/var/lib/krb5kdc/principal' for realm 'DEP8', 935s master key name 'K/M@DEP8' 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "nfs/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal nfs/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Authenticating as principal root/admin@DEP8 with password. 935s Principal "host/nfs-server.dep8@DEP8" created. 935s Authenticating as principal root/admin@DEP8 with password. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 935s Entry for principal host/nfs-server.dep8 with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab. 936s exporting *:/storage 938s mount.nfs: mount system call failed for /mnt 938s umount: /mnt: not mounted. 938s autopkgtest [14:51:02]: test kerberos-mount: ---] 939s kerberos-mount FAIL non-zero exit status 32 ** Affects: nfs-utils (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/2060217 Title: DEP8 failures in noble/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2060217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052789] Update Released
The verification of the Stable Release Update for livecd-rootfs 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/2052789 Title: AppArmor profiles missing in kernel 5.15.0-1051+ release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058576] Re: FTBFS: armhf: build-time test failures
It is enabled: Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports Suites: noble noble-updates noble-backports noble-proposed Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Or is there some other trick specific to the state noble is in now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058576 Title: FTBFS: armhf: build-time test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2058576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
