On Thu, Dec 10, 2020 at 5:31 PM Dimitri John Ledkov
<1890...@bugs.launchpad.net> wrote:
>
> "just retry the build" is our solution to this issue.
It is not - in hirsute the builds of the actual package on LP hit 100%
fail-rate.
Unfortunately not in the repro, but due to the above the workaround
cu
I'll give things a try in current Hirsute (gcc on 10.2.1, qemu on 5.2) building
with gcc-10.
If we are back at a level where retries work I'm ok to lower severity.
I'll let you know about these results in a few days.
But since we have had the case of it reaching 100% breakage (and then
would be e
In the test env (not LP build infra, but canonistack) I've got 30 good
runs on 10.2.1 which gives me some hope ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Title:
gcc-10 breaks on armhf
Hi,
while it was a mistake that made it non-fully-enabled in 1.14 (in Groovy) it
just is "not available" instead of a provided but broken functionality.
Thereby (even for Groovy) it would be a a new feature which is harder to
provide in regard to the SRU policy [1].
Then furthermore this isn't a
Indeed as you assumed - here from your log
Dec 10 10:23:44 servio php-fpm7.4[209511]: [10-Dec-2020 10:23:44] ERROR: [pool
www] please specify user and group other than root
Dec 10 10:23:44 servio php-fpm7.4[209511]: [10-Dec-2020 10:23:44] ERROR: FPM
initialization failed
That is a local configu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Thank you, that contains all I need for the SRU later on!
The work on qemu 5.2 for hirsute will take a bit more time, but I've added the
bug to the changelog.
So once it completes this bug will be auto-updated.
** Changed in: qemu (Ubuntu Groovy)
Status: New => Triaged
** Changed in: qem
>From your log:
Job for tftpd-hpa.service failed because the control process exited with error
code.
See "systemctl status tftpd-hpa.service" and "journalctl -xe" for details.
invoke-rc.d: initscript tftpd-hpa, action "start" failed.
[0;1;31m●[0m tftpd-hpa.service - LSB: HPA's tftp server
Lo
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Hi,
here from your log:
Job for rabbitmq-server.service failed because the control process exited with
error code.
See "systemctl status rabbitmq-server.service" and "journalctl -xe" for details.
The attached files and the report do not hold much else to help.
In most cases these issues are due t
Public bug reported:
The qemu build reaches (and always did) a step where it tries to link some
img files. That is done via the command:
$ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s
-o multiboot.img multiboot.o
Recently that still works in Debian [1] but no more in Ubuntu [2]
** Attachment added: "flat.lds - build artifact to re-create the issue"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442723/+files/flat.lds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Attachment added: "linuxboot.o - build artifact to re-create the issue"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1907789/+attachment/5442724/+files/linuxboot.o
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Indeed, gcc-10.2.1 with qemu 5.2 no more breaks 100%.
Here a good build log
https://launchpadlibrarian.net/510811599/buildlog_ubuntu-hirsute-armhf.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILDING.txt.gz
I'll need a few more builds anyway and will let you know.
As mentioned before that does lower severity,
FYI:
- pgl-ddl-deploy resolved
- postgres-logical + logical-ticker resolved
=> All migrated to -release
The one thing that is left is powa-archivist which has the fix that we
discussed and tracked upstream and waits in the new queue.
=> https://ftp-master.debian.org/new/powa-archivist_4.1.0-1.htm
r11-5879 - bad 8 of 10
So we know:
a) the bug has not been fixed yet
b) as we've seen with later GCC-10 runs, the chances to trigger further
increased
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
I left r11-5879 running over the weekend and it concluded with 37 of 75 runs
failing
That is ~50%
I'll look at -O1 next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890435
Title:
gcc-10 breaks o
powa-archivist 4.1 synced and working fine so far.
Just waiting on armhf autopkgtests.
Once that is done we can remove postgresql-12 and thereby complete this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899180
Title:
autopkgtest fails Bionic@amd64 (service) and Hirsute@arm64 (racy)
To manage notifications about this bug go
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Hi Marcus,
from your log:
error: Bind to port 22 on :: failed: Address already in use.
fatal: Cannot bind any address
This indicates that some local configuration causes another service to run and
bind port 22 which blocks sshd from (re-)starting.
Sshd itself (the one of the package) would no
*** This bug is a duplicate of bug 1899248 ***
https://bugs.launchpad.net/bugs/1899248
** This bug has been marked a duplicate of bug 1899248
package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess r
*** This bug is a duplicate of bug 1899248 ***
https://bugs.launchpad.net/bugs/1899248
** This bug has been marked a duplicate of bug 1899248
package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess r
*** This bug is a duplicate of bug 1899248 ***
https://bugs.launchpad.net/bugs/1899248
>From your log:
2020-12-13T19:47:52.762413Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx
reported: 'Preparation of I/O interfaces failed, X Protocol won't be accessible'
2020-12-13T19:47:52.762630Z 0 [ERROR
FYI - I've dup'ed a few more bugs that I've seen on triage onto this one.
This shall help to either better find the discussion that was had so far and to
ensure all further comments on the same case happen here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
That indeed contains the offending "search .".
Since the file is managed by systemd-resolved the question becomes where
exactly that comes from.
To ensure this is the case check /run/systemd/resolve/stub-resolv.conf which is
the file that pushes info from systemd-resolved into resolv.conf.
There
Thanks for tackling that in edk2 Dannf!
For qemu I think setting ICH9-LPC.disable_s3=1 as default will negatively
affect as much (or actually more) cases that it fixes. So if you can get the
IA32X64 working without major impacts I'd clearly prefer that.
Setting qemu to Won't Fix for now but subsc
Since this started to seem different between Mate&KDE as discussed above I was
giving a few more terminals I regularly use a try:
- tilix (VTE based) - warns me that I'll close processes under this session,
keeps screen alive detached
- yakuake (kde based) - warns me that I'll close processes und
I can also confirm this behavior
$ at -t 202012140849.27
warning: commands will be executed using /bin/sh
at> date > /tmp/testme
at>
job 2 at Mon Dec 14 08:49:00 2020
$ cat /tmp/testme
Mo 14. Dez 08:49:00 CET 2020
So it announces AND executes ignoring the seconds.
That code is in since 3.1.11
The following should get you the same test environment I used.
$ qemu-img create /var/lib/libvirt/images/ubuntu20.04-UEFI.qcow2 25
# feel free to use a closer mirror
$ wget
http://ftp.uni-kl.de/pub/linux/ubuntu.iso/20.04.1/ubuntu-20.04.1-desktop-amd64.iso
$ mv ubuntu-20.04.1-desktop-amd64.iso
/v
** Description changed:
[Impact]
- autopkgtest failures on for Xenial(pep8) and Bionic(pep8 & pyflakes)
- - Cherry-picking upstream changes for ESM Product renaming and messaging
- for bug 1901627 trigger these issues.
+ - Cherry-picking upstream changes for ESM Product renaming and m
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: qemu (Ubuntu)
Importance: Undecided =
FYI - fix submitted to qemu upstream and for now added to the qemu package. If
upstream eventually prefers a different solution I can refresh it accordingly.
=> https://lists.gnu.org/archive/html/qemu-devel/2020-12/msg03684.html
--
You received this bug notification because you are a member of U
Public bug reported:
Hi,
with the completion of powa-archivist tonight we have resolved the last reverse
dependency of src:postgresql-12 in hirsute. Now everything depends on
postgresql-13 as it should.
The one dependency left is - as mentioned - postgresql-12-powa which is
in the [1] NBS repor
Ok, this is complete.
- PG-13 is migrated and all dependencies with it
- Various leftovers were removed in bug 1907110 and via further NBS removal
- bug 1908185 removed PG-12
This is fully complete.
If cstore-fdw completes and releases support for PG-13 before FeatureFreeze we
will happily sync
> LOL. This really is very odd. I'm open to any thoughts you have.
Thanks!
Indeed - it might come down to the actual USB devices/Hubs in play and
their exact type and firmware.
OTOH that might also explain why not everyone ever using it complains
about it being dysfunctional but a few do.
> Could
Fails with -O1 as well, although I have to admit that different -O
levels are deeply integrated in qemus build system. So it is hard to
overwrite "all of them". Therefore - while I set -O1 and that affected
some builds, it isn't implying that all compiler calls were -O1.
I know dannf has made some
I was unable to trigger the issue on my rpi4 yet, but as you'd imagine it is
rather slow.
But (thanks Dannf) I got access to an X-gene - and carrying my known bad setup
there (LXD container export FTW) I was able to recreate this on bare-metal as
well.
(Host) Kernel: 5.4.0-58-generic
Model: X-
The canonistack machines I used to crash it (and likely the LP builders) are
X-Gene as well.
So we might have a chance to lock this in on specific HW if there are other
chip types I could use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So far 2/4 failed of r11-5879 on X-Gene BareMetal.
Doko asked me to try if I could get these to fail with -j1 as well (in
the past I was unable to do so, but it is worth a try).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Hi,
this test now fails as seen on ppc here
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/s/systemd/20201214_224336_8b0d8@/log.gz
+ /bin/qemu-system-ppc64 -smp 1 -net none -m 512M -nographic -vga
Added qemu task for update-excuse tag to be resolved.
I have a fix prepared that is building/testing right now. If successful
I'll open an upstream issue&PR for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Tests are somewhat blocked by PPA being under maintenance.
But I have filed the issue upstream for discussion and to trigger their CI.
Issue => https://github.com/systemd/systemd/issues/17986
PR => https://github.com/systemd/systemd/pull/17987
** Bug watch added: github.com/systemd/systemd/issues
On BareMetal now also triggered with -j1 (but there were multiple LXD
containers each running -j1 to increase the chance to find it).
/root/qemu-5.0/memory.c: In function ‘memory_region_write_accessor’:
/root/qemu-5.0/memory.c:485:1: internal compiler error: Segmentation fault
485 | }
| ^
https://github.com/systemd/systemd/pull/17987 was accepted upstream.
I assume with the amount of dependencies that systemd has there is no easy
"just apply this and upload" that will make anyone happy :-/
But now that everything seems ready I wanted to ask the package
maintainer (who usually has
Upstream CI as well as local autopkgtest runs confirm that the new
systemd test code will make the new qemu pass.
# Formerly failing
$ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries -o
systemd-vs-qemu5.2 --apt-upgrade --apt-pocket=proposed=src:qemu
--setup-commands="a
There was a fix suggested on https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=975242 and I tried that. It works great.
I've let the Debian postgresql-maintainer know and there might be an NMU
that would then allow to make this package a sync again.
--
You received this bug notification because
FYI proper migration into 21.04 of qemu 5.2 is held back by systemd bug
1908259
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907656
Title:
[UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices d
Ok, let us tackle bug 1908331 then and consider breaking the fixes for
this bug here into what we need afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906479
Title:
qemu:handle_cpu_signal
It is a pain to see how often other things beat the priority of this ...
But having a config-based (no rebuilds, no custom patches) workaround just
always de-prioritizes it :-/
One day I'll get to it ... (he said and looked at his retirement in 30
years)
** Tags removed: qemu-20.10
** Tags added
> Hmm, not sure what else to do - or is it just ... live with it?
You still have the option to report it upstream and hope that someone
in the wider community has seen it before.
Especially now that we already checked plenty of corner cases and
special conditions your report should be more substan
Thanks for the great report TJ.
Indeed configure --static converts to
4.2
LDFLAGS -Wl,--warn-common -m64 -static -g -Wl,-Bsymbolic-functions
-Wl,-z,relro -Wl,--as-needed
QEMU_LDFLAGS···
5.0
QEMU_LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -m64
-g -O2 -fde
If -static-pie is indeed impoartant here - it is rather new and had problems
before.
An excerpt from d/rules:
114 ifneq ($(filter $(DEB_HOST_ARCH),i386 x32),)
115 # XXX as of 2020-04-29, i386 buildd fails to link -static-pie executable:
116 # /usr/b
Confirmed to recreate from git as well:
v5.0.0
./aarch64-linux-user/qemu-aarch64: ELF 64-bit LSB shared object, x86-64,
version 1 (GNU/Linux), dynamically linked,
BuildID[sha1]=1521984faacf9472c1df8fe37c2a0fb5e2f55aba, for GNU/Linux 3.2.0,
with debug_info, not stripped
v4.2.0
./aarch64-linux-u
Just looking at git history maybe
https://git.qemu.org/?p=qemu.git;a=commit;h=127814629b32d5e0de2873d742e08cb9bd412af7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-u
Building v5.0.0 with --disable-pie:
flags now are:
QEMU_LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static -m64
-fstack-protector-strong
And the file is as we'd like it to be:
./aarch64-linux-user/qemu-aarch64: ELF 64-bit LSB executable, x86-64, version 1
(GNU/Linux), statically
Bisect agrees
$ git bisect log
git bisect start
# old: [b0ca999a43a22b38158a33d3f5881648bb4f] Update version for v4.2.0
release
git bisect old b0ca999a43a22b38158a33d3f5881648bb4f
# new: [fdd76fecdde1ad444ff4deb7f1c4f7e4a1ef97d6] Update version for v5.0.0
release
git bisect new fdd76fecd
Now that root-cause and solution is rather clear I have submitted that to
Debian (which is affected the same way).
But I will personally enter the EOY-downtime before I can fix it in an Ubuntu
upload - OTOH this isn't super urgent I guess - and if my prio-assumption is
wrong the fix is available
Paul mentioned he will be a few days unavailable but chime in once he gets back.
Did you start this discussion on the ML (I didn't see it, but then mail filters
could have hidden it)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Will be in 7.7p2 per (next stable release)
https://github.com/openssh/openssh-portable/commit/484fc023af92ee30bc99eb9798235a00e8f929cc
Upstream Bug:
https://bugzilla.mindrot.org/show_bug.cgi?id=2851
Seems to be broken in 7.7 only so no need to SRU.
** Bug watch added: OpenSSH Portable Bugzi
** Also affects: qemu (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/1274247
Title:
[MIR] Glusterfs
To manage notifications about this bug go to:
>From your LOG:
Starting amavisd: head: cannot open '/etc/mailname' for reading: No such file
or directory
The value of variable $myhostname is "shivam-G41T-R3", but should have been
a fully qualified domain name; perhaps uname(3) did not provide such.
You must explicitly assign a FQDN of t
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Another way to hit this upgrade path is Xenial using libvirt and then
upgrading to Cloud-Archive Pike (Artful based).
Since we already have 18.04/Queens which also is longer supported I
tried with that.
This most likely is due to "--no-restart-on-upgrade" that is used for virtlogd.
Which was actu
This was it:
The virtlogd daemon has the ability to re-exec() itself upon receiving SIGUSR1,
to allow live upgrades without downtime.
** Changed in: libvirt (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
>From http://manpages.ubuntu.com/manpages/bionic/man8/virtlogd.8.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738834
Title:
virtlogd should be restarted on upgrade
To manage notifications ab
For that it has:
ExecReload=/bin/kill -USR1 $MAINPID
defined and would do the right thing.
** Bug watch added: Debian Bug tracker #833745
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
But that should be done in postinst:
129 # Force virtlockd to reexec if enabled
130 if [ -d /run/systemd/system ]; then
131 ! systemctl is-active -q virtlogd || systemctl reload
virtlogd.service >/
Here after an install of libvirt-daemon-system (which has the snippet to
reload)
systemctl status virtlogd --no-pager
...
Jun 26 10:37:11 x systemd[1]: Started Virtual machine log manager.
Jun 26 10:37:26 x systemd[1]: Reloading Virtual machine log manager.
Jun 26 10:37:26 x systemd[1]: Reloaded V
*** This bug is a duplicate of bug 1302436 ***
https://bugs.launchpad.net/bugs/1302436
** This bug has been marked a duplicate of bug 1302436
cgmanager saturates one core
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Also affects: nagios-nrpe (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: nagios-nrpe (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nagios-nrpe (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are
@Damiön - this bug was waiting to get better data to be able to tack down the
issue.
Without that it can't be actions, one either needs working steps to reproduce
or log-data that is enough to pinpoint the issue.
No one benefits form this bug being open but otherwise not going forward at all.
Th
Found the extra data in bug 1759482
But nothing in there is enough for me (not a cgmanager expert) to find a root
cause.
I'll mark the other bug a dup to this to be found from here.
@Serge - if you still look at this and see something in the trace please
let us know.
--
You received this bug no
Hi,
coming by checking older bugs - unfortunately there wasn't a good idea/log that
helps us to continue on understanding this issue.
Due to that for now it is not really actionable and I'll mark it incomplete to
reflect that.
** Changed in: php7.1 (Ubuntu)
Status: New => Incomplete
--
*** This bug is a duplicate of bug 1670629 ***
https://bugs.launchpad.net/bugs/1670629
Hi,
the error you ran into is from your logs:
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through
socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the MySQL server
That
Glad that you have no issue anymore, even thou we don't really know what
the reason was :-/
I have to beg your pardon, but I have no extra experience with large
disk access mdoe other than seeing a few forum/blog entries referring to
it - there were no related bugs nor a lot of official documentat
*** This bug is a duplicate of bug 1755629 ***
https://bugs.launchpad.net/bugs/1755629
Hi Paul,
what you report seems correct to me but there is a very similar bug about this
where I'll dup this to to get a better overview on this.
** This bug has been marked a duplicate of bug 1755629
ep
Fix is known and seems backportable, marking as server-next and subscribing for
somebody to take a look.
Also as mentioned it is in 2.9, so newer releases are already fixed.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Stat
I agree that LP#1626318 is essentially the same and dup'ed it onto this
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755629
Title:
ephemeral-disk-warning yields /mnt 0444 immutable on package
I'd suggest to at least add something like
if [ -d "$(dirname $warn_file)" ]
around the cat
and then before the chmod/chattr
if [ -f "$warn_file" ]
This does not stop the current detection from being broken for multi
/bind-mounts, but should avoid at least some of the issues.
The file is not
*** This bug is a duplicate of bug 1670629 ***
https://bugs.launchpad.net/bugs/1670629
Hi Oliver,
this is a known issue that is being worked on, from your log:
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through
socket '/var/run/mysqld/mysqld.sock' (2) while connecting
Under the assumption of the auto-translate being:
The server lost and lost all the balance and the company asked for refund.
The company did not
answer anything, and I do not answer every time I try to contact them.
Is this company firm and deceptive?
I have to say that I can't help you at
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it, so I am marking this bug
Incomplete for now.
If you can provide exact steps so that a develope
TL;DR to get a newer version of postrgesql-client you need to update
your Ubuntu Releases
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749585
Title:
postgresql-client-common is not compatible with
Hi,
the version in Xenial is afaik only postgresql 9.5 (for the server and the
tools).
9.6 would be available in later releases like Ubuntu 17.10 and Ubuntu 18.04 is
already on postgresql-10.
I would not even see how you start to install postgresql-client-9.6 in
xenial without adding non support
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
No php7.1 in Bionic anymore - closing this old bug.
Whatever brought it back into proposed was resolved.
$ rma php7.1
php7.1 | 7.1.0-5 | unstable | source, all
php7.1 | 7.1.0-5 | unstable-debug | source
php7.1 | 7.1.16-1 | testing| source, all
php7.1
I don't know how your config change broke the configuration from the logs.
But that is what then breaks the update/reinstall.
For a service to be upgraded it needs to be restarted.
If you want to start from scratch you have to "apt remove --purge ..." which
will wipe any configuration. Otherwise
That would imply it was resolved in slang2 (libslang2) 2.3.0-4 which is
in everything later than Xenial.
The change to consider for backporting would be
https://git.launchpad.net/ubuntu/+source/slang2/tree/debian/patches
/init-crash.patch?id=e633289c99ede705274a1b337a0deff5f8e08779
We should try
This was made available in Ubuntu Bionic (ethtool 4.15 along kernel
4.15).
Even thou there are HWE kernels that bring the newer Kernels to LTS releases
AFAIK there are no plans to also backport ethtool changes along that to ethtool
(which lives in the kernel teams scope now).
Subscribing Kerne
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Your logs indicate that your service is unable to start/restart due to local
configuration changes.
A fresh install starts just fine and the logs do not show a reason to assume it
is different.
On upgrading a se
Hi this looks like a broken config to me, from your logs:
[/etc/systemd/system/clamav-daemon.socket.d/extend.conf:4] Failed to parse
address value, ignoring: localhost:3310
clamav-daemon.socket: Unit lacks Listen setting. Refusing.
clamav-daemon.socket: Cannot add dependency job, ignoring: U
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
The GH issue calls this closed for 18.04 - setting the bug that way.
If there is more to do that I missed please update the bug accordingly.
** Changed in: walinuxagent (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs
The new versions are made available via the cloud-archive already on a regular
base.
We backport isolated fixed that have a low regression risk for other users, but
not sull versions per the SRU Policy
(https://wiki.ubuntu.com/StableReleaseUpdates).
Since it seems it was identified that the ver
The logs just have:
systemd[1]: tomcat8.service: Failed with result 'exit-code'.
But since a newly installed tomcat8 works there must be some setup/config
change that triggers that.
Without finding this - and at least to me I can't find it in the logs attache
so far - this bug can not really b
That fail to start then breaks the install/upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745193
Title:
package libvirt-daemon-system 3.6.0-1ubuntu6 failed to
install/upgrade: Unterprozess
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
801 - 900 of 10728 matches
Mail list logo
