Thank you Andreas and Stefan,
I've pinged the Debian MR [1] and upstream (via Mail which you are on CC) about
it.
Let us see how things evolve from here.
[1]: https://salsa.debian.org/med-team/clustalo/-/merge_requests/1
** Changed in: gcc-10 (Ubuntu)
Status: New => Invalid
** Changed in
FYI: Also filed as Debian bug (linked here) and got a response on the
Debian MR.
** Bug watch added: Debian Bug tracker #975511
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975511
** Also affects: clustalo (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975511
Importa
Hi Sean,
last time I used our riscv in VMs it still had to use a lot of hand-collected
bits in [1]. Could you outline exactly what bits you used and from where?
Furthermore I've just made qemu 5.1 [2] available in 21.04 a few days
ago. For the sake of trying if a fix already might exist in this r
Ok, then this is fixed in Ubuntu 21.04 (done) and will need someone to
pick up verification of the PPA to get going on the SRUs for 20.04 and
20.10.
It never really "hurt" me so far (was never like the reported 3 seconds
for me), therefore alone I can't make a good case convincing the SRU
team tha
And by fixed in 21.04 I mean by https://launchpad.net/ubuntu/+source
/virt-manager/1:3.1.0-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854396
Title:
virt-manager freezes the whole desktop for 3
This looks a lot like
https://mail.gnu.org/archive/html/qemu-devel/2020-09/msg00212.html
You'd think the offending commit mentioned there is actually in 5.1 and not
earlier.
But it is backported in Groovy as part of
Bug-Debian: https://bugs.debian.org/964793
On Fri, Nov 20, 2020 at 9:00 PM Heather Ellsworth
<1785...@bugs.launchpad.net> wrote:
>
> I agree that the uicheck-sw test has increased in flakiness. How about
> instead of removing the test or sinking the resources into actually
> fixing them right now, I can mark them flaky so that at least a fa
FYI fixed in 1.2.4-7 which is coming our way via auto-sync
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903817
Title:
Clustalo 1.2.4-6 segfaults on s390x
To manage notifications about this bug go
Thanks for the ping Łukasz,
during RTL pass: reload
/<>/fpu/softfloat.c: In function ‘soft_f64_muladd’:
/<>/fpu/softfloat.c:1535:1: internal compiler error:
Segmentation fault
1535 | }
| ^
that is bug 1890435 which should be flaky in groovy.
I'd really prefer not to switch to gcc
Hi Yury,
until implemented for real adding apparmor rules for the uncommon paths are the
way to go.
The difference I'd suggest to your solution is to use local overrides since
they will neither prompt you nor be overwritten on updates.
This can be done in:
# allow virt-aa-helper to generate per-
Retest:
- Q5.0 / L6.6 -> Q5.0 / L6.6 - working
- Q5.1 / L6.9 -> Q5.1 / L6.9 - failing
- Q5.1 / L6.9 -> Q5.0 / L6.6 - working
- Q5.0 / L6.6 -> Q5.1 / L6.9 - working
So if either end is not on the most recent versions things still work.
--
You received this bug notification because you are a membe
The armhf build is resolved (third was a charm)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902654
Title:
failure to migrate virtual machines with pc-i440fx-wily type to ubuntu
20.04
To manage
Public bug reported:
Hi,
just FYI I've seen this while looking at proposed migration for other things.
Currently glusterfs is FTFBS in hirsute
libtool: link: gcc -Wall -I/usr/include/uuid -I/usr/include/tirpc -Wformat
-Werror=format-security -Werror=implicit-function-declaration -g -O2
-fdebug-
FYI: Systems are back up, restarted tests on r10-3727
--
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 (flaky): internal compiler error: Segmentation
fault
To m
Public bug reported:
Removing qemu-system-gui:amd64 (1:5.1+dfsg-4ubuntu1) ...
rm: cannot remove '/var/run/qemu/Debian': Is a directory
dpkg: error processing package qemu-system-gui:amd64 (--remove):
installed qemu-system-gui:amd64 package post-removal script subprocess
returned error exit statu
Example from Focal (how it should be):
26 rm -f
/var/run/qemu/Debian_1_5.0-5ubuntu9~backport20.04-202010241037~ubuntu20.04.1/ui-gtk.so
27 rm -f
/var/run/qemu/Debian_1_5.0-5ubuntu9~backport20.04-202010241037~ubuntu20.04.1/audio-*.so
This is generated from debversion in d/rules a
prerm (and others) have the same issue:
mkdir -p /var/run/qemu/Debian 1:5.1+dfsg-4ubuntu1
cp /usr/lib/x86_64-linux-gnu/qemu/block-*.so /var/run/qemu/Debian
1:5.1+dfsg-4ubuntu1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Due to the above it also might leave dirs like "1:5.1+dfsg-4ubuntu1"
wherever it was running - bump severity
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
Until resolved affected users can rather safely run
rm -rf /var/run/qemu/Debian
Afterwards the remove/purge will work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905377
Title:
postrm fails in
The string in --version is the same:
QEMU emulator version 5.1.0 (Debian 1:5.1+dfsg-4ubuntu1)
QEMU emulator version 5.0.0 (Debian 1:5.0-5ubuntu9.1)
Templates as well:
mkdir -p /var/run/qemu/@PKGVERSION@
cp /usr/lib/@ARCH@/qemu/block-*.so /var/run/qem
df9ba08d6cdb50bd66792db2b02a31e1fc8befef has also added
+# save block-extra loadable modules on upgrades
+# other module types for now (5.0) can't be loaded at runtime, only at startup
+ echo 'case $$1 in (upgrade|deconfigure) mkdir -p ${SAVEMODDIR}; cp -p
${libdir}/qemu/block-*.so ${SAVEMO
Fixed in PPA [1] for testing
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4348
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905377
Title:
postrm fails in hirsute as the path g
Extending the above list changing Qemu and Libvirt individually to
better identify what we need to look at:
- Q5.1 / L6.9 -> Q5.1 / L6.6 - working
- Q5.1 / L6.6 -> Q5.1 / L6.9 - working
- Q5.1 / L6.6 -> Q5.1 / L6.6 - working
- Q5.1 / L6.9 -> Q5.1 / L6.9 - (still) failing
- Q5.1 / L6.9 -> Q5.0 / L6
Bad case:
1. trigger migration
2. sleep 2m
3. fetch the logs
^^ this shall ensure we don't have the error path when I abort the migration in
the log
# reset the logfile via (so both have a log from the start of the service into
a migration)
$ systemctl stop libvirtd
$ rm /var/log/libvirtd.
Public bug reported:
Hi,
I was puzzled today at my install aborting until I was lookgin in the crash
file.
There I've found:
Running command ['vgcreate', '--force', '--zero=y', '--yes', 'ubuntu-vg',
'/dev/dasda2'] with allowed return codes [0] (capture=True)
An error occured handling 'lvm_volg
** Attachment added: "log as it was left in the installer environment"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1905412/+attachment/5437532/+files/1606223663.332479477.install_fail.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Also affects: curtin (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/1905412
Title:
LVM install broken if other disks have meta-data on the VG n
r10-3727 had another 2.5 good runs, overall it LGTM now.
I'll re-run r10-4054 just to be sure not to hunt a ghost.
20190425 good
r10-1014
r10-2027 good
r10-2533
r10-3040 good
r10-3220
r10-3400 good
r10-3450
r10-3475
r10-3478
r10-3593
r10-3622
r10-3657 good
r10-3727 good
r10-4054 bad next
r10-6080
** Attachment added: "stripped logs of good and bad case at source and target
of the migration"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437542/+files/stripped-log.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Attachment added: "full logs of good and bad case at source and target of
the migration"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437541/+files/full-log.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I pinged upstream about the case at
https://www.redhat.com/archives/libvir-list/2020-November/msg01399.html
I'll try how easy (or not) it would be to build 6.7 and 6.8 with otherwise
mostly the same.
That could help to spot where the change happened.
--
You received this bug notification becaus
On this re-check r10-4054 had 7 complete runs without a fail.
So as I was afraid of in comment 71 already, it might have been another much
more rare ICE hidden in there as well. Or OTOH we are cursed by some very bad
statistical chances :-/.
I'll check r10-6080 next to see if it
a) reproduces an
FYI I just looked at this system after installing with only one disk
enabled.
I found this which might be interesting for LVM handling:
#1 two LVMs with same name co-exist
$ sudo vgs -o vg_name,vg_uuid
VGVG UUID
ubuntu-vg 6j9dUF-KO8t-7Svv-RRze-VcMu-pMUY-
The patch in in 5.2 so it would be needed in >=Focal - I marked bug tasks
accordingly.
But for now let us test it in one place (=Focal being the LTS and the furthest
back) and if confirmed to work then prep the dev-fix and SRUs.
Could you try the build 4.2-3ubuntu6.10~ppa1 at [1] if it resolved
Hi Paride,
This is tied into upgrade mechanisms (as that is what it needs to fix, long
running qemu's through an upgrade)
It needs an upgrade to happen to enter the bad state:
That upgrade doesn't have to be another version
For example:
$ apt install qemu-block-extra
$ apt install --reinstall qem
Hmm, the other one takes at least a few day - maybe more due to other
involved people being out for thanksgiving. Prepping this for a review.
MP here:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/394453
--
You received this bug notification because you are a member of
** Package changed: qemu-kvm (Ubuntu) => qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905424
Title:
Live migration failure
To manage notifications about this bug go to:
https://bugs
Prep Bisecting - info in case anyone needs to repro or take over
# Build
$ rm -rf build install
$ mkdir build install
$ V=$(git describe)
$ cd build
$ LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain
--prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-g
ps output of the hanging receiving virt-ssh-helper
Source:
4 0 41305 1 20 0 1627796 23360 poll_s Ssl ? 0:05
/usr/sbin/libvirtd
0 0 41523 41305 20 0 9272 4984 poll_s S ? 0:02 \_
ssh -T -e none -- testkvm-hirsute-to sh -c 'virt-ssh-helper 'qemu:/
In comparison NC mode:
Source:
4 0 41305 1 20 0 1627796 23456 poll_s Ssl ? 0:05
/usr/sbin/libvirtd
0 0 41545 41305 20 0 9064 4440 poll_s S? 0:00 \_
ssh -T -e none -- testkvm-hirsute-to sh -c 'if 'nc' -q 2>&1 | grep "requires an
argument" >/dev
bad case: running into a hang - takes at least 2 minutes
good case: migrates without error in <20s; I'm migrating forward and back
between two systems to be sure (in case anything is flaky) and ready (start the
next test with the same conditions).
git bisect start
git bisect good v6.8.0
git bise
With that knowledge I also was able to confirm that it really is the
native mode
$ virsh migrate --unsafe --live --p2p --tunnelled h-migr-test
qemu+ssh://testkvm-hirsute-to/system?proxy=netcat
$ virsh migrate --unsafe --live --p2p --tunnelled h-migr-test
qemu+ssh://testkvm-hirsute-to/system?pro
I got suspicious that the target has virt-ssh-helper always in run state.
With something that transports network data I'd expect more sleepy/poll states
sometimes (as the NC case shows).
If I only start it manually it is in
0 0 35497 35490 20 0 69888 9924 poll_s S+ pts/0 0:00
Backtraces also look like iterating events.
virEventRunDefaultImpl is an event loop and an infinite loop by design. I'll
report my new info upstream - maybe the Authors have a good hint now that we
know that much.
A few Backtraces:
Program received signal SIGINT, Interrupt.
g_source_ref (sourc
The upstream bug identified (and asked the reporter to check) to remove the
"nodeset".
IMHO progress there depends on someone saying on the upstream bug "yes indeed
it is the same for me, once nodeset is gone it works, but with it it fails".
If you could in your environment do this modification
FYI: I added a tracker task to the upstream bug.
After lunch I'll try to recreate this if possible without HP (just
nodeset) if there is a way to do it. Would help testability, but no
promises ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
What I found interesting in your bug vs the upstream one is that you
have a single node in your nodeset, that might help to simplify things.
# new guest with UVT (any other probably does as well)
$ uvt-kvm create --host-passthrough --password=ubuntu h-migr-nodeset
release=hirsute arch=amd64 labe
Subscribing James/Corey - have you seen these issues with HP backed
guests as generated by openstack?
** Changed in: qemu (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are
FYI - discussion with upstream ongoing, see the link above
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904584
Title:
libvirt 6.8 / qemu 5.1 - --p2p --tunnelled is hanging
To manage notifications
** Attachment added: "libvirt debug log - netcat (classic) mode being fast"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437959/+files/vol-download.netcat.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
The upstream discussion helped to eliminate migration as well as networking
from the equation.
It seems the new virt-ssh-helper mode is just rather slow and thereby
stalling/hanging.
Here are logs of:
virsh -c qemu+ssh://127.0.0.1/system?proxy=netcat vol-download --pool uvtool
h-migr-test.qcow
** Attachment added: "libvirt debug log - native (new) mode being slow"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437960/+files/vol-download.native.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In a similar way as we found in bug 1845506 that multiple disks can kill
the rules for each other the rarely used snapshot option --memspec has
issues as well.
If used the flow reaches access to the disks before rules are added (maybe none
are added for memspec, but the fail
r10-6080 now had 10 good runs.
I'm going back to test 20200507 next - we had bad states with that
version so often this MUST trigger IMHO,
Reminder this runs on in armhf LXD containers on arm64 VMs (like our builds do).
I'm slowly getting the feeling it could be an issue with the underlying
virt
FYI - inquiry for the underlying HW/SW is in RT 128805 - I set Doko and
Rick to CC on that.
--
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 (flaky): internal comp
https://www.redhat.com/archives/libvir-list/2020-November/msg01472.html has
fixes.
I've done some extensive testing and the work fine for me.
Let us wait the few days until it lands in 6.10 and then either upgrade
to 6.10 (if trivial) or apply the two patches for now (I've done that
already - no
Ok, 20200507 almost immediately triggered the ICE
/root/qemu-5.0/linux-user/syscall.c: In function ‘do_syscall1’:
/root/qemu-5.0/linux-user/syscall.c:12479:1: internal compiler error:
Segmentation fault
12479 | }
| ^
0x5518cb crash_signal
../../gcc/gcc/toplev.c:328
0x542673 avoid_c
Another crash with 20200507 at first try:
/root/qemu-5.0/fpu/softfloat.c: In function ‘float128_div’:
/root/qemu-5.0/fpu/softfloat.c:7504:1: internal compiler error: Segmentation
fault
7504 | }
| ^
0x5518cb crash_signal
../../gcc/gcc/toplev.c:328
0x43e363 add_regs_to_insn_regno_in
Doko is so kind and builds r10-7093 got me.
20190425 good
r10-1014
r10-2027 good
r10-2533
r10-3040 good
r10-3220
r10-3400 good
r10-3450
r10-3475
r10-3478
r10-3593
r10-3622
r10-3657 good
r10-3727 good
r10-4054 other kind of bad?
r10-6080 good
r10-7093 next
20200507 bad bad bad
--
You received thi
Public bug reported:
In the tests it seems that since some - yet to be found - change ~20th
Nov the tests of ubuntu-image fail.
Tests all list those three sub-tests as failing:
unittests.sh FAIL non-zero exit status 1
qa FAIL non-zero exit status 1
coverage.sh
** Description changed:
In the tests it seems that since some - yet to be found - change ~20th
Nov the tests of ubuntu-image fail.
Tests all list those three sub-tests as failing:
- unittests.sh FAIL non-zero exit status 1
- qa FAIL non-zero exit status 1
- co
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4353/
...
killing the rest as I've seen seb128 to do the same ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905735
Title:
ubunt
Seb has opened:
https://code.launchpad.net/~seb128/ubuntu-image/+git/ubuntu-image/+merge/394533
It is idential to what I build and tested in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4353/+packages
If we don't want to wait and retrigger the tests with the new version, here a
hi
Hi Rasmus,
this looks soemwhat ready to me - it is on the Desktop team to now integrate
and thereby trigger the component mismatch that will pull it into main.
I've last week pinged seb128 and didrocks about it - AFAIK they will take a
look.
=> https://irclogs.ubuntu.com/2020/11/19/%23ubuntu-des
Changes are upstream as:
829142699ecf1b51e677c6719fce29282af62c92
6d69afe4517646811ee96981408bc6fc18b5ffbb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904584
Title:
libvirt 6.8 / qemu 5.1 - --p2p
Uploaded the fix after some more testing, this should fix the remaining
known issues we had with L6.9/Q5.1 in 21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904584
Title:
libvirt 6.8 / qemu 5.
3 full runs good with r10-7093 but then I got:
/root/qemu-5.0/disas/nanomips.cpp: In member function ‘std::string
NMD::JALRC_HB(uint64)’:
/root/qemu-5.0/disas/nanomips.cpp:7969:1: internal compiler error: Segmentation
fault
7969 | }
| ^
0x602fa7 crash_signal
../../gcc/gcc/toplev.c
We again need to ask, is this the one we are hunting for - or might it be
another issue in between.
Doko ?
--
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 (flaky
Public bug reported:
mpi4py fails with new openmpi:
- On amd64 and arm64 fail
- On armhf and s390x the tests are skipped and therefore work
Errors:
test/test_rma.py::TestRMAWorld::testAccumulate FAILEDFAILED
[ 82%]
test/test_rma.py::TestRMASelf::testStartComplete FAILED
** Tags added: 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/1905790
Title:
Recompile SSSD in 20.04 using OpenSSL (instead of NSS) support
To manage notifications about this bug go to:
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868703
Title:
Support "ad_use_ldaps" flag for new AD requirements (ADV190023)
To manage notifications about this bug
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
>From your logs
modified.conffile..etc.apache2.mods-available.wsgi.conf: [deleted]
modified.conffile..etc.apache2.mods-available.wsgi.load: [deleted]
Other than that there isn't much in the logs you attached, but this
quite likely could break the service from starting. And restarting the
service
To be sure i was running r10-7093 again and so far got 8 good runs in a row :-/
If only we could have a better trigger :-/
--
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
14 runs and going ...
It was never "so rare" when we were at the gcc that is in hirsute or 20200507.
I'll let it continue to run for now
--
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:
Failed on #17
during RTL pass: reload
/root/qemu-5.0/fpu/softfloat.c: In function ‘soft_f64_muladd’:
/root/qemu-5.0/fpu/softfloat.c:1535:1: internal compiler error: Segmentation
fault
1535 | }
| ^
cc -iquote /root/qemu-5.0/b/qemu/target/mips -iquote target/mips -iquote
/root/qemu-5.0/tcg/
I'm not yet sure what we should learn from that - do we need 30 runs of
each step to be somewhat sure? That makes an already slow bisect even
slower ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
FYI - another 8 runs without a crash on r10-7093.
My current working theory is that the root cause of the crash might have been
added as early as r10-4054 but one or many later changes have increased the
chance (think increase the race window or such) for the issue to trigger.
If that assumption
Hi Russel,
I haven't seen such issues recently, but let us try to sort it out.
For that I beg your pardon but I need to start asking for a few details:
1. what exactly (commands) does "reset of the VM" mean for you?
2. in the guest does the output of lspci -v (or whatever the macos counterpart
is
Since this seems to become a reproducibility-fest I've spawned and
prepared two more workers using the same setup as the one we used
before. That should allow for some more runs/days to increase the rate
at we can process it - given the new insight to its unreliability.
--
You received this bug n
Thanks for the feedback Oliver!
IMHO re-enabling SDL for that is still no option for all the reasons
outlined and discussed when it was disabled. Since we still miss a good
"next step to go" other than trying new versions I'm unsure what to do
for now.
For the sake of trying - I have qemu 5.1 in
@Sean - I guess you were on a thanksgiving break, once you are back and
had a chance to test - please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905067
Title:
qemu-system-riscv64 sb
*** This bug is a duplicate of bug 1905377 ***
https://bugs.launchpad.net/bugs/1905377
Hi Matthieu,
thanks for the report, but this bug is known and fixed under bug 1905377 in the
version you report this against.
It is the "old" maintainer script that still has an issue (and we can't fix
tha
We've bundled this fix for Groovy (Thanks Mark) with another upcoming upload.
This should soon be resolved in groovy as well.
** Also affects: qemu (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Could you report me a "ls -laF /var/run/qemu/" what else might be the issue
there?
I mean you even removed it so ... ?!
The failing script should be
/var/lib/dpkg/info/qemu-system-gui\:amd64.prerm
Could you replace the "set -e" with "set -ex" there please and report back all
the output your upg
Interesting - taking the dup away until we found what is different for
you then.
** This bug is no longer a duplicate of bug 1905377
postrm fails in hirsute as the path generation for modules is broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Thanks for the data Matthieu!
Hmm, that is indeed the "old & broken" style that should be (and is for
qemu-block-extra) fixed in 5.1+dfsg-4ubuntu2.
...
Packaging:
- d/qemu-system-gui.*.in is gone in the packaging as intended.
Binary Package:
$ apt install qemu-system-gui
$ dpkg -l qemu-system-
Summary:
of [1] "upgrading" we can not prevent "1.2-3->prerm upgrade 1.2-4" to fail.
But we can make the fallback of "1.2-4-prerm failed-upgrade 1.2-3" working
(which it already is for qemu-block-extra).
We essentially need a rather empty "prerm" in hirsute that can be
dropped in the next release
** Changed in: qemu (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906245
Title:
qemu-system-gui 1:5.1+dfsg-4ubuntu2 fails to upgrade
To manage notific
Test:
# install current version - will be >=1:5.1+dfsg-4ubuntu2
$ apt install qemu-system-gui
# get old broken version and install it
$ wget
https://launchpad.net/ubuntu/+source/qemu/1:5.1+dfsg-4ubuntu1/+build/20311790/+files/qemu-system-gui_5.1+dfsg-4ubuntu1_amd64.deb
$ dpkg --force-all -i qemu-s
FYI - While the fix for this bug worked fine on qemu-block-extra (which is the
only place module upgrade handling will be done in future). The dropping of any
prerm for qemu-syste-gui has triggered bug 1906245.
That essentially surfaces as the same issue, but for qemu-syste-gui by the
broken old
FYI postgresql-common 223 and postgresql-13 13.1 are now ready to
migrate, but waiting for perl to be ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902059
Title:
[MIR] postgresql-13
To mana
Bfore upgrade:
ubuntu@g-test:~$ sudo ebtables -t nat -N foo
ubuntu@g-test:~$ sudo ebtables -t nat -E foo bar
ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists
Try `ebtables -h' or 'ebtables --help' for more information.
Upgrade:
ubuntu@g-test:~$ sudo apt install iptables
Reading package li
Hi Iain,
we've already become aware of this and were discussing how to fix in
https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/78
That should be in 6.10/6.11 by Debian. I'll recheck this case when going
for ~7.0 in January.
** Tags added: libvirt-21.04
** Changed in: libvirt (Ubun
Fix works:
Preparing to unpack .../qemu-system-gui_1%3a5.1+dfsg-4ubuntu3_amd64.deb ...
cp: -r not specified; omitting directory '/var/run/qemu/Debian'
dpkg: warning: old qemu-system-gui:amd64 package pre-removal script subprocess
returned error exit status 1
dpkg: trying script from the new packag
Repackaged deb of 5.1+dfsg-4ubuntu1 to allow users unable to wait for
5.1+dfsg-4ubuntu1 to work around the issue.
** Attachment added: "Repackaged deb of 5.1+dfsg-4ubuntu1 to allow users unable
to wait for 5.1+dfsg-4ubuntu1 to work around the issue."
https://bugs.launchpad.net/ubuntu/+source/
For those in a hurry that just want things to work again here a few
workarounds for now:
Workaround #1 - uninstall and install
$ apt remove qemu-system-gui
# the remove will complain the same way as the upgrade, but an install
# of the new version over this state "rH" works.
# You most likely had
Workaround #3 - use the PPA version
$ sudo add-apt-repository ppa:ci-train-ppa-service/4356
$ apt install qemu-system-gui
# or
$ apt install upgrade
# This will need libgdk-pixbuf-2.0-0 from proposed thou
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
r10-6586 - passed 27 good runs, no fails
Updated Result Overview:
20190425 good
r10-1014
r10-2027 good?4
r10-2533
r10-3040 good?4
r10-3220
r10-3400 good?4
r10-3450
r10-3475
r10-3478
r10-3593
r10-3622
r10-3657 good?5
r10-3727 good?3
r10-4054 other kind of bad - signature different, and rare?
r10-60
FYI This is all good in regard to autopkgtests now, should move to
released in the next Britney run.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906245
Title:
qemu-system-gui 1:5.1+dfsg-4ubuntu2
1 - 100 of 10726 matches
Mail list logo
