*** This bug is a duplicate of bug 1851858 ***
https://bugs.launchpad.net/bugs/1851858
** This bug has been marked a duplicate of bug 1851858
adds ESM to sources.list.d unconditionally, despite it being x86-only
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed
mysql-server-8.0 package post-installation script subprocess returned error
exit status 1
+ NO_AUTO_CREATE_USER removed in mysql-8, broke upgrade
--
You received this bug notification because
*** This bug is a duplicate of bug 1851741 ***
https://bugs.launchpad.net/bugs/1851741
** This bug has been marked a duplicate of bug 1851741
package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess was
*** This bug is a duplicate of bug 1850895 ***
https://bugs.launchpad.net/bugs/1850895
** This bug has been marked a duplicate of bug 1850895
package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il
sottoprocesso installato pacchetto mysql-hostname-8.0 script
** Summary changed:
- package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade: installed
mysql-server-8.0 package post-installation script subprocess was killed by
signal (Terminated)
+ Unable to lock ./ibdata1 error: 11
--
You received this bug notification because you are a
** Summary changed:
- package mysql-hostname-8.0 8.0.17-0ubuntu2 failed to install/upgrade: il
sottoprocesso installato pacchetto mysql-hostname-8.0 script post-installation
ha restituito lo stato di errore 1
+ query_cache_limit removed in mysql-8, upgrade broke
--
You received this bug
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1851858
Title:
adds ESM to
** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-client/issues #911
https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/911
** Also affects: ubuntu-advantage-script via
https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/911
Importance: Unknown
** Changed in: bind9 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1850699
Title:
Please remove net-tools from bind9 Depends (replaced by
Checking smb.conf with testparm
WARNING: The "idmap uid" option is deprecated
WARNING: The "idmap gid" option is deprecated
Load smb config files from /etc/samba/smb.conf
WARNING: The "idmap uid" option is deprecated
WARNING: The "idmap gid" option is deprecated
Loaded services file OK.
'winbind
Public bug reported:
There are DEP8 failures with the new lz4 package on focal-proposed,
1.9.2-1
[ 78%] main.mysqlpump_basic_lz4 [ fail ]
Test ended at 2019-11-04 20:04:36
CURRENT_TEST: main.mysqlpump_basic_lz4
Dump progress: 1/2 tables, 0/9 rows
mysqlpump: [NOTE]
Public bug reported:
nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf:
autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest
autopkgtest [09:46:25]: test command1: [---
[info] Testing github.com/theupdateframework/notary...
[info] Source code
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you
@lars, is this something that should be taken care of by the package
during upgrades?
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1850998
@lars, is this something that should be taken care of by the package
during upgrades?
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to mysql-8.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1850895
** Tags removed: server-triage-discuss ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage
Passing by this bug after 180 days of no activity, no changes.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1811496
Title:
Make grub-ipxe work under UEFI
To manage notifications about
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
To manage notifications about
Thanks for filing this bug in ubuntu.
It's unclear why this error happened. May I suggest you run the
following to see if that fixes it:
sudo apt-get update
sudo apt-get -f install
You could also try to reinstall the libmspack package:
sudo apt-get install --reinstall libmspack0:i386
I just
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1837734
Title:
libnss3
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
** Changed in: nmap (Ubuntu Xenial)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to nmap in Ubuntu.
https://bugs.launchpad.net/bugs/1684304
Title:
nmap man page lacks port state headlines
To manage
This is the debian bug report: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=454595
** Bug watch added: Debian Bug tracker #454595
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454595
** Also affects: spamassassin (Debian) via
Looks like this bug fell through the cracks.
It's still valid, and easy to reproduce in a VM:
$ multipass launch daily:xenial -n x1
$ multipass exec x1 cat /sys/class/net/ens3/speed
-1
And if you have munin-node installed:
$ multipass exec x1 sudo munin-run if_ens3 config|tail -n 3
up.max
** Changed in: munin (Ubuntu Xenial)
Status: New => Triaged
** Changed in: munin (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Thanks for filing this bug in Ubuntu.
I'll note that both Precise (12.04) and Trusty (14.04) have reached
their normal support lifespan, and are nowadays only supported via ESM
(https://ubuntu.com/esm).
That being said, I suspect you had a problem with the many apache
modules that you have
Thanks for filing this bug in Ubuntu.
Subscribing Stefan Bader, who has handled xen uploads/bugs in the past,
to see if he has any insights.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to xen in Ubuntu.
Thanks for filing this bug in Ubuntu.
This seems to be the error:
Renaming removed key_buffer and myisam-recover options (if present)
ERROR: Unable to start MySQL server:
2019-11-02T02:24:50.952742Z 0 [Warning] [MY-011068] [Server] The syntax
'expire-logs-days' is deprecated and will be removed
*** This bug is a duplicate of bug 1850998 ***
https://bugs.launchpad.net/bugs/1850998
** This bug has been marked a duplicate of bug 1850998
package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess returned
*** This bug is a duplicate of bug 1850998 ***
https://bugs.launchpad.net/bugs/1850998
** This bug has been marked a duplicate of bug 1850998
package mysql-server-8.0 8.0.17-0ubuntu2 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess returned
Thanks for filing this bug in Ubuntu, and for your troubleshooting and
the debian MR.
The logrotate systemd service is actually triggered by a timer, and not
by a reboot specifically. You can view when it last run, and when it
will run, with the command "systemctl list-timers".
Regarding your
Thanks for filing this bug in Ubuntu, and the upstream one as well.
Upstream doesn't seem very keen in making such a change for the general
case. Maybe if you could propose a command-line option that would add
it?
** Bug watch added: github.com/sosreport/sos/issues #1844
Focal has version 3.8, so the main bug task is fix released.
If you need a fix for the bug in previous versions of Ubuntu, then the
relevant procedure is documented here:
https://wiki.ubuntu.com/StableReleaseUpdates
However, I'm not sure this bug would qualify under that policy,
Thanks for filing this bug in Ubuntu.
Could you please share the following logs:
- /var/log/dist-upgrade/*
- /var/log/dpkg.log
- /var/log/apache2/error.log
I'm trying to determine exactly from which version of each package did
you upgrade, and if there were any errors during that process.
You
Thanks for filing this bug in Ubuntu.
I see the following messages in the mysql log file:
2019-11-01T08:12:31.317917Z 0 [Warning] [MY-011068] [Server] The syntax
'expire-logs-days' is deprecated and will be removed in a future release.
Please use binlog_expire_logs_seconds instead.
Thanks for filing this bug in Ubuntu.
The logs just confirm that samba-common's postinst script failed, but do
not show why. Your smb.conf file looks correct with no syntax errors.
There is not enough information in this bug report to figure out what
happened. I suggest you investigate the samba
** Changed in: python-django (Ubuntu)
Status: New => Triaged
** Changed in: python-django (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to python-django in Ubuntu.
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848902
** Changed in: strongswan (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1772705
Title:
IKEv2 VPN connections fail to use DNS servers
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Title:
sssd offline on boot, stays offline forever
To manage notifications about this bug go to:
Good to know. I also couldn't reproduce it just by using those commands,
some more setting up is probably needed. If we get reproducible steps,
we might be able to identify the commit (or series of commits) that
fixed it after 1.1.14. I took a quick look at the ChangeLog file but
failed to spot
For reference:
https://wiki.ubuntu.com/DebuggingInstallationIssues#triggers_ci_file_contains_unknown_directive_syntax
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1851302
Title:
Error
*** This bug is a duplicate of bug 1851302 ***
https://bugs.launchpad.net/bugs/1851302
** This bug has been marked a duplicate of bug 1851302
Error in update
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
Thanks for filing this bug in ubuntu.
You seem to have a corrupted trigger file. What's the contents of
/var/lib/dpkg/info/samba-libs.triggers? It might have a slightly
different name, like have an architecture as part of the name.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
Bug still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/810736
Title:
logrotate script needs to notify all samba processes when logs are
rotated
To manage notifications
This bug is still in our queue.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1670450
Title:
samba4 bind dlz module stops working on rndc reload
To manage notifications about this bug go
Thanks for filing this bug in Ubuntu.
Do you mean that in your current disco system, dist-upgrade does not
install all available updates? Or is this error something you only get
when running do-release-upgrade?
Could you please also attach the release upgrader logs from /var/log
/dist-upgrade?
Thanks for filing this bug in Ubuntu.
The package you were upgrading from, 7.70-2, was apparently never
published in Ubuntu, according to the list here:
https://launchpad.net/ubuntu/+source/nmap/+publishinghistory
Was that a local build perhaps?
** Changed in: nmap (Ubuntu)
Status: New
Thanks for filing this bug in Ubuntu.
It's not clear why the postfix postinst script failed. I suggest you
look in /var/log/mail.log and /var/log/mail.err to see if there is more
helpful information there.
Since there is not enough information in this bug report to diagnose the
problem, I'll
I personally think what we have is good enough. If someone thinks
otherwise, please file a merge request in https://salsa.debian.org/php-
team/php-defaults
** Changed in: php7.2 (Ubuntu)
Status: Triaged => Opinion
** Changed in: php7.3 (Ubuntu)
Status: Triaged => Opinion
--
You
I agree. Do you have a way to reproduce this somewhat reliably?
** Changed in: sssd (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1723350
Salsa MR: https://salsa.debian.org/postfix-team/postfix-
dev/merge_requests/3
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To manage
I have a pass with python3 for 3.4.7-1 in debian/sid. Let me clean that
branch up now and make a MR in salsa.
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1845334/+attachment/5302040/+files/log
--
You received this bug notification because you are a
Looking at this now.
** Changed in: postfix (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To
I'm satisfied with the results, also considering test (5) done in the
other bug. Just to be sure, I also tried it via dist-upgrade. That is a
bit more hacky, as it involves changing s/precise/trusty/ in
sources.list snippets, ignoring gpg errors (as precise doesn't have the
gpg key for trusty-esm)
Test 4:
>From a fresh trusty instance, which has uat installed (from updates):
a) enable esm (via ubuntu-advantage enable-esm), upgrade to proposed
b) upgrade to proposed, enable esm (via ua attach)
Result: PASS
Details:
In the end, both instances have the same proposed package:
$ lxc exec
Test 3:
>From a fresh trusty system, no uat installed, no ubuntu-minimal installed
a) install uat from updates, enable esm, upgrade to proposed
b) install uat from proposed, enable esm (via ua attach)
Result: PASS
Details:
At the end, confirmed that both chroots have esm enabled and with a
Test 2:
a) fresh install from t-updates, go to t-proposed
b) fresh install from t-proposed directly
Result: PASS
Details:
At the end, we have two chroots: /tank/trusty-2a and /tank/trusty-2b
# chroot /tank/trusty-2a apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed:
addendum for test 2:
# diff -uNr /tank/trusty-2{a,b}/ 2>/dev/null|diffstat
root/.bash_history |2
var/cache/apt/archives/ubuntu-advantage-tools_10ubuntu0.14.04.4_all.deb |binary
var/cache/apt/pkgcache.bin
Test 1: basic attach w/ proposed
Result: PASS
Details:
$ lxc launch ubuntu-daily:trusty t1
Creating t1
Starting t1
# enable proposed, update, check
$ lxc exec t1 apt-get update
$ lxc exec t1 apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Repeating tests 1-4 here.
Test number 5, which failed in the previous verification, can be seen
done in bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1850672. It was done with do-release-upgade, which is how I
expect users would upgrade from precise, and I took care
Trusty verification, in two parts:
a) following the [testing] section, i.e., upgrading from precise, to trusty,
then to trusty-updates
b) almost the same setup, but upgrading from precise to trusty with the u-a-t
proposed package, without going through the intermediary current u-a-t from
trusty verification succeeded
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1850672
The package https://launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/19.6~ubuntu14.04.3 built just fine, confirming the fix.
trusty verification succeeded.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you
b) almost the same setup, but upgrading from precise to trusty with the
u-a-t proposed package, without going through the intermediary current
u-a-t from trusty-updates.
$ lxc launch ubuntu-daily:precise p1
$ lxc exec p1 ubuntu-advantage enable-esm $u:$p
Running apt-get update...
Ubuntu ESM
a) upgrading from precise, to trusty, then to trusty-updates
$ lxc launch ubuntu-daily:precise p1
Creating p1
Starting p1
$ lxc exec p1 ubuntu-advantage enable-esm $u:$p
Running apt-get update...
Ubuntu ESM repository enabled.
# esm enabled, positive pinning:
$ lxc exec p1 apt-cache policy|grep
Please remember that in order for this update to be released, the tags
need to be updated, as explained in comment #16.
Thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
Importance: Undecided => High
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Server,
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from
there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug
#1832757.
The reason is
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Status: New => In Progress
** Changed in:
Public bug reported:
When enabling ESM on precise, then upgrading that to current trusty, and
from there to the proposed new trusty client (see #1832757), ESM gets
disabled.
Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage-
client/issues/899
The reason is that d/postinst, when
An 19.6~ubuntu14.04.3 upload with the fix will be done shortly.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1832757
Title:
Update ubuntu-advantage-client
To manage
Test (5a) failed. The scenario is an upgrade from precise with esm
enabled to trusty, and then to trusty-proposed. What happened is that
after installing the trusty proposed package in this sequence, ESM
became disabled.
Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage-
I'll resume distro packaging work starting tomorrow, thanks for the
ping.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1845334
Title:
Update DEP8 test to python3
To manage
trusty verification, test case (4)
Both scenarios, (a) and (b), start from trusty with u-a-t already
installed from updates
Test (a): enable esm -> upgrade to proposed
Test (b): upgrade to proposed -> ua attach (which enables esm)
The u-a-t package from updates that was used is:
trusty verification, test case (3)
Both start from fresh trusty minimal with no u-a-t installed
a) u-a-t updates -> enable esm -> upgrade proposed
b) u-a-t proposed -> attach
The u-a-t package from updates that was used is: 10ubuntu0.14.04.4
The u-a-t package from proposed that was used is:
I saw something similar a while back, and had a conversation with juliank about
it:
out 09 11:22:08juliank: but apt list --upgradable is showing:
out 09 11:22:12apport/trusty-updates,trusty-security,now
2.14.1-0ubuntu3.29 all [installed,upgradable to: 2.14.1-0ubuntu3.29]
out 09 11:22:19
Have you used apt 1.0.1ubuntu2.24 ? It should have the fix for the bug
that was filed during the conversation above, which I'm assuming is the
same as this one.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ubuntu-advantage-tools in
Public bug reported:
In trusty, python3-flake8 is in universe, and back then (trusty times)
it wasn't allowed to have such a build dependency even if the final
result didn't depend on the universe package.
In this case, it's used to run a flake8 check at package build time, so
it indeed doesn't
Thanks for reporting that here:
https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1847716
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1798786
Title:
can't retrieve gmail emails.
** Description changed:
[Impact]
This is a major rewrite of ubuntu-advantage-client. This version introduces
an updated command line interface (UA Client) to simplify some interaction with
Ubuntu Advantage support offerings, and interacts with a new service backend
built specifically for
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Status: In Progress => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server, which is
Public bug reported:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {}
The python-azure test failed in bileto in the same way, so it can be
used to further troubleshoot this issue. My first attempt would be to
unset the http_proxy variable, or set it to localhost so connections
fail, and see what happens.
--
You received this bug notification because you are a
Given the tests pass locally in a container (autopkgtest ... -- lxd
ubuntu-daily;eoan), I'm trying a bileto run
(https://bileto.ubuntu.com/#/ticket/3818) to see if that reproduces the
test failure. If yes, then I can use that platform for troubleshooting.
--
You received this bug notification
comment #4 suggested that the panic only happened because
kernel.softlockup_panic was set to 1, was that verified?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1846237
Title:
Kernel
This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
When using vfat and running rsync twice, this is the diff in the stats output:
--- log1.vfat 2019-10-08 11:43:04.381667860 -0300
+++ log2.vfat 2019-10-08 11:43:17.609728451 -0300
@@ -1,5 +1,5 @@
Number of files: 78 (reg: 77, dir: 1)
-Number of created files: 77 (reg: 77)
+Number of created
** Changed in: asterisk (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1845765
Title:
asterisk-modules package built without amr_codec.so
To
Adding a task for python-cryptography so this bug shows up in the
excuses page, even though it's not a bug in python-cryptography itself.
** Also affects: python-cryptography (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
In bionic, that codec was added by a debian patch:
debian/patches/amr.patch
Description: Add AMR and AMR-WB codec modules supporting transcoding
That patch is present in disco and eoan, but neither have the
codec_arm.so file shipped, nor is codec_amr.c mentioned in their
respective build logs.
What's the filesystem on the target? If the target is vfat, for example,
setting ownership and permissions won't work, and -W tells rsync to
transfer the whole file.
** Changed in: rsync (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
@cosmos-door, thanks for that merge request against upstream. We are
just a few days away from Final Freeze, though. Would you perhaps be
able to make a merge proposal against the packaging, with a quilt patch?
That would be the ubuntu/devel branch, if you clone the repository
according to the
Public bug reported:
This is a regression in eoan for me. I use virt-manager to create vms,
and I noticed that creating one now takes more than a minute.
Looking at the process listing while the backing disk is being created, I see
this qemu-img command line:
15658 ?Ssl0:00
** Changed in: haproxy (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1828496
Title:
service haproxy reload sometimes fails to pick up new TLS
So, on the GA iso, one cannot get to the step where the installer is
updated. Do you get at least to the language selection prompt, i.e.,
does the installer at least stop somewhere asking you a question? You
say:
"4. We get a continuous flash at early install stage."
I ask because if you are
This may be tricky to reproduce reliably on a test machine, unless you
own a system where it is already happening.
In the upstream bug at
https://github.com/libstatgrab/libstatgrab/issues/102, there is a hint
that
801 - 900 of 143428 matches
Mail list logo
