Public bug reported:
Binary package hint: xorg
When I have a high resolution (1280x1024 +) screen hooked to my computer
I'm unable to pass the gdm login (X restarts after username+password). I
have those error in /var/log/kern.log :
[ 57.477288] mtrr: base(0x4400) is not aligned on a size(0x
*** This bug is a duplicate of bug 458697 ***
https://bugs.launchpad.net/bugs/458697
Just to make it clear, I no longer use my KVM because it is buggy. So
the bug #458697 was reproduced with 2 different monitors connected
directly to the computer.
** This bug has been marked a duplicate of bu
There is something really weird with that bug. The GDM login screen
always has the right resolution (even on high resolution screen) but the
Gnome session fails to start when I use a high resolution monitor. The
errors in /var/log/kern.log make me think that the driver wants to
allocate memory but
I just checked the file return when accessing
http://yp.shoutcast.com/sbin/tunein-station.pls?id=632567. Here is the
content :
[playlist]
numberofentries=0
Version=2
The field "file" is missing. Here is a working example comming from
http://www.di.fm/aacplus/ambient.pls
[playlist]
NumberOfEntrie
*** This bug is a duplicate of bug 450351 ***
https://bugs.launchpad.net/bugs/450351
** This bug has been marked a duplicate of bug 450351
cannot start memtest86+
--
Memtest GRUB2 entry is invalid
https://bugs.launchpad.net/bugs/449180
You received this bug notification because you are a
*** This bug is a duplicate of bug 450351 ***
https://bugs.launchpad.net/bugs/450351
** Changed in: memtest86+ (Ubuntu)
Status: New => In Progress
** Changed in: memtest86+ (Ubuntu)
Status: In Progress => Confirmed
--
Memtest GRUB2 entry is invalid
https://bugs.launchpad.net/b
** Summary changed:
- cannot start memtest86+
+ cannot start memtest86+ when /boot is a separate partition
--
cannot start memtest86+ when /boot is a separate partition
https://bugs.launchpad.net/bugs/450351
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "Fix the memtest86+ GRUB menu entry"
http://launchpadlibrarian.net/34333267/fix_memtest86%2B_boot.diff
--
cannot start memtest86+ when /boot is a separate partition
https://bugs.launchpad.net/bugs/450351
You received this bug notification because you are a member of Ubunt
Here is a debdiff for Karmic-proposed.
** Attachment removed: "Fix the memtest86+ GRUB menu entry"
http://launchpadlibrarian.net/34333267/fix_memtest86%2B_boot.diff
** Attachment added: "Fix the memtest86+ GRUB menu entry"
http://launchpadlibrarian.net/34334223/fix_memtest86%2B_boot.diff
*
** Attachment added: "Fix the memtest86+ GRUB menu entry"
http://launchpadlibrarian.net/34334258/fix_memtest86%2B_boot.diff
--
cannot start memtest86+ when /boot is a separate partition
https://bugs.launchpad.net/bugs/450351
You received this bug notification because you are a member of Ubunt
I think that it could help if you try to reproduce this bug using this
ISO http://www.memtest.org/download/4.00/memtest86+-4.00.iso.gz
If it works OK you should add a comment this bug
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/435575.
--
some interrupt error with Lenovo T500
https
You should try to reproduce this bug using a more recent version of
memtest86+. You can use this ISO
http://www.memtest.org/download/4.00/memtest86+-4.00.iso.gz
If it's fixed in that version, you should add a comment in this bug
https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/435575
--
Your CPU is fairly recent. Currently Ubuntu (even the development
version) is still using memtest86+ version 2.11.
If version 4.00 (ISO available here
http://www.memtest.org/download/4.00/memtest86+-4.00.iso.gz) shows the
right data about your CPU you should add a comment in this bug
https://bugs.
The post removal script of memtest86+
(/var/lib/dpkg/info/memtest86+.postrm) almost only calls update-grub2.
You should try to manually run update-grub2 :
sudo update-grub2
For your kernel update problem have you tried to run a dist-upgrade ?
sudo apt-get update && sudo apt-get dist-upgrade
Whe
*** This bug is a duplicate of bug 459606 ***
https://bugs.launchpad.net/bugs/459606
** This bug has been marked a duplicate of bug 459606
Several scripts fail due to lack of execute permissions
--
checkbox-gtk cannot disk benchmark
https://bugs.launchpad.net/bugs/456569
You received this
After several tests I was able to make my Gnome session works with high
resolution. I've attach my xorg.conf.
When I set the "Depth" to 16 or 24 and the "Modes" to "1280x1024" I can
login *most* of the time. It seems that there is a timing issue. I've
tried several times with higher resolutions bu
I have a package in my PPA if someone need it.
https://launchpad.net/~sdeziel/+archive/ppa
--
cannot start memtest86+ when /boot is a separate partition
https://bugs.launchpad.net/bugs/450351
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
According to this https://help.launchpad.net/Bugs/Statuses "Fix
Committed" is the right status for this bug. As soon as there will have
a package integrate to Ubuntu (maybe Lucid) the status will need to be
change to "Fix Released".
--
openarena bad quality sound when using OpenAL engine
https://
Public bug reported:
Launching thunderbird's snap result in the following logs:
Nov 23 20:07:37 simon-lemur kernel: audit: type=1326 audit(1606180057.636:655):
auid=1000 uid=1000 gid=1000 ses=2 pid=8588 comm="thunderbird-bin"
exe="/snap/thunderbird/95/thunderbird-bin" sig=0 arch=c03e syscal
No visible user impact other than the noise, sorry for not mentioning
this outright.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905344
Title:
[snap] thunderbird seccomp profile missing a few sys
@colin-king, it's been going well for the past month.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900889
Title:
BUG: kernel NULL pointer dereference, address:
To manage notifica
*** This bug is a duplicate of bug 1913187 ***
https://bugs.launchpad.net/bugs/1913187
** This bug has been marked a duplicate of bug 1913187
iproute2 segfaults when filtering sockets
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hello Warren,
Looking at the logs, you seem to be referencing a SSL certificate that's
nowhere to be found:
nginx: [emerg] cannot load certificate
"/etc/letsencrypt/live/collabora.princelaw.com/fullchain.pem":
BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such
file or
directo
Hello Stephane, maybe joining the amavisd-new user's to the clamav group
would be a simpler way around the stricter socket permissions you are
proposing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hello Mikey, I remember OnAccessIncludePath working well as long as it
was coupled with clamonacc --fdpass. The FD passing allowed to sidestep
problems coming from Apparmor IIRC.
It's unfortunate that the package doesn't ship a clamonacc.service but
this should work:
[Unit]
Description=ClamAV On-
Hello Logan, I believe that those directories are normally created as a
side effect of an admin manually invoking the iscsiadm command as
suggested in https://ubuntu.com/server/docs/service-iscsi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
As far as I can remember, the open-iscsi.service was not needed to run
the iscsiadm command (on 18.04 and 20.04 at least). Could you share the
full steps to reproduce the issue along with the errors you are getting,
please?
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I had a .odt file opened in libreoffice.writer when it suddenly reported
having crashed. `snap info libreoffice` confirmed the snap was refreshed
few minutes before I noticed the crash. This is related to LP: #1616650
but I wouldn't expect the currently running app to simply c
I no longer have access to the affected machine(s) so I'll mark it as
incomplete waiting for an ex-colleague to check if the problem still
occurs.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@ddstreet, unfortunately, even with 245.4-4ubuntu3.8 on Focal, the mtime
keeps changing as RAs are received :/
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry about the noise, I had a problem in my reproducing steps, the
previous comment should be ignored. I got confused by stat's output
changing but that was the atime, not the mtime that was changing.
** Tags removed: verification-failed-focal
** Tags added: verification-needed-focal
--
You rec
Verification for Focal (245.4-4ubuntu3.8)
# Initial repro on focal:
root@focal:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
fbfde622ae28a4dcfbf73a397a10c6ae /etc/resolv.conf
/etc/resolv.conf 717 8 81a4 101 103 76 123 1 0 0 1625844292 1625844273
1625844273 0 4096
root@focal:~# ip lin
Verification for Groovy (246.6-1ubuntu1.5)
# Initial repro on groovy:
root@groovy:~# md5sum /etc/resolv.conf; stat -t -L /etc/resolv.conf
6b21d96b644bdafc7a3094fe04ab4e88 /etc/resolv.conf
/etc/resolv.conf 729 8 81a4 102 104 8f 111 1 0 0 1625844827 1625844823
1625844823 0 4096
root@groovy:~# i
@xnox, I _think_ SHA1 isn't used in the insecure way that you seem to be
referring to.
The problem seems to be that the certification path used by gnutls ends
up with a root CA self-signed with SHA1. The rest of the path is using
SHA256 as it should. This can be visualized in "Certification Paths
I'm attaching a debdiff to have Focal upgraded from 2.0.13 to 2.0.22
(latest upstream 2.0 stable).
** Patch added: "lp1919468.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1919468/+attachment/5489911/+files/lp1919468.debdiff
--
You received this bug notification because you
Hello Utkarsh,
Yes, that sounds like a good plan, thanks. I forgot to mention, but aside from
the changelog, they also maintain this wonderful list of fixed bugs:
https://www.haproxy.org/bugs/bugs-2.0.13.html
Let me know if I can help with this SRU ;)
Thank you!
--
You received this bug notif
@Utkarsh, I'm not affected by this bug. I am interested in the MRE to
fix the other 305 bugs waiting to bite me or others ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919468
Title:
HAProxy 2.0
@sergiodj, I was able to reproduce this in a container based on your
instruction but by adding the apparmor package to the mix.
With Apparmor installed, after upgrading from 0.102.4+dfsg-
0ubuntu0.18.04.1 -> 0.103.2+dfsg-0ubuntu0.18.04.1, I have this in
"journalctl -fk":
Apr 21 20:56:57 bclam ker
I just took a closer look and the postinst is clearly wrong. The
freshclam daemon is started before the profile is deployed:
cat /var/lib/dpkg/info/clamav-freshclam.postinst:
...
case "$1" in
configure)
...
if [ "$runas" = 'daemon' ]; then
update-rc.d clamav-freshclam defaults >/dev/null
proposed fix in https://salsa.debian.org/clamav-
team/clamav/-/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925182
Title:
ERROR: Can't open /var/log/clamav/freshclam.log in append
Lots have changed since this bug was opened. Please try to reproduce it
with an up to date system and if it still crashes, please provide the
info @hmh requested. Thank you.
** Changed in: intel-microcode (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
@David, thanks for the feedback!
** Changed in: firefox (Ubuntu)
Status: Incomplete => 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/1578853
Title:
Firefox blotchy graphics in G
Thanks Jan for confirming it was fixed!
** Changed in: firefox (Ubuntu)
Status: Incomplete => 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/794036
Title:
Unable to open pages fr
@anuragiitb, the config references a file that doesn't exist:
Jul 05 00:30:07 anurag-Latitude-E7440 nginx[14951]: nginx: [emerg]
open() "/path/to/hello/logs/access.log" failed (2: No such file or
directory)
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug not
The steps to reproduces are mentioned in [1]. One basically needs a
unbound machine and 2 DNS servers that are master for a given zone. The
idea is to then simulate an outage of one of the masters and see if
unbound will still try to reach that dead master even after having
received an answer from
I'm sorry Christian, I had the terminology wrong as you figured you need
1 master and 1 slave.
Your setup looks sane except for the TTL of your test record that seems
way too high. I believe unbound will simply answer from it's cache
without trying to contact any authoritative server. To reproduce
Public bug reported:
systemd-analyze always says "Bootup is not yet finished. Please try
again later." no matter how long I wait (hours, days, ...).
The graphical.target (default one) is indeed never reached due to
snapd.seeded.service still running:
$ systemctl list-jobs
JOB UNIT
$ for pid in $(pidof qemu-system-x86_64); do echo PID $pid; for task in
/proc/$pid/task/*; do cat $task/status | grep Secc; done; done
PID 21066
Seccomp:2
Seccomp:0
Seccomp:2
Seccomp:2
Seccomp:2
Seccomp:2
Seccomp:2
Seccomp:2
$ sudo a
>From https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg04892.html
> Starting with libseccomp 2.2.0 and kernel >= 3.17, we can use
> seccomp_attr_set(ctx, > SCMP_FLTATR_CTL_TSYNC, 1) to update the policy
> on all threads.
== Xenial ==
Since Xenial fulfills those requirements, I'd think th
Yes, I've been using "-sandbox on" since at least Trusty and filled a
few bugs about this feature in the past. I've replied to the "call for
testing" email you sent but maybe my response is being delayed somehow.
I agree with you that Trusty should be "won't fix" but I would have hope
that Xenial
@aixguy, Firefox got an update recently so version 63 should be
available. Would you mind checking if this new version also segfaults?
** Changed in: firefox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Thanks for confirming with version 63. In the apport report from version
62.0.3 there was:
[68851.399630] firefox[9800]: unhandled signal 11 at
nip 0954e70ece40 lr 0954e70ed414 code 1
I'd check if that's still the case with version 63. Attaching a fresh
apport report mig
Public bug reported:
The gateways/firewalls in our DC are highly available and when there is
a failover their IPv6 VIP (fe80::1) moves from the master to the backup
one.
We found that only our Bionic VMs behind those gateways had issues after
a failover. Those Bionic VMs were all running systemd-
*** This bug is a duplicate of bug 1795653 ***
https://bugs.launchpad.net/bugs/1795653
Public bug reported:
The commit [1] was applied to 4.16 but not marked for stable inclusion.
It fixes commit [2] that was introduced in 4.15. Please include [1] in
Bionic's 4.15 kernel.
Not having it cause
Verification with bionic-proposed's version 3.5.27-1ubuntu1.1 went well.
Thanks!
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
@Rodman, as a workaround, maybe you could try to add an "After=systemd-
networkd-wait-online.service" clause in a drop-in snippet?
--
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/216847
Title:
Sorry, it should have read "After=network-online.target".
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/#cutthecraphowdoimakesurethatmyservicestartsafterthenetworkisreallyonline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
@almajava, it seems that your system is missing the main configuration
file (/etc/nginx/nginx.conf) as shown in the systemctl status output:
nginx: [emerg] open() "/etc/nginx/nginx.conf" failed (2: No such file
or directory)
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
** Cha
Public bug reported:
update-motd(5) says:
Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the
root user at each
login, and this information is concatenated in /run/motd.dynamic. The order
of script execu‐
tion is determined by the run-parts(8) --lsbsysinit optio
A possible fix would be to make the unit execution conditional to the
update-motd fragment being executable:
[Unit]
ConditionFileIsExecutable=/etc/update-motd.d/50-motd-news
I'm not sure if this should be added to motd-news.service, motd-
news.timer or both.
** Description changed:
update
systemd from Cosmic is not affected by this bug:
# apt-cache policy systemd
systemd:
Installed: 239-7ubuntu10.3
Candidate: 239-7ubuntu10.3
Version table:
*** 239-7ubuntu10.3 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
500 http://archive.ubuntu
The pki command was moved to a separated binary and package:
$ apt-cache policy strongswan-pki
strongswan-pki:
Installed: (none)
Candidate: 5.6.2-1ubuntu2.3
Version table:
5.6.2-1ubuntu2.3 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
5
You have an broken config it seems:
nginx[15009]: nginx: [emerg] unknown directive "passenger_root" in
/etc/nginx/passenger.conf:1
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Problem description:
Running squid in a container with a host using Bionic's kernel fails if
squid's apparmor profile is enabled. The denial messages is:
Sep 15 13:28:34 simon-laptop kernel: audit: type=1400
audit(1537032514.528:312): apparmor="DENIED" operation="file_mmap"
Thanks Christian, you help is always much appreciated as always!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792728
Title:
[apparmor] allow reading squid binary
To manage notifications about thi
*** This bug is a security vulnerability ***
Public security bug reported:
Upstream has put out many more microversions addressing security issues
and other bug fixes. Here is a list of the CVEs addressed by those:
PHP 7.0.32 / 7.2.10 (13 Sep 2018):
* https://bugs.php.net/bug.php?id=76582 / ht
*** This bug is a security vulnerability ***
Public security bug reported:
Upstream has put out many more microversions addressing security issues
and other bug fixes. Here is a list of the CVEs addressed by those:
PHP 5.6.36 (26 Apr 2018):
* https://bugs.php.net/bug.php?id=76130 /
https://cve
@mdeslaurier, it seems like it fell through the cracks and in the
meantime more microreleases were pushed out by upstream, see
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1792991 and
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1792987
--
You received this bug notification becaus
All the builds failed presumably due to stricter gcc checks [-Werror
=class-memaccess]. Let me know if there is anything I should be doing to
get this fixed properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: php7.0 (Ubuntu)
Status: New => Fix Released
** Changed in: php7.2 (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/1792987
Title:
[MRE
** Changed in: php5 (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/1792991
Title:
Please apply security fixes from PHP 5.5.36 to 5.5.38
To manage notifica
*** This bug is a duplicate of bug 1379309 ***
https://bugs.launchpad.net/bugs/1379309
** This bug is no longer a duplicate of bug 1318021
Not Find mcrypt.ini
** This bug has been marked a duplicate of bug 1379309
Missing maintainer scripts
--
You received this bug notification because
*** This bug is a duplicate of bug 1379309 ***
https://bugs.launchpad.net/bugs/1379309
** This bug has been marked a duplicate of bug 1379309
Missing maintainer scripts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
*** This bug is a duplicate of bug 1379309 ***
https://bugs.launchpad.net/bugs/1379309
** This bug has been marked a duplicate of bug 1379309
Missing maintainer scripts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
*** This bug is a duplicate of bug 1379309 ***
https://bugs.launchpad.net/bugs/1379309
** This bug has been marked a duplicate of bug 1379309
Missing maintainer scripts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
This bug was reported a long time ago. The mcrypt extension has been
deprecated in PHP 7.1 and removed in 7.2. That means the latest
(community) supported release would be in Xenial (php7.0-mcrypt). Would
you mind testing this again with that version?
** Changed in: php-mcrypt (Ubuntu)
Stat
@David, since Zesty has reached its end of life, would you mind testing
with a newer release?
** Changed in: php5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Marking as fix released because Ubuntu Trusty ships version 5.5.9+dfsg-
1ubuntu4.26 that includes the fix from Debian's version 5.4.4-14+deb7u3
released on 17 Jul 2013.
** Changed in: php5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
** Changed in: php5 (Ubuntu)
Status: New => Invalid
** Changed in: linuxmint
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586639
Title:
PHP Upgrade Failure
T
** Changed in: php7.0 (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: php5 (Ubuntu Trusty)
Status: Confirmed => Fix Released
** Changed in: php7.2 (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: php7.2 (Ubuntu Cosmic)
Status: Confirme
I just confirmed that Cosmic's version works:
$ lxc exec foo -- apt-cache policy squid
squid:
Installed: 4.1-1ubuntu2
Candidate: 4.1-1ubuntu2
Version table:
*** 4.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
@cpaelz
Thanks Christian for the test PPA!
I'm unfortunately unable to run tests myself but maybe Adam and/or
Stephen would be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770532
Title:
DKIM signing not
Thanks for the template and the PPA build for Bionic. 3.5.27-1ubuntu1.1
from the PPA tested fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792728
Title:
[apparmor] allow reading squid binary
*** This bug is a security vulnerability ***
Public security bug reported:
Upstream has released microversions addressing security issues (pending
CVE attribution) and other bug fixes.
PHP 7.2.16 / 7.3.3 (07 Mar 2019):
* The CVEs addressed were backported by the security team already
PHP 7.2.1
Public bug reported:
After the automatic upgrade from lxd's snap from 3.20 to 3.21, those
denials appeared:
audit: type=1400 audit(1581974677.106:144): apparmor="DENIED"
operation="open" profile="snap.lxd.hook.configure"
name="/var/lib/snapd/hostfs/usr/lib/os-release" pid=13303 comm="snap-exe
Public bug reported:
Since lvm2 was updated to 2.02.176-4.1ubuntu3.18.04.2 on Bionic (LP:
#1854981), we notice that some of our machines have lingering pvscan
processes apparently running from the initramfs's root that
persist/never finish/exit.
On the affected servers, this is visible as there a
Using a single "listen [::]:80 default_server ipv6only=off;" seems to do
the right thing in all situations: IPv4-only, IPv6-only or dual-stack.
The drawback of using this single socket is that IPv4 clients have their
IPs represented as IPv4-Mapped IPv6 in access_log:
==> /var/log/nginx/access.log
** Tags added: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862262
Title:
[snap] apparmor denials on /sys/devices/virtual/dmi/id/sys_vendor and
product_name
To manage notifications about t
So this bug will be fixed when snapd's 2.43 SRU goes through. I
appreciate the pointer for the gpu-process sanboxing problem and its
workaround! Many thanks Jalon!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
tl;dr: it would be nice to be able to set environment variable on a per-
snap basis.
I ran into this need when trying to workaround a chrome/chromium bug [1]
where one needs to export MESA_GLSL_CACHE_DISABLE=true when starting the
browser to have the GPU sandbox working. It's
@jessegoodier, you will need to change your Nagios checks from
check_nrpe to check_nrpe_nossl and tell the old target NRPE server to
run without SSL. This can be done by setting DAEMON_OPTS="-n" in
/etc/default/nagios-nrpe-server.
--
You received this bug notification because you are a member of
Marking as fix-released as this went in snapd 2.40 according to
https://github.com/snapcore/snapd/commit/1832205560164f725d7400ba0c09b40aa1ba365f
Thanks!
** Changed in: snapd (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ub
Thanks Robie! I should have mentioned that GnuTLS doesn't make SSL
bumping possible. My request was to enable the compile option in future
releases which is why I did not mention the one I was using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Bug watch added: Debian Bug tracker #898307
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898307
** Also affects: squid via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898307
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
When starting chromium's snap, those messages are logged:
Feb 6 12:34:17 foo kernel: [106190.836260] audit: type=1400
audit(1581010457.097:1372): apparmor="DENIED" operation="open"
profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor"
pid=20044 co
Tested on various Bionic machines:
The following packages will be upgraded:
apache2 (2.4.29-1ubuntu4.11 => 2.4.29-1ubuntu4.12)
apache2-bin (2.4.29-1ubuntu4.11 => 2.4.29-1ubuntu4.12)
apache2-data (2.4.29-1ubuntu4.11 => 2.4.29-1ubuntu4.12)
apache2-utils (2.4.29-1ubuntu4.11 => 2.4.29-1ubu
** Tags removed: verification-failed verification-failed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772705
Title:
IKEv2 VPN conne
While the fix only applies to the client side, you got me questioning
what I had done so I redid the test.
This time it worked with 5.6.2-1ubuntu2.5 on the client side and
5.6.2-1ubuntu2.4 on the server side. I must have forgot to restart
NetworkManager or something stupid like that in my first te
Public bug reported:
In order to do SSL bumping [1], it seems that squid needs to be
configured '--with-openssl'.
Justification/use cases:
Nowadays, HTTPS represents the majority of the traffic and it cannot be
observed as easily as HTTP. With SSL bumping, squid can use the SNI
header that is (s
It would be useful if you could include steps to reproduce the problem.
If you also have logs about the failure, please do provide them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855567
Title:
101 - 200 of 2209 matches
Mail list logo
