Public bug reported:
We have have rebuilt cyrus-imap as-is for perl
https://launchpad.net/ubuntu/+source/cyrus-imapd/3.2.3-2ubuntu2
But it holds back perl and many (22) other things in proposed by breaking on
PPC64 with a dependency issue:
pandoc : Depends: pandoc-data (< 2.9.2.1-1ubuntu2.~)
This now indeed breaks on all architectures:
https://launchpadlibrarian.net/507574538/buildlog_ubuntu-hirsute-amd64.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507575283/buildlog_ubuntu-hirsute-armhf.pgpool2_4.1.4-2_BUILDING.txt.gz
https://launchpadlibrarian.net/507578381/buildlo
FYI These issues might exist for a long time, but seem to grow recently
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489482
-
https://sources.debian.org/src/vim/2:8.2.1913-1/debian/changelog/?hl=2026#L2026
** Bug watch added: Debian Bug tracker #489482
https://bugs.debian.org/cgi-bi
I've found that:
- recompiling openjade on Debian nowadays makes it exhibit the same behavior
- recompiling openjade in Debian&Ubuntu with gcc-9 also fails the same way
I'd love to find the root cause, but my hope of identifying either a
compiler-default-option or compiler-version that made it bre
Notes to myself for another day if I need to revisit this
Repro:
# enable sources for apt
$ apt upgrade
$ apt install dpkg-dev openjade docbook-dsssl
$ apt source pgpool2
$ cd pgpool2-4.1.1/doc/src/sgml/
$ openjade -wall -wno-unused-param -wno-empty -wfully-tagged -c
/usr/share/sgml/docbook/sty
Since I before had only arm traces here, this is x86:
Program received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:384
384 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file
or directory.
https://launchpad.net/ubuntu/+source/cyrus-imapd/3.2.4-3
built and published.
A test with all waiting packages being good:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/c/cyrus-imapd/20201119_063054_75d99@/log.gz
=> F
This recently showed up often enough that I bothered to find this bug :-/
I think it degraded again into a state where we should consider:
IRC:
[13:16] Was there any hope to not expect this to be a retry-monster
forever?
[13:17] The desktop team should be asked if they can work on making
that
** Summary changed:
- openjade segfaults on arm (due to gcc optimization)
+ openjade segfaults on all arch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869734
Title:
openjade segfaults on all arc
** Bug watch added: Debian Bug tracker #975242
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975242
** Also affects: openjade (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975242
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
postgresql-multicorn is the only one directly holding postgresql-common &
postgresql-13 back right now. I filed a request for a test hint at [1].
The obvious alternative (as discussed before) would be removing
postgresql-multicorn from hirsute.
[1]: https://code.launchpad.net/~paelzer/britney/+g
Hi Nicolas,
I think I recognize that behavior and it should actually be fixed by this
libvirt upload:
https://launchpad.net/ubuntu/+source/libvirt/6.0.0-0ubuntu8.2
See bug 691590 for more details on it.
You have that in place (...8.4 is reported) so I wonder what else might be
missing for you.
T
FYI: This is in v3.0 and I'm working on v3.1 for Ubuntu 21.04
** Changed in: virt-manager (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/1854396
Title:
vir
Do you mean the stats that are enabled via
"Edit" -> "Preferences" -> "Polling" -> "Poll Memory stats"
And then shown via
"View" -> "Graph" -> "Memory usage"
?
That would be what is probed from the host and default off as that is
considered "expensive" in terms of CPU burnt for it.
That is base
r10-2027 seems to be good passing 4 runs without a fail.
Continuing with r10-3040 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 on armhf (flaky): internal compile
r10-3040 got 4.5 good passes before I aborted it - it seems to be good
as well.
That means next is r10-3400
--
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 (flak
Migrated to release
=> https://launchpad.net/ubuntu/+source/virt-manager/1:3.1.0-1
Thereby setting this to fixed in coming Ubuntu 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/1854396
Title:
The patch does not cleanly, but almost apply to recent versions.
IMHO an SRU to Focal&Groovy would be useful if it works out well.
I've provided test builds in [1] and wanted to ask if you could test
those for your case please?
[1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4341
Hi Mihail,
your image slightly confuses me - there are multiple windows guests (bottom
three) that have "some data" and one (forth from the bottom) that does not.
What differentiates that one from the others?
It does not have any data - is it maybe just off?
What view exactly is that actually? R
Hi,
from your log
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255:
/etc/ssh/sshd_config line 35: missing argument.
That means you (or a program) have modified /etc/ssh/sshd_config and due
to that the update (which needs to restart the server) fails. You can
restore 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
Hi Naveed,
from your log:
ERROR: Unable to start MySQL server:
2020-11-19T14:47:14.950724Z 0 [ERROR] [MY-77] [Server] /usr/sbin/mysqld:
Error while setting value
'ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' to
'sql_mode'.
2020-11-19T14:47:14.953306Z 0 [ERROR] [MY
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.
Now on any update of the related packages that service has to be restarted, but
since its config is incomplete/faulty it fails to rest
r10-3400 is good
I need to switch to a different overview to make sure I can track this
:-)
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 next
r10-3727
r10-4054 bad
r10-6080
20200507 bad
--
You received t
r10-3657 had 5 good runs
Status:
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 next
r10-4054 bad
r10-6080
20200507 bad
I might want to do a re-run of r10-4054 if r10-3727 is also good. Just
t
1.5 builds good on r10-3727, but that is not enough to make a decision.
Right now there is some machine downtime due to a datacenter move. Back
on Monday I guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
r10-6819 had 22 good runs.
r10-6829 will be the next to try.
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0 of 10
r10-65
On Hirsute this now also became (from a yet unknown change in a different
component) flaky.
Essentially having timing issues between "start" and "lxc-enter-namespace".
Since we like the test, but not actually care too much about libvirt-lxc (we
favor LXD by orders of magnitude for that use case)
Recent Hirsute stats:
arm64
smoke-lxc (F 22% f 0% S 0% B 15% => P 62%/)
..FF.F...BF..F...BF.FB.F...BBB.F
All seem to be like:
+ check_domain
+ grep+ -qs sl[[:space:]]\+running
virsh list
+ virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls
error: Reque
Hi Ankit,
I'll mark this as a dup of bug 1771630 and comment there for you.
Because this is "another, but still similar case" to that other bug.
Please read there for what this is about and how to resolve.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
+1 to Timo to not go for "system nssdb" for the cause of this case here.
Also system-wide-trust would be bug 1647285 and is quite a different scope.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190579
I've just marked another bug report a dup.
For the sake of collecting all different-but-same causes in one place I wanted
to quote the issue.
In the new case it is - again - a mysql from a 3rd party that is interfering
with what is provided by Ubuntu.
In this case due to leftovers of mysql-commu
*** This bug is a duplicate of bug 1771630 ***
https://bugs.launchpad.net/bugs/1771630
** This bug has been marked a duplicate of bug 1771630
package mysql-server-5.7 (not installed) failed to install/upgrade:
installed mysql-server-5.7 package post-installation script subprocess returned
Thank you so much for the high quality report Gerard.
I've pinged the Author of the broken update and marked the bug here as
regression accordingly.
Since he is aware of the context he should be the fastest to resolve this and
might have additional questions about your setup.
** Changed in: sssd
Ref: SRU bug of the offending update => bug 1868703
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906673
Title:
Realm join hangs
To manage notifications about this bug go to:
https://bugs.launchpa
@Mattew - FYI a new bug report indicates that this update might have broken
some users.
Might I ask you - as the Author - to please investigate bug 1906673
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I think we can agree that it is "guest dependent"
Either Windows has a way to fix up the issue or it doesn't even have it to
begin with (compare to MacOS).
Chances are that your (virtual) bootloader/UEFI are what breaks it to
begin with (and not the MacOS later). Do you think you could play aroun
I've created two PPAs to iterate on amd64+arm64 tests for this:
- https://launchpad.net/~paelzer/+archive/ubuntu/lp-1899180-unmodified
- https://launchpad.net/~paelzer/+archive/ubuntu/lp-1899180-new
I've triggered just the arm64 test 4 times on each to see if we can
reproduce the bug on one but no
Note to my self, trigger and result check via
$ lp-test-ppa ppa:paelzer/lp-1899180-unmodified --release hirsute -a amd64
--showpass
$ lp-test-ppa ppa:paelzer/lp-1899180-new --release hirsute -a amd64 --showpass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Tobias for the hint!
FYI: To give some relieve to analyze and resolve the issue the new version was
removed from -updates and -security pockets.
People that have already installed and are negatively affected by this can
downgrade to the former version (which now will be the newest availa
So far:
- unmodified 2/5 fails
- new 0/5 fails
=> I'll schedule a bunch more for the weekend to get a better feeling if this
really works out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899180
Ti
r10-6829 has 2 fails in 35 runs
Signature matches, both are: add_regs_to_insn_regno_info (lra)
r10-6824 = next
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18
r10-6824 bad 1 of 24, signature matches
We have only a few steps to go and need to increase the number of runs to be
sure, so I'll let it run for a while longer.
Also - eventually - I'll re-run what we consider to be the last good, quite a
few times to be sure.
Most likely I'll later today switc
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0 of 10
r10-6586 good 0 of 27
r10-6760 good 0 of 20
r10-6799 good 0 of 20
r1
r10-6822 so far has 0 of 20, but I'll let it run another ~24h
--
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
fau
Ok the results over the weekend look promising, tested on arm64:
- unmodified 6/31 fails
- new 0/31 fails
But when checking the good cases in detail what I found was that in all
cases the domain was considered running, but then continuously (= not a race)
failed to enter namespace. I've had 9 cas
Thanks for your feedback Russell.
You resolved the apparmor issue faster than I could reply :-)
About the actual issue, it indeed seems like an issue between UEFI and QEMU
here.
But I'm still wondering why it then would be any different with Windows and/or
Linux guests.
Is the UEFI in those Wind
> On the apparmor issue, is this the "right" fix? I modified
> /etc/apparmor.d/abstractions/libvirt-qemu, adding,
> /usr/local/bin/qemu-system-x86_64 rmix,
> /usr/local/share/qemu/** r,
>
> Or is there a "better" (correct) way?
Doing the same in /etc/apparmor.d/local/abstractions/libvirt-qemu is
Public bug reported:
Hi,
this is a request to remove a few packages related to the move from
postgresql-12 -> postgresql-13.
The overall move is handled, tracked and discussed in bug 1902059.
For now that would be:
- src:cstore-fdw
All it's binaries
- bin:postgresql-12-cstore-fdw
- bin:postgr
FYI - There will be some more similar NBS once pgl-ddl-deploy clears
(see https://code.launchpad.net/~paelzer/britney/+git/hints-
ubuntu/+merge/394953) but since these will then be "only NBS" they can
be done without bugs then.
--
You received this bug notification because you are a member of Ubu
Ok, things migrated \o/
As of today I started to clear some remaining dependencies (custom triggers,
test fixes, ...) to get rid of postgresql-12 soon.
Right now we are waiting for:
https://github.com/enova/pgl_ddl_deploy/pull/59
Which will unblock pgl-ddl-deploy and due to that also pg-logical.
Ok, the new issue can be seen on arm64 as well, see
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-paelzer-lp-1899180-new/hirsute/arm64/libv/libvirt/20201207_083430_0fb55@/log.gz
I need to extend the skipping if for it.
--
You receiv
On Mon, Dec 7, 2020 at 4:05 PM Russell Morris
<1906...@bugs.launchpad.net> wrote:
>
> > Doing the same in /etc/apparmor.d/local/abstractions/libvirt-qemu is
> > better to now get conflicts on upgrades.
>
> Makes sense, thanks! Will move the items there. Both entries are needed?
> Seems like I can j
Also the try-restart needs to cover more on bionic (added as well now).
New builds uploaded to the PPA ...
--
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
r10-6822 seems good.
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0 of 10
r10-6586 good 0 of 27
r10-6760 good 0 of 20
r1
>
> I get to the UEFI menu, but it won't seem to boot to my drive. Thoughts
> / suggestions?
I guess for that to work you'd have had to install it with UEFI
already present to prep the boot entries accordingly.
I'm not asking you to modify (and break) your existing guest.
Recommendation: just inst
FYI - I've not forgotten this.
On a recheck today I've found that so far nothing has yet happened.
Therefore I pinged the related bugs and people as well as starting an Ubuntu
upload for this (to be sure to be in time).
--
You received this bug notification because you are a member of Ubuntu
Bug
@Meabert - why was this closed? It seems several people are still
affected and it is worth to look at it again.
@Sergio - do you think you could take a look again to identify if the
old fix was incomplete or if here we might have multiple underlying
issues?
@MasterCatz / @Rapper_skull / jsquared
Bob, glad to hear that you found a workaround for yourself. But still for the
overall user-base it would help a lot if we can make an SRU of it, but for that
a good case is needed.
Even with you having found your own workaround it would be great if you could
provide a detailed answer to the ques
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
>From your logs:
ERROR: Unable to start MySQL server:
2020-12-04T16:13:25.340543Z 0 [Warning] [MY-011068] [Server] The syntax
'expire-logs-days' is deprecated and will be removed in a future release.
Pleas
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
Thanks for the feedback Tinodj.
I've marked two other similar cases as a dup now.
But now that it is confirmed we also happen to know that this is a variant of
bug 1612517.
I'll mark it as dup and add info
*** This bug is a duplicate of bug 1612517 ***
https://bugs.launchpad.net/bugs/1612517
** This bug has been marked a duplicate of bug 1864958
package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade:
installed mysql-server-8.0 package post-installation script subprocess r
FYI - a new "category" for this bug is recently in a few bug reports.
If sql_mode was set to NO_AUTO_CREATE_USER this won't work anymore.
Thereby triggering the usual "failed to upgrade, can't restart" condition.
In that case please check upstreams documentation on sql_mode, so far
all users were
>From your log:
2020-12-06T10:42:45.614546Z 0 [ERROR] [MY-010262] [Server] Can't start server:
Bind on TCP/IP port: Address already in use
2020-12-06T10:42:45.614831Z 0 [ERROR] [MY-010257] [Server] Do you already have
another mysqld server running on port: 3306 ?
Common reasons for that are
a) f
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 Klaus,
>From your log:
newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc..
That comes down to the initial install&configuration requiring a fully
qualified domain name.
And your systems seems to have an invalid one for that use case.
There are two paths out of this.
a) f
Hi Alex,
the logs you attached do not hold much more info to debug/analyze your case.
But in general you'd more or less follow the steps mentioned in
=>
https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error
Could you try those out and see if they help
The rest was also cleaned up - thanks !
[11:13] cpaelzer: I didn't understand what you were asking for about
pgsphere - is it old binaries that the NBS report isn't picking up?
[11:24] Laney: no up to yesterday there were binaries in the NBS
report
[11:24] rechecking the current state
[11:25]
Test build worked fine, https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4371/+build/20380291
But the Debian maintainer just missed the ping and patch before and will
likely soon upload the change (as originally intended).
Let us re-check if that properly synced into Ubuntu in a few d
To close this out, fixed in Groovy
apache2 | 2.4.46-1ubuntu1 | groovy | source, amd64,
arm64, armhf, i386, ppc64el, riscv64, s390x
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
FYI
https://github.com/canonical/ubuntu-advantage-client/issues/954
was fixed by
https://github.com/canonical/ubuntu-advantage-client/commit/c2abbebfd4296153a69a311a9d215598fc6a2d9b
But that is not yet in any tagged release
https://github.com/canonical/ubuntu-advantage-client/tags
--
You received
If affected by the bug we see in Bionic things would now look like:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic-paelzer-
lp-1899180-new/bionic/amd64/libv/libvirt/20201208_112813_c5366@/log.gz
autopkgtest [11:24:35]: test smoke-lxc
Good on Hirsute as well
good:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-paelzer-lp-1899180-new/hirsute/arm64/libv/libvirt/20201208_113807_f0d9e@/log.gz
bad:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a849
This contains the fix and will likely today auto-sync and tonight build&test
seabios| 1.14.0-2 | unstable| source, all
It has the LP bug referenced, so once it works this bug should be auto-
closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As mentioned before, the change on it's own isn't SRUable.
But we can push it to Hirsute and to all active releases as block-proposed.
There it can
a) be used in custom autopkgtest triggers if needed
b) more likely is picked up on the next upload
I'm preparing merge proposals for that ...
--
You
** Description changed:
+ [Impact]
+
+ * The test overall success rate degraded over time. This happened
+unrelated to a libvirt upload and affects AFAICS all Ubuntu releases.
+The assumption is that some underlying changes to the LP-test-
+infrastructure cause this.
+It is hard
FYI in MIR meeting of today:
[16:44] waveform: I wanted to know if this is incomplete as in "ack
I'll do it at some point" or as in "we'll give u then"
[16:44] cpaelzer, that's basically done - I've just got to update
the bug
--
You received this bug notification because you are a member of U
Updated Result Overview:
20190425 good 0 of 13
r10-2027 good 0 of 4
r10-3040 good 0 of 4
r10-3400 good 0 of 4
r10-3657 good 0 of 5
r10-3727 good 0 of 3
r10-4054 other kind of bad 1 of 18 (signature different)
r10-6080 good 0 of 10
r10-6586 good 0 of 27
r10-6760 good 0 of 20
r10-6799 good 0 of 20
r1
r10-6823 bad 1 of 28
during RTL pass: reload
/root/qemu-5.0/migration/ram.c: In function ‘ram_load_postcopy’:
/root/qemu-5.0/migration/ram.c:3298:1: internal compiler error: Segmentation
fault
3298 | }
| ^
0x524cf3 crash_signal
../../gcc/gcc/toplev.c:328
0x411e07 add_regs_to_insn_r
=> https://launchpad.net/ubuntu/+source/seabios/1.14.0-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899546
Title:
Missing vgabios-ramfb.bin from seabios
To manage notifications about this bug g
Public bug reported:
This is a stub for coming MIR activity.
Since this was already seeded [1] it regularly shows up as component mismatch
now.
Therefore we want to raise this from "status is unknown" to "nothing
done yet, but documented as that" :-)
The bug status will be incomplete util prope
> I also here have to do a reset (of the guest), to get the USB to show
> up. So it really does seem to be an issue between QEMU and UEFI, agreed?
As it seems right now - yes
I've not yet seen/reproduced the same on qemu 5.0/edk2 2020.08-1 :-/
I can ping here once I have qemu 5.2 (just released)
Thanks - build and migrated in Ubuntu as well
https://launchpad.net/ubuntu/+source/clustalo/1.2.4-7
** Changed in: clustalo (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Changed in: opensbi (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906668
Title:
[MIR] opensbi
To manage notificati
use of sudo, gksu, pkexec, or LD_LIBRARY_PATH
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
** Changed in: opensbi (Ubuntu)
Assignee:
Public bug reported:
Example:
https://launchpadlibrarian.net/510522900/buildlog_ubuntu-hirsute-amd64.edb-debugger_1.2.0-2build1_BUILDING.txt.gz
...
/<>/src/widgets/QDisassemblyView.cpp: In member function ‘void
QDisassemblyView::drawRegiserBadges(QPainter&,
QDisassemblyView::DrawingContext*)’:
A fix is in DELAYED/2 and we are a sync - so it should get to Ubuntu
automatically.
** Changed in: edb-debugger (Ubuntu)
Status: New => In Progress
** Also affects: capstone (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a membe
Public bug reported:
Example:
https://launchpadlibrarian.net/510521872/buildlog_ubuntu-hirsute-amd64.uftrace_0.9.4-0.2_BUILDING.txt.gz
...
[047] mcount_wrap_dlopen: FAIL
...
This is known in Debian and tracked in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966988
FYI this blo
Going fine in Hirsute - even though full proposed migration is behind a wall of
tests.
Uploaded for B/F/G SRUs.
** Tags removed: block-proposed-bionic block-proposed-focal
block-proposed-groovy
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubun
As mentioned before - I didn't trust this result.
And with "likeliness" of this being so low we all know that results are
unreliable.
Due to that now r10-6822 is
r10-6822 - bad 2 of 67
The signature was the same "add_regs_to_insn_regno_info (lra)" as before
on (again) different places tcg/tcg.c:
** Tags removed: block-proposed
--
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
As I already said it is in delayed/2 - which means we can just wait and it will
happen.
Our task is to afterwards confirm that it worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907462
Title:
> Required TODOs:
> - embedded libfdt is outdated and well, embedded. Please build and link
> against the libfdt1 / libfdt-dev that is in main.
>
> Cannot do =)
>
...
Thanks for the explanation why even a normal static link won't work here.
I didn't think about it Firmware'ish execution in that r
The failure of "cockpit/unknown (armhf)" was an infrastructure issue unrelated
to this upload and resolved on a retry.
The modified libvirt autopkgtests worked as expected.
E.g. on Bionic it would have hit the issue of this bug.
See
https://autopkgtest.ubuntu.com/packages/l/libvirt/bionic/amd64
T
> > I've not yet seen/reproduced the same on qemu 5.0/edk2 2020.08-1 :-/
>
> So you don't see this issue, or haven't had a chance to check it? No
> biggie either way, just trying to understand your comment :-).
Sorry to be unclear:
- I was not having the issues doing the same in the past.
- Nor di
\o/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899546
Title:
Missing vgabios-ramfb.bin from seabios
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seabi
** Tags added: qemu-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/1907656
Title:
[UBUNTU 21.04] s390x/s390-virtio-ccw: Reset PCI devices during
subsystem reset
To manage notifications about
This is in qemu 5.2 which I'm already working on for hirsute.
So -devel should be fixed soon (althrough testing on 5.2 will consume a few
days).
Three questions for the following SRU as this was flagged for Focal and
Groovy as well.
1. How urgent/severe is it, do we need to move heaven and earth
On Thu, Dec 10, 2020 at 1:41 PM Russell Morris
<1906...@bugs.launchpad.net> wrote:
>
> Thanks for the details! I thought we may be on to something, but not quite. I
> saw a couple deltas in your config (vs. mine),
> 1) No OVMF_VARS - tried removing this, no difference.
If not specified an empty t
> "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 currently
is to build with gcc-9 on armhf.
But that is not a long term solution.
Therefor
701 - 800 of 10728 matches
Mail list logo
