date:20220603

@Wileam, since it's in essence a cosmetic issue, I haven't made any
plans myself to backport it.  The fix itself is pretty straightforward,
however I think to get a backport approved by the SRU team, a case would
need to be made regarding it having a severe impact on users.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920217

Title:
  id: ‘clamav’: no such user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920217/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE

2022-06-03 Thread Soumadeep Sarkar

Installed 5.17.0-1009-oem unsigned kernel image on Ubuntu 22.04 and
tested the fix. The fix works. My phone can connect to the wifi hotspot
and browse the internet.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/jammy/+source/linux-oem-5.17/+bug/1969326/+attachment/5594782/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969326

Title:
  Enable hotspot feature for Realtek 8821CE

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964711] Re: [amdgpu] Locked Ubuntu is frozen and cannot be unlocked

[Expired for linux-hwe-5.13 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-hwe-5.13 (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964711

Title:
  [amdgpu] Locked Ubuntu is frozen and cannot be unlocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964711/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967528] Re: package autofs 5.1.6-2ubuntu0.1 failed to install/upgrade: installed autofs package post-installation script subprocess returned error exit status 1

[Expired for autofs (Ubuntu) because there has been no activity for 60
days.]

** Changed in: autofs (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967528

Title:
  package autofs 5.1.6-2ubuntu0.1 failed to install/upgrade: installed
  autofs package post-installation script subprocess returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1967528/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967595] Re: Xubuntu Display Issue in 5:4

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967595

Title:
  Xubuntu Display Issue in 5:4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967595/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967741] Re: Crash while using MS teams in webbrowser Google Chrome

[Expired for Ubuntu because there has been no activity for 60 days.]

** Changed in: ubuntu
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967741

Title:
  Crash while using MS teams in webbrowser Google Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1967741/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967768] Re: can not start libreoffice: execv failed: No such file or directory

[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967768

Title:
  can not start libreoffice: execv failed: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967768/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972140] Re: UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20

2022-06-03 Thread js1

Same problem with latest official 5.15.0-35-generic.  I am willing to
test any patched 5.15 kernel build that also includes the linux-headers
package.  Thanks for your efforts.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972140

Title:
  UBSAN: array-index-out-of-bounds in /build/linux-
  HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972140/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920217] Re: id: ‘clamav’: no such user

2022-06-03 Thread Wileam Yonatan Phan

Thanks for fixing this! Any plans to backport this to focal or jammy?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920217

Title:
  id: ‘clamav’: no such user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920217/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977630] [NEW] machinectl pull-tar/pull-raw Operation not permitted

2022-06-03 Thread Kane Foss

Public bug reported:

There is a bug in systemd 249, where one can't pull any images. This was
fixed in version 250, and never got backported. (FIX:
https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851)

Hopefully this can be addressed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-container 249.11-0ubuntu3.1
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  4 04:51:42 2022
InstallationDate: Installed on 2022-06-01 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977630

Title:
  machinectl pull-tar/pull-raw Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977630/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920217] Re: id: ‘clamav’: no such user

This bug was fixed in the package clamav - 0.103.6+dfsg-1ubuntu1

---
clamav (0.103.6+dfsg-1ubuntu1) kinetic; urgency=medium

  * clamav-base.postinst.in: Quell warning from check for clamav user
(LP: #1920217)

 -- Bryce Harrington   Wed, 18 May 2022 17:26:41
-0700

** Changed in: clamav (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/1920217

Title:
  id: ‘clamav’: no such user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920217/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975766] Re: Backport postgresql as MRE for bionic, focal, jammy (August)

** Changed in: postgresql-10 (Ubuntu)
   Status: Invalid => New

** Changed in: postgresql-12 (Ubuntu)
   Status: Invalid => New

** Changed in: postgresql-14 (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975766

Title:
  Backport postgresql as MRE for bionic, focal, jammy (August)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1975766/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977627] Re: New upstream microrelease 2.5.12

** Changed in: openldap (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977627

Title:
  New upstream microrelease 2.5.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1977627/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Description changed:

  [ Impact ]
  
  When the user sends a message to someone, if the server responsible for
  receiving this message defers it, and if there are other possible
  servers (i.e., other servers listed as secondary MX) to try, exim4 will
  segfault while trying to connect to the second server.
  
  [ Test Plan ]
  
  The test case for this bug is a bit involved.  It makes use of the
  upstream reporter's mail server, which has been configured to defer
  emails when they come through the primary MX, but accept when they come
  through the secondary MX.  This means that you will need access to port
  25 (unfortunately canonistack seems to block it).
  
  $ lxc launch ubuntu-daily:jammy exim4-bug1974214
  $ lxc shell exim4-bug1974214
  # apt update && apt full-upgrade
  # apt install -y exim4
  # dpkg-reconfigure exim4-config
  ... In the "Mail Server configuration" screen, select "internet site; mail is 
sent and received directly using SMTP".  Leave everything else untouched.
  # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_
  network:
    ethernets:
  eth0:
    link-local: [ ipv4 ]
  _EOF_
  # netplan apply
  # reboot
  $ lxc shell exim4-bug1974214
  # cat > 1.msg << _EOF_
  Subject: test
  
  this is a test
  _EOF_
  # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg
  # exim4 -bp
   0m   321 1nxC3o-Ax-AS 
    geda...@gedalya.net
  
  ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in
  this case.  You have to use this ID in the following command.
  
  # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug
  ...
  # grep SEGV /tmp/exim.debug
  
  You should be able to see exim4 signalling the segmentation fault that
  occurred while attempting to connect to the second server.
  
  [ Where problems could occur ]
  
  The patches, albeit well contained and relatively simple, touch code
  that deals with TLS and security.  There is always the risk of
  introducing an unwanted vulnerability or normal regression here.  If
  that happens, the very first thing we need to do is revert the patches
  and work with upstream to develop a fix.
+ 
+ In the unlikely case that we encounter regressions, they are probably
+ going to affect TLS connections when sending/receiving messages.  Email
+ servers nowadays generally offer encrypted connections (via TLS or
+ STARTTLS), and some still offer plaintext as well.  If there is a
+ problem with TLS and exim4 is configured to fallback to plaintext,
+ things will still work assuming that the other end also talks plaintext.
+ Otherwise, we might see reports of undelivered emails.
+ 
+ Finally, the fix is composed of two patches.  The first one prevents
+ exim4 from discarding the cached credentials when the transport
+ connection with the primary MX closes, and the second resets headers
+ before trying to connect to the secondary MX.
  
  [ Original Description ]
  
  We are experiencing segfaults in exim since upgrading from impish
  (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy
  (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in
  _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify
  callout during message submission.
  
  Typically the initial attempt to submit a message crashes an exim child
  thread, but the same message is accepted when the sender retries.
  
  gdb backtrace:
  
  Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fe2f844d080 (LWP 29278)]
  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, 
issuer=, cert=, list=) at 
x509/../../../lib/x509/verify-high.c:1026
  1026x509/../../../lib/x509/verify-high.c: No such file or directory.
  (gdb) bt
  #0  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=,
  list=) at x509/../../../lib/x509/verify-high.c:1026
  #1  gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, 
cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510,
  flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129
  #2  0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 
(list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0,
  cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0)
  at x509/../../../lib/x509/verify-high.c:1522
  #3  0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers 
(status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150)
  at ../../lib/cert-session.c:597
  #4  gnutls_certificate_verify_peers (session=0x55ef6c0c1150, 
data=data@entry=0x0, elements=elements@entry=0,
  status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776
  #5  0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 
(session=, status=status@entry=0x7ffc82dba888)
  at ../../lib/cert-session.c:653
  #6  0x55ef6b7698ef in verify_certificate (state=, 
errstr=0x7ffc82dbaa20)
  at

[Bug 1970808] Re: [nvidia] Lock screen is frozen

2022-06-03 Thread Sam Magura

Yes, the mouse cursor does get frozen.

The bug occurred and I was able to ssh into the computer. I've attached
the results of `ps auxw` as you requested.

** Attachment added: "locked-screen-ps-auxw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1970808/+attachment/5594777/+files/locked-screen-ps-auxw.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970808

Title:
  [nvidia] Lock screen is frozen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970808/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977628] [NEW] 2 USB ports have stopped working

2022-06-03 Thread Kartik Agaram

Public bug reported:

My Thinkpad X13 has 1 USB-C port that is usually used by the battery
charger, and 2 USB ports.

Sometime in the past 2-4 weeks, the 2 USB ports have stopped working.
Nothing I plug into them causes any change in the output of `usb-
devices`.

It isn't a hardware fault because both ports are impacted, and one of
them is seldom used.

I am still able to use the USB-C port for data transfer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  3 18:10:52 2022
InstallationDate: Installed on 2021-09-23 (253 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977628

Title:
  2 USB ports have stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1977628/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1959907] Re: DEP8 failure due to py3.10 incompatible import

2022-06-03 Thread Bug Watch Updater

** Changed in: python-fysom (Debian)
   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/1959907

Title:
  DEP8 failure due to py3.10 incompatible import

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-fysom/+bug/1959907/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920217] Re: id: ‘clamav’: no such user

** Changed in: clamav (Ubuntu)
   Status: In Progress => Fix Committed

** Bug watch added: Debian Bug tracker #1008279
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008279

** Also affects: clamav (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008279
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920217

Title:
  id: ‘clamav’: no such user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920217/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977617] Re: ddebs.ubuntu.com size mismatch error on repository metadata after updates

2022-06-03 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on
Libera.chat.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1977617/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977617

Title:
  ddebs.ubuntu.com size mismatch error on repository metadata after
  updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1977617/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977627] [NEW] New upstream microrelease 2.5.12

Public bug reported:

[ Impact ]

 * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.12.

This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/StableReleaseUpdates/OpenLDAPUpdates.

[ Major Changes ]

 * See the list of bugs fixed in this release here:

https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/LSEQKADYZFFMZJGPEVBRR3OVOY4IOGRA/

[ Test Plan ]

 * Upstream gitlab pipeline results:
https://git.openldap.org/openldap/openldap/-/pipelines/4298

 * Upstream "call for testing":
https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/thread/5ZJEOQSVFQBG5TRLAAF6S5M3VRJH5IAV/

 * As described in the MRE wiki page for OpenLDAP, the test plan is to
build the package in bileto and make sure that (1) all build-time tests
pass and (2) all autopkgtest runs (from reverse dependencies) also pass.

[ Where problems could occur ]

 * Upstream tests are always executed during build-time.  There are many
reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage
is good.  Nevertheless, there is always a risk for something to break
since we are dealing with a microrelease upgrade.  Whenever a test
failure is detected, we will be on top of it and make sure it doesn't
affect existing users.

[ Other Info ]

 * This is a reoccurring MRE.  See below for previous MRE's links.
 * CVEs fixed by this release:
   - CVE-2022-29155, which has already been addressed in Jammy

Current versions in supported releases that got updates:
 openldap | 2.5.11+dfsg-1~exp1ubuntu3.1 | jammy-updates   | source

Special cases:
- None.

Standing MRE - Consider last updates as template:
- None so far.

As usual we test and prep from the PPA and then push through
SRU/Security as applicable.

** Affects: openldap (Ubuntu)
 Importance: High
 Status: Invalid

** Affects: openldap (Ubuntu Jammy)
 Importance: High
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: Confirmed


** Tags: needs-mre-backport server-todo

** Also affects: openldap (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: openldap (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: openldap (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: openldap (Ubuntu Jammy)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Changed in: openldap (Ubuntu)
 Assignee: Sergio Durigan Junior (sergiodj) => (unassigned)

** Changed in: openldap (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977627

Title:
  New upstream microrelease 2.5.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1977627/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Description changed:

  [ Impact ]
  
  When the user sends a message to someone, if the server responsible for
  receiving this message defers it, and if there are other possible
  servers (i.e., other servers listed as secondary MX) to try, exim4 will
  segfault while trying to connect to the second server.
  
- [ Test Case ]
+ [ Test Plan ]
  
  The test case for this bug is a bit involved.  It makes use of the
  upstream reporter's mail server, which has been configured to defer
  emails when they come through the primary MX, but accept when they come
  through the secondary MX.  This means that you will need access to port
  25 (unfortunately canonistack seems to block it).
  
  $ lxc launch ubuntu-daily:jammy exim4-bug1974214
  $ lxc shell exim4-bug1974214
  # apt update && apt full-upgrade
  # apt install -y exim4
  # dpkg-reconfigure exim4-config
  ... In the "Mail Server configuration" screen, select "internet site; mail is 
sent and received directly using SMTP".  Leave everything else untouched.
  # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_
  network:
-   ethernets:
- eth0:
-   link-local: [ ipv4 ]
+   ethernets:
+ eth0:
+   link-local: [ ipv4 ]
  _EOF_
  # netplan apply
  # reboot
  $ lxc shell exim4-bug1974214
  # cat > 1.msg << _EOF_
  Subject: test
  
  this is a test
  _EOF_
  # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg
  # exim4 -bp
-  0m   321 1nxC3o-Ax-AS 
-   geda...@gedalya.net
+  0m   321 1nxC3o-Ax-AS 
+   geda...@gedalya.net
  
  ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in
  this case.  You have to use this ID in the following command.
  
  # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug
  ...
  # grep SEGV /tmp/exim.debug
  
  You should be able to see exim4 signalling the segmentation fault that
  occurred while attempting to connect to the second server.
  
  [ Where problems could occur ]
  
  The patches, albeit well contained and relatively simple, touch code
  that deals with TLS and security.  There is always the risk of
  introducing an unwanted vulnerability or normal regression here.  If
  that happens, the very first thing we need to do is revert the patches
  and work with upstream to develop a fix.
  
  [ Original Description ]
  
  We are experiencing segfaults in exim since upgrading from impish
  (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy
  (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in
  _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify
  callout during message submission.
  
  Typically the initial attempt to submit a message crashes an exim child
  thread, but the same message is accepted when the sender retries.
  
  gdb backtrace:
  
  Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fe2f844d080 (LWP 29278)]
  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, 
issuer=, cert=, list=) at 
x509/../../../lib/x509/verify-high.c:1026
  1026x509/../../../lib/x509/verify-high.c: No such file or directory.
  (gdb) bt
  #0  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=,
  list=) at x509/../../../lib/x509/verify-high.c:1026
  #1  gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, 
cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510,
  flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129
  #2  0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 
(list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0,
  cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0)
  at x509/../../../lib/x509/verify-high.c:1522
  #3  0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers 
(status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150)
  at ../../lib/cert-session.c:597
  #4  gnutls_certificate_verify_peers (session=0x55ef6c0c1150, 
data=data@entry=0x0, elements=elements@entry=0,
  status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776
  #5  0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 
(session=, status=status@entry=0x7ffc82dba888)
  at ../../lib/cert-session.c:653
  #6  0x55ef6b7698ef in verify_certificate (state=, 
errstr=0x7ffc82dbaa20)
  at 
/build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519
  #7  0x55ef6b7a5d7b in tls_client_start.constprop.0 
(cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8,
  tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, 
cookie=)
  at 
/build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593
  #8  0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, 
suppress_tls=) at transports/smtp.c:2673
  #9  0x55ef6b776350 in do_callout (pm_mailfrom=, 
se_mailfrom=, options=,
  callout_connect=, callout_overall=, 
callout=, tf=0x7ffc82dbbc10,
  host_list=, addr=0x7ffc82dbbdd0)
  at

[Bug 1971295] Re: Merge net-snmp from Debian unstable for kinetic

Thanks, Bryce.  I'll address this one next week.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971295

Title:
  Merge net-snmp from Debian unstable for kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1971295/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971309] Re: Merge pep8 from Debian unstable for kinetic

There is a -10 version now available from Debian, but this has no
changes for Ubuntu needing merged, so leaving as Incomplete.

pep8 (1.7.1-10) unstable; urgency=medium

  [ Ondřej Nový ]
  * d/control: Update Maintainer field with new Debian Python Team
contact address.
  * d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.

 -- Sandro Tosi   Wed, 04 May 2022 17:44:53 -0400

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971309

Title:
  Merge pep8 from Debian unstable for kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pep8/+bug/1971309/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971328] Re: Merge strongswan from Debian unstable for kinetic

$ rmad strongswan
 strongswan | 5.9.5-2ubuntu2 | jammy  
 strongswan | 5.9.5-2ubuntu2 | kinetic
strongswan | 5.9.6-1 | unstable  

strongswan (5.9.6-1) unstable; urgency=medium

  * New upstream version 5.9.6
  * d/p/0006-fix-format-string-issue-in-enum_flags_to_string added
  * d/libstrongswan.install: install kdf plugin in libstrongswan

 -- Yves-Alexis Perez   Sat, 07 May 2022 20:19:18
+0200


** Changed in: strongswan (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971328

Title:
  Merge strongswan from Debian unstable for kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1971328/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

2022-06-03 Thread Bug Watch Updater

** Changed in: exim4 (Debian)
   Status: Unknown => 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/1974214

Title:
  Segfaults on verify callout, in _gnutls_trust_list_get_issuer

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977626] Re: Kubuntu 22.04 screen lock would not type a password to unlock

2022-06-03 Thread Bernard Stafford

** Description changed:

  Kubuntu 22.04 LTS Screen lock would not type a password to unlock.
  Tried 3 times to enter a password to unlock screen.
  Clicked the password bar and typed.
  It will not accept any letter or number for a password.
  This is a new install and completed the first updates.
  Manually shutdown computer to make bug report.
+ 
+ KDE Frameworks 5.92.0
+ Qt 5.15.3   using X-11
  
  lsb_release -a; uname -a;python3 --version
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04 LTS
  Release:22.04
  Codename:   jammy
  Linux b3-VirtualBox 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux
  Python 3.10.4
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libkscreenlocker5 5.24.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun  3 18:09:52 2022
  InstallationDate: Installed on 2022-06-03 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: kscreenlocker
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977626

Title:
  Kubuntu 22.04 screen lock would not type a password to unlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1977626/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971295] Re: Merge net-snmp from Debian unstable for kinetic

There is a -2 available from debian with a few bugfixes:

$ rmad net-snmp
 net-snmp | 5.9.1+dfsg-1ubuntu2.1 | kinetic 
 net-snmp | 5.9.1+dfsg-1ubuntu2.1 | kinetic-proposed
net-snmp   | 5.9.1+dfsg-1  | testing   
net-snmp   | 5.9.1+dfsg-2  | unstable  

net-snmp (5.9.1+dfsg-2) unstable; urgency=medium

  * Fix path for net-snmp-create-v3-user Closes: #997895
  * Use pidof for net-snmp-create-v3-user so don't need procps
  * Make snmpd.conf group readable Closes: #998152
  * Reapplied perl callback patch Closes: #1011440

 -- Craig Small   Wed, 25 May 2022 22:09:23 +1000


** Changed in: net-snmp (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971295

Title:
  Merge net-snmp from Debian unstable for kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1971295/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971248] Re: Merge apache2 from Debian unstable for kinetic

I considered including mention of lp 1974251 as fixed with the release,
however more recent comments there leave the situation a bit ambiguous
so I decided to omit mention of that for now.

** Changed in: apache2 (Ubuntu)
   Status: In Progress => 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/1971248

Title:
  Merge apache2 from Debian unstable for kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1971248/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977626] [NEW] Kubuntu 22.04 screen lock would not type a password to unlock

2022-06-03 Thread Bernard Stafford

Public bug reported:

Kubuntu 22.04 LTS Screen lock would not type a password to unlock.
Tried 3 times to enter a password to unlock screen.
Clicked the password bar and typed.
It will not accept any letter or number for a password.
This is a new install and completed the first updates.
Manually shutdown computer to make bug report.

lsb_release -a; uname -a;python3 --version
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy
Linux b3-VirtualBox 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux
Python 3.10.4

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libkscreenlocker5 5.24.4-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jun  3 18:09:52 2022
InstallationDate: Installed on 2022-06-03 (0 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
SourcePackage: kscreenlocker
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kscreenlocker (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Attachment added: "journal"
   https://bugs.launchpad.net/bugs/1977626/+attachment/5594770/+files/journal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977626

Title:
  Kubuntu 22.04 screen lock would not type a password to unlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1977626/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849684] Re: casper preseed url not working

2022-06-03 Thread Steven Clarkson

I can also confirm that preseed/url= still does not work correctly.

The line

url_location="${x#url=}"

should be changed to

url_location="${x#*url=}"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849684

Title:
  casper preseed url not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/casper/+bug/1849684/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket

This bug was fixed in the package rubygems - 3.3.15-1

---
rubygems (3.3.15-1) unstable; urgency=medium

  * New upstream release.
  * Add ruby-test-unit (>= 3.3.9~) as b-d (Closes: 1008361) (LP: #1976264)
  * d/ruby-tests.skip: add more tests trying to execute commands on the system
  * Declare compliance with Debian Policy 4.6.1

 -- Lucas Kanashiro   Thu, 02 Jun 2022 16:23:32
-0300

** Changed in: rubygems (Ubuntu Kinetic)
   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/1976264

Title:
  rubygems ftbfs in the jammy release pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849684] Re: casper preseed url not working

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: casper (Ubuntu Eoan)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849684

Title:
  casper preseed url not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/casper/+bug/1849684/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969775] Re: rbd-target-api crashes with `blacklist removal failed`

2022-06-03 Thread Luciano Lo Giudice

The fix proposed in https://bugs.launchpad.net/ubuntu/+source/ceph-
iscsi/+bug/1883112 provides a partial solution (changing the test to use
bytes instead of strings). However, that in itself is insufficient since
that only helps to avoid TypeError exceptions - An additional fix is
needed so that the messages being checked for inclusion are changed from
`blacklist` to `blocklist` (they could be added instead of removed, to
be safe).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969775

Title:
  rbd-target-api crashes with `blacklist removal failed`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1969775/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

** Tags added: jammy

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
- addresses. With NetworkManager 1.36.4 this was not the case.
- 
- Unfortunately, this introduced this bug, which is really breaking a lot
- of my use cases.
+ addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
+ kernel uses the top address as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
- kernel uses the top address as preferred.)
+ kernel uses the address highest in the list as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
  altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case. (The Linux
  kernel uses the address highest in the list as preferred.)
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.
+ 
+ /etc/os-release:
+ 
+ PRETTY_NAME="Ubuntu 22.04 LTS"
+ NAME="Ubuntu"
+ VERSION_ID="22.04"
+ VERSION="22.04 LTS (Jammy Jellyfish)"
+ VERSION_CODENAME=jammy
+ ID=ubuntu
+ ID_LIKE=debian
+

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

I guess these commits are relevant:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa

Bottom line: addresses are now being added in the wrong order, which is
known and fixed upstream for 1.38.x, but never fixed for 1.36.x.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: vim (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968912

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950692] Re: Ubuntu advantage tools should be removable without breakage of the core system functionality

2022-06-03 Thread Steve Langasek

This bug was already closed 'opinion' once by the developers but has
been reopened by the submitter. The developers asked that discussion
about this decision be taken to the mailing list.

A release cycle and change later, this continues to come up in
discussions, but the submitter of this bug has not participated on the
mailing list thread to offer any arguments; so the Server Team has asked
me to comment.

I have also posted my comment to the mailing list at
https://lists.ubuntu.com/archives/ubuntu-devel/2022-June/042115.html but
am copying it here for the record.

The ubuntu-minimal metapackage defines the minimal experience that we
consider to be "Ubuntu". It is possible to remove this metapackage from
the system, from a packaging system / policy perspective this is
permitted. However, by doing so, you are making the system "not Ubuntu"
and you will not receive support for such a system from the Ubuntu
community.

We have always taken an opinionated view on what defines the minimal "Ubuntu".
For instance: at one point in the past, upstart was our supported init system,
but there were other init system packages in the archive. It was possible to
install these - but only by removing the ubuntu-minimal package. Requests to
relax the dependency in order to allow other init
systems as an alternative were rejected, because that was not the defined
Ubuntu experience.

We should always be willing to reconsider the contents of our minimal install
based on technical considerations. To date, however, the objections I've seen
to ubuntu-advantage-tools being a required minimal package have not been
technical, but rather questions of taste: specifically, some people appear to
find it distasteful that a paid service from Canonical is being
advertised without the ability to opt out.

Firstly, users are always entitled to their opinion when it comes to
questions of taste; but the Ubuntu developers are not obligated to
accomodate differences of taste when it comes to the Ubuntu experience.

But secondly, as I've commented before, the purpose of ubuntu-advantage-tools
inclusion in ubuntu-minimal isn't to advertise
commercial services; it's to ensure users are informed regarding the security
status of their systems, and to provide a clean user experience for enabling
the ESM service - which in some contexts is a paid service, in some contexts
not - to provide the best possible security for those systems.

There are two other issues that have come up in discussion around
ubuntu-advantage-tools. Neither requires making the package removable
in order to address, and ensuring they are addressed in the package
itself improves the Ubuntu experience for all users, not just those that
choose to remove this package.

- https://bugs.launchpad.net/bugs/1956115 objects about not being able
to opt out of the MOTD messages. This bug report however is marked
incomplete, as the behavior described does not appear to correspond to
the default behavior in Ubuntu Desktop or Server. If there are problems
being unable to opt out, we certainly want to address those.

- ubuntu-advantage-tools is now a bit larger than it was originally,
weighing in at around 2.8MB. We should always be mindful of managing
the size of a minimal Ubuntu install; however I have not actually seen
anyone say that they were trying to remove ubuntu-advantage-tools from
their system because of the disk space used. In any case, the team is
looking at bringing the size of this package back down to under 1MB.

In conclusion, in the absence of any other arguments being advanced,
ubuntu-advantage-tools will remain a dependency of ubuntu-minimal at
this time. This is always subject to revision in light of new technical
arguments that might be put forward, but explains the current state of
affairs for the released Ubuntu 22.04 LTS.

** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Confirmed => Opinion

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950692

Title:
Ubuntu advantage tools should be removable without breakage of the
core system functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1950692/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977622] Re: Bionic update: upstream stable patchset 2022-06-03

2022-06-03 Thread Kamal Mostafa

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2022-06-03
  
-upstream stable patchset 2022-06-03
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.277, v4.19.240
+ 
+    from git://git.kernel.org/
+ 
+ etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead
+ mm: page_alloc: fix building error on -Werror=array-compare
+ tracing: Dump stacktrace trigger to the corresponding instance
+ gfs2: assign rgrp glock before compute_bitstructs
+ ALSA: usb-audio: Clear MIDI port active flag after draining
+ tcp: fix race condition when creating child sockets from syncookies
+ tcp: Fix potential use-after-free due to double kfree()
+ dmaengine: imx-sdma: Fix error checking in sdma_event_remap
+ net/packet: fix packet_sock xmit return value checking
+ netlink: reset network and mac headers in netlink_dump()
+ ARM: vexpress/spc: Avoid negative array index when !SMP
+ platform/x86: samsung-laptop: Fix an unsigned comparison which can never be 
negative
+ ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant
+ vxlan: fix error return code in vxlan_fdb_append
+ cifs: Check the IOCB_DIRECT flag, not O_DIRECT
+ brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant
+ drm/msm/mdp5: check the return of kzalloc()
+ net: macb: Restart tx only if queue pointer is lagging
+ stat: fix inconsistency between struct stat and struct compat_stat
+ ata: pata_marvell: Check the 'bmdma_addr' beforing reading
+ dma: at_xdmac: fix a missing check on list iterator
+ powerpc/perf: Fix power9 event alternatives
+ openvswitch: fix OOB access in reserve_sfa_size()
+ ASoC: soc-dapm: fix two incorrect uses of list iterator
+ e1000e: Fix possible overflow in LTR decoding
+ ARC: entry: fix syscall_trace_exit argument
+ ext4: fix symlink file size not match to file content
+ ext4: fix overhead calculation to account for the reserved gdt blocks
+ ext4: force overhead calculation if the s_overhead_cluster makes no sense
+ staging: ion: Prevent incorrect reference counting behavour
+ block/compat_ioctl: fix range check in BLKGETSIZE
+ ax25: add refcount in ax25_dev to avoid UAF bugs
+ ax25: fix reference count leaks of ax25_dev
+ ax25: fix UAF bugs of net_device caused by rebinding operation
+ ax25: Fix refcount leaks caused by ax25_cb_del()
+ ax25: fix UAF bug in ax25_send_control()
+ ax25: fix NPD bug in ax25_disconnect
+ ax25: Fix NULL pointer dereferences in ax25 timers
+ ax25: Fix UAF bugs in ax25 timers
+ ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek
+ net/sched: cls_u32: fix possible leak in u32_init_knode()
+ drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised
+ drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare
+ UBUNTU: upstream stable to v4.14.277, v4.19.240

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977622

Title:
  Bionic update: upstream stable patchset 2022-06-03

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977622/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.

Before (network-manager 1.36.4):

2: eno0:  mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43194sec
inet6 fd10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43194sec
inet6 fd10:3781::0:9875:4dec:b9f9:e768/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781::0:f802:2428:9af1:dcb3/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::36e2:ec4c:fddb:3c89/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

After (network-manager 1.36.6):

2: eno0:  mtu 1500 state UP qlen 1000
inet6 fd10:3781::0:9875:4dec:b9f9:e768/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781::0:f802:2428:9af1:dcb3/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43194sec preferred_lft 43194sec
inet6 fd10:3781:::bd0/128 scope global dynamic noprefixroute 
   valid_lft 43194sec preferred_lft 43194sec
inet6 fe80::36e2:ec4c:fddb:3c89/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

On another machine with Debian sid and network-manager 1.38.0, it looks
like the way it should be again (dynamic addresses at the top of the
list, preferred to autoconfigured / temporary addresses):

2: wlan0:  mtu 1500 state UP qlen 1000
inet6 fd10:3781:::5bf/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43193sec
inet6 2a10:3781:::5bf/128 scope global dynamic noprefixroute 
   valid_lft 43193sec preferred_lft 43193sec
inet6 2a10:3781::0:42cd:4f1b:89b8:77fd/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fd10:3781::0:8a59:df52:9ea1:e7c8/64 scope global noprefixroute 
   valid_lft forever preferred_lft forever
inet6 fe80::a738:71dc:f10e:924e/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever

So this bug was not present in NetworkManager 1.36.4, introduced in
1.36.6, and then fixed in 1.38.0.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977623] [NEW] unable to mirror repos with no dest

2022-06-03 Thread AEA IT

Public bug reported:

When trying to mirror something like the r-project they don't have a
dest folder.  https://cloud.r-project.org/bin/linux/ubuntu/bionic-
cran40/.  I can set the url to cloud.r-project.org/bin/linux/ubuntu and
use remoteroot as focal-cran40 but then it wants to append /dest/// to
the url.

$host="cloud.r-project.org/bin/linux/ubuntu";

$remoteroot=("focal-cran40" , 'bionic-cran40');
$download_method="https";
$check_gpg=0;
@rsync_extra=( 'none',);

@dists=( '/',);
@sections=( '/',);
@arches=( 'amd64',);

** Affects: debmirror (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/1977623

Title:
  unable to mirror repos with no dest

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1977623/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977622] [NEW] Bionic update: upstream stable patchset 2022-06-03

2022-06-03 Thread Kamal Mostafa

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2022-06-03
   from git://git.kernel.org/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977622

Title:
  Bionic update: upstream stable patchset 2022-06-03

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977622/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets

2022-06-03 Thread Bodong Wang

Need to revert this patch as it introduces a new issue for IPSec.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974096

Title:
  cls_flower: Fix inability to match GRE/IPIP packets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974096/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Removing the SLAAC addresses with `ip addr del` or disabling RA's
- altogether is the only way to stop NetworkManager from prefering SLAAC
+ altogether is the only way to stop NetworkManager from preferring SLAAC
  over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case.
  
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

Thanks for the testing and feedback, I've uploaded the fix in the SRU
reviews queue now

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958267

Title:
  wpa can't connect to servers using TLS 1.1 or older

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

2022-06-03 Thread Luís Cunha dos Reis Infante da Câmara

Looking at the changelog of 1.38.0:


* Fix bug setting priority for IP addresses.

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS

So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
- Physically removing the SLAAC addresses or disabling RA's altogether is
- the only way to stop NetworkManager from prefering SLAAC over DHCPv6
- now.
+ Removing the SLAAC addresses with `ip addr del` or disabling RA's
+ altogether is the only way to stop NetworkManager from prefering SLAAC
+ over DHCPv6 now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
  When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
  addresses. With NetworkManager 1.36.4 this was not the case.
  
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2

Running Lintian on the changes file for Ubuntu 22.04 (amd64) reports the
following warnings:

W: ffmpeg-dbgsym: elf-error In program headers: Unable to find program 
interpreter name 
[usr/lib/debug/.build-id/01/31a3a53a5037d9cfce0b08e65bdf645b5fc6a6.debug]
W: ffmpeg-dbgsym: elf-error In program headers: Unable to find program 
interpreter name 
[usr/lib/debug/.build-id/11/d6ba1af19b58684bb4d9ec94ce27e8875a9a86.debug]
W: ffmpeg-dbgsym: elf-error In program headers: Unable to find program 
interpreter name 
[usr/lib/debug/.build-id/ca/9a440e0e634449b6d5c328fbc4868d4d3ff142.debug]
W: ffmpeg-dbgsym: elf-error In program headers: Unable to find program 
interpreter name 
[usr/lib/debug/.build-id/d8/68041f35b67ed9d73e571b7e178cafffac394d.debug]
W: ffmpeg source: orig-tarball-missing-upstream-signature 
ffmpeg_4.4.2.orig.tar.xz

The last warning can be fixed with the signature in comment 17.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970674

Title:
  New bug fix releases 3.4.11, 4.2.7 and 4.4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975875] Re: libgail-3-0 install blocked by "=" dependency

No worry, thanks for following up. I will still check with our oem team
to make sure updates are enabled by default on those images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975875

Title:
  libgail-3-0 install blocked by "=" dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1975875/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977620] [NEW] package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-510 package post-installation script subprocess returned error exit status 10

2022-06-03 Thread mathieg2

Public bug reported:

Install failure after ubuntu upgrade to 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jun  3 22:46:18 2022
ErrorMessage: installed nvidia-dkms-510 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2014-12-28 (2714 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.5
SourcePackage: nvidia-graphics-drivers-510
Title: package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to 
install/upgrade: installed nvidia-dkms-510 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: Upgraded to jammy on 2022-06-03 (0 days ago)

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977620

Title:
  package nvidia-dkms-510 510.73.05-0ubuntu0.22.04.1 failed to
  install/upgrade: installed nvidia-dkms-510 package post-installation
  script subprocess returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1977620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977621] [NEW] Transparency come and go

2022-06-03 Thread Robert Dinse

Public bug reported:

Prior to upgrading to 22.04 everything worked as expected, after upgrading my 
panels are no longer transparent.  The mate-tweak settings are not properly 
applied during login or reboot.  If I after
reboot set my panels transparent again, sometimes it will let me, sometimes it 
won't.  If it lets
me, the next time I logout and login again they are no longer transparent.  I 
am not using Wayland, I use the Xorg Intel kernel server, this because I have 
Intel graphics and use virtualized GPU on a virtual machine, this does not work 
with Wayland and for that matter neither does Synaptic.  Really
I wish Wayland and Systemd and a bunch of the other modern atrocities that have 
transformed Ubuntu from a good reliable OS into an unstable difficult OS would 
just die.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mate-desktop 1.26.0-1
Uname: Linux 5.17.12 x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Jun  3 14:51:00 2022
SourcePackage: mate-desktop
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mate-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977621

Title:
  Transparency come and go

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1977621/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/exim4/+git/exim4/+merge/423963

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214

Title:
  Segfaults on verify callout, in _gnutls_trust_list_get_issuer

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976154] Re: nvidia-kernel-source-510 510.73.05-0ubuntu0.22.04.1: nvidia kernel module failed to build

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976154

Title:
  nvidia-kernel-source-510 510.73.05-0ubuntu0.22.04.1: nvidia kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1976154/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] Re: DHCPv6 addresses are no longer preferred over SLAAC addresses

** Description changed:

  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be preferred
  over SLAAC addresses when available.
  
  NetworkManager has always been able to adhere to that by simply setting
  ip6.privacy=0 for the connection.
  
  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.
  
  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr = 0 and
  net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
  has any effect.
  
  Physically removing the SLAAC addresses or disabling RA's altogether is
  the only way to stop NetworkManager from prefering SLAAC over DHCPv6
  now.
  
  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS
  
+ When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6
+ addresses. With NetworkManager 1.36.4 this was not the case.
+ 
  Unfortunately, this introduced this bug, which is really breaking a lot
  of my use cases.
  
  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

2022-06-03 Thread Bug Watch Updater

Launchpad has imported 48 comments from the remote bug at
http://bugs.exim.org/show_bug.cgi?id=2886.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2022-05-11T18:41:54+00:00 Gedalya-b wrote:

Created attachment 1414
exim4-daemon-light 4.96~RC0-1

Versions: 4.94 good, 4.9[56] bad.
OS: Debian testing x86_64
TLS: gnutls 3.7.4-2, haven't tried OpenSSL

This doesn't happen in an immediate delivery attempt or in "exim -M",
but in a queue runner, if the first remote server responds with a
deferral, exim crashes some time when talking to the next server. It can
happen in tls_close() (after the message was successfully delivered, if
the remote parry allows, or after getting a deferral): smtp_deliver ->
tls_close -> gnutls_certificate_free_credentials ->
gnutls_x509_trust_list_deinit,

or it can be: smtp_deliver -> smtp_setup_conn -> tls_client_start ->
verify_certificate -> gnutls_certificate_verify_peers2 ->
gnutls_certificate_verify_peers -> _gnutls_x509_cert_verify_peers ->
gnutls_x509_trust_list_verify_crt2 -> gnutls_x509_trust_list_get_issuer
-> _gnutls_trust_list_get_issuer

And on one occasion it crashed in arc_sign() (on an exim thus built)

But long story short, it seems like exim would consistently crash,
SIGFPE or SIGSEGV, during a subsequent delivery attempt after a deferral
response.

The real life circumstances are a gmail account over quota or a
forwarded message graylisted by gmail or such. But I am reproducing this
by simply configuring my own exim servers to defer.

Attached is a log excerpt and backtrace from Debian's exim4-daemon-light
4.96~RC0-1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/0


On 2022-05-11T18:55:58+00:00 Gedalya-b wrote:

Created attachment 1415
backtrace for crash during ARC signing

Adding a backtrace for crash in arc_sign()

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/1


On 2022-05-11T19:02:45+00:00 Gedalya-b wrote:

The deferrals are either in response to RCPT TO (gmail over quota) or
post DATA (suspicious content)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/2


On 2022-05-12T12:50:56+00:00 Jgh146exb wrote:

This needs following up; we can't trust that bt

>  warning: core file may not match specified executable file.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/3


On 2022-05-12T13:02:51+00:00 Gedalya-b wrote:

If I go out of my way to invoke "/usr/sbin/exim4 -q" when causing the crash, 
that message is not displayed.
On Debian, /usr/sbin/exim -> exim4. One naturally uses "exim -q", and gdb gives 
that message, every single time. The rest of the bt seems unaffected.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/4


On 2022-05-12T13:06:48+00:00 Gedalya-b wrote:

Either way I think this should be very easily reproducible, I've tried
several boxes, several custom builds, with or without ARC, DMARC, MySQL
and so on, exim 4.95 and 4.96, the only thing in common was that I was
using Debian's packaging and stuck with gnutls.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/5


On 2022-05-12T14:32:56+00:00 Jgh146exb wrote:

I wonder if your build is failing to null-fill not-specifically-initialized
file-scope statics?

#0  0x5620ff359503 in arc_sign (signspec=,
sigheaders=0x5621001fc580, errstr=errstr@entry=0x7ffd081d0980) at
./b-exim4-daemon-custom/build-Linux-x86_64/arc.c:1663

   1660 if ((rheaders = arc_sign_scan_headers(_sign_ctx, sigheaders)))
   1661   {
   1662   hdr_rlist ** rp;
   1663   for (rp = _rlist; *rp; ) rp = &(*rp)->prev;
   1664   *rp = rheaders;
   1665   }


What do "p *rp"  and "p headers_rlist" say for that core?
(On that theory, an "=NULL" at line 93 would help.  But only for the arcsigning
case).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/comments/6


On 2022-05-12T14:38:25+00:00 Gedalya-b wrote:

I didn't keep that exact same core, but I have a new one that seems
equivalent.

#0  0x559e51e3 in arc_sign (signspec=, 
sigheaders=0x559e529bb580, errstr=errstr@entry=0x7ffcc0624e20) at 
./b-exim4-daemon-custom/build-Linux-x86_64/arc.c:1663
rp =

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/exim4/+git/exim4/+merge/423962

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214

Title:
  Segfaults on verify callout, in _gnutls_trust_list_get_issuer

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

2022-06-03 Thread Luís Cunha dos Reis Infante da Câmara

Do you mean after this update? Could you do a new report and include
details on the step to trigger the issue?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2

Patch for typo in architecture name for Ubuntu 22.04

** Patch added: "architecture_typo_jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+attachment/5594759/+files/architecture_typo_jammy.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970674

Title:
  New bug fix releases 3.4.11, 4.2.7 and 4.4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Tags added: server-todo

** Changed in: exim4 (Ubuntu Jammy)
   Status: Triaged => In Progress

** Changed in: exim4 (Ubuntu Kinetic)
   Status: Triaged => In Progress

** Bug watch added: Debian Bug tracker #1004740
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740

** Also affects: exim4 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004740
   Importance: Unknown
   Status: Unknown

** Also affects: exim via
   http://bugs.exim.org/show_bug.cgi?id=2886
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974214

Title:
  Segfaults on verify callout, in _gnutls_trust_list_get_issuer

To manage notifications about this bug go to:
https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977619] [NEW] DHCPv6 addresses are no longer preferred over SLAAC addresses

Public bug reported:

My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.

NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the connection.

So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
address would be used to connect to the outside world.

Since the update to 1.36.6, this is no longer the case. NetworkManager
now routes outgoing traffic through the SLAAC address, even if
ip6.privacy=0 is set for the connection. Setting
net.ipv6.conf.all.use_tempaddr = 0 and
net.ipv6.conf..use_tempaddr = 0 with sysctl also no longer
has any effect.

Physically removing the SLAAC addresses or disabling RA's altogether is
the only way to stop NetworkManager from prefering SLAAC over DHCPv6
now.

Looking at the changelog of NetworkManager 1.36.6, things regarding IP
address order and temporary addresses have been changed in that release:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

Unfortunately, this introduced this bug, which is really breaking a lot
of my use cases.

I should note that the bug is not present in NetworkManager 1.38.0 on
Debian sid. That just prefers DHCPv6 addresses when available, like it
should.

** Affects: network-manager (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/1977619

Title:
  DHCPv6 addresses are no longer preferred over SLAAC addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1281652] Re: AutomocInfo.cmake.in depends on environment variables

2022-06-03 Thread Timo Röhling

** Changed in: cmake (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/1281652

Title:
  AutomocInfo.cmake.in depends on environment variables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1281652/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973784] Re: [MIR] libldac

2022-06-03 Thread Luís Cunha dos Reis Infante da Câmara

libldac 2.0.2.3+git20200429+ed310a0-4ubuntu1 in kinetic: universe/misc -> main
Override [y|N]? y
1 publication overridden.


** Changed in: libldac (Ubuntu)
   Status: In Progress => 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/1973784

Title:
  [MIR] libldac

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libldac/+bug/1973784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977506] Re: installation crash

2022-06-03 Thread Seth Arnold

** Information type changed from Private Security 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/1977506

Title:
  installation crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1977506/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953373] Re: cmake does not find FindQuaZip-Qt5.cmake

2022-06-03 Thread Timo Röhling

** Changed in: cmake (Ubuntu)
   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/1953373

Title:
  cmake does not find FindQuaZip-Qt5.cmake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1953373/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 969891] Re: cmake fails with current libgtest-dev 1.6.0-1ubuntu4

2022-06-03 Thread Timo Röhling

** Changed in: cmake (Ubuntu)
   Status: Confirmed => 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/969891

Title:
  cmake fails with current libgtest-dev 1.6.0-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/969891/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2

All tests from the upstream testsuite (FATE) pass on 22.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970674

Title:
  New bug fix releases 3.4.11, 4.2.7 and 4.4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974428] Re: Update to the current 1.36 stable version

All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977617] Re: ddebs.ubuntu.com size mismatch error on repository metadata after updates

2022-06-03 Thread Jack Aboutboul

** Description changed:

  Hello, this is a follow up bug which is being seen after RT Ticket
- #61842 was resolves. It seems as though, after the repository is updated
+ #61842 was resolved. It seems as though, after the repository is updated
  there is a period of time where we are seeing size mismatch errors on
  the metadata. Perhaps it is being generated at an interval which is not
  in sync with the repository?
  
  If someone could look into this it would be appreciated as we consume
  these packages as part of our build pipelines and it is causing builds
  to error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977617

Title:
  ddebs.ubuntu.com size mismatch error on repository metadata after
  updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1977617/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer

** Description changed:

+ [ Impact ]
+ 
+ When the user sends a message to someone, if the server responsible for
+ receiving this message defers it, and if there are other possible
+ servers (i.e., other servers listed as secondary MX) to try, exim4 will
+ segfault while trying to connect to the second server.
+ 
+ [ Test Case ]
+ 
+ The test case for this bug is a bit involved.  It makes use of the
+ upstream reporter's mail server, which has been configured to defer
+ emails when they come through the primary MX, but accept when they come
+ through the secondary MX.  This means that you will need access to port
+ 25 (unfortunately canonistack seems to block it).
+ 
+ $ lxc launch ubuntu-daily:jammy exim4-bug1974214
+ $ lxc shell exim4-bug1974214
+ # apt update && apt full-upgrade
+ # apt install -y exim4
+ # dpkg-reconfigure exim4-config
+ ... In the "Mail Server configuration" screen, select "internet site; mail is 
sent and received directly using SMTP".  Leave everything else untouched.
+ # cat > /etc/netplan/99-disable-ipv6.yaml << _EOF_
+ network:
+   ethernets:
+ eth0:
+   link-local: [ ipv4 ]
+ _EOF_
+ # netplan apply
+ # reboot
+ $ lxc shell exim4-bug1974214
+ # cat > 1.msg << _EOF_
+ Subject: test
+ 
+ this is a test
+ _EOF_
+ # exim4 -odq -f defe...@example.com geda...@gedalya.net < 1.msg
+ # exim4 -bp
+  0m   321 1nxC3o-Ax-AS 
+   geda...@gedalya.net
+ 
+ ... You will have to grab the message ID, which is 1nxC3o-Ax-AS in
+ this case.  You have to use this ID in the following command.
+ 
+ # exim4 -d+all -q 1nxC3o-Ax-AS 2>&1 | tee /tmp/exim.debug
+ ...
+ # grep SEGV /tmp/exim.debug
+ 
+ You should be able to see exim4 signalling the segmentation fault that
+ occurred while attempting to connect to the second server.
+ 
+ [ Where problems could occur ]
+ 
+ The patches, albeit well contained and relatively simple, touch code
+ that deals with TLS and security.  There is always the risk of
+ introducing an unwanted vulnerability or normal regression here.  If
+ that happens, the very first thing we need to do is revert the patches
+ and work with upstream to develop a fix.
+ 
+ [ Original Description ]
+ 
  We are experiencing segfaults in exim since upgrading from impish
  (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy
  (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in
  _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify
  callout during message submission.
  
  Typically the initial attempt to submit a message crashes an exim child
  thread, but the same message is accepted when the sender retries.
  
  gdb backtrace:
  
  Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7fe2f844d080 (LWP 29278)]
  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, 
issuer=, cert=, list=) at 
x509/../../../lib/x509/verify-high.c:1026
  1026x509/../../../lib/x509/verify-high.c: No such file or directory.
  (gdb) bt
  #0  0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=,
  list=) at x509/../../../lib/x509/verify-high.c:1026
  #1  gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, 
cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510,
  flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129
  #2  0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 
(list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0,
  cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0)
  at x509/../../../lib/x509/verify-high.c:1522
  #3  0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers 
(status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150)
  at ../../lib/cert-session.c:597
  #4  gnutls_certificate_verify_peers (session=0x55ef6c0c1150, 
data=data@entry=0x0, elements=elements@entry=0,
  status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776
  #5  0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 
(session=, status=status@entry=0x7ffc82dba888)
  at ../../lib/cert-session.c:653
  #6  0x55ef6b7698ef in verify_certificate (state=, 
errstr=0x7ffc82dbaa20)
  at 
/build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519
  #7  0x55ef6b7a5d7b in tls_client_start.constprop.0 
(cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8,
  tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, 
cookie=)
  at 
/build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593
  #8  0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, 
suppress_tls=) at transports/smtp.c:2673
  #9  0x55ef6b776350 in do_callout (pm_mailfrom=, 
se_mailfrom=, options=,
  callout_connect=, callout_overall=, 
callout=, tf=0x7ffc82dbbc10,
  host_list=, addr=0x7ffc82dbbdd0)
  at 
/build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:677
  #10 verify_address (vaddr=, fp=, 
options=,

[Bug 1887195] Re: [snap] "Show in folder" for downloaded files doesn't work

2022-06-03 Thread Fink Nottle

Note that the issue is that the file is not highlighted. It always
opened the correct directory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887195

Title:
  [snap] "Show in folder" for downloaded files doesn't work

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1887195/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976361] Re: man page “passes the buck” to a dead end for .netrc docs

2022-06-03 Thread Matthias Andree

Athos, just to make sure we do not misunderstand: there has been no word of 
patches from me. 
Any downstream backporting will be "pluck the commits from Git repo and 
integrate them yourselves". I may answer questions, but I will not sort out the 
SRU merge for Ubuntu Linux.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976361

Title:
  man page “passes the buck” to a dead end for .netrc docs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1976361/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977617] [NEW] ddebs.ubuntu.com size mismatch error on repository metadata after updates

2022-06-03 Thread Jack Aboutboul

Public bug reported:

Hello, this is a follow up bug which is being seen after RT Ticket
#61842 was resolves. It seems as though, after the repository is updated
there is a period of time where we are seeing size mismatch errors on
the metadata. Perhaps it is being generated at an interval which is not
in sync with the repository?

If someone could look into this it would be appreciated as we consume
these packages as part of our build pipelines and it is causing builds
to error.

** Affects: 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/1977617

Title:
  ddebs.ubuntu.com size mismatch error on repository metadata after
  updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1977617/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket

2022-06-03 Thread Lucas Kanashiro

** Description changed:

+ [Impact]
+ 
+ The package is FTBFSing in Jammy which does not allow anyone to perform
+ any kind of update there. This package is in main and to be fully
+ supported one needs to be able to rebuild it and perform updates.
+ 
+ [Test Plan]
+ 
+ Build the package in jammy successfully.
+ 
+ [Where problems could occur]
+ 
+ It could pull in different version of build dependencies causing
+ unexpected issues. I do not foresee any issue TBH.
+ 
+ [Original description]
+ 
  as seen in a test rebuild, this package fails to build in the jammy
  release pocket (note the log behind the link might go away):
  
  https://launchpadlibrarian.net/604215677/buildlog_ubuntu-jammy-
  amd64.rubygems_3.3.5-2_BUILDING.txt.gz
  
  [...]
  
  
---
  2205 tests, 5870 assertions, 5 failures, 0 errors, 42 pendings, 0 omissions, 
0 notifications
  97.8685% passed
  
---
  71.17 tests/s, 189.47 assertions/s
  rake aborted!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976264

Title:
  rubygems ftbfs in the jammy release pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736583] Re: Evince annotations lost on save

2022-06-03 Thread kinow

Just had the same issue.

```
kinow@ranma:~$ uname -a
Linux ranma 5.4.0-113-generic #127-Ubuntu SMP Wed May 18 14:30:56 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
kinow@ranma:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"
```

evince 3.36.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736583

Title:
  Evince annotations lost on save

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1736583/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799268] Re: CIFS option 'cruid' does not appear to work properly with 'multiuser' and 'vers=1.0'

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cifs-utils (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799268

Title:
  CIFS option 'cruid' does not appear to work properly with 'multiuser'
  and 'vers=1.0'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1799268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799268] Re: CIFS option 'cruid' does not appear to work properly with 'multiuser' and 'vers=1.0'

2022-06-03 Thread William Blew

I have precisely the same issue. Here is a related RedHat bug. It seems
they fixed it, twice, and pushed two? patches upstream. The first
attempt got merged, but their second more complete patch (that seems to
address this scenario) seems to have gone missing.

Here is the RedHat bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=517195

Edited: While following up, I realized that while the RedHat bug's
commentary implies there was a later, more complete fix, I could not
find any such patch attached to that bug report.

** Bug watch added: Red Hat Bugzilla #517195
   https://bugzilla.redhat.com/show_bug.cgi?id=517195

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799268

Title:
  CIFS option 'cruid' does not appear to work properly with 'multiuser'
  and 'vers=1.0'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1799268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977614] [NEW] [MIR] fdk-aac

2022-06-03 Thread Jeremy Bicha

Public bug reported:

[Availability]
The package fdk-aac is already in Ubuntu **multiverse**.

The package fdk-aac builds for the architectures it is designed to work on.
It currently builds and works for architetcures: amd64 arm64 armhf ppc64el 
riscv64 s390x
Link to package https://launchpad.net/ubuntu/+source/fdk-aac

[Rationale]
- fdk-aac will be required by gnome-remote-desktop 43 to allow audio forwarding 
from the Ubuntu desktop host to the remote client.

- fdk-aac is required in Ubuntu main no later than Aug 25 due to kinetic
feature freeze

[Security]
- No CVEs/security issues in this software in the past

- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Package does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024)
- Packages does not contain extensions to security-sensitive software

[Quality assurance - function/usage]
- The package works well right after install

[Quality assurance - maintenance]
- The package is maintained well in Debian/Ubuntu and has no open bug reports 
except for this MIR and a similar "move to main" bug in Debian
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/fdk-aac
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=fdk-aac
- The package does not deal with exotic hardware we cannot support

[Quality assurance - testing]
- The package does not run tests at build time because upstream doesn't provide 
one

- The package does not run an autopkgtest

[Quality assurance - packaging]
- debian/watch is present. It wasn't working so I pushed a trivial fix to the 
Salsa packaging repo.

- No significant Lintian warnings or errors
https://lintian.debian.org/sources/fdk-aac

- Lintian overrides are not present

- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies

- The package will be installed by default, but does not ask debconf
questions

- Packaging and build is easy, link to d/rules
https://salsa.debian.org/multimedia-team/fdk-aac/-/blob/master/debian/rules

[UI standards]
- Application is not end-user facing (does not need translation)

[Dependencies]
- No further depends or recommends dependencies that are not yet in main

[Standards compliance]
- This package correctly follows FHS and Debian Policy

[Maintenance/Owner]
- Owning Team will be desktop-packages
- Team is not yet, but will subscribe to the package before promotion

- This does not use static builds
- This does not use vendored code

- The package successfully built during the most recent test rebuild

[Background information]
The Package description explains the package well
Upstream Name is fdk-aac
Link to upstream project https://github.com/mstorsjo/fdk-aac

fdk-aac is currently in Debian non-free. It has been in the Debian NEW
queue since the end of January waiting for ftpmasters to review it for a
move to Debian main. Some discussion (from people who aren't ftpmasters)
at https://bugs.debian.org/981285

** Affects: fdk-aac (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977614

Title:
  [MIR] fdk-aac

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fdk-aac/+bug/1977614/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872255] Re: mate-tweak doesn't save custom panels correctly 20.04 beta

2022-06-03 Thread arQon

Sorry Wimpy - I just did fresh installs of two machines with 20.04.4,
and the bug triggered on one of them, i.e. the fix is incomplete.

Examining the .panel and .layout files in pluma, I can see that the
problem element (mate-control-center) is listed in the files twice
(elements 2 and 15) - which is "correct", in that I had to add it a
second time because the panel failed to show it after the first reboot -
but removing the second instance (via the UI) means that on the next
reboot the element isn't displayed at all, UNTIL another item (of any
type) is added to the panel. If that "new" item is a duplicate, then the
same "either 0 or 2, but never 1" bug triggers again, repeat ad
infinitum.

ISTR a very detailed breakdown of this a few years ago in the UM forums
here: https://ubuntu-mate.community/t/19-10-loading-saving-custom-panel-
layouts-is-utterly-broken/20340/10 which I think certainly provides
everything one could ever want to know about the *bug*, but obv doesn't
provide the solution.

add> To be clear, this is not a multi-monitor issue: both of today's
machines are laptops with a single inbuilt screen and no external
display.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872255

Title:
  mate-tweak doesn't save custom panels correctly 20.04 beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-tweak/+bug/1872255/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969939] Re: puppet 5 package incompatible with ruby 3 / ubuntu 22.04

2022-06-03 Thread Lucas Kanashiro

Thanks for the feedback everyone. I'll give a chance to others to test
it over the weekend, if I get no negative feedback until Monday I'll be
uploading this fix to kinetic and SRU it to jammy.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939

Title:
  puppet 5 package incompatible with ruby 3 / ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1969939/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977567] Re: security oversight that makes users vulnerable to doxxing

2022-06-03 Thread Bill Yikes

** Description changed:

  Neomutt gives no possible way to send a PGP-encrypted msg and then save
  an unencrypted local copy. This forces users to choose from the
  following workflows:
  
  1) Encrypt the msg only to the recipients & store a copy of it, which
  the sender can never again see the payload they sent. In this case the
  body of the msg is just a useless & space-wasting blob. The sender can
  have a record that they sent a msg (the metadata) but no way to recall
  what they sent. In fact the payload serves as a risk with zero benefit,
  because in the event that the recipients key is compromized the sender’s
  copy can then be read by an adversary.
  
  2) The sender adds an “encrypt-to” config option to gpg.conf that causes
  all msgs sent to be encrypted to themself. This enables the sender to
  keep an accessible record of what they sent out. One side-effect is that
  they may choose to keep email records longer than they keep their
  private key, and so when they lose or delete their private key or
  password, they can no longer access records of what they sent. That’s
  not serious, but consider this scenario: Alice anonymously sends a
  highly sensitive PGP-encrypted msg to wikileaks & forgets that she has
  everything set to encrypt to self. Wikileaks (or someone forcing
  wikileaks) can run pgpdump on the encrypted payload and see Alice’s
  keyID. Doxxed!
  
  Both options 1 & 2 need improvement.
  
  Approach 1 can be improved by giving users the option to store metadata
  only. Mutt should save only the headers (perhaps including the original
  payload size), but delete the payload itself both for security and for
  wiser use of storage space.
  
  Approach 2 should perhaps be possible for users who want that option
  (everyone has their own threat model), but there needs to a be a 3rd
  option: give users the possibility to store a plaintext copy so they are
  not always at risk of accidentally doxxing themselves.
+ 
+ (edit)
+ The fcc_clear option is that 3rd option. So a lot of this is moot now. But 
note two problems still remain:
+ 
+ * wasted space if a user chooses approach one
+ 
+ * the fcc_clear behavior leaves no trace that the msg was sent encrypted
+ which is a bit annoying. It’s useful to know when looking at old sent
+ msgs whether or not a msg was encrypted.  Ideally mutt should add a
+ header that lists encrypted recipients.  E.g.:
+ 
+ X-Mutt-PGP-Encrypted-To: 0xabc123 0xdef456

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977567

Title:
  security oversight that makes users vulnerable to doxxing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neomutt/+bug/1977567/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket

2022-06-03 Thread Lucas Kanashiro

** Changed in: rubygems (Ubuntu Kinetic)
   Status: Triaged => Fix Committed

** Changed in: rubygems (Ubuntu Jammy)
   Status: Triaged => 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/1976264

Title:
  rubygems ftbfs in the jammy release pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976264] Re: rubygems ftbfs in the jammy release pocket

** Merge proposal linked:
   
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/rubygems/+git/rubygems/+merge/423957

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976264

Title:
  rubygems ftbfs in the jammy release pocket

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rubygems/+bug/1976264/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965808] Re: [SRU] 2.55.5

This bug was fixed in the package snapd - 2.56+22.10

---
snapd (2.56+22.10) kinetic; urgency=medium

  * New upstream release, LP: #1974147
- portal-info: Add CommonID Field
- asserts/info,mkversion.sh: capture max assertion formats in
  snapd/info
- tests: improve the unit testing workflow to run in parallel
- interfaces: allow map and execute permissions for files on
  removable media
- tests: add spread test to verify that connections are preserved if
  snap refresh fails
- tests: Apparmor sandbox profile mocking
- cmd/snap-fde-keymgr: support for multiple devices and
  authorizations for add/remove recovery key
- cmd/snap-bootstrap: Listen to keyboard added after start and
  handle switch root
- interfaces,overlord: add support for adding extra mount layouts
- cmd/snap: replace existing code for 'snap model' to use shared
  code in clientutil (2/3)
- interfaces: fix opengl interface on RISC-V
- interfaces: allow access to the file locking for cryptosetup in
  the dm-crypt interface
- interfaces: network-manager: add AppArmor rule for configuring
  bridges
- i/b/hardware-observe.go: add access to the thermal sysfs
- interfaces: opengl: add rules for NXP i.MX GPU drivers
- i/b/mount_control: add an optional "/" to the mount target rule
- snap/quota: add values for journal quotas (journal quota 2/n)
- tests: spread test for uc20 preseeding covering snap prepare-image
- o/snapstate: remove deadcode breaking static checks
- secboot/keymgr: extend unit tests, add helper for identify keyslot
  used error
- tests: use new snaps.name and snaps.cleanup tools
- interfaces: tweak getPath() slightly and add some more tests
- tests: update snapd testing tools
- client/clientutil: add shared code for printing model assertions
  as yaml or json (1/3)
- debug-tools: list all snaps
- cmd/snap: join search terms passed in the command line
- osutil/disks: partition UUID lookup
- o/snapshotstate: refactor snapshot read/write logic
- interfaces: Allow locking in block-devices
- daemon: /v2/system-recovery-keys remove API
- snapstate: do not auto-migrate to ~/Snap for core22 just yet
- tests: run failed tests by default
- o/snapshotstate: check installed snaps before running 'save' tasks
- secboot/keymgr: remove recovery key, authorize with existing key
- deps: bump libseccomp to include build fixes, run unit tests using
  CC=clang
- cmd/snap-seccomp: only compare the bottom 32-bits of the flags arg
  of copy_file_range
- osutil/disks: helper for obtaining the UUID of a partition which
  is a mount point source
- image/preseed: umount the base snap last after writable paths
- tests: new set of nested tests for uc22
- tests: run failed tests on nested suite
- interfaces: posix-mq: add new interface
- tests/main/user-session-env: remove openSUSE-specific tweaks
- tests: skip external backend in mem-cgroup-disabled test
- snap/quota: change the journal quota period to be a time.Duration
- interfaces/apparmor: allow executing /usr/bin/numfmt in the base
  template
- tests: add lz4 dependency for jammy to avoid issues repacking
  kernel
- snap-bootstrap, o/devicestate: use seed parallelism
- cmd/snap-update-ns: correctly set sticky bit on created
  directories where applicable
- tests: install snapd while restoring in snap-mgmt
- .github: skip misspell and ineffassign on go 1.13
- many: use UC20+/pre-UC20 in user messages as needed
- o/devicestate: use snap handler for copying and checksuming
  preseeded snaps
- image, cmd/snap-preseed: allow passing custom apparmor features
  path
- o/assertstate: fix handling of validation set tracking update in
  enforcing mode
- packaging: restart our units only after the upgrade
- interfaces: add a steam-support interface
- gadget/install, o/devicestate: do not create recovery and
  reinstall keys during installation
- many: move recovery key responsibility to devicestate/secboot,
  prepare for a future with just optional recovery key
- tests: do not run mem-cgroup-disabled on external backends
- snap: implement "star" developers
- o/devicestate: fix install tests on systems with
  /var/lib/snapd/snap
- cmd/snap-fde-keymgr, secboot: followup cleanups
- seed: let SnapHandler provided a different final path for snaps
- o/devicestate: implement maybeApplyPreseededData function to apply
  preseed artifact
- tests/lib/tools: add piboot to boot_path()
- interfaces/builtin: shared-memory drop plugs allow-installation:
  true
- tests/main/user-session-env: for for opensuse
- cmd/snap-fde-keymgr, secboot: add a tiny FDE key manager
- tests: re-execute the failed tests when "Run failed" label is set
  in the PR
-

[Bug 1974147] Re: [SRU] 2.56

This bug was fixed in the package snapd - 2.56+22.10

---
snapd (2.56+22.10) kinetic; urgency=medium

  * New upstream release, LP: #1974147
- portal-info: Add CommonID Field
- asserts/info,mkversion.sh: capture max assertion formats in
  snapd/info
- tests: improve the unit testing workflow to run in parallel
- interfaces: allow map and execute permissions for files on
  removable media
- tests: add spread test to verify that connections are preserved if
  snap refresh fails
- tests: Apparmor sandbox profile mocking
- cmd/snap-fde-keymgr: support for multiple devices and
  authorizations for add/remove recovery key
- cmd/snap-bootstrap: Listen to keyboard added after start and
  handle switch root
- interfaces,overlord: add support for adding extra mount layouts
- cmd/snap: replace existing code for 'snap model' to use shared
  code in clientutil (2/3)
- interfaces: fix opengl interface on RISC-V
- interfaces: allow access to the file locking for cryptosetup in
  the dm-crypt interface
- interfaces: network-manager: add AppArmor rule for configuring
  bridges
- i/b/hardware-observe.go: add access to the thermal sysfs
- interfaces: opengl: add rules for NXP i.MX GPU drivers
- i/b/mount_control: add an optional "/" to the mount target rule
- snap/quota: add values for journal quotas (journal quota 2/n)
- tests: spread test for uc20 preseeding covering snap prepare-image
- o/snapstate: remove deadcode breaking static checks
- secboot/keymgr: extend unit tests, add helper for identify keyslot
  used error
- tests: use new snaps.name and snaps.cleanup tools
- interfaces: tweak getPath() slightly and add some more tests
- tests: update snapd testing tools
- client/clientutil: add shared code for printing model assertions
  as yaml or json (1/3)
- debug-tools: list all snaps
- cmd/snap: join search terms passed in the command line
- osutil/disks: partition UUID lookup
- o/snapshotstate: refactor snapshot read/write logic
- interfaces: Allow locking in block-devices
- daemon: /v2/system-recovery-keys remove API
- snapstate: do not auto-migrate to ~/Snap for core22 just yet
- tests: run failed tests by default
- o/snapshotstate: check installed snaps before running 'save' tasks
- secboot/keymgr: remove recovery key, authorize with existing key
- deps: bump libseccomp to include build fixes, run unit tests using
  CC=clang
- cmd/snap-seccomp: only compare the bottom 32-bits of the flags arg
  of copy_file_range
- osutil/disks: helper for obtaining the UUID of a partition which
  is a mount point source
- image/preseed: umount the base snap last after writable paths
- tests: new set of nested tests for uc22
- tests: run failed tests on nested suite
- interfaces: posix-mq: add new interface
- tests/main/user-session-env: remove openSUSE-specific tweaks
- tests: skip external backend in mem-cgroup-disabled test
- snap/quota: change the journal quota period to be a time.Duration
- interfaces/apparmor: allow executing /usr/bin/numfmt in the base
  template
- tests: add lz4 dependency for jammy to avoid issues repacking
  kernel
- snap-bootstrap, o/devicestate: use seed parallelism
- cmd/snap-update-ns: correctly set sticky bit on created
  directories where applicable
- tests: install snapd while restoring in snap-mgmt
- .github: skip misspell and ineffassign on go 1.13
- many: use UC20+/pre-UC20 in user messages as needed
- o/devicestate: use snap handler for copying and checksuming
  preseeded snaps
- image, cmd/snap-preseed: allow passing custom apparmor features
  path
- o/assertstate: fix handling of validation set tracking update in
  enforcing mode
- packaging: restart our units only after the upgrade
- interfaces: add a steam-support interface
- gadget/install, o/devicestate: do not create recovery and
  reinstall keys during installation
- many: move recovery key responsibility to devicestate/secboot,
  prepare for a future with just optional recovery key
- tests: do not run mem-cgroup-disabled on external backends
- snap: implement "star" developers
- o/devicestate: fix install tests on systems with
  /var/lib/snapd/snap
- cmd/snap-fde-keymgr, secboot: followup cleanups
- seed: let SnapHandler provided a different final path for snaps
- o/devicestate: implement maybeApplyPreseededData function to apply
  preseed artifact
- tests/lib/tools: add piboot to boot_path()
- interfaces/builtin: shared-memory drop plugs allow-installation:
  true
- tests/main/user-session-env: for for opensuse
- cmd/snap-fde-keymgr, secboot: add a tiny FDE key manager
- tests: re-execute the failed tests when "Run failed" label is set
  in the PR
-

[Bug 1977467] Re: Update gvfs to 1.48.2

2022-06-03 Thread Jeremy Bicha

** Description changed:

  Impact
  --
+ There was a new release in the stable 1.48 series.
+ 
+ https://gitlab.gnome.org/GNOME/gvfs/-/blob/1.48.2/NEWS
+ 
+ The biggest improvement is greater compatibility with connecting over ssh/sftp
+ https://gitlab.gnome.org/GNOME/gvfs/-/commit/f1b599da1141e
+ 
  
  Test Case
  -
+ Install the update
+ Open the Files app.
+ Connect to a variety of Other Locations.
+ - sftp
+ - Google Drive (set up with GNOME Online Accounts)
+ 
  
  What Could Go Wrong
  ---
+ gvfs provides mounting services for a variety of protocols: sftp, webdav, etc.
+ And is used in apps like Nautilus or the GTK file chooser
+ If gvfs breaks, you might not be able to access files stored on remote 
servers via your usual desktop apps.
+ 
+ gvfs is part of core GNOME and has a microrelease exception
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Changed in: gvfs (Ubuntu Jammy)
   Status: Triaged => 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/1977467

Title:
  Update gvfs to 1.48.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1977467/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594745/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594746/+files/acpidump.txt

** Changed in: ubuntu-mate
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1977476/+attachment/5594744/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594743/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594742/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594741/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594739/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594740/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1977476/+attachment/5594738/+files/PaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1977476/+attachment/5594737/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977476

Title:
  powersave governor behaves diferently after resume from suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1977476/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977476] Lsusb-t.txt