[Touch-packages] [Bug 2039235] [NEW] gnome-online-accounts -> when signing into google account, infinite loading after entering password

[nathan li]

Public bug reported:

1) What you expected to happen
- sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

2) What actually happened
- sign in hangs infinitely after entering the password
- the process is able to detect that the password is correct or incorrect. When 
entering an incorrect password, it will correctly and quickly complain that the 
password is incorrect. When entering the correct password, the bug will occur.

3) Steps to reproduce
  a) start the program
  b) select online accounts
  c) select google
  d) enter email
  e) enter password
  f) loads forever

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-online-accounts 3.48.0-2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 22:27:59 2023
InstallationDate: Installed on 2023-10-12 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

Hardware info (not sure if relevant):
cpu: intel
gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

** Description changed:

  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)
  
  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.
  
  3) Steps to reproduce
-   a) start the program
-   b) select online accounts
-   c) select google
-   d) enter email
-   e) enter password
-   f) loads forever
+   a) start the program
+   b) select online accounts
+   c) select google
+   d) enter email
+   e) enter password
+   f) loads forever
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ Hardware info (not sure if relevant):
+ cpu: intel
+ gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

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

Title:
  gnome-online-accounts -> when signing into google account, infinite
  loading after entering password

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.

  3) Steps to reproduce
    a) start the program
    b) select online accounts
    c) select google
    d) enter email
    e) enter password
    f) loads forever

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 

[Touch-packages] [Bug 2038811] Re: NetworkManager crashes when updating wpa-eap connections

[Lukas Märdian]

** Summary changed:

- 
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection
+ NetworkManager crashes when updating wpa-eap connections

-- 
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/2038811

Title:
  NetworkManager crashes when updating wpa-eap connections

Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager.  This problem was most recently seen with package version 
1.44.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+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 2039218] [NEW] NetworkManager doesn't connect to Wi-Fi after suspend

[Łukasz Konieczny]

Public bug reported:

After upgrading to Mantic Minotaur, when I suspend and resume the
system, NetworkManager doesn't see any Wi-Fi networks and i can't
connect to Wi-Fi, unless I log out and log in. I don't know exactly in
which package there is a problem, I can only guess, that it is network-
manager or plasma-nm. My Wi-Fi adapter is Intel AX201 (Wi-Fi 6),
operating under iwlwifi driver. Plasma Network Manager applet doesn't
see any connections, unless I log out and log in. Or I can modprobe -r
iwlwifi, modprobe iwlwifi. Then I can use nmcli to connect, but
graphical interface doesn't work anymore.

System info:

Operating System: Kubuntu 23.10
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.0-9-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: System76
Product Name: Darter Pro
System Version: darp7

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Oct 12 21:31:21 2023
InstallationDate: Installed on 2021-07-23 (811 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: network-manager
UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
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/2039218

Title:
  NetworkManager doesn't connect to Wi-Fi after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to Mantic Minotaur, when I suspend and resume the
  system, NetworkManager doesn't see any Wi-Fi networks and i can't
  connect to Wi-Fi, unless I log out and log in. I don't know exactly in
  which package there is a problem, I can only guess, that it is
  network-manager or plasma-nm. My Wi-Fi adapter is Intel AX201 (Wi-Fi
  6), operating under iwlwifi driver. Plasma Network Manager applet
  doesn't see any connections, unless I log out and log in. Or I can
  modprobe -r iwlwifi, modprobe iwlwifi. Then I can use nmcli to
  connect, but graphical interface doesn't work anymore.

  System info:

  Operating System: Kubuntu 23.10
  KDE Plasma Version: 5.27.8
  KDE Frameworks Version: 5.110.0
  Qt Version: 5.15.10
  Kernel Version: 6.5.0-9-generic (64-bit)
  Graphics Platform: Wayland
  Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
  Memory: 31.2 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics
  Manufacturer: System76
  Product Name: Darter Pro
  System Version: darp7

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 12 21:31:21 2023
  InstallationDate: Installed on 2021-07-23 (811 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039218/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Prashanth Suvarna]

Ok. Feel free to close this ticket in that case.
Thanks, Prashanth

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2017414] Re: cp --parents fails without reason

[Launchpad Bug Tracker]

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

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

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

Title:
  cp --parents fails without reason

Status in coreutils package in Ubuntu:
  Confirmed

Bug description:
  Upstream bug: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63245

  The following example of a copy command fails without reason:

  # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all 
--parents /etc/apt/sources.list && echo yes ; ls -lR 
/tmp/f/etc/apt/sources.list /etc/apt/sources.list
  /etc -> /tmp/f/etc
  /etc/apt -> /tmp/f/etc/apt
  '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list'
  cp: ‘etc/apt’: No such file or directory
  -rw-r--r-- 1 root root 2437 Apr 23 09:53 /etc/apt/sources.list
  -rw-r--r-- 1 root root 2437 Apr 23 09:53 /tmp/f/etc/apt/sources.list
  #

  /tmp is on the same filesystem as /. The same on Ubuntu 22.04 works
  without a problem:

  # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=all 
--parents /etc/apt/sources.list && echo yes ; ls -lR 
/tmp/f/etc/apt/sources.list /etc/apt/sources.list
  /etc -> /tmp/f/etc
  /etc/apt -> /tmp/f/etc/apt
  '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list'
  yes
  -rw-r--r-- 1 root root 263 Mär 26 15:20 /etc/apt/sources.list
  -rw-r--r-- 1 root root 263 Mär 26 15:20 /tmp/f/etc/apt/sources.list
  #

  Why I omit the --preservce=all then it works without a problem:

  # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --parents 
/etc/apt/sources.list && echo yes ; ls -lR /tmp/f/etc/apt/sources.list 
/etc/apt/sources.list
  /etc -> /tmp/f/etc
  /etc/apt -> /tmp/f/etc/apt
  '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list'
  yes
  -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list
  -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list
  #

  Also, when I only use --preserve=mode, then it again fails:

  # rm -Rf /tmp/f && mkdir /tmp/f && cp --verbose -t /tmp/f -L --preserve=mode 
--parents /etc/apt/sources.list && echo yes ; ls -lR 
/tmp/f/etc/apt/sources.list /etc/apt/sources.list
  /etc -> /tmp/f/etc
  /etc/apt -> /tmp/f/etc/apt
  '/etc/apt/sources.list' -> '/tmp/f/etc/apt/sources.list'
  cp: ‘etc/apt’: No such file or directory
  -rw-r--r-- 2 root root 2437 Apr 23 09:53 /etc/apt/sources.list
  -rw-r--r-- 1 root root 2437 Apr 23 11:02 /tmp/f/etc/apt/sources.list
  #

  Is this a bug in cp or something else?

  I'm one of the maintainers of Relax-and-Recover (rear) and noticed
  this in https://github.com/rear/rear/issues/2972

  OS Release Info:
  PRETTY_NAME="Ubuntu 23.04"
  NAME="Ubuntu"
  VERSION_ID="23.04"
  VERSION="23.04 (Lunar Lobster)"
  VERSION_CODENAME=lunar
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=lunar
  LOGO=ubuntu-logo

  Coreutils version:

  # cp --version
  cp (GNU coreutils) 9.1

  # dpkg-query -l coreutils
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  coreutils  9.1-1ubuntu2 amd64GNU core utilities

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: coreutils 9.1-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Apr 23 10:48:56 2023
  InstallationDate: Installed on 2023-04-23 (0 days ago)
  InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 
(20230415)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2017414/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

On 2023-10-12 18:39, Brian Murray wrote:
> however the title bar was corrupted but that's fine.

Yeah, that's expected. I didn't think it was motivated to play with
multiple dconf keys only for MATE.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

I've tested an upgrade of Ubuntu MATE (running Lunar) with -proposed
enabled with version 1:23.04.7 installed and the fonts in the body of
the ubuntu-release-upgrader were legible, however the title bar was
corrupted but that's fine.

** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Gunnar Hjalmarsson]

Hmm.. The XDG_CURRENT_DESKTOP variable keeps being present when you use
sudo, which is the reason why we successfully tested the MATE specific
code. Apparently the pkexec environment differs.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

Hello Brian, or anyone else affected,

Accepted ubuntu-release-upgrader into lunar-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:23.04.7
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-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. 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: ubuntu-release-upgrader (Ubuntu Lunar)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Committed
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - 

Re: [Touch-packages] [Bug 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Steve Langasek]

On Thu, Oct 12, 2023 at 03:10:19PM -, Prashanth Suvarna wrote:
> It's fine if you think it's not a problem that needs fixing at this time
> within Ubuntu.  I reckon that leaves me with two options :

> 1) Build OpenSSH myself with the fix in question on Ubuntu

Which would be our general recommendation.  You have requirements for a
bugfix for OpenSSH that is not critical for users who are not replacing
official base Ubuntu packages with unsupported versions.  This is not a
priority for Ubuntu to fix.

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

  [ Impact ]
  
   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.
  
   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.
  
   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.
  
   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.
  
-  * Also in the change are:
-* an update of the mirrors.cfg, adding and removing 2 mirrors
-* rev the POT-Creation-Date of the po files
-* an update to tests
+  * Also in the change are
+    * an update to tests
+* from pre-build.sh
+      * an update of the mirrors.cfg, adding and removing several
+mirrors
+      * a refresh of the po files
  
  [ Test Plan ]
  
   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
  
   * as user, run "update-manager -d"
  
   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.
  
   * Repeat the above for Ubuntu Desktop
  
  [ Where problems could occur ]
  
   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.
  
  [ Other Info ]
  
   * TBD
  
  ---
  
  Original description:
  
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
  
  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

  [ Impact ]
  
   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.
  
   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.
  
   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.
  
   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.
  
+  * Also in the change are:
+* an update of the mirrors.cfg, adding and removing 2 mirrors
+* rev the POT-Creation-Date of the po files
+* an update to tests
+ 
  [ Test Plan ]
  
   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
  
   * as user, run "update-manager -d"
  
   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.
  
   * Repeat the above for Ubuntu Desktop
  
  [ Where problems could occur ]
  
   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
-additional XDG_CURRENT_DESKTOP variable is relatively low risk.
+    additional XDG_CURRENT_DESKTOP variable is relatively low risk.
  
  [ Other Info ]
  
   * TBD
  
  ---
  
  Original description:
  
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
  
  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Brian Murray]

** Also affects: ubuntu-meta (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
   Importance: Undecided => Critical

** Changed in: ubuntu-release-upgrader (Ubuntu Lunar)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Prashanth Suvarna]

https://packages.ubuntu.com/jammy/openssh-server clearly states the following 
under dependency section:
 
libssl3 (>= 3.0.1) [not amd64, i386]
Secure Sockets Layer toolkit - shared libraries 
libssl3 (>= 3.0.2) [amd64, i386]

I am trying to use libssl3 version 3.1 which is in fact greater than
3.0.2. This in my opinion should be supported or the documentation
updated to state '>=3.0.2` and '<3.1' explicitly.

I also acknowledge that this is not a bug in ubuntu itself. 
However, this is a bug in OpenSSH. Their code isn't treating 3.1 as being 
greater than 3.0 which is wrong. And this is a critical bug because the impact 
of this is that we lose SSH access to our machines when we run into this.

To your comment "Unless you have specific needs, I suggest sticking with
the Ubuntu packaged version of OpenSSL." - I am trying to evaluate and
benchmark OpenSSL 3.1 so that we can consider moving to it soon since we
intend to use the functionality that comes with it. At the moment, the
OpenSSH bug is blocking that work. So I would think that my needs are
"specific" and I unfortunately can't "stick with the Ubuntu packaged
version of OpenSSL".

It's fine if you think it's not a problem that needs fixing at this time within 
Ubuntu. I reckon that leaves me with two options : 
1) Build OpenSSH myself with the fix in question on Ubuntu
2) Move away from Ubuntu and start using Debian Trixie (because it already 
comes with the newer version of OpenSSH) for our OpenSSL 3.1 
evaluation/benchmarking work

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/453457

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
 additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

  [ Impact ]
  
   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.
  
   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.
  
   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.
  
   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
-critical criteria for making the Mate version of the fix work.
+    critical criteria for making the Mate version of the fix work.
  
  [ Test Plan ]
  
   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
  
   * as user, run "update-manager -d"
  
   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.
  
   * Repeat the above for Ubuntu Desktop
  
  [ Where problems could occur ]
  
   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
-    than just Ubuntu Mate.
- 
-  * We are proposing to move this package update to Ubuntu Lunar as
-    fast as possible.  The risk is high here that we, in the rush,
-    create new problems.
+    than just Ubuntu Mate.  That said, it is believed that passing the
+additional XDG_CURRENT_DESKTOP variable is relatively low risk.
  
  [ Other Info ]
  
   * TBD
  
  ---
  
  Original description:
  
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
  
  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/453456

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Lunar:
  New
Status in ubuntu-release-upgrader source package in Lunar:
  In Progress
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
 additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/2034986/+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 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

  [ Impact ]
  
-  * On Ubuntu Mate with the Lunar series, when running
-ubuntu-release-upgrader, the displayed font of running
-applications (including the upgrader) becomes very corrupted.
+  * On Ubuntu Mate with the Lunar series, when running
+    ubuntu-release-upgrader, the displayed font of running
+    applications (including the upgrader) becomes very corrupted.
  
-  * This is not just a display problem, it is also a functional one.
-The release upgrader will have text corrupted to the point
-where a dialog asks a decision, and displays two buttons, but the
-text is unreadable and one has to guess which button is the one
-that carries out their desired action.
+  * This is not just a display problem, it is also a functional one.
+    The release upgrader will have text corrupted to the point
+    where a dialog asks a decision, and displays two buttons, but the
+    text is unreadable and one has to guess which button is the one
+    that carries out their desired action.
  
-  * In the early parts of the upgrader tool, users are told in bold:
-"To prevent data loss close all open applications and documents."
-This is just before the "Start Upgrade" button is available.
-But they may not do so.  Many applications may have a corrupted
-font.
+  * In the early parts of the upgrader tool, users are told in bold:
+    "To prevent data loss close all open applications and documents."
+    This is just before the "Start Upgrade" button is available.
+    But they may not do so.  Many applications may have a corrupted
+    font.
  
-  * To address this, an additional environment variable is being
-passed along to pkexec, XDG_SESSION_TYPE, as this is the critical
-criteria for making the Mate version of the fix work.
+  * To address this, an additional environment variable is being
+    passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
+critical criteria for making the Mate version of the fix work.
  
  [ Test Plan ]
  
-  * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
+  * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
  
-  * as user, run "update-manager -d"
+  * as user, run "update-manager -d"
  
-  * monitor the "Distribution Upgrade" screen.  During the "Installing
-the upgrades" step (and mind that this step will be long), observe
-the text of the "Distribution Upgrade" screen and verify that the
-font does not corrupt.
+  * monitor the "Distribution Upgrade" screen.  During the "Installing
+    the upgrades" step (and mind that this step will be long), observe
+    the text of the "Distribution Upgrade" screen and verify that the
+    font does not corrupt.
  
-  * Repeat the above for Ubuntu Desktop
+  * Repeat the above for Ubuntu Desktop
  
  [ Where problems could occur ]
  
-  * We are changing, at release time, ubuntu-release upgrader.  If we
-are careless, we could regress upgrades for a wider group of users
-than just Ubuntu Mate.
+  * We are changing, at release time, ubuntu-release upgrader.  If we
+    are careless, we could regress upgrades for a wider group of users
+    than just Ubuntu Mate.
  
-  * We are proposing to move this package update to Ubuntu Lunar as
-fast as possible.  The risk is high here that we, in the rush,
-create new problems.
+  * We are proposing to move this package update to Ubuntu Lunar as
+    fast as possible.  The risk is high here that we, in the rush,
+    create new problems.
  
  [ Other Info ]
  
-  * TBD
+  * TBD
  
  ---
  
  Original description:
  
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
  
  mtime.conffile..etc.update-manager.meta-release:
  

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

  [ Impact ]
  
   * On Ubuntu Mate with the Lunar series, when running
 ubuntu-release-upgrader, the displayed font of running
 applications (including the upgrader) becomes very corrupted.
  
   * This is not just a display problem, it is also a functional one.
 The release upgrader will have text corrupted to the point
 where a dialog asks a decision, and displays two buttons, but the
 text is unreadable and one has to guess which button is the one
 that carries out their desired action.
  
   * In the early parts of the upgrader tool, users are told in bold:
 "To prevent data loss close all open applications and documents."
 This is just before the "Start Upgrade" button is available.
 But they may not do so.  Many applications may have a corrupted
 font.
+ 
+  * To address this, an additional environment variable is being
+passed along to pkexec, XDG_SESSION_TYPE, as this is the critical
+criteria for making the Mate version of the fix work.
  
  [ Test Plan ]
  
   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
  
   * as user, run "update-manager -d"
  
   * monitor the "Distribution Upgrade" screen.  During the "Installing
 the upgrades" step (and mind that this step will be long), observe
 the text of the "Distribution Upgrade" screen and verify that the
 font does not corrupt.
  
   * Repeat the above for Ubuntu Desktop
  
  [ Where problems could occur ]
  
   * We are changing, at release time, ubuntu-release upgrader.  If we
 are careless, we could regress upgrades for a wider group of users
 than just Ubuntu Mate.
  
   * We are proposing to move this package update to Ubuntu Lunar as
 fast as possible.  The risk is high here that we, in the rush,
 create new problems.
  
  [ Other Info ]
  
   * TBD
  
  ---
  
  Original description:
  
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
  
  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
 ubuntu-release-upgrader, the displayed font of running
 applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
 The release upgrader will have text corrupted to the point
 where a dialog asks a decision, and displays two buttons, but the
 text is unreadable and one has to guess which button is the one
 that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
 "To prevent data loss close all open applications and documents."
 This is just before the "Start Upgrade" button is available.
 But they may not do so.  Many applications may have a corrupted
 font.

   * To address this, an additional environment variable is being
 passed along to pkexec, XDG_SESSION_TYPE, as this is the critical
 criteria for making the Mate version of the fix work.

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

[Dan Bungert]

** Description changed:

+ [ Impact ]
+ 
+  * On Ubuntu Mate with the Lunar series, when running
+ubuntu-release-upgrader, the displayed font of running
+applications (including the upgrader) becomes very corrupted.
+ 
+  * This is not just a display problem, it is also a functional one.
+The release upgrader will have text corrupted to the point
+where a dialog asks a decision, and displays two buttons, but the
+text is unreadable and one has to guess which button is the one
+that carries out their desired action.
+ 
+  * In the early parts of the upgrader tool, users are told in bold:
+"To prevent data loss close all open applications and documents."
+This is just before the "Start Upgrade" button is available.
+But they may not do so.  Many applications may have a corrupted
+font.
+ 
+ [ Test Plan ]
+ 
+  * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64
+ 
+  * as user, run "update-manager -d"
+ 
+  * monitor the "Distribution Upgrade" screen.  During the "Installing
+the upgrades" step (and mind that this step will be long), observe
+the text of the "Distribution Upgrade" screen and verify that the
+font does not corrupt.
+ 
+  * Repeat the above for Ubuntu Desktop
+ 
+ [ Where problems could occur ]
+ 
+  * We are changing, at release time, ubuntu-release upgrader.  If we
+are careless, we could regress upgrades for a wider group of users
+than just Ubuntu Mate.
+ 
+  * We are proposing to move this package update to Ubuntu Lunar as
+fast as possible.  The risk is high here that we, in the rush,
+create new problems.
+ 
+ [ Other Info ]
+ 
+  * TBD
+ 
+ ---
+ 
+ Original description:
+ 
  I was upgrading from Lunar to Mantic the other day and left a couple of
  applications open during the upgrade process. During the upgrade the
  text in audacious became unreadable (I'll attach a screenshot) and I
  seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:
-  
- mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490
+ 
+ mtime.conffile..etc.update-manager.meta-release:
+ 2021-05-27T16:30:16.970490

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

Title:
  some text became unreadable during a distribution upgrade

Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
 ubuntu-release-upgrader, the displayed font of running
 applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
 The release upgrader will have text corrupted to the point
 where a dialog asks a decision, and displays two buttons, but the
 text is unreadable and one has to guess which button is the one
 that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
 "To prevent data loss close all open applications and documents."
 This is just before the "Start Upgrade" button is available.
 But they may not do so.  Many applications may have a corrupted
 font.

   * To address this, an additional environment variable is being
 passed along to pkexec, XDG_SESSION_TYPE, as this is the critical
 criteria for making the Mate version of the fix work.

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
 the upgrades" step (and mind that this step will 

[Touch-packages] [Bug 2028082] Re: Update glib to 2.76.4

[Sebastien Bacher]

The autopkgtests issues listed earlier have been resolved with retries
now

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

Title:
  Update glib to 2.76.4

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Lunar:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.76 series

  The current release in Ubuntu 23.04 is 2.76.1

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopkgtest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  The upstream gnome-remote-desktop maintainer requested that we do this update 
to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 2037874] Re: Totem black screen playing an webm video

[Sebastien Bacher]

Thank you for your bug report. Is that a specific webm video or any video in 
that format? Is playing 
/usr/share/help/fr/gnome-help/figures/gnome-launching-applications.webm for 
example working for you?
If that's only one could you attach an example maybe to the report?

** Changed in: gstreamer1.0 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Totem black screen playing an webm video

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Totem black screen playing an webm video. Video is payed ok by mpv.
  corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams 
-show_format DSCF0001.webm 

  [STREAM]
  index=0
  codec_name=vp9
  codec_long_name=Google VP9
  profile=Profile 1
  codec_type=video
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  width=1280
  height=720
  coded_width=1280
  coded_height=720
  closed_captions=0
  film_grain=0
  has_b_frames=0
  sample_aspect_ratio=1:1
  display_aspect_ratio=16:9
  pix_fmt=yuv422p
  level=-99
  color_range=tv
  color_space=bt470bg
  color_transfer=unknown
  color_primaries=unknown
  chroma_location=center
  field_order=progressive
  refs=1
  id=N/A
  r_frame_rate=30/1
  avg_frame_rate=30/1
  time_base=1/1000
  start_pts=0
  start_time=0.00
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libvpx-vp9
  TAG:DURATION=00:00:15.0
  [/STREAM]
  [STREAM]
  index=1
  codec_name=opus
  codec_long_name=Opus (Opus Interactive Audio Codec)
  profile=unknown
  codec_type=audio
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  sample_fmt=fltp
  sample_rate=48000
  channels=1
  channel_layout=mono
  bits_per_sample=0
  initial_padding=312
  id=N/A
  r_frame_rate=0/0
  avg_frame_rate=0/0
  time_base=1/1000
  start_pts=-7
  start_time=-0.007000
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  extradata_size=19
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libopus
  TAG:DURATION=00:00:15.00800
  [/STREAM]
  [FORMAT]
  filename=DSCF0001.webm
  nb_streams=2
  nb_programs=0
  format_name=matroska,webm
  format_long_name=Matroska / WebM
  start_time=-0.007000
  duration=15.008000
  size=6005941
  bit_rate=3201461
  probe_score=100
  TAG:ENCODER=Lavf60.3.100
  [/FORMAT]
  corrado@corrado-n02-mm-0923:~/Videos$ totem DSCF0001.webm

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libgstreamer1.0-0 1.22.5-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 09:39:34 2023
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2023-09-23 (8 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2037874/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Paride Legovini]

Hello, while [1] by itself is a straightforward patch, I don't think we
can acknowledge this to be a bug in in Ubuntu, given that you are trying
to use an Ubuntu packaged software using a manually compiled version of
a library it depends on. This is not a supported use case, so the
prerequisites for a SRU [2] are missing.

OpenSSL 3.0 has upstream support until 2026-09-07 [3], and even after
that the Ubuntu package will get security coverage from the Ubuntu
security team. Unless you have specific needs, I suggest sticking with
the Ubuntu packaged version of OpenSSL.

[1] 
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237
[2] https://wiki.ubuntu.com/StableReleaseUpdates
[3] https://www.openssl.org/policies/releasestrat.html

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Dimitri John Ledkov]

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

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

** Changed in: maas
   Status: Fix Committed => Fix Released

** Changed in: apparmor
   Status: Fix Committed => Fix Released

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

Title:
  udev fails to make prctl() syscall with apparmor=0 (as used by maas by
  default)

Status in AppArmor:
  Fix Released
Status in MAAS:
  Fix Released
Status in maas-images:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in apparmor source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in systemd source package in Lunar:
  Invalid

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
/run/net6
  -*.conf
  :: 
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
fsverity
  =yes
  shfs
  :: mount_squash downloading 
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
  wget: can't connect to remote host (10.229.32.21): Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
  done.

  Still gathering logs and info and will update as I go.

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2039142] Re: openssl v3.0.2 is not work with dynamic engine libengine-gost-openssl1.1

[Adrien Nader]

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

-- 
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/2039142

Title:
  openssl v3.0.2 is not work with dynamic engine libengine-gost-
  openssl1.1

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Hello

  We use from a source code the gost engine for a check certificates
  chains. But openssl the version 3.0.2 is not correct load dynamic
  engines. openssl return error "40D7F65B7F7F:error:1280006A:DSO
  support routines:dlfcn_bind_func:could not bind to the requested
  symbol name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id):
  /usr/lib/x86_64-linux-gnu/engines-3/gost.so: undefined symbol:
  EVP_PKEY_base_id".

  We checked openssl the version 3.0.1, and 3.0.3, and 3.1.3 with the
  same engine. It work.

  In the openssl it fixed, but in the version >=3.0.3.
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1.10
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 09:44:36 2023
  InstallationDate: Installed on 2023-01-13 (271 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2039142/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Launchpad Bug Tracker]

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

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

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

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2038567] Re: Disable restricting unprivileged change_profile by default, due to LXD latest/stable not yet compatible with this new apparmor feature

[Launchpad Bug Tracker]

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

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

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

Title:
  Disable restricting unprivileged change_profile by default, due to LXD
  latest/stable not yet compatible with this new apparmor feature

Status in Release Notes for Ubuntu:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Triaged
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Following upgrade to 6.5.0-7 kernel in mantic cloud images we are
  seeing a regression in our cloud image tests. The test runs the
  following:

  ```
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  ```

  The `lxc exec mantic -- cloud-init status --wait` times out after 240s
  and will fail our test as a result.

  I have been able to replicate in a local VM

  ```
  wget 
http://cloud-images.ubuntu.com/mantic/20231005/mantic-server-cloudimg-amd64.img 
  wget --output-document=launch-qcow2-image-qemu.sh 
https://gist.githubusercontent.com/philroche/14c241c086a5730481e24178b654268f/raw/7af95cd4dfc8e1d0600e6118803d2c866765714e/gistfile1.txt
 
  chmod +x launch-qcow2-image-qemu.sh 

  ./launch-qcow2-image-qemu.sh --password passw0rd --image 
./mantic-server-cloudimg-amd64.img 
  cat < "./reproducer.sh"
  #!/bin/bash -eux
  lxd init --auto --storage-backend dir
  lxc launch ubuntu-daily:mantic mantic
  lxc info mantic
  lxc exec mantic -- cloud-init status --wait
  EOF
  chmod +x ./reproducer.sh
  sshpass -p passw0rd scp -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -P  ./reproducer.sh ubuntu@127.0.0.1:~/
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get update
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 sudo apt-get upgrade 
--assume-yes
  sshpass -p passw0rd ssh -o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o 
StrictHostKeyChecking=no -p  ubuntu@127.0.0.1 ./reproducer.sh
  ```

  The issue is not present with the 6.5.0-5 kernel and the issue is
  present regardless of the container launched. I tried the jammy
  container to test this.

  From my test VM

  ```
  ubuntu@cloudimg:~$ uname --all
  Linux cloudimg 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 29 
09:14:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@cloudimg:~$ uname --kernel-release
  6.5.0-7-generic
  ```

  This is a regression in our test that will block 23.10 cloud image
  release next week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038567/+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 2037874] Re: Totem black screen playing an webm video

[Launchpad Bug Tracker]

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

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Totem black screen playing an webm video

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem black screen playing an webm video. Video is payed ok by mpv.
  corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams 
-show_format DSCF0001.webm 

  [STREAM]
  index=0
  codec_name=vp9
  codec_long_name=Google VP9
  profile=Profile 1
  codec_type=video
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  width=1280
  height=720
  coded_width=1280
  coded_height=720
  closed_captions=0
  film_grain=0
  has_b_frames=0
  sample_aspect_ratio=1:1
  display_aspect_ratio=16:9
  pix_fmt=yuv422p
  level=-99
  color_range=tv
  color_space=bt470bg
  color_transfer=unknown
  color_primaries=unknown
  chroma_location=center
  field_order=progressive
  refs=1
  id=N/A
  r_frame_rate=30/1
  avg_frame_rate=30/1
  time_base=1/1000
  start_pts=0
  start_time=0.00
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libvpx-vp9
  TAG:DURATION=00:00:15.0
  [/STREAM]
  [STREAM]
  index=1
  codec_name=opus
  codec_long_name=Opus (Opus Interactive Audio Codec)
  profile=unknown
  codec_type=audio
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  sample_fmt=fltp
  sample_rate=48000
  channels=1
  channel_layout=mono
  bits_per_sample=0
  initial_padding=312
  id=N/A
  r_frame_rate=0/0
  avg_frame_rate=0/0
  time_base=1/1000
  start_pts=-7
  start_time=-0.007000
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  extradata_size=19
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libopus
  TAG:DURATION=00:00:15.00800
  [/STREAM]
  [FORMAT]
  filename=DSCF0001.webm
  nb_streams=2
  nb_programs=0
  format_name=matroska,webm
  format_long_name=Matroska / WebM
  start_time=-0.007000
  duration=15.008000
  size=6005941
  bit_rate=3201461
  probe_score=100
  TAG:ENCODER=Lavf60.3.100
  [/FORMAT]
  corrado@corrado-n02-mm-0923:~/Videos$ totem DSCF0001.webm

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libgstreamer1.0-0 1.22.5-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 09:39:34 2023
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2023-09-23 (8 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2037874/+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 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes error on login/live session

[Launchpad Bug Tracker]

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

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

-- 
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/2038765

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes error on
  login/live session

Status in lightdm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  Note - raised separate issue for the installation crash which has now
  been duplicated against
  https://bugs.launchpad.net/subiquity/+bug/2003222

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2038765/+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 2039142] Re: openssl v3.0.2 is not work with dynamic engine libengine-gost-openssl1.1

[Adrien Nader]

Hi,

I have not been able to reproduce your issue. Since you did not provide
the exact command you've used, I did a different test that relies on the
engine. I did the following (lots of trial and error):

* git clone https://github.com/gost-engine/engine
* mkdir build
* cd build
* cmake -DOPENSSL_ENGINES_DIR=/usr/lib/x86_64-linux-gnu/engines-3/  ..
* make install # install paths are pretty inconsistent and there's no way to 
uninstall but I'm going to throw away my test container
* vim example.conf
* change dynamic_path to "dynamic_path = 
/usr/lib/x86_64-linux-gnu/engines-3/gost.so"
* OPENSSL_CONF=$(pwd)/example.conf openssl dgst -md_gost94 README.md

I'm also a bit surprised by your error.

The only recent commit I've found that touches EVP_PKEY_base_id reads
the following:

> if the newly loaded engine contains the symbol
> EVP_PKEY_base_id, we know it is linked to 1.1.x openssl.
> Abort loading this engine, as it will definitely crash.

As far as I understand it, the only use for this symbol is to detect
that there's a version mismatch. Are you sure you don't have both in
your path? Moreover I didn't notice a change related to that between
3.0.2 and 3.0.3.

Also, there is still libengine-gost-openssl1.1 in the archive for jammy
(it's removed now). I tried with it too and it worked even though the
gost.so is installed directly in / rather than in
/usr/lib//engines .

I would need a reproducer to investigate further.

-- 
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/2039142

Title:
  openssl v3.0.2 is not work with dynamic engine libengine-gost-
  openssl1.1

Status in openssl package in Ubuntu:
  New

Bug description:
  Hello

  We use from a source code the gost engine for a check certificates
  chains. But openssl the version 3.0.2 is not correct load dynamic
  engines. openssl return error "40D7F65B7F7F:error:1280006A:DSO
  support routines:dlfcn_bind_func:could not bind to the requested
  symbol name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id):
  /usr/lib/x86_64-linux-gnu/engines-3/gost.so: undefined symbol:
  EVP_PKEY_base_id".

  We checked openssl the version 3.0.1, and 3.0.3, and 3.1.3 with the
  same engine. It work.

  In the openssl it fixed, but in the version >=3.0.3.
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1.10
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 09:44:36 2023
  InstallationDate: Installed on 2023-01-13 (271 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2039142/+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 2039149] [NEW] readelf riscv unknown

[Nico Verrijdt]

Public bug reported:

1)
Description:Ubuntu 22.04.3 LTS
Release:22.04

2)
binutils:
  Installed: 2.38-4ubuntu2.3
  Candidate: 2.38-4ubuntu2.3
  Version table:
 *** 2.38-4ubuntu2.3 500
500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status
 2.38-3ubuntu1 500
500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

3)
I'm hand assembling an ELF file and the readelf utility in the binutils package 
doesn't recognize riscv which is the e_machine 243. LoongArch or 258 and x86 or 
3 are recognized, for example. But not riscv.

4)
Readelf states that 243 is an unknown e_machine.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: binutils 2.38-4ubuntu2.3
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Oct 12 10:14:30 2023
InstallationDate: Installed on 2023-07-12 (91 days ago)
InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
SourcePackage: binutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

-- 
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/2039149

Title:
  readelf riscv unknown

Status in binutils package in Ubuntu:
  New

Bug description:
  1)
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2)
  binutils:
Installed: 2.38-4ubuntu2.3
Candidate: 2.38-4ubuntu2.3
Version table:
   *** 2.38-4ubuntu2.3 500
  500 http://be.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.38-3ubuntu1 500
  500 http://be.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  3)
  I'm hand assembling an ELF file and the readelf utility in the binutils 
package doesn't recognize riscv which is the e_machine 243. LoongArch or 258 
and x86 or 3 are recognized, for example. But not riscv.

  4)
  Readelf states that 243 is an unknown e_machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: binutils 2.38-4ubuntu2.3
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Oct 12 10:14:30 2023
  InstallationDate: Installed on 2023-07-12 (91 days ago)
  InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: binutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2039149/+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 2037874] Re: Totem black screen playing an webm video

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2037874

** Tags added: iso-testing

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

Title:
  Totem black screen playing an webm video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Totem black screen playing an webm video. Video is payed ok by mpv.
  corrado@corrado-n02-mm-0923:~/Videos$ ffprobe -loglevel error -show_streams 
-show_format DSCF0001.webm 

  [STREAM]
  index=0
  codec_name=vp9
  codec_long_name=Google VP9
  profile=Profile 1
  codec_type=video
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  width=1280
  height=720
  coded_width=1280
  coded_height=720
  closed_captions=0
  film_grain=0
  has_b_frames=0
  sample_aspect_ratio=1:1
  display_aspect_ratio=16:9
  pix_fmt=yuv422p
  level=-99
  color_range=tv
  color_space=bt470bg
  color_transfer=unknown
  color_primaries=unknown
  chroma_location=center
  field_order=progressive
  refs=1
  id=N/A
  r_frame_rate=30/1
  avg_frame_rate=30/1
  time_base=1/1000
  start_pts=0
  start_time=0.00
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libvpx-vp9
  TAG:DURATION=00:00:15.0
  [/STREAM]
  [STREAM]
  index=1
  codec_name=opus
  codec_long_name=Opus (Opus Interactive Audio Codec)
  profile=unknown
  codec_type=audio
  codec_tag_string=[0][0][0][0]
  codec_tag=0x
  sample_fmt=fltp
  sample_rate=48000
  channels=1
  channel_layout=mono
  bits_per_sample=0
  initial_padding=312
  id=N/A
  r_frame_rate=0/0
  avg_frame_rate=0/0
  time_base=1/1000
  start_pts=-7
  start_time=-0.007000
  duration_ts=N/A
  duration=N/A
  bit_rate=N/A
  max_bit_rate=N/A
  bits_per_raw_sample=N/A
  nb_frames=N/A
  nb_read_frames=N/A
  nb_read_packets=N/A
  extradata_size=19
  DISPOSITION:default=0
  DISPOSITION:dub=0
  DISPOSITION:original=0
  DISPOSITION:comment=0
  DISPOSITION:lyrics=0
  DISPOSITION:karaoke=0
  DISPOSITION:forced=0
  DISPOSITION:hearing_impaired=0
  DISPOSITION:visual_impaired=0
  DISPOSITION:clean_effects=0
  DISPOSITION:attached_pic=0
  DISPOSITION:timed_thumbnails=0
  DISPOSITION:captions=0
  DISPOSITION:descriptions=0
  DISPOSITION:metadata=0
  DISPOSITION:dependent=0
  DISPOSITION:still_image=0
  TAG:ENCODER=Lavc60.3.100 libopus
  TAG:DURATION=00:00:15.00800
  [/STREAM]
  [FORMAT]
  filename=DSCF0001.webm
  nb_streams=2
  nb_programs=0
  format_name=matroska,webm
  format_long_name=Matroska / WebM
  start_time=-0.007000
  duration=15.008000
  size=6005941
  bit_rate=3201461
  probe_score=100
  TAG:ENCODER=Lavf60.3.100
  [/FORMAT]
  corrado@corrado-n02-mm-0923:~/Videos$ totem DSCF0001.webm

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libgstreamer1.0-0 1.22.5-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 09:39:34 2023
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2023-09-23 (8 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230923)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2037874/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

** Tags added: rls-jj-incoming

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2039142] [NEW] openssl v3.0.2 is not work with dynamic engine libengine-gost-openssl1.1

[Youriy]

Public bug reported:

Hello

We use from a source code the gost engine for a check certificates
chains. But openssl the version 3.0.2 is not correct load dynamic
engines. openssl return error "40D7F65B7F7F:error:1280006A:DSO
support routines:dlfcn_bind_func:could not bind to the requested symbol
name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id):
/usr/lib/x86_64-linux-gnu/engines-3/gost.so: undefined symbol:
EVP_PKEY_base_id".

We checked openssl the version 3.0.1, and 3.0.3, and 3.1.3 with the same
engine. It work.

In the openssl it fixed, but in the version >=3.0.3.
Thanks

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openssl 3.0.2-0ubuntu1.10
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 09:44:36 2023
InstallationDate: Installed on 2023-01-13 (271 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

-- 
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/2039142

Title:
  openssl v3.0.2 is not work with dynamic engine libengine-gost-
  openssl1.1

Status in openssl package in Ubuntu:
  New

Bug description:
  Hello

  We use from a source code the gost engine for a check certificates
  chains. But openssl the version 3.0.2 is not correct load dynamic
  engines. openssl return error "40D7F65B7F7F:error:1280006A:DSO
  support routines:dlfcn_bind_func:could not bind to the requested
  symbol name:../crypto/dso/dso_dlfcn.c:188:symname(EVP_PKEY_base_id):
  /usr/lib/x86_64-linux-gnu/engines-3/gost.so: undefined symbol:
  EVP_PKEY_base_id".

  We checked openssl the version 3.0.1, and 3.0.3, and 3.1.3 with the
  same engine. It work.

  In the openssl it fixed, but in the version >=3.0.3.
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1.10
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 09:44:36 2023
  InstallationDate: Installed on 2023-01-13 (271 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2039142/+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