I tried to reproduce this, to test the fix, but I am stuck trying to figure out
how to manually set the ntp server. I can't see any difference between when the
vm (with no network) has this
/etc/NetworkManager/dispatcher.d/10-update-timesyncd file in place or not. I
think that's good but maybe
** Changed in: mutter (Ubuntu)
Status: Opinion => Confirmed
** Changed in: mutter (Ubuntu)
Assignee: Bernard Stafford (bernard010) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Bernard Stafford (bernard010)
** Changed in: mutter (Ubuntu)
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
This bug was fixed in the package libxml2 - 2.9.12+dfsg-4
---
libxml2 (2.9.12+dfsg-4) unstable; urgency=medium
* Team upload.
* Add a few patches from upstream:
+ Work around lxml API abuse.
+ Fix regression in xmlNodeDumpOutputInternal. LP: #1943277
+ Fix whitespace
>From the original debdiff, two items catch the eye:
+- Cherry-pick seccomp fixes for glibc 2.33 thanks to Dave Jones for
+ reports on armhf.
This is a carried delta so I shouldn't think it creates a new issue,
however I note we're now on glibc 2.34 in impish so wonder if there's
some
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1776381
Title:
lxc-test-api-reboot will hang with autopkgtest
Status in ubuntu-kernel-tests:
Confirmed
Status in lxc package
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1942031
Title:
gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
from
This is stuck in -proposed due to some test failures.
a. snapd's autopkgtests are failing. I'm not sure why but it's failing
against a bunch of stuff, and unlikely to be related to openssh. For
this, I think just wait until snapd gets sorted.
b. openssh's autopkgtest for armhf fails:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1941799
Title:
Please merge openssh 1:8.4p1-6 from Debian unstable
Status in openssh package
@xnox I'm working on an update for Debian Jessie (1.0.1t) as part of Debian
ELTS.
I got one test suite failure in 'verify_extra_test' that I fixed by partially
reverting
https://github.com/openssl/openssl/commit/cb22d2ae5a5b6069dbf66dbcce07223ac15a16de
(hence aligning the test with later
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1941799
Title:
Please merge openssh 1:8.4p1-6 from Debian unstable
Status in openssh package
Hi, I had another look at this one and Ciaby's analysis looks correct to
me, however I want to setup a full reproducer before attempting a fix. I
assigned the bug to myself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1778073
Title:
dnsmasq and
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1916485
Title:
test -x fails
this was marked fix-released for f/h just due to the tooling matching
the bug number; this was actually reverted as shown in the changelogs
posted in the above comments. I'll just correct f/h to indicate this is
wontfix, and a new bug will or has been opened to fix this correctly.
** Changed in:
Also observed with impish linux-aws 5.13.0-1000.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943441
Title:
lxc: lxc-test-parse-config-file failure
Status in lxc package
So, I upgraded from 20.04 to 21.04 to answer that question. And no, it
doesn't work in 21.04 hirsute either.
And now, since the last known working version 20.0.4-2ubuntu1 is not in
hirsute repos I can't downgrade to a working state. :/
```
$ apt policy mesa-vdpau-drivers
mesa-vdpau-drivers:
Thanks for building the packages for focal.
I can confirm that this fixes the problem for me!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144
Title:
monitor_read:
** Changed in: snapd
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1850667
Title:
Switch to "unified" cgroup hierarchy
** Attachment added: "lxc-vs-old-systemd.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1943704/+attachment/5525407/+files/lxc-vs-old-systemd.log
** Description changed:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified
Public bug reported:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the hybrid
hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests:
It looks like I was wrong, and the crash is still occurring with
libx11-6 2:1.7.0-2ubuntu0.1 in hirsute, for example:
https://errors.ubuntu.com/oops/91f6b2d4-1353-11ec-a828-fa163e102db1
The fact that the crash frequency dropped way off after 20.04 could just
be explained by:
* Most people
snapd landed the support in upstream git as of yesterday
(https://github.com/snapcore/snapd) and it is expected to be shipped
with snapd v2.53
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I can confirm this bug, I'm also on 20.04. Manually replacing the i915
binaries at /lib/firmware/i915 with the binaries from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/i915 seems and running update-initramfs -u seems to
fix it for me as well.
--
You
I think it occured before too. But as I mentioned in a older bug report
of me (https://bugs.launchpad.net/bugs/1930192) it could be a Firefox-
thing because it occur mostly after I started Firefox. Now I switched to
Brave and will test if the issue also occur here.
--
You received this bug
25 matches
Mail list logo
