Any news ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1887210
Title:
USB DAC/AMP unselectable from Sound Settings and crashes alsamixer
Status in alsa-driver
My initial conclusion may not have been correct.
I now think that the fix in iproute2 4.15.0-2ubuntu1.3 made the problem
more apparent.
The Network Name Resolution service is not actually failing. It is being
stopped and restarted (based on the logs).
So the real problem seems to be a very
** Changed in: cups
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1890572
Title:
USB backend never ends if the printer is not connected
Public bug reported:
The following is repeated periodically in the syslog:
Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
Feb 28 20:25:02 em-cel1 systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:25:02 em-cel1 systemd[1]: Started
focal:
$ pull-lp-source systemd 245.4-4ubuntu3.4
...
$ stat -c '%y' systemd-245.4/NEWS
2020-04-01 13:23:42.0 -0400
$ lxc launch --vm ubuntu:focal lp1878969-f
...
$ lxc exec lp1878969-f systemctl disable systemd-timesyncd
Removed
I've observed the failure in the i386 build of glibc_2.33-0ubuntu4:
Linux lcy01-amd64-014 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47
UTC 2021 i686 athlon i686 GNU/Linux
...
if [ -f /proc/cpuinfo ] ; then cat /proc/cpuinfo ; fi
processor : 0
vendor_id : AuthenticAMD
cpu
ACK, go for it (with 11 for now, I agree that switching to an RC
compiler feels dodgy)
** Changed in: mesa (Ubuntu)
Status: New => Triaged
** Changed in: mesa (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch
Note that migrating to llvm 12 can be done later, and use llvm 11 for
now until 12.0 is released (is at rc3 now).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1917763
Title:
** Description changed:
Hi. I'm using 20.04, and I need a fix for
https://github.com/lxc/lxc/pull/3589
- I think my only options to get that via packaging are
- a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master
- b.) build my own.
+ I think my only options to get
Public bug reported:
We have no sounds on speakers nor signals during the starting.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.11
ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18
Uname: Linux 4.15.0-136-generic i686
ApportVersion:
Public bug reported:
Hi. I'm using 20.04, and I need a fix for
https://github.com/lxc/lxc/pull/3589
I think my only options to get that via packaging are
a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master
b.) build my own.
I don't love either of those options.
Can we
> I feel that openssl upstream needs to add:
server_context.verify_consistent()
Yeah, I agree with you. :) The idea came up three years ago when I filed
issue https://github.com/openssl/openssl/issues/5127
> 1) if openssl version 3.x, and security level is greater than 0, assume no
> TLS1.1 is
> s->cert->sec_cb() and then call it with SSL_SECOP_VERSION operation
with nbits set to TLS1.1 version? then it will return and tell us if it
is acceptable or not, by the security level.
Nice!
Could you hook up the check to SSL_CTX_set_min_proto_version() and return an
error code when level and
On SSLcontext, security callback has prototype
/* Security callback */
int (*sec_cb) (const SSL *s, const SSL_CTX *ctx, int op, int bits, int nid,
void *other, void *ex);
if one calls that function, with context passed in, "op" set to
SSL_SECOP_VERSION, "bits" set to zero,
APT can't know how "critical" the other packages are compared to the
packages which failed to download (which really shouldn't happen to
begin with). I mean, if you don't (normally) use an SSH server, but
hard-depend on a sublime text-editor experience…
Have you tried the --fix-missing option the
Oooh,
can we add bindings for:
s->cert->sec_cb() and then call it with SSL_SECOP_VERSION operation with
nbits set to TLS1.1 version? then it will return and tell us if it is
acceptable or not, by the security level.
--
You received this bug notification because you are a member of Ubuntu
Touch
ideally it would be nice if we could access sec_cb and call it with the
protocol versions to check the versions there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1917625
I feel that openssl upstream needs to add:
server_context.verify_consistent()
Because in the above example, even before trying to establish the
connection between the two context, the server context is already
internally inconsistent.
And upstream has changed the meaning of security levels in
Public bug reported:
An unexpected file size error of *one* package interrupts the whole
update process for *all* packages and this can leave the system in a
vulnerable state - this is not a constructed situation, but very real
right now, look at the following console output - sublime has some
Public bug reported:
We want to release the APT SRUs from Mar 2021 in a staggered manner,
such that we have 2-3 days between each release to get more chance to
discover regressions before rolling out to older releases.
Hence this bug, which we tag block-proposed-{bionic,focal} and then
untag
According to migrated upstream bug
https://gitlab.gnome.org/GNOME/librsvg/-/issues/141
This works correctly on librsvg 2.42.3.
** Bug watch added: gitlab.gnome.org/GNOME/librsvg/-/issues #141
https://gitlab.gnome.org/GNOME/librsvg/-/issues/141
--
You received this bug notification because
I've read through this bug and I don't see a good way forward with a
solution here. OpenSSL 1.1.1 doesn't provide the exact API that is
required to solve it, which would probably be 3) as suggested above, but
I don't think Ubuntu should change the meaning of the value returned by
that API.
Ubuntu
** Changed in: apt (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829860
Title:
APT unlocks in same order as it locks
Status
Fixed since 2.1.10, which is in groovy already.
** No longer affects: apt (Ubuntu Groovy)
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
"; realtime-scheduling = yes" is commented away in
/etc/pulse/daemon.conf (this is a very fresh install of 20.04 and I
haven't customized much). Should I enable this?
Either way, I'll try to exercise suspend and keep an eye out for this
issue happening again. I tried looking around but didn't
This is fixed in 2.2.2 which will be synced ASAP, but this bug was
created after 2.2.2 and hence is not closed in the changelog.
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
[Impact]
test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less
flaky. No end user impact as it's a test-only change.
[Test plan]
Running autopkgtest, which runs our extensive integration test suite which
includes the changed test.
[Where problems
Hey,
The above regression was a false-positive; there were several retries,
all of them passed (cf:
https://autopkgtest.ubuntu.com/packages/c/chrony/bionic/armhf).
So this should be good to go (regression-wise)! \o/
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Focal)
Importance:
Public bug reported:
[Impact]
APT 1.6-2.0 deny third-party repositories from changing their Suite value. This
change was reverted in later apt releases, and will be reverted in 1.8 in
Debian as well, so for consistency, we want to push that change to stable
[Test plan]
We added test cases to
30 matches
Mail list logo
