[Touch-packages] [Bug 1975549] Re: NetworkManager uses tethered Android phone as ethernet connection instead of wired ethernet connection

[Jeffrey Walton]

Sebastien, do you know how I can mark my ethernet connection as the
default one? The ethernet connection I want to set as default is the
wired ethernet, which is enp4s0 in the dumps shown above.

I cannot find a setting in the Settings program to set a default
connection. I also cannot find a discussion of it in the docs.[1,2] The
docs only say the program usually picks the right one:[1]

In most cases the wired network connection will simply work
without any changes to the default Kubuntu configuration.
Wired network connections are selected as default when they
are available.

(And it is not picking a wired connection as stated in the docs. It is
picking a Wifi connection via the Android phone).

[1] https://userbase.kde.org/Kubuntu/Basic/en#Networking
[2] https://userbase.kde.org/NetworkManagement

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1975549

Title:
  NetworkManager uses tethered Android phone as ethernet connection
  instead of wired ethernet connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm running Kubuntu 22.04 LTS, x86_64, fully patched. I've been having
  trouble the last week or two ssh'sing into the machine, and printing
  from the machine when I am sitting at the keyboard. I also could not
  connect to my external firewall when sitting at the keyboard.

  I keep a Google Pixel 4a tethered to the USB hub for charging. The
  Android phone is running Android 12, and the phone is set to "USB
  Tethering". The phone is fully patched, too.

  I found if I reboot the machine with the phone tethered, then the
  machine uses the Android phone as the ethernet connection. It
  literally calls the connection "ethernet", as if it was using the
  network adapter. This is new behavior over the last week or two.

  This is unexpected behavior for three reasons. First, it is new
  behavior. Second, the wired gigabit ethernet connection is not used by
  default. And thrid, the Android phone's connection is called
  "ethernet" instead of something more meaningful like "USB" or
  "Android" or "wired hotspot".

  The third item ("ethernet" name when using Android phone) was
  misleading enough to waste a lot of time troubleshooting the issue. I
  thought I had an odd firewall issue or a mDNS issue.

  The reason I was having so many troubles, like printing and ssh, is
  the Android phone uses Wifi and it is on a different VLAN and subnet
  to keep traffic segregated from my trusted internal network.

  -

  It looks like I am running network-manager via systemd:

  # service systemd-networkd status
  ● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendor prese>
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)
  # service network-manager  status
  ● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: >
   Active: active (running) since Mon 2022-05-23 21:16:52 EDT; 59min ago
 Docs: man:NetworkManager(8)
 Main PID: 928 (NetworkManager)
Tasks: 3 (limit: 76693)
   Memory: 12.0M
   CGroup: /system.slice/NetworkManager.service
   └─928 /usr/sbin/NetworkManager --no-daemon
...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (107 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  IpRoute:
   default via 172.16.1.1 dev enp4s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0 scope link metric 1000 
   172.16.0.0/12 dev enp4s0 proto kernel scope link src 172.16.2.10 metric 100
  Package: network-manager 1.22.10-1ubuntu2.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Tags:  focal
  Uname: Linux 5.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE  FILENAME 

   Ethernet  5d31ea14-c1cd-318f-a982-09ce6723dadb  ethernet  1653403311  Tue 24 
May 2022 10:41:51 AM EDT  yes  -100  no
/org/freedesktop/NetworkManager/Settings/1  yes enp4s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/4  -- 
/etc/NetworkManager/system-connec

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

[Gael Lafond]

Ubuntu 21.10
The issue still remain.

In colour setting window, the "remove" button is now disabled.

There is what fixed the issue for me:

Deny any access to any user to the folder contains the ICC files.

$ sudo chmod 000 ~/.local/share/icc
$ reboot

Here is how a track down the ICC folder in use:

1. Install gnome-color-manager
2. Open colour settings.
3. Click the colour profile in use and click the "View profile" button.
4. Find the path to the ICC file.
5. Deny any access to any user to the folder contains the ICC files.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/938751

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1974456] Re: regression: apt.postint fails if never previously configured

[Chris Halse Rogers]

Hello David, or anyone else affected,

Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.9 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1974456

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.36.6-0ubuntu1

---
network-manager (1.36.6-0ubuntu1) jammy; urgency=medium

  * New stable version (lp: #1974428)
  * debian/gbp.conf:
- updated the packaging vcs serie
  * d/p/supplicant-add-BIP-interface-capability.patch,
d/p/supplicant-enable-WPA3-transition-mode-only-when-interfac.patch:
- remove, included in the new version

 -- Sebastien Bacher   Fri, 20 May 2022 13:08:51
+0200

** Changed in: network-manager (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  It's a stable update from upstream, the changes are listed in the NEWS
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  * Test Case

  Since it's an update with several fixes the testing should focus on a
  specific point but rather by validating that the testplan is green,
  https://wiki.ubuntu.com/NetworkManager/DistroTesting

  * Regression potential

  There are fixes around IPv6 handling, VPN connections and the hotspot
  feature, verify that those configurations are still working as
  expected.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1974428] Update Released

[Chris Halse Rogers]

The verification of the Stable Release Update for network-manager has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1974428

Title:
  Update to the current 1.36 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  It's a stable update from upstream, the changes are listed in the NEWS
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  * Test Case

  Since it's an update with several fixes the testing should focus on a
  specific point but rather by validating that the testplan is green,
  https://wiki.ubuntu.com/NetworkManager/DistroTesting

  * Regression potential

  There are fixes around IPv6 handling, VPN connections and the hotspot
  feature, verify that those configurations are still working as
  expected.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.99.24

---
software-properties (0.99.24) kinetic; urgency=medium

  * softwareproperties/gtk/SoftwarePropertiesGtk.py:
Don't crash if the driver package does not have a matching modules package
Fixes LP: #1969460

 -- Alberto Milone   Mon, 30 May 2022
16:50:03 +0200

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1969460

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

Status in OEM Priority Project:
  New
Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  - Impact

  software-properties-gtk hit an exception when dealing some drivers

  - Test Case

  On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and
  try to install libcamhal-ipu6ep0 using software-properties-gtk

  https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57
  should not include reports on the new version

  - Regression potential

  The change make the driver code ignore one extra type of error, it
  shouldn't impact on any of the already working cases. Ensure that
  drivers that were hitting the error correctly install now

  

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22

  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.

  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1975898] Re: RM: ntp from kinetic?

[Gianfranco Costamagna]

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

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1975898

Title:
  RM: ntp from kinetic?

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  Should we delete it now that ntpsec has migrated?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

[Henrik Toth]

Same here.
Installed the Ubuntu-based Pop OS, used for a few days beside Windows 11 on the 
same dual-boot PC. 

It was OK, but a subjective feeling started to grow that the colours are
not so nice as with Windows: a bit washed-out under Linux on my HP U32,
otherwise fine display. Especially the human skin was lifeless, lacking
red. The contrast also seemed to be worse, shadows a bit too gray.

Then I noticed in Settings / Colour there is a profile called "Automatic
- HP U32 4K HDR" is installed and selected.

Clicked on "Add profile" added a plain "Standard Space - sRGB" - and display 
quality is fine now! Quite similar, perhaps the same as in Windows.
Now it is easy to quickly compare the difference: switch between these colour 
profiles, open a photo in Image Viewer, and don't have to rely on memory of the 
same photo under Windows.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/938751

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

  Originally reported in
  https://bugzilla.gnome.org/show_bug.cgi?id=675645

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1971621] Re: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-db

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnih in Ubuntu.
https://bugs.launchpad.net/bugs/1971621

Title:
  package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package
  libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-
  installable with libnih-dbus1 which has multiple installed instances

Status in libnih package in Ubuntu:
  Confirmed

Bug description:
  This is a desktop system that has been upgraded from 14.04 -> 16.04 ->
  18.04 -> 20.04.  The error happened during the upgrade process to
  22.04 (command line).  It seems similar to, but not the same as
  #1948346

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libnih-dbus1 1.0.3-6ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178
  Uname: Linux 5.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed May  4 13:59:53 2022
  DuplicateSignature:
   package:libnih-dbus1:1.0.3-6ubuntu2
   Unpacking libnfsidmap2:amd64 (0.25-6build1) over (0.25-5.1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FIA5UV/559-libnih-dbus1_1.0.3-12_amd64.deb (--unpack):
package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not 
co-installable with libnih-dbus1 which has multiple installed instances
  ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: 
no' is not co-installable with libnih-dbus1 which has multiple installed 
instances
  InstallationDate: Installed on 2014-10-10 (2763 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: libnih
  Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable 
with libnih-dbus1 which has multiple installed instances
  UpgradeStatus: Upgraded to impish on 2022-05-04 (0 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976339] Re: Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php Openssl_get_cipher_methods Function

[Dimitar Dimitrov]

Hi Paulo,
Thank you for the fast fix.
We don't have a test system for this.
I have to check on a live one (VM) after creating a snapshot.
This will be done the next evening (approx 20 hours from now).
I will keep you informed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1976339

Title:
  Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php
  Openssl_get_cipher_methods Function

Status in openssl package in Ubuntu:
  New

Bug description:
  The system is Ubuntu 16.04 with ESM support.
  After the update (28.5.2022) of openssl and libssl1.0.0 packages from 
1.0.2g-1ubuntu4.20+esm2 to 1.0.2g-1ubuntu4.20+esm3 the php function 
openssl_get_cipher_methods (php7 from the distribution) is broken.
  It randomly returns empty array when called.
  Testing from php-cli it always returns proper data.
  Testing with web server most of the times it returns an empty array.
  Tested with apache + mod-php and apache + php-fpm.
  Downgrading to versions to 1.0.2g-1ubuntu4.20 fixes the problem.
  This downgrade makes the systems work, but introduces security risks.

  An example code to reproduce the issue:
  
  
  

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Sebastien Bacher]

upstream replied

'''
NetworkManager does currently nothing at all about this.

crda binaries were deprecated, but because there is an alternative
mechanism (wireless-regdb?), isn't it?

It could be maybe added to NetworkManager, if somebody sends a patch. But it's 
not actually clear to me that this is really NetworkManager's task. Maybe it 
is, but what are the arguments for that?
'''

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Triaged
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Sebastien Bacher]

extra questions, when you wrote

> it's apparently never worked for me at home or at various friends
houses, and only once worked when I travelled to Germany for a sprint.

is that having a visible impact for users? like was your computer not
able to connect to some access point? if that's the consequence of the
issue it is a bit surprising that we got no user report of the type of
'my laptop isn't able to connect to my AP anymore since the upgrade to
the new LTS' no? or is the issue somehow specific to raspi devices?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Triaged
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Sebastien Bacher]

Thanks for the details Dave, there is also a feature request upstream
for network manager on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/960

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #960
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/960

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Triaged
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1971901]

[mr.larch]

*** Bug 53077 has been marked as a duplicate of this bug. ***

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1971901

Title:
  dlltool uses non-unique temp filenames

Status in binutils:
  Fix Released
Status in Wine:
  Won't Fix
Status in binutils package in Ubuntu:
  New
Status in binutils-mingw-w64 package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1

  /usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like

  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.delay.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec
  Assembler messages:
  Error: can't open winmm_dll_t.s for reading: No such file or directory
  /usr/bin/x86_64-w64-mingw32-dlltool: /usr/bin/x86_64-w64-mingw32-as exited 
with status 1
  /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: 
winmm_dll_t.o: No such file or directory
  winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1
  make: *** [Makefile:195227: dlls/winmm/libwinmm.delay.a] Error 1
  make: *** Waiting for unfinished jobs
  tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o 
dlls/winmm/libwinmm.cross.a --export \
../wine-6.0.4/dlls/winmm/winmm.spec

  Due to dlltool using names like winmm_dll_t.s and winmm_dll_t.o for
  it's temp file - these are not unique when building libwinmm.delay.a
  and libwinmm.cross.a in parallel. (This can of course affect any dll
  wine is building import libs for, winmm is just the one I happaned to
  get caught on).

  This is regression newly introduced in binutils 2.38 vs older versions
  which used getpid() as the basis of their temp name. We just
  encountered it as part of updating our CI for a winelib application
  from focal to jammy, but it seems to have been discovered by others
  already: see https://sourceware.org/bugzilla/show_bug.cgi?id=28885

  There is an upstream fix on master (2.39) which is already backported
  to the binutils-2_38 branch:
  https://sourceware.org/git/gitweb.cgi?p=binutils-
  gdb.git;h=99852365513266afdd793289813e8e565186c9e6, so it should just
  be a matter of cherry-picking. Hopefully the fact it's a regression
  from impish->jammy and that upstream already backported it to 2.38
  might make this a candidate for jammy-updates?

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976339] Re: Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php Openssl_get_cipher_methods Function

[Paulo Flabiano Smorigo]

Hello Dimitar, I've just publish a new release with the fix
(1.0.2g-1ubuntu4.20+esm4) for the issue you had. Can you check if this
version is fine?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1976339

Title:
  Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php
  Openssl_get_cipher_methods Function

Status in openssl package in Ubuntu:
  New

Bug description:
  The system is Ubuntu 16.04 with ESM support.
  After the update (28.5.2022) of openssl and libssl1.0.0 packages from 
1.0.2g-1ubuntu4.20+esm2 to 1.0.2g-1ubuntu4.20+esm3 the php function 
openssl_get_cipher_methods (php7 from the distribution) is broken.
  It randomly returns empty array when called.
  Testing from php-cli it always returns proper data.
  Testing with web server most of the times it returns an empty array.
  Tested with apache + mod-php and apache + php-fpm.
  Downgrading to versions to 1.0.2g-1ubuntu4.20 fixes the problem.
  This downgrade makes the systems work, but introduces security risks.

  An example code to reproduce the issue:
  
  
  

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Dave Jones]

I'll take a shot at responding to @seb128's questions:

Why is this a rls issue in the LTS?
===

Prior to jammy, the crda database was in userland, and the crda package
provided a means (via editing /etc/default/crda) to persist the wireless
region across reboots. From jammy onwards, the regulatory database is
now baked into the kernel, and the crda package is gone (from Debian
upstream and from Ubuntu). There is now no mechanism to set the wifi
regulatory region that will persist across reboots on either server or
desktop (iw reg set is transitory).

It appears (see comments 16 thru 19 above) that under *some*
circumstances, with some APs that wpa-supplicant does correctly
determine the wifi region, and sets it automatically (though the user
has no way of knowing this other than digging through wpa-supplicant's
logs). However, I'm not convinced this is terribly reliable -- it's
apparently never worked for me at home or at various friends houses, and
only once worked when I travelled to Germany for a sprint.

There is currently (in jammy onwards) one hacky way of ensuring the
region is set on each reboot (from comment 12 above): set
"cfg80211.ieee80211_regdom" on the kernel command line. Obviously this
isn't terribly user friendly!

That covers the deficiency, which is new to jammy, but why is setting
the regulatory region particularly important? In the 2.4GHz band [1],
there's a "world" region which covers the vast majority of the available
bands (1 thru 11). So for older wifi hardware, defaulting to the "world"
region doesn't result in *much* limitation (though it does mean European
users can't use bands 12 or 13, and Japanese users don't get their
wonderfully separate band 14).

However, the 5GHz band [2] is a considerably different story. For
starters, there's a great deal more variation in which channels are
available in which regions. Moreover, certain channels have specific
limitations in certain regions. Some require radar detection or
mitigation mechanisms to ensure that 5GHz capable wifi devices don't
interfere with certain radar applications [3]. Others require that
certain channels are strictly for indoor use only. Leaving one's wifi
device in the "world/unset" state for 5GHz typically results in a more
limited experience than it does for 2.4GHz devices [4].

Then, of course, there's the legal aspect. I'm not qualified to comment
on the relevant regulations around the globe but the section "Helping
compliance by allowing to change regulatory domains" under [5] contains
some interesting notes on the fact that wifi devices have both a
"programmed" regulatory domain and a "selected" region (the latter is
affected by crda) which can only *enhance* restrictions. That said, this
is likely important from a legal perspective for those travelling with
wifi capable equipment between countries with differing regulatory
requirements.

[1]: 
https://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/n/ax)
[2]: 
https://en.wikipedia.org/wiki/List_of_WLAN_channels#5_GHz_(802.11a/h/j/n/ac/ax)
[3]: https://en.wikipedia.org/wiki/Dynamic_frequency_selection
[4]: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1851129/comments/1
[5]: 
https://wireless.wiki.kernel.org/en/developers/Regulatory/CRDA#helping_compliance_by_allowing_to_change_regulatory_domains


What's the intended priority?
=

Given this relates to legal requirements in many jurisdictions (again,
I'm not qualified to comment on these specifically, but I don't think
there's any argument that legal restrictions are at least present),
would suggest this should be a reasonably high priority. The counter-
point would be: it would appear there's been *never* been a graphical
interface for setting this and (I presume?) no jurisdiction has ever
complained about this.

However, the fact that the 5GHz experience (which is becoming more and
more common) is, in certain jurisdictions, significantly affected by
lacking this setting (because without setting the regulatory region,
users in such regions can't access a large number of channels) would
also suggest a reasonably high priority to me.


What's the impact?
==

Hopefully covered in the prior sections.


What do we expect to be changed?


At a bare minimum some mechanism for persisting a selected wifi
regulatory domain is required, both on server images (via netplan) and
desktop images (via network manager). During boot, some mechanism should
restore the wifi regulatory domain from this persistent location.

There's some nuance here over whether an AP's broadcast region (if any)
should take precedence over the persistent setting, and when exactly the
restoration of the setting should occur (i.e. particularly in the server
case, whether wifi should only be enabled strictly *after* restoration
of this setting). There's probably more questions around this setting
I'm not th

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

[Matthew Faigan]

I've just installed 2:2.10-9ubuntu1 amd64 and I can confirm that it
works on Kubuntu 22.04 LTS for my university's WPA2 Enterprise network.

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

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

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Sebastien Bacher]

I've uploaded a candidate patch proposed upstream for testing to
kinetic, could those having the issue try if the deb on
https://launchpad.net/ubuntu/+source/wpa/2:2.10-9ubuntu1/+build/23801450/+files/wpasupplicant_2.10-9ubuntu1_amd64.deb
resolve the connection problems? the deb should install without issue on
the LTS

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

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

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976259] Re: librsvg ftbfs in the jammy release pocket

[Sebastien Bacher]

** Changed in: librsvg (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1976259

Title:
  librsvg ftbfs in the jammy release pocket

Status in librsvg package in Ubuntu:
  Triaged

Bug 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/604216345/buildlog_ubuntu-
  jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz

  test url_resolver::tests::allows_relative ... ok

  failures:

   transform::tests::parses_transform_list stdout 
  thread 'transform::tests::parses_transform_list' panicked at 'assertion 
failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9

   transform::tests::parses_valid_transform stdout 
  thread 'transform::tests::parses_valid_transform' panicked at 'assertion 
failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9

  
  failures:
  transform::tests::parses_transform_list
  transform::tests::parses_valid_transform

  test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0
  filtered out; finished in 0.02s

  error: test failed, to rerun pass '--lib'
  make[5]: *** [Makefile:1537: check-local] Error 101

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

[Sebastien Bacher]

Kinetic is switching to pipewire, unsure if the issue is already there
with it, could someone try?

** Changed in: pulseaudio (Ubuntu Kinetic)
 Assignee: (unassigned) => Dave Jones (waveform)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1877194

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  New
Status in pulseaudio source package in Kinetic:
  Triaged
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1951586] Re: Need option to specify wifi regulatory domain

[Sebastien Bacher]

The issue has been nominated for network-manager on jammy which put it
on the desktop rls list but it's unclear for us why that is consider a
rls issue in the LTS and what's the intended priority? Could you provide
a bit more explanation of the impact and what do you expect to be
changed?

** Changed in: network-manager (Ubuntu Jammy)
   Status: New => Incomplete

** Changed in: network-manager (Ubuntu Kinetic)
   Status: New => Incomplete

** Changed in: network-manager (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Kinetic)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1951586

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Triaged
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

[Sebastien Bacher]

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

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

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

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976371] Re: SRU for evolution-data-server 3.44.2

[Jeremy Bicha]

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1976371

Title:
  SRU for evolution-data-server 3.44.2

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.2/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976259] Re: librsvg ftbfs in the jammy release pocket

[Sebastien Bacher]

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

** Changed in: librsvg (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1976259

Title:
  librsvg ftbfs in the jammy release pocket

Status in librsvg package in Ubuntu:
  Triaged

Bug 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/604216345/buildlog_ubuntu-
  jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz

  test url_resolver::tests::allows_relative ... ok

  failures:

   transform::tests::parses_transform_list stdout 
  thread 'transform::tests::parses_transform_list' panicked at 'assertion 
failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9

   transform::tests::parses_valid_transform stdout 
  thread 'transform::tests::parses_valid_transform' panicked at 'assertion 
failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9

  
  failures:
  transform::tests::parses_transform_list
  transform::tests::parses_valid_transform

  test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0
  filtered out; finished in 0.02s

  error: test failed, to rerun pass '--lib'
  make[5]: *** [Makefile:1537: check-local] Error 101

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976371] Re: SRU for evolution-data-server 3.44.2

[Jeremy Bicha]

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Committed

** Changed in: evolution-data-server (Ubuntu)
   Importance: Undecided => Medium

** Also affects: evolution-data-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: evolution-data-server (Ubuntu Jammy)
   Importance: Undecided => Medium

** Tags added: jammy upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1976371

Title:
  SRU for evolution-data-server 3.44.2

Status in evolution-data-server package in Ubuntu:
  Fix Committed
Status in evolution-data-server source package in Jammy:
  Triaged

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.2/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Dan Streetman]

** Description changed:

- A customer reported network disconnections on their storage 
+ [impact]
+ 
+ manual disabling of ipv4 DAD (IACD) for static link-local address does
+ not work in jammy
+ 
+ [test case]
+ 
+ see 'Reproducer' in original description below
+ 
+ [regression potential]
+ 
+ failure to disable DAD, or incorrect disabling of DAD, or networkd
+ issues around parsing of DAD config parsing
+ 
+ [scope]
+ 
+ this is needed for j and k
+ 
+ introduced upstream by commit 1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e,
+ first included in v249, so this bug does not affect impish or earlier
+ 
+ fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53
+ 
+ [original description]
+ 
+ A customer reported network disconnections on their storage
  servers when running 'netplan apply'. The culprit was that
- they have link-local addresses configured and the Duplicate 
- Address Detection (DAD) mechanism was delaying the interfaces 
- from coming back up. 
+ they have link-local addresses configured and the Duplicate
+ Address Detection (DAD) mechanism was delaying the interfaces
+ from coming back up.
  
- As a workaround we tried to disable DAD for the interfaces 
+ As a workaround we tried to disable DAD for the interfaces
  but that's not working in Ubuntu 22.04:
  
  I've noticed that setting DuplicateAddressDetection=none for an
- interface with a link-local address (e.g., 169.254.*) via a 
- .network file added to /etc/systemd/network/ doesn't really 
+ interface with a link-local address (e.g., 169.254.*) via a
+ .network file added to /etc/systemd/network/ doesn't really
  disable Duplicate Address Detection.
  
  OS and package versions:
  
-  - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
-  - systemd 249.5-2ubuntu4
+  - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
+  - systemd 249.5-2ubuntu4
  
  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:
  
-   mkdir -p /etc/systemd/system/systemd-networkd.service.d/
-   cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf < /etc/systemd/system/systemd-networkd.service.d/10-debug.conf  /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1976371] [NEW] SRU for evolution-data-server 3.44.2

[Nathan Teodosio]

Public bug reported:

Impact
--
This is a new stable release in the 3.44 series.

https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.44.2/NEWS

Test Case
-
Install the update
Log out and log back in (or restart)
Ensure that GNOME Calendar and Evolution still work fine.

What Could Go Wrong
---
As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1976371

Title:
  SRU for evolution-data-server 3.44.2

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.2/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1969901] Re: network-manager fails to renew ipv6 address

[Sebastien Bacher]

Thanks, the issue is fixed in newer series and I've sponsored your
bionic SRU now and updated the description to be a bit more specific
about the impact and what to verify

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

** Description changed:

  [Impact]
  
-  * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
+  * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.
  
   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.
  
   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
  
   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
  [Test Plan]
  
   * The exact conditions for reproducing this bug on mixed IPv4/IPv6
     networks are not known but includes using both IPv4 and IPv6,
     both using dhcp.
  
  [Where problems could occur]
  
-  * This patch could possibly break networking using and that would be bad.
-    Network manager should be able to restart connection more properly with
-    this patch though.
+  * The change is in the dchp lease expiration handling so verify that
+ there is no regression in dhcp renewals on different type of
+ configuration include IPv6
  
  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1969901

Title:
  network-manager fails to renew ipv6 address

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
  used.

   * Network manager might kill dhclient(6) and fail to start it again
     causing the IPv6 address to be lost on a network that uses mixed
     IPv4/IPV6.
     The network status will still be seen as online in gnome since ipv4
     is still active.
     The user then have to manually remove the dhcpv6 lease files and
     restart ipv6 connection/restart network manager to regain IPv6
     connectivity.

   * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
     is based on 1.10.6):
     
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f

   * Upstream bug:
     https://bugzilla.gnome.org/show_bug.cgi?id=783391

  [Test Plan]

   * The exact conditions for reproducing this bug on mixed IPv4/IPv6
     networks are not known but includes using both IPv4 and IPv6,
     both using dhcp.

  [Where problems could occur]

   * The change is in the dchp lease expiration handling so verify that
  there is no regression in dhcp renewals on different type of
  configuration include IPv6

  [Other Info]
   * We have tested this patch on a couple of clients where we have seen this
     this problem. If this patch is feasible to include in Ubuntu 18.04 we
     could request more users to test.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

[Utkarsh Gupta]

Hi Shyam,

Thank you for testing this out. Marking the same.

** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to keyutils in Ubuntu.
https://bugs.launchpad.net/bugs/1962453

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Released
Status in keyutils source package in Focal:
  Fix Committed
Status in keyutils source package in Impish:
  Fix Committed
Status in keyutils source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

[Shyam Prasad]

Verified in both focal and impish that the bug is fixed with the keyutils 
package in the proposed repo.
Also ran some sanity tests to make sure that other functionalities are not 
affected. 
You can mark this as verified.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to keyutils in Ubuntu.
https://bugs.launchpad.net/bugs/1962453

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Released
Status in keyutils source package in Focal:
  Fix Committed
Status in keyutils source package in Impish:
  Fix Committed
Status in keyutils source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

[Sebastien Bacher]

** Description changed:

+ - Impact
+ 
+ software-properties-gtk hit an exception when dealing some drivers
+ 
+ - Test Case
+ 
+ On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try
+ to install libcamhal-ipu6ep0 using software-properties-gtk
+ 
+ - Regression potential
+ 
+ The change make the driver code ignore one extra type of error, it
+ shouldn't impact on any of the already working cases. Ensure that
+ drivers that were hitting the error correctly install now
+ 
+ 
+ 
+ 
+ 
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
-  software-properties-gtk 0.99.22
+  software-properties-gtk 0.99.22
  
  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.
  
  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

** Description changed:

  - Impact
  
  software-properties-gtk hit an exception when dealing some drivers
  
  - Test Case
  
  On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try
  to install libcamhal-ipu6ep0 using software-properties-gtk
  
+ https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57
+ should not include reports on the new version
+ 
  - Regression potential
  
  The change make the driver code ignore one extra type of error, it
  shouldn't impact on any of the already working cases. Ensure that
  drivers that were hitting the error correctly install now
  
- 
  
- 
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22
  
  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.
  
  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1969460

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

Status in OEM Priority Project:
  New
Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  - Impact

  software-properties-gtk hit an exception when dealing some drivers

  - Test Case

  On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and
  try to install libcamhal-ipu6ep0 using software-properties-gtk

  https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57
  should not include reports on the new version

  - Regression potential

  The change make the driver code ignore one extra type of error, it
  shouldn't impact on any of the already working cases. Ensure that
  drivers that were hitting the error correctly install now

  

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22

  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.

  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1973779] Re: Could not enable livepatch 22.04 LTS

[Sebastien Bacher]

*** This bug is a duplicate of bug 1972809 ***
https://bugs.launchpad.net/bugs/1972809

** This bug has been marked a duplicate of bug 1972809
   Cant enable ua from GUI, works from CLI

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1973779

Title:
  Could not enable livepatch 22.04 LTS

Status in software-properties package in Ubuntu:
  New

Bug description:
  Once upgraded from 20.10 to 22.04 I try to enable livepatch (the PC is 
attached to Ubuntu Advantage Subscription) 
   "Could not Enable Livepatch. Please try again."
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-01-04 (497 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: ubuntu-release-upgrader (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-05-15 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeTermlog:
   
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu Jammy)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: software-properties (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Jammy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1969460

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

Status in OEM Priority Project:
  New
Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22

  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.

  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1972055] Re: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

[Rustem]

Thank you for confirming this bug.

Do you have any news when this could be addressed? This bug makes it
very difficult to listen to videos and to participate in online meetings
- speakers keep on getting cutoff.

Thanks, Rustem

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1972055

Title:
  [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Carbon X1 gen 9 to Ubuntu 22.04 (from 20.04), there
  appeared strange problem with speaker sound in video conferences
  (Zoom) and also with Chrome (for example YouTube & Preply).

  The problem is as following: the speaker sound level is reduced when
  somebody speaks after a gap of silence, then the sound level is
  quickly increased to normal level. This creates the very strange
  fluctuating up/down sound level which when sound level is low at the
  start of each sentence.

  This problem was not there with Ubuntu 20.04 on the same laptop. This
  problem is also not presented when using Zoom with Windows 11 on the
  same machine.

  Thank you for your consideration.

  Best regards, Rustem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rustem 1576 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  7 11:24:53 2022
  InstallationDate: Installed on 2022-04-23 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: May 07 11:15:06 rox1 pulseaudio[1002]: After module 
unload, module 'module-null-sink' was still loaded!
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS62S00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS62S00:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS62S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS62S00
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1970190] Re: [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad

[Sebastien Bacher]

Thank you for the report, I'm unsure ubiquity has logic to be able to
pick the layout depending of the device specific, the default are
currently by country

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1970190

Title:
  [Feature]Wrong default value for Brazil Keyboard layout on ThinkPad

Status in OEM Priority Project:
  New
Status in console-setup package in Ubuntu:
  New

Bug description:
  On ThinkPad, when I select 'Portuguese(Brazil)', it will use
  'Portuguese(Brazil)' on second column, but the default value should be
  'Portuguese(Brazil)-Portuguese(Brazil, IBM/Lenovo ThinkPad)'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1970190/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768488] Re: dependency problem lightdm -> pam

[Saverio Miroddi]

Still present in Focal and Jammy.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1768488

Title:
  dependency problem lightdm -> pam

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've installed Lubuntu 18.04 and found that problem:

  the display-manager service complains:

   ● lightdm.service - Light Display Manager
 Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor 
preset: enabled)
 Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
   Docs: man:lightdm(1)
Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, 
status=0/SUCCESS)
   Main PID: 1720 (lightdm)
  Tasks: 6 (limit: 4915)
 CGroup: /system.slice/lightdm.service
 ├─1720 /usr/sbin/lightdm
 ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
 └─1786 lightdm --session-child 12 19

  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: 
pam_kwallet5.so
  Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open 
shared object file: No such file or directory
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_gnome_keyring.so
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet.so
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet5.so
  Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): 
requirement "user ingroup nopasswdlogin" not met by user "danisch"

  
  It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load 
pam modules which are not installed since there are not dependencies to 
libpam-gnome-keyring  libpam-kwallet4 libpam-kwallet5


  If it is not intended to let things run into error message (and
  possible further trouble), you should either remove these lines from
  the config files or add dependencies to pull in that packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed May  2 12:21:26 2018
  InstallationDate: Installed on 2018-04-30 (2 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976339] Re: Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php Openssl_get_cipher_methods Function

[Dimitar Dimitrov]

An additional comment.
I opened a case in the support portal, but they recommended opening a bug here:
https://portal.support.canonical.com/selfservice/s/case/5004K0EA3Ox/openssl-andor-libssl100-breaks-php-opensslgetciphermethods-function
I'm not sure if the main packages repository is the proper place for bugs in 
ESM versions of the packages.
But this is a serious issue and I hope it can be resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1976339

Title:
  Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php
  Openssl_get_cipher_methods Function

Status in openssl package in Ubuntu:
  New

Bug description:
  The system is Ubuntu 16.04 with ESM support.
  After the update (28.5.2022) of openssl and libssl1.0.0 packages from 
1.0.2g-1ubuntu4.20+esm2 to 1.0.2g-1ubuntu4.20+esm3 the php function 
openssl_get_cipher_methods (php7 from the distribution) is broken.
  It randomly returns empty array when called.
  Testing from php-cli it always returns proper data.
  Testing with web server most of the times it returns an empty array.
  Tested with apache + mod-php and apache + php-fpm.
  Downgrading to versions to 1.0.2g-1ubuntu4.20 fixes the problem.
  This downgrade makes the systems work, but introduces security risks.

  An example code to reproduce the issue:
  
  
  

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1976339] [NEW] Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php Openssl_get_cipher_methods Function

[Dimitar Dimitrov]

Public bug reported:

The system is Ubuntu 16.04 with ESM support.
After the update (28.5.2022) of openssl and libssl1.0.0 packages from 
1.0.2g-1ubuntu4.20+esm2 to 1.0.2g-1ubuntu4.20+esm3 the php function 
openssl_get_cipher_methods (php7 from the distribution) is broken.
It randomly returns empty array when called.
Testing from php-cli it always returns proper data.
Testing with web server most of the times it returns an empty array.
Tested with apache + mod-php and apache + php-fpm.
Downgrading to versions to 1.0.2g-1ubuntu4.20 fixes the problem.
This downgrade makes the systems work, but introduces security risks.

An example code to reproduce the issue:




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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1976339

Title:
  Openssl update to 1.0.2g-1ubuntu4.20+esm3 Breaks Php
  Openssl_get_cipher_methods Function

Status in openssl package in Ubuntu:
  New

Bug description:
  The system is Ubuntu 16.04 with ESM support.
  After the update (28.5.2022) of openssl and libssl1.0.0 packages from 
1.0.2g-1ubuntu4.20+esm2 to 1.0.2g-1ubuntu4.20+esm3 the php function 
openssl_get_cipher_methods (php7 from the distribution) is broken.
  It randomly returns empty array when called.
  Testing from php-cli it always returns proper data.
  Testing with web server most of the times it returns an empty array.
  Tested with apache + mod-php and apache + php-fpm.
  Downgrading to versions to 1.0.2g-1ubuntu4.20 fixes the problem.
  This downgrade makes the systems work, but introduces security risks.

  An example code to reproduce the issue:
  
  
  

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp