Public bug reported:
After running ‘add-apt-repository ppa:git-core/ppa’ on Ubuntu 24.04,
‘apt update’ gives this warning:
W: https://ppa.launchpadcontent.net/git-
core/ppa/ubuntu/dists/noble/InRelease: Signature by key
E1DD270288B4E6030699E45FA1715D88E1DF1F24 uses weak algorithm (rsa1024)
But
Seems resolved.
** Changed in: file (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete libmagic1 1:5.45-2 from the archive (in
Same problem is back now that 1:5.45-3build1 is uploaded and 1:5.45-2
still isn’t deleted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Title:
Please delete libmagic1 1:5.45-2 from the
It seems like 1:5.45-3 was deleted instead of 1:5.45-2? That resolves
the immediate issue, I guess, but it’s probably not the intended
resolution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059723
Public bug reported:
As part of the 64-bit time_t transition, libmagic1 was renamed to
libmagic1t64 in https://bugs.debian.org/1063113. However, libmagic1
1:5.45-2 is still in the archive, despite being non-installable:
# apt-get install libmagic1
Reading package lists... Done
Building
Debian policy is very clear that the the description title is not
expected to include the package name:
https://www.debian.org/doc/debian-policy/ch-binary.html#the-single-line-
synopsis
“Do not include the package name in the synopsis line.”
See
** Bug watch added: Debian Bug tracker #1009643
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643
** Also affects: puppet (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643
Importance: Unknown
Status: Unknown
--
You received this bug notification
*** This bug is a duplicate of bug 1969939 ***
https://bugs.launchpad.net/bugs/1969939
** Also affects: puppet (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643
Importance: Unknown
Status: Unknown
** This bug has been marked a duplicate of bug 1969939
Fixed in 3.10.2-7 in jammy-proposed.
** Changed in: python3.10 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962791
Title:
python3 -m venv
This new sysconfig-debian-schemes.diff has broken virtual environments
(venv and virtualenv). Please take a look at the fix in
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1962791.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1951279 ***
https://bugs.launchpad.net/bugs/1951279
** This bug has been marked a duplicate of bug 1951279
OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
sysconfig-debian-schemes.patch uses an incorrect test for a virtual
environment:
if 'real_prefix' in sys.__dict__ or 'VIRTUAL_ENV' in os.environ:
Both sys.real_prefix and VIRTUAL_ENV are only set by virtualenv, not
venv, and then only when the virtualenv is activated by
VENV_ROOT/bin/activate,
** Tags added: jammy testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962791
Title:
python3 -m venv installs pip to incorrect path VENV_ROOT/local/bin/pip
To manage notifications about this
** Bug watch added: Debian Bug tracker #1006707
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006707
** Also affects: python3.10 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006707
Importance: Unknown
Status: Unknown
--
You received this bug notification
Trying virtualenv instead of venv, it installs pip to the right path,
but if you use it to install other packages before activating the
virtualenv, their binaries end up in the wrong path. Ubuntu 21.10:
# apt update; apt install python3-virtualenv
# virtualenv /tmp/my-virtualenv
#
Public bug reported:
python3 -m venv worked correctly in Ubuntu 21.10:
# apt update; apt install python3.10-venv
# python3.10 -m venv /tmp/my-venv
# . /tmp/my-venv/bin/activate
# type pip
pip is /tmp/my-venv/bin/pip
# pip --version
pip 20.3.4 from /tmp/my-venv/lib/python3.10/site-packages/pip
** Changed in: openssh (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/47958
Title:
ssh-agent clobbers LD_LIBRARY_PATH and other environment
Here’s a debdiff with the two-line upstream fix.
** Patch added: "openssl_1.1.1f-1ubuntu2.10_lp1951279.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279/+attachment/5559328/+files/openssl_1.1.1f-1ubuntu2.10_lp1951279.debdiff
** Tags added: focal patch
David Hess’s analysis is correct. This is a bug in the ARM64 assembly
for Poly1305, introduced in
https://github.com/openssl/openssl/commit/2cf7fd698ec1375421f91338ff8a44e7da5238b6
(OpenSSL_1_1_1b~37)
and fixed upstream in
The patches are in 1.8.6-5, currently in hirsuite-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912468
Title:
OpenAFS emergency release 1.8.7
To manage notifications about this bug go
(Closing since the PPA is not part of Ubuntu.)
To use the PPA on bionic, you need to have the bionic-backports
repository enabled (it should be enabled by default, see
https://help.ubuntu.com/community/UbuntuBackports#Enabling_Backports)
and run `apt install init-system-helpers/bionic-backports`.
Public bug reported:
Please sync openafs 1.8.6-4 (universe) from Debian unstable (main)
Explanation of the Ubuntu delta and why it can be dropped:
* Import upstream 5.8 FTBFS fixes
* Import upstream 5.8 FTBFS fixes
These patches were added to Debian in 1.8.6-3.
Changelog entries since
Public bug reported:
A Docker container, like an LXD container (bug 1759257), cannot load
kernel modules, so it should not report Canonical Livepatch as being
available in the motd.
$ docker run --rm -it ubuntu:18.04
root@12d1934cc2df:/# apt-get update
root@12d1934cc2df:/# apt-get install
This change will need to happen upstream first. Upstream is making
progress on it:
https://lore.kernel.org/git/pull.656.git.1591823971.gitgitgad...@gmail.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I assume Rafael added block-proposed mistakenly; there is no staged
upload involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878721
Title:
memcached looks for SASL configuration at wrong
** Tags removed: block-proposed-eoan block-proposed-focal block-
proposed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878721
Title:
memcached looks for SASL configuration at wrong path
Verified that 1.5.22-2ubuntu0.1 works on focal with the config file in
all four locations.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Although the openafs-client package happens to include a command named
‘sys’, it’s almost certainly not the one you’re looking for. openafs-
client is for connecting to the AFS network filesystem
(https://en.wikipedia.org/wiki/Andrew_File_System). What are you trying
to do?
As for the errors
** Description changed:
[Impact]
memcached 1.5.22 in focal has a bug where it looks for its SASL
configuration at /etc/sasl2/memcached.conf/memcached.conf instead of
/etc/sasl2/memcached.conf. This causes a memcached setup with
authentication that was working in bionic to fail in
** Description changed:
[Impact]
memcached 1.5.22 in focal has a bug where it looks for its SASL
configuration at /etc/sasl2/memcached.conf/memcached.conf instead of
/etc/sasl2/memcached.conf. This causes a memcached setup with
authentication that was working in bionic to fail in
** Description changed:
[Impact]
memcached 1.5.22 in focal has a bug where it looks for its SASL
configuration at /etc/sasl2/memcached.conf/memcached.conf instead of
/etc/sasl2/memcached.conf. This causes a memcached setup with
authentication that was working in bionic to fail in
Rafael: I said that bionic is *not* affected, both because bionic has
1.5.6 while the bug was introduced in 1.5.7, and because the test case
passes on bionic. What makes you think otherwise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here’s a debdiff with the upstream patch. I built this in
https://launchpad.net/~andersk/+archive/ubuntu/ppa and verified it
against the test case.
** Patch added: "memcached_1.5.22-2_lp1878721.debdiff"
Public bug reported:
[Impact]
memcached 1.5.22 in focal has a bug where it looks for its SASL
configuration at /etc/sasl2/memcached.conf/memcached.conf instead of
/etc/sasl2/memcached.conf. This causes a memcached setup with
authentication that was working in bionic to fail in focal.
The bug
Alright, so, when I asked in #5 whether symlinks for classic snaps in
/snap/bin could point directly do the target binary instead of
indirecting through snap and snap-confine, am I at least asking a
legitimate question? Surely making a handful of symlink changes would
be easier than developing a
John, did you read more than three words of the report? We’re talking
about a classic snap inheriting an fd from a classic snap (the same
classic snap, in fact) for a file to which they should both have access
(because they’re classic snaps). There can’t be information leaking
across a security
Marking confirmed based on the forum reports.
To be clear, I’m not using ‘snap run’, just the ‘node’ that snap has put
in the PATH, which is /snap/bin/node (a symlink to /usr/bin/snap). Lots
of applications expect to be able to run ‘node’ from the PATH, including
the ‘node’ snap’s own ‘npm’,
Public bug reported:
For example, with the ‘node’ classic snap:
$ touch /tmp/test.js
$ /snap/bin/node
Welcome to Node.js v12.13.0.
Type ".help" for more information.
> fd = fs.openSync("/tmp/test.js")
21
> child_process.execFileSync('/snap/bin/node', {stdio: [fd, 'inherit',
> 'inherit']})
Public bug reported:
Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
color profile switching. The commit at fault is
104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
when processing update” (which was intended to fix LP bug 1847044).
Upstream issue:
Public bug reported:
If I install docker.io on xenial, remove it, upgrade to bionic, and
install it again, then the docker service doesn’t start.
This is because the xenial docker.io postrm left docker.service and
docker.socket masked (via an autogenerated deb-systemd-helper snippet),
and the
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/185
Title:
gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()
To manage
** CVE removed: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2018-17456
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713690
Title:
Restore /usr/share/doc/contrib/diff-highlight/diff-highlight
This seems to have been fixed at some point; there are no ‘for each…in’
loops in the current version.
** Changed in: gnome-shell-extensions (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed by
https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested
850ef518795dcc20d3b9a4f661f70ff8d0ddacb2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843107
Title:
Themes
** Also affects: mutter (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/1843107
Title:
Themes and font settings don’t apply to X apps running in
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771
https://gitlab.gnome.org/GNOME/mutter/issues/771
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/771
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
By adding some debugging output to mutter and gnome-shell I verified
that mutter emits the x11-display-opened signal before gnome-shell is
able to connect a handler for it, and the handler never runs.
(Possibly things would be different in the experimental autostart-
xwayland mode, but the whole
Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem. Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t
Public bug reported:
After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
tweaks are no longer applied to X11 applications when running in a
Wayland session (I tried Firefox and Emacs). This seems to be because
Public bug reported:
Please sync python3-stdlib-extensions 3.7.4-3 (main) from Debian
unstable (main)
I expect this to fix the inability to create a virtualenv with
python3.8:
$ virtualenv -p python3.8 /tmp/env
[…]
File "/usr/lib/python3.8/distutils/sysconfig.py", line 461, in _init_posix
The patch is also in stable kernel v5.2.11:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=v5.2.11~55
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830192
Title:
I believe this is
https://bugzilla.kernel.org/show_bug.cgi?id=203929
https://bugzilla.kernel.org/show_bug.cgi?id=203315
which has been patched in kernel 5.3-rc4:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=v5.3-rc4~36^2~6^2~1^2~20
** Bug watch added: Linux
Or since Launchpad doesn’t like ^ in links:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cfb21b11b891b08b79be07be57c40a85bb926668
** Tags added: patch patch-accepted-upstream
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=203315
** Bug watch added: Debian Bug tracker #929417
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
** Also affects: debconf (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
Importance: Unknown
Status: Unknown
** Also affects: debconf (Ubuntu)
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
I hope 3.32.1 will get into Disco, but in case this can’t happen and a
more minimal set of patches is required, these are the nine upstream
patches I added to my mutter package to get it to stop crashing on
wakeup:
fe86694dd renderer/native: Make EGLStream page flip errors non-fatal
1eabaf12d
*** This bug is a security vulnerability ***
Public security bug reported:
Please sync flatpak 1.2.3-2 (universe) from Debian unstable (main)
Changelog entries since current disco version 1.2.3-1:
flatpak (1.2.3-2) unstable; urgency=high
* seccomp: Reject all ioctls that the kernel will
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820331
Title:
gnome-shell crashed with SIGABRT
To manage notifications about this bug go to:
(FWIW, Qt5 was embedding pcre1 before they switched to embedding pcre2,
so I don’t see anything specifically uncool about that move: it has
always been up to the package maintainer to look at embedded
dependencies and provide system versions if desired.)
--
You received this bug notification
The crash occurs with glibc 2.28 and not with glibc 2.27. Bisecting
glibc.git shows glibc-2.28~122 as the first bad commit:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=eb04c21373e2a2885f3d52ff192b0499afe3c672
“posix: Sync gnulib regex implementation”
I verified that it was fixed in
Bisecting git.git shows v1.9-rc0~63^2 as the first bad commit:
https://github.com/git/git/commit/9c0495d23e6999375976ca44e3812fc65b73626e
That commit merely removes a setlocale(LC_CTYPE, "C") call on
sufficiently new glibc, so the real bug is elsewhere.
--
You received this bug notification
Reproduced on different hardware. It’s not entirely deterministic, and
seems to disappear entirely with --threads=1, so it must be some kind of
race condition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This seems to be reproducible with
git clone https://github.com/zulip/zulip.git
cd zulip
git grep -i 'redirect.*login'
Valgrind log attached.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: git 1:2.19.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic
@Nish: Remember, that’s neither “revert” nor “back”. pcre3 is misnamed,
it’s the old library; pcre2 is the new one. This MIR is for pcre2.
What I’m saying is, as long as this MIR is rejected, the new dependency
of php7.3 on pcre2 will keep it out of main.
--
You received this bug notification
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in
1.12.4 is in cosmic-proposed now with the upstream fix.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: network-manager (Ubuntu)
Assignee: Anders Kaseorg (andersk) => (unassigned)
--
You received this bug notification becau
As long as you're working on this package would you mind including the
one-line upstream patch for bug 1788483, if you haven't already?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795556
Title:
That was a local build. I also saw it on Launchpad with an unrelated
patch (bug 1788483):
https://launchpadlibrarian.net/391298478/buildlog_ubuntu-
cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz
However, the failure seems to have disappeared with today’s updates of
other packages, or maybe
This security update has been stuck in cosmic-proposed for two and a
half weeks, so this isn’t fixed.
** Changed in: openafs (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
A full build log is attached. The relevant part is these test failures.
==
clutter 1.26.1: tests/conform/test-suite.log
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Tags added: patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788483
Title:
(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Anders Kaseorg (andersk)
** Tags added: patch
(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)
** Patch added: "debdiff adding upstream patch, rebased"
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And is this going to mean keeping php7.3 out of main?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163
Title:
[MIR] pcre2
To manage notifications about this bug go to:
There’s still a bundled copy of PCRE2 in libqt5core5a. Build log:
https://launchpadlibrarian.net/385332013/buildlog_ubuntu-cosmic-amd64
.qtbase-opensource-src_5.11.1+dfsg-7ubuntu1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: "rebased on 1.12.2-0ubuntu5"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793975
Title:
vinagre crashed with SIGSEGV
To manage notifications about this bug go to:
** Patch added: "debdiff adding upstream patch"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
To manage notifications about this bug go to:
** Bug watch added: GNOME Bug Tracker #797136
https://bugzilla.gnome.org/show_bug.cgi?id=797136
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=797136
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
The requested analysis, relevant or not, has now been provided on bug
1792544.
** Changed in: pcre2 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720
** Bug watch added: trac.nginx.org/nginx/ #720
http://trac.nginx.org/nginx/ticket/720
** Changed in: nginx (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a
I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.
** Changed
Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792544
Title:
demotion
• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support,
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support
** Changed in: libpam-mount (Ubuntu)
Status: New => Incomplete
** Changed in: nmap (Ubuntu)
• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support
** Changed in: quagga (Ubuntu)
Status: New => Incomplete
** Changed in: rasqal (Ubuntu)
Status: New => Incomplete
** Changed in: slang2 (Ubuntu)
Status: New => Incomplete
--
You received this
• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug:
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing:
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support
** Bug watch added:
Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.
https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped. A corresponding Depends was already dropped in
https://bugs.debian.org/757140.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Andreas: No, it’s not a bug. PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”). The API is completely different and this is expected. See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug
It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.
https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213
/* Contrary to what cURL manual claim
Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.
** Attachment added: "nm.19802.log"
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792745
Title:
NetworkManager crashed with SIGSEGV in _int_malloc()
To manage notifications about
-16948).
- Fix OPENAFS-SA-2018-003: denial of service due to excess resource
consumption (CVE-2018-16949).
-- Anders Kaseorg Tue, 11 Sep 2018 22:53:43 -0700
** Affects: openafs (Ubuntu)
Importance: Undecided
Status: New
** CVE added: https://cve.mitre.org/cgi-bin
GNOME on Wayland works around the crash.
Based on the apport-retrace results, this is possibly a duplicate of bug
1788483.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790992
Title:
gnome-shell
Older versions in bionic than in xenial, as of now:
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29
** Summary changed:
- Older version in artful than in xenial
+ Older version in bionic
** Description changed:
These packages have an older version in artful than in xenial.
fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 <
** Description changed:
This package has an older version in xenial than in trusty:
dh-golang 1.12ubuntu1 < 1.13~0ubuntu0~14.04
- Shouldn’t there be an automated check for this?
+ Shouldn’t there be an automated check for this? (See also: bug 1780680,
+ bug 1780681.)
--
You received
** Description changed:
These packages have an older version in bionic than in artful:
libvorbisidec 1.0.2+svn18153-1+deb9u1 < 1.0.2+svn18153-1+deb9u1build0.17.10.1
nvidia-graphics-drivers-384 384.111-0ubuntu1 < 384.130-0ubuntu0.17.10.1
The latter is older than in xenial, too.
-
1 - 100 of 2560 matches
Mail list logo
