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
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));
|^~~~
** 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
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
** 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:
nee: 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 ab
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
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
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
** 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
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
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
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
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
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
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
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
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
> 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.
**
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
)
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
** 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)
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)
--
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
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
--
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
--
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
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
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
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
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
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
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
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
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
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
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
** 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
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
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:
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 (>=
*** 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
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.
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.
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.
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
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
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,
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.
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
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
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
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
> # 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,
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
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
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
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
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
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
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
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
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
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.
: 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)
Milest
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:
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
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.
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
> 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
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
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
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
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
** 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
** 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:
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
> 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
** 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
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
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
** 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
-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
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
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
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
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
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
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:
** 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
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
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
** 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
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
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
** 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
** 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
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-
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
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
601 - 700 of 11569 matches
Mail list logo
