Thank you for taking the time to file a bug report.
In order to reproduce the bug you faced, could you please share your
config files? OpenSSH and OpenVPN ones. Otherwise we cannot do anything.
Since there is not enough information in your report to begin triage or to
differentiate between a
I also tried to reproduce the mentioned failure in a clean Xenial
container with no success. Since this is an old bug and no one replied
to it for years I am removing the server-next tag.
** Tags removed: server-next
--
You received this bug notification because you are a member of Kernel
Thanks for the patch Sergio! Also for the well explained reason why
those patches are needed. I did not build the package since it takes too
long but I see it built fine in the PPA so far (I'd wait until the
builds end in all architectures before uploading it to the archive).
One thing that you
@family-gan are you saying this is an issue in Ubuntu Impish (21.10)? It
seems to be already fixed in supported releases. Could you share any
steps to reproduce it? If you consider the issue you are facing
different than the one discussed in this bug please consider filing a
separate bug.
--
You
The fix for this bug is already verified but the same upload also
contains the fix for this bug which is still not verified:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482
That's why it is blocked in jammy-proposed at the moment.
--
You received this bug notification because
There is no task for this bug targeting Ubuntu Focal (20.04), that's why
it is not fixed there. Apparently, no one reported this issue there,
only in Jammy (22.04). @shadowlmd could you confirm if you are facing
the very same issue described on this bug in Focal? If it is another
issue please file
@mrichtarsky from the logs, mysql was not able to redo the actions
during the upgrade because the size of the ib_redo6 file was not
multiple of innodb_page_size. However, the default of innodb_page_size
is 16kb (https://dev.mysql.com/doc/refman/8.0/en/server-status-
Thanks for taking the time to report this bug an trying to make Ubuntu
better.
Is this the only relevant message you found in the syslog? Is this error
causing some unexpected behavior apart from this message in the syslog?
You mentioned the error in the log but did not mention what is the
impact
According to the Debian bug this seems to be a bug in linux and not in
samba and apache2.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
This bug does not seem to be caused by containerd, so I am marking its
tasks as Invalid. If you disagree, please say so.
** Changed in: containerd (Ubuntu Focal)
Status: Confirmed => Invalid
** Changed in: containerd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
FWIW the packaging changes look good to me. But I'd like raof (or
someone with more knowledge about this) to check koba's reply before
uploading the package.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
Chris reviewed your proposed debdiff almost 2 months ago, are you
planning to address the comments? I am re-checking this because it is in
our general sponsorship queue. If you do not need sponsorship for this
upload, please, unsubscribe ~ubuntu-sponsors.
--
You received this bug notification
Public bug reported:
The tuned package has some plugins which rely on the perf python module
[1], and right now they are not working because we do not have the perf
python module available in Ubuntu.
Initially, this was reported in this other bug [2], but it seems the
scope of that bug is bigger
Thanks for the patch @Kai-Heng! I took a look and in general it looks
good, but I'd like to ask you to add some DEP-3 headers [1] to your
patch, that will give us (packagers) more context when revisiting this
package for whatever reason.
Now a personal opinion, I like when the patch file name is
14 matches
Mail list logo
