[Touch-packages] [Bug 2018132] Re: wifi tray indicator lost on firefox crash

[Launchpad Bug Tracker]

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

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

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

Title:
  wifi tray indicator lost on firefox crash

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  firefox snap occasionally crashes, ie shown a black screen on startup.
  lately, when it crashes, nm-applet disappears from the tray without 
disconnecting from the router.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: network-manager 1.42.4-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
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 11:13:03 2023
  InstallationDate: Installed on 2023-04-24 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp src 192.168.1.3 metric 600 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.3 metric 600
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
 
   wlo1  wifi  connected   full  full   
   /org/freedesktop/NetworkManager/Devices/2  Forthnet-4jPPK  
eb56363e-28c9-432a-864b-cebcedbfdacf  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   loloopback  connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
ccbf9b80-8294-485c-bc1c-3050ad48b3d9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlo1  wifi-p2p  disconnectednone  none   
   /org/freedesktop/NetworkManager/Devices/3  --  --
--
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.42.4   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/2018132/+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 2025674] Re: ruby-cairo test failure with cairo 1.17.8

[Launchpad Bug Tracker]

This bug was fixed in the package ruby-cairo - 1.17.8-1

---
ruby-cairo (1.17.8-1) unstable; urgency=medium

  [ Jeremy Bícha ]
  * New upstream release needed for cairo 1.17.8
(Closes: #1040230, LP: #2025674)
  * Build-Depend on ruby-poppler & stop ignoring build test failures
(Closes: #1040231)
  * Add minimal debian/gbp.conf
  * Add patch to avoid dependency on ruby-red-colors
  * Refresh patches

  [ Debian Janitor ]
  * Bump debhelper from old 12 to 13
  * Update standards version to 4.6.2, no changes needed

 -- Jeremy Bícha   Mon, 03 Jul 2023 17:06:23 -0400

** Changed in: ruby-cairo (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  ruby-cairo test failure with cairo 1.17.8

Status in cairo package in Ubuntu:
  Fix Released
Status in ruby-cairo package in Ubuntu:
  Fix Released
Status in ruby-cairo package in Debian:
  Unknown

Bug description:
  We need to update ruby-cairo to version 1.17.7 or higher to fix its
  test suite to pass with cairo 1.17.8 in mantic-proposed.

  https://github.com/rcairo/rcairo/blob/master/NEWS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/2025674/+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 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Sergio Durigan Junior]

You're correct, but your message made me look a bit deeper into the
issue and made me remember that, for Jammy, installing libdebuginfod-
common alone won't configure the system to use our debuginfod service.

I would like to turn this bug into a broader "make sure we enable
support for debuginfod.ubuntu.com when installing libdebuginfod-common"
thing.  WDYT (as an SRU team member)?

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Users installing libdebuginfod-common (the package that ships the
  shell snippets responsible for configuring the DEBUGINFOD_URLS
  environment variable, which will ultimately be used by GDB to contact
  the Ubuntu debuginfod service) experience a problem caused by
  permissions being set too tightly for
  /etc/profile.d/debuginfod.{sh,csh}.  This results in DEBUGINFOD_URLS
  not being set for non-root users.

  [ Test Plan ]

  Inside a Jammy container:

  # apt install -y libdebuginfod-common
  # ls -lah /etc/profile.d/debuginfod*

  Verify that the permission of both files allow them to be world-
  readable.

  [ Where problems could occur ]

  Care has been taken to not modify existing file permissions
  unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
  possible to conceive a scenario where upgrading the package would make
  the files world-readable when the user is actually expecting
  otherwise.  However, such "regression" would arguably not be something
  supported because if the intention is to prevent non-root users from
  making use of debuginfod, there are better ways to achieve it.

  [ Original Description ]

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 1991606] Autopkgtest regression report (distro-info/0.23ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted distro-info (0.23ubuntu1.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

autopkgtest/5.11ubuntu1.1 (amd64)
update-manager/1:20.04.10.11 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#distro-info

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  Fix Committed
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
     

[Touch-packages] [Bug 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Robie Basak]

> This results in DEBUGINFOD_URLS not being set for non-root users.

Should the Test Plan not then check that DEBUGINFOD_URLS is actually set
correctly, and that debuginfod functionality actually works?

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Users installing libdebuginfod-common (the package that ships the
  shell snippets responsible for configuring the DEBUGINFOD_URLS
  environment variable, which will ultimately be used by GDB to contact
  the Ubuntu debuginfod service) experience a problem caused by
  permissions being set too tightly for
  /etc/profile.d/debuginfod.{sh,csh}.  This results in DEBUGINFOD_URLS
  not being set for non-root users.

  [ Test Plan ]

  Inside a Jammy container:

  # apt install -y libdebuginfod-common
  # ls -lah /etc/profile.d/debuginfod*

  Verify that the permission of both files allow them to be world-
  readable.

  [ Where problems could occur ]

  Care has been taken to not modify existing file permissions
  unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
  possible to conceive a scenario where upgrading the package would make
  the files world-readable when the user is actually expecting
  otherwise.  However, such "regression" would arguably not be something
  supported because if the intention is to prevent non-root users from
  making use of debuginfod, there are better ways to achieve it.

  [ Original Description ]

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command

[john doe]

adding the .desktop file and logging back in and re-running did not fix
the issue for me with 23.04, unfortunately.

To be clear, my app is calling multiple of these commands and the bug is
that one "allow" and one password entry are not enough. both dialogs pop
up for each invocation of the SUOD_ASKPASS commands as if no gnome
inhibitShortcuts preference or password were entered.

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command

[john doe]

my mistake

** Package changed: gnome-shell (Ubuntu) => openssh (Ubuntu)

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command

[john doe]

** Package changed: openssh (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => New

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Joao Andre Simioni]

Steve,

We got the okay from the user to hold this until we have another high-
impact change. It'd be interesting to set a time frame - if we don't
have any of those happening in, let's say, 6 months, would it be fair to
re-consider the SRU?

Thanks

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  Incomplete
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Sergio Durigan Junior]

** Description changed:

+ [ Impact ]
+ 
+ Users installing libdebuginfod-common (the package that ships the shell
+ snippets responsible for configuring the DEBUGINFOD_URLS environment
+ variable, which will ultimately be used by GDB to contact the Ubuntu
+ debuginfod service) experience a problem caused by permissions being set
+ too tightly for /etc/profile.d/debuginfod.{sh,csh}.  This results in
+ DEBUGINFOD_URLS not being set for non-root users.
+ 
+ [ Test Plan ]
+ 
+ Inside a Jammy container:
+ 
+ # apt install -y libdebuginfod-common
+ # ls -lah /etc/profile.d/debuginfod*
+ 
+ Verify that the permission of both files allow them to be world-
+ readable.
+ 
+ [ Where problems could occur ]
+ 
+ Care has been taken to not modify existing file permissions
+ unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
+ possible to conceive a scenario where upgrading the package would make
+ the files world-readable when the user is actually expecting otherwise.
+ However, such "regression" would arguably not be something supported
+ because if the intention is to prevent non-root users from making use of
+ debuginfod, there are better ways to achieve it.
+ 
+ [ Original Description ]
+ 
  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:
  
  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh
  
  ```
  
  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set because
  the permissions are incorrect on the profile files.
  
  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

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

** Tags added: server-todo

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  Users installing libdebuginfod-common (the package that ships the
  shell snippets responsible for configuring the DEBUGINFOD_URLS
  environment variable, which will ultimately be used by GDB to contact
  the Ubuntu debuginfod service) experience a problem caused by
  permissions being set too tightly for
  /etc/profile.d/debuginfod.{sh,csh}.  This results in DEBUGINFOD_URLS
  not being set for non-root users.

  [ Test Plan ]

  Inside a Jammy container:

  # apt install -y libdebuginfod-common
  # ls -lah /etc/profile.d/debuginfod*

  Verify that the permission of both files allow them to be world-
  readable.

  [ Where problems could occur ]

  Care has been taken to not modify existing file permissions
  unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
  possible to conceive a scenario where upgrading the package would make
  the files world-readable when the user is actually expecting
  otherwise.  However, such "regression" would arguably not be something
  supported because if the intention is to prevent non-root users from
  making use of debuginfod, there are better ways to achieve it.

  [ Original Description ]

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 1980239] Proposed package upload rejected

[Steve Langasek]

An upload of gstreamer-editing-services1.0 to jammy-proposed has been
rejected from the upload queue for the following reason: "not covered by
GNOME exception; includes distro changes not documented in changelog".

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Released
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Steve Langasek]

Mauricio, this SRU is still waiting for an answer to
https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/2019856/comments/17

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  Incomplete
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Bug Watch Updater]

** Changed in: systemd
   Status: New => 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/2009743

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2009743/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

Hello wieczyk, or anyone else affected,

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

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

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

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

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

** Changed in: distro-info (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  Fix Committed
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 

[Touch-packages] [Bug 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Sergio Durigan Junior]

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

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

** Changed in: elfutils (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  Triaged

Bug description:
  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

[Dan Czuchra]

Hi all, are there any updates to this issue? This has broken our 20.04
builds over iPXE. We're trying to update the initrd and vmlinuz files,
but there's not very good documentation on how to update these files.

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

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Triaged
Status in initramfs-tools source package in Hirsute:
  Won't Fix
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 2019212] Re: Backport packages for 22.04.3 HWE stack

[Steve Langasek]

Hello Timo, or anyone else affected,

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

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

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  mesa-amber
  - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
changes to the classic dri drivers
  - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
i915g
  - fixes installation (LP: #2006744) and image build

  [Test case]
  mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  mesa-amber:
  no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 1991606] Autopkgtest regression report (gpgme1.0/1.16.0-1.2ubuntu4.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gpgme1.0 (1.16.0-1.2ubuntu4.1) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

flatpak/1.12.7-1 (arm64)
ros-ros-comm/blacklisted (s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#gpgme1.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version 

[Touch-packages] [Bug 1956111] Re: Colord's colorhug no longer exists but the URI and library do as a required dependency.

[wontfix]

** Tags added: mantic

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

Title:
  Colord's colorhug no longer exists but the URI and library do as a
  required dependency.

Status in colord package in Ubuntu:
  New
Status in colord package in Debian:
  New

Bug description:
  
https://github.com/hughsie/colord/commit/98f83acc910f527496fc149511c9dfa35f954be9

  The domain listed in the upload URI in the gschema has been taken over
  by spammers.

  The library libcolorhug2 is still installed by default as a dependency
  of colord.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1956111/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Marcus Pope]

Thanks Nathan, I came to the same conclusion as the tickets you
provided, as we were trying to run the snap from a shared nfs mount, but
glad/sad to know that snap was the ultimate problem - sigh.  I can now
run the snap directly, without glibc issues so hooray.

I'm now dealing with a different issue after switching to
`/snap/bin/chromium.chromedriver` - `error: unknown flag `port'`

Are you able to confirm that there should be no difference in the cli of
these binaries?

/snap/chromium/current/usr/lib/chromium-browser/chromedriver
vs
/snap/bin/chromium.chromedriver

I'll investigate further on the selenium side, but if I have to open a
different ticket for the driver would I do that here as well? or is
there a separate bug repo for that package?

Thanks a bunch! Your support ethos is superb.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Michaelus]

Nathan Teodosio:

>> "That invocation is not supported, so one could argue that it breaks
unsupported setups."

My apologies, but that comes off as a rather convenient way of saying,
"Well, you shouldn't have been doing it that way in the first place, and
be happy it's worked for you this long."

To be clear, you're saying invoking chromium via a fully qualified,
real-path, with a SNAP-created symbolic link to a actual build
directory, is a "unsupported setup" ?

If I could just install Chromium directly via apt, and not be forced
into a SNAP ...

(I'm not going to try to argue that, here, though)

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026599] [NEW] rsyslogd does not have enough permission to do its job

[Marco Galicia]

Public bug reported:

I have installed a new ubuntu  22.04 server. After installing ufw and a
mailer daemon and activate them. Rsyslog starts complaining about
permission denied error in the following files:

/var/log/ufw.log
/var/log/mail.err
/var/log/mail.log

and the following lines appear in journalctl.
Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed 
(module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ]
Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended 
(module 'builtin:omfile'), retry 0. There should be messages before this one 
giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 
]
Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed 
(module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ]
Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended 
(module 'builtin:omfile'), retry 0. There should be messages before this one 
giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 
]

Creating the files manually and adding the group rsyslog:rsyslog solves
the logs.

Expected behaviour: rsyslog has the adequate configuration to create the files 
in /var/log and update them.
What happened instead: the log files have to be created manually, or maybe, the 
default config of rsyslog modified. Or the permission of the /var/log folder 
have to be modified.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: rsyslog 8.2112.0-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
Uname: Linux 5.15.0-76-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jul  7 17:07:50 2023
InstallationDate: Installed on 2023-07-07 (0 days ago)
InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230217.1)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

- I have installed a new ubuntu server. After installing ufw and a mailer
- daemon and activate them. Rsyslog starts complaining about permission
- denied error in the following files:
- 
+ I have installed a new ubuntu  22.04 server. After installing ufw and a
+ mailer daemon and activate them. Rsyslog starts complaining about
+ permission denied error in the following files:
  
  /var/log/ufw.log
  /var/log/mail.err
  /var/log/mail.log
  
- 
- and the following lines appear in journalctl. 
+ and the following lines appear in journalctl.
  Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed 
(module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ]
  Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended 
(module 'builtin:omfile'), retry 0. There should be messages before this one 
giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 
]
  Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed 
(module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ]
  Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended 
(module 'builtin:omfile'), retry 0. There should be messages before this one 
giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 
]
  
- 
- Creating the files manually and adding the group rsyslog:rsyslog solves the 
logs. 
+ Creating the files manually and adding the group rsyslog:rsyslog solves
+ the logs.
  
  Expected behaviour: rsyslog has the adequate configuration to create the 
files in /var/log and update them.
  What happened instead: the log files have to be created manually, or maybe, 
the default config of rsyslog modified. Or the permission of the /var/log 
folder have to be modified.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: rsyslog 8.2112.0-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jul  7 17:07:50 2023
  InstallationDate: Installed on 2023-07-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  rsyslogd does not have enough permission to do its job

Status in rsyslog package in Ubuntu:
  New

Bug description:
  I have installed a new ubuntu  22.04 server. After installing ufw and
  a mailer daemon and activate them. Rsyslog starts complaining about
  permission denied error in the 

Re: [Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Nathan Teodosio]

I also appreciate your situation and I'm sorry this has been giving you 
a hard time. I'm happy to help with what I can.

 > 1. Is there any way we can influence where chromium looks for glibc to
 > find the base 2.35?  (Is this something that would be resolved if I
 > could get /snap/bin/chromium working?)

Not really. Yes, this would be resolved if you managed to get 
/snap/bin/chromium working.

 > 2. I still cannot get `chromium` or `/snap/bin/chromium` to work on any
 > of the versions, stable / edge / stable/core20.  It reports the rather
 > unhelpful `cannot open path of the current working directory: Permission
 > denied`

That could be some things, e.g. LP:1973321, LP:1620771.

 > Migrating to 22.04 is pretty much off the table for our situation as
 > 20.04 is still under lts and we have a _lot_ of other dependencies to
 > deal with. I'm also ok with opening a new ticket if you are set on
 > keeping this one closed.

20.04 is definitely supported and your experience should be as good as 
in 22.04; I'm sorry that is not the case.

Please, if your problem isn't already covered in the ones I mentioned, 
do open a new ticket, this one is a bit mixed up.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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

Re: [Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Nathan Teodosio]

Am 07/07/2023 um 17:59 schrieb Michaelus:
 > ... by the Apache user, and, because APT forces the SNAP Chromium
 > package, rather than the standard Debian package, and because the Apache
 > user's (www-data) home directory is /var/www and not /home/www-data, one
 > cannot invoke Chromium via Apache at /snap/bin/chromium because of the
 > SNAP home directory requirement

That is LP:1620771.

 > It is my opinion that IF Ubuntu 20.04 LTS (supported until April 2025)
 > is built with SNAP Core20, building a single Chromium SNAP on Core22
 > going forward will continue to break Ubuntu 20.04 systems

That invocation is not supported, so one could argue that it breaks 
unsupported setups. I say that although I appreciate that as per 
LP:1620771 that might currently have been the only way for you.

 > ... well, the fact that /snap/chromium/**current**/usr/lib/chromium-
 > browser/chrome  (current) is a symlink to whatever build # is the
 > "current" suggests Chromium can/and-without-problems-should-be-able-to-
 > be called from that path (as it has been, until someone decided to make
 > the latest Chromium build against Core22)

That's unfortunate because, in general, it cannot. Please feel free file 
a bug against snapd if you believe that should change, this one is mixed 
up with printing so it wouldn't be proper to target it to snapd as of now.

 > That, and the fact that there's no option to revert to a previous
 > Chromium build, is why this is "broken"

There is, as for all snaps, with "snap revert", but that is indeed not 
at all a solution.

 > With respect, not "everyone and everything" is running on the "latest
 > and greatest"

Sure, and I'm glad no one here holds that opinion.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Marcus Pope]

Nathan, thanks for the detailed followup.  I'm unfortunately not in a
good working state, as I introduced a typo in an environment variable
used to run our functional test harness when I converted to invoking
/snap/bin/chromium with `runuser` instead of a direct invocation form
our vagrant user.  The result was our test harness ran firefox instead
of chromium :(

After fixing that issue, I'm back where I started with chromium failing
to find the proper glibc library with stable or edge.

I can fully appreciate your situation regarding the core22, and I can
re-confirm that the stable/core20 package does work for us with the
unconfirmed command, but I knew that was never going to get a support
path.  That being said, I'm wondering if you have any advice on the
following issues:

1. Is there any way we can influence where chromium looks for glibc to
find the base 2.35?  (Is this something that would be resolved if I
could get /snap/bin/chromium working?)

2. I still cannot get `chromium` or `/snap/bin/chromium` to work on any
of the versions, stable / edge / stable/core20.  It reports the rather
unhelpful `cannot open path of the current working directory: Permission
denied`

Migrating to 22.04 is pretty much off the table for our situation as
20.04 is still under lts and we have a _lot_ of other dependencies to
deal with.  I'm also ok with opening a new ticket if you are set on
keeping this one closed.

Thanks in advance!
-Marcus

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Michaelus]

I've been using headless chromium on the cli with the --print-to-pdf
parameter to generate PDF documents on Ubuntu 20.04 for well over a
year.

Chromium has been invoked at:

/snap/chromium/current/usr/lib/chromium-browser/chrome

... by the Apache user, and, because APT forces the SNAP Chromium
package, rather than the standard Debian package, and because the Apache
user's (www-data) home directory is /var/www and not /home/www-data, one
cannot invoke Chromium via Apache at /snap/bin/chromium because of the
SNAP home directory requirement

It is my opinion that IF Ubuntu 20.04 LTS (supported until April 2025)
is built with SNAP Core20, building a single Chromium SNAP on Core22
going forward will continue to break Ubuntu 20.04 systems

Please do not make assumptions that everyone is calling Chromium with an
actual/normal user

I can confirm that this "fixes" the issue for me:

  snap refresh --channel stable/core20 chromium


Nathan Teodosio said: "...And that's why we discourage and cannot support 
unconfined runs."

... well, the fact that /snap/chromium/**current**/usr/lib/chromium-
browser/chrome  (current) is a symlink to whatever build # is the
"current" suggests Chromium can/and-without-problems-should-be-able-to-
be called from that path (as it has been, until someone decided to make
the latest Chromium build against Core22)

That, and the fact that there's no option to revert to a previous
Chromium build, is why this is "broken"

With respect, not "everyone and everything" is running on the "latest
and greatest"

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026307] Re: ssh-askpass-gnome pops up for every sudo command

[Lena Voytek]

Thanks for the bug report. I tested this on my system and can confirm this is 
an issue in Jammy, Kinetic, Lunar, and Mantic. I found this issue noted on the 
gnome gitlab here too - https://gitlab.gnome.org/GNOME/seahorse/-/issues/352 
Based on the comments in that issue I was able to come up with a workaround 
that fixes this bug by creating a desktop file for the program at 
~/.local/share/applications/gnome-ssh-askpass.desktop and inserting the 
following:

[Desktop Entry]
Name=GNOME ssh-askpass
GenericName=ssh-askpass
Type=Application
Exec=/usr/lib/openssh/gnome-ssh-askpass
Terminal=false



** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #352
   https://gitlab.gnome.org/GNOME/seahorse/-/issues/352

** Also affects: openssh (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: openssh (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2026307/+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 1970144] Re: [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu 22.04

[andru shevchenko]

Maybe and just maybe, this is the issue of the desktop environment
Ubuntu 22.04 (which I use on VM). I have solved this `inconvenience` by
installing the [xubuntu-desktop]

sudo apt install xubuntu-desktop

And after the reboot, I switched it [Xfce session], and that's it.

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

Title:
  [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu
  22.04

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  xdpyinfo 
  name of display::0
  version number:11.0
  vendor string:The X.Org Foundation
  vendor release number:12201001
  X.Org version: 1.22.1.1
  maximum request size:  16777212 bytes
  motion buffer size:  256
  bitmap unit, bit order, padding:32, LSBFirst, 32
  image byte order:LSBFirst
  number of supported pixmap formats:7
  supported pixmap formats:
  depth 1, bits_per_pixel 1, scanline_pad 32
  depth 4, bits_per_pixel 8, scanline_pad 32
  depth 8, bits_per_pixel 8, scanline_pad 32
  depth 15, bits_per_pixel 16, scanline_pad 32
  depth 16, bits_per_pixel 16, scanline_pad 32
  depth 24, bits_per_pixel 32, scanline_pad 32
  depth 32, bits_per_pixel 32, scanline_pad 32
  keycode range:minimum 8, maximum 255
  focus:  None
  number of extensions:23
  BIG-REQUESTS
  Composite
  DAMAGE
  DOUBLE-BUFFER
  DRI3
  GLX
  Generic Event Extension
  MIT-SHM
  Present
  RANDR
  RECORD
  RENDER
  SHAPE
  SYNC
  X-Resource
  XC-MISC
  XFIXES
  XFree86-VidModeExtension
  XINERAMA
  XInputExtension
  XKEYBOARD
  XTEST
  XVideo
  default screen number:0
  number of screens:1

  screen #0:
dimensions:3838x1781 pixels (1015x471 millimeters)
resolution:96x96 dots per inch
depths (7):24, 1, 4, 8, 15, 16, 32
root window id:0x2bb
depth of root window:24 planes
number of colormaps:minimum 1, maximum 1
default colormap:0x43
default number of colormap cells:256
preallocated pixels:black 0, white 16777215
options:backing-store WHEN MAPPED, save-unders NO
largest cursor:3838x1781
current input event mask:0xda0030
  EnterWindowMask  LeaveWindowMask  StructureNotifyMask 
 
  SubstructureNotifyMask   SubstructureRedirectMask PropertyChangeMask  
 
  ColormapChangeMask

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:25:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=e6bcbb51-635a-42a1-ab99-75af8c14475f ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: 

[Touch-packages] [Bug 24600] Re: Should honour hostname from DHCP

[Benjamin Drung]

initramfs-tools 0.142ubuntu7 has an autopkgtest qemu-net that tests that
the hostname is set to the value provided by the DHCP server.

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Should honour hostname from DHCP

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  scripts/nfs should set the hostname if available from the
  net-${DEVICE}.conf file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/24600/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Nathan Teodosio]

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Invalid
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026199] Re: Please merge 3.137 into mantic

[Mateus Rodrigues de Morais]

** Description changed:

  The upstream version 3.137 should be merged into mantic. The current
  version is 3.134ubuntu1.
  
  * PPA for review: 
https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199
  * Git rebase of Ubuntu delta available at: 
https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel
+   - To be pushed to ubuntu/devel at 
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/adduser/+git/adduser
  
  Note: this is a tracking bug

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

Title:
  Please merge 3.137 into mantic

Status in adduser package in Ubuntu:
  In Progress

Bug description:
  The upstream version 3.137 should be merged into mantic. The current
  version is 3.134ubuntu1.

  * PPA for review: 
https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199
  * Git rebase of Ubuntu delta available at: 
https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel
- To be pushed to ubuntu/devel at 
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/adduser/+git/adduser

  Note: this is a tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2026199/+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 2025599] Re: BlueZ release 5.68

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.68-0ubuntu1

---
bluez (5.68-0ubuntu1) mantic; urgency=medium

  * Move FIRMWARE_DIR change out of raspi-bcm43xx-load-firmware.patch and
into its own patch: use-lib-firmware.patch
  * New upstream release 5.68 (LP: #2025599):
- Fix issue with A2DP and handling of Transport.Acquire.
  * Includes short-lived upstream release 5.67:
- Fix issue with BAP and initiating QoS and Enable procedures.
- Fix issue with BAP and detaching streams when PAC is removed.
- Fix issue with BAP and reading all instances of PAC.
- Fix issue with BAP and not being able to reconfigure.
- Fix issue with BAP and transport configuration changes.
- Fix issue with BAP and handling unexpected disconnect.
- Fix issue with GATT and not removing pending services.
- Fix issue with GATT and client ready handling.
- Fix issue with handling fallback to transient hostname.
- Add support for SecureConnections configuration option.
- Add support for Mesh Remove Provisioning.
- Add support for Mesh Private Beacons.
  * Dropped patches:
- obex-Use-GLib-helper-function-to-manipulate-paths.patch rather
  than resolving the conflicts it has with upstream now. It was proposed
  in 2013 and raised again in 2017 where it was rejected by upstream.
  * Refreshed patches:
- 0002-hostname-handle-chassis-type-handset.patch

 -- Daniel van Vugt   Thu, 06 Jul 2023
12:09:23 +0200

** Changed in: bluez (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  BlueZ release 5.68

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  BlueZ release 5.68 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Joel Vandal]

Previously, I'm used /snap/chromium/current/usr/lib/chromium-
browser/chrome to start Chrome in kiosk mode in order to access file://
on local system.

Now all work as expected using latest version (2529) when I execute
using : /snap/bin/chromium

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2004505] Re: apt-key is still packaged

[Julian Andres Klode]

I have adjusted the manual page in git to say 23.10 but this may be
postponed to 24.04 once more.

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

Title:
  apt-key is still packaged

Status in apt package in Ubuntu:
  New

Bug description:
  The apt-key(8) manpage includes:

  apt-key(8) will last be available in Debian 11 and Ubuntu 22.04.

  It appears that apt-key was shipped in Ubuntu 22.10 by accident.
  apt-key is still in the 2.5.5 apt packaged for Lunar:
  https://launchpad.net/ubuntu/lunar/amd64/apt/2.5.5

  ⏚ [sarnold:/tmp] $ wget 
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  --2023-02-01 18:58:39--  
http://launchpadlibrarian.net/646589288/apt_2.5.5_amd64.deb
  Resolving launchpadlibrarian.net (launchpadlibrarian.net)... 
2620:2d:4000:1001::8007, 2620:2d:4000:1001::8008, 185.125.189.229, ...
  Connecting to launchpadlibrarian.net 
(launchpadlibrarian.net)|2620:2d:4000:1001::8007|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 1377746 (1.3M) [application/x-debian-package]
  Saving to: ‘apt_2.5.5_amd64.deb’

  apt_2.5.5_amd64.deb
  
100%[>]
  1.31M  1.26MB/sin 1.0s

  2023-02-01 18:58:41 (1.26 MB/s) - ‘apt_2.5.5_amd64.deb’ saved
  [1377746/1377746]

  ⏚ [sarnold:/tmp] 2s $ ar x apt_2.5.5_amd64.deb 
  ⏚ [sarnold:/tmp] $ tar tf data.tar.zst | grep bin
  ./usr/bin/
  ./usr/bin/apt
  ./usr/bin/apt-cache
  ./usr/bin/apt-cdrom
  ./usr/bin/apt-config
  ./usr/bin/apt-get
  ./usr/bin/apt-key
  ./usr/bin/apt-mark
  ⏚ [sarnold:/tmp] $ 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2004505/+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 2025462] Re: Apt deletes ubuntu-desktop during dist-upgrade

[Julian Andres Klode]

The regression fix causes an issue whereby any new dependencies or
recommends of updates that are phasing will be installed, we're
currently investigating how to solve this, I believe this is also a
problem in the apt upgrade code path (which can install new packages),
but not in apt-get upgrade.

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

Title:
  Apt deletes ubuntu-desktop during dist-upgrade

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Jammy:
  New
Status in apt source package in Kinetic:
  New
Status in apt source package in Lunar:
  New
Status in apt source package in Mantic:
  In Progress

Bug description:
  [Impact]
  gnome-shell gets removed on upgrades of gnome-shell and mutter if due to 
phasing we can only upgrade src:gnome-shell.

  [Test plan]
  This adds a minimal test case to the test suite that reproduced the issue and 
verifies the fix, test plan consists of the autopkgtests.

  [Where problems could occur]
  We could see a resurgence of bugs like LP#1990586 where the solver failed to 
run at all because things got too complex, however this is a bit more unlikely 
as we now use the by-keep resolver to handle rolling back phased updates.

  [Other Info]
  gnome-shell Depends: gnome-shell-common (= ${binary-Version), mutter (>= 
matching)

  So when mutter cannot be updated due to phasing, gnome-shell becomes
  non-installable, but gnome-shell-common can be updated, so APT decided
  to remove gnome-shell and the meta packages in its infinite wisdom.

  The fix addresses this by resolving the dist-upgrade as if there were
  no phasing, and then retroactively marks phases for keep and then
  anything broken by that for keep.

  This required some restructuring because normally we'd also keep
  broken Recommends back, but here dist-upgrade may have decided that
  was ok, so we need to build an allowlist of where Recommends can be
  broken to avoid undoing unrelated changes.

  [Original bug report]

  This morning I got surprised by my laptop booting to a tty instead of
  a desktop environment. It turned out that the entire desktop
  environment was no longer present on my machine. Doing an apt install
  ubuntu-desktop-minimal resolved the issue.

  The machine had been running for a while. Looking at the apt logs, it
  looks like apt deleted ubuntu-desktop on its own during a dist-upgrade
  a couple of weeks back.

  Start-Date: 2023-06-08  14:20:46
  Commandline: apt dist-upgrade
  Requested-By: alex (1000)
  Upgrade: gnome-shell-common:amd64 (44.0-2ubuntu3, 44.1-0ubuntu1)
  Remove: gnome-shell:amd64 (44.0-2ubuntu3), ubuntu-desktop:amd64 (1.501), 
gdm3:amd64 (44.0-1ubuntu1), gnome-shell-extension-desktop-icons-ng:amd64 
(46+really47.0.2-3), gnome-shell-extension-appindicator:amd64 (53-1), 
ubuntu-session:amd64 (44.0-1ubuntu1), gnome-shell-extension-manager:amd64 
(0.4.0-1), gnome-shell-extension-ubuntu-dock:amd64 (79ubuntu2.23.04.1), 
ubuntu-desktop-minimal:amd64 (1.501)
  End-Date: 2023-06-08  14:20:48

  I'm using the following version of Ubuntu:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 23.04
  Release:  23.04
  Codename: lunar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2025462/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Gunnar Hjalmarsson]

Nah, it's fine to test on lunar. I do it on mantic since I don't have a
lunar installation easily available.

Previously, when I couldn't reproduce, I tested in a Wayland session.
Now I have tried "Ubuntu on Xorg", and there I see bad things when using
gnome-terminal or gedit, i.e. gtk3 applications. When trying to use a
dead key followed by a character, it all disappears. And it's not only
dead keys: The same happens when trying to input a character using
Ctrl+Shift+U or when trying to use some advanced input method, e.g.
ibus-libpinyin.

Are you able to confirm that the issue is limited to gtk3 applications
in X sessions?

I reported the observation on the upstream issue:
https://github.com/ibus/ibus/issues/2486#issuecomment-1625042967

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

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1996652/+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 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Launchpad Bug Tracker]

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

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

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Confirmed

Bug description:
  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 2024950] Re: add support for Green Linux, fork linux mint

[Simon Chopin]

Hi,

I'm sorry, I'm not entirely sure I understood that correctly, but if
you're looking for the apport sources, you can find them there:

https://github.com/canonical/apport

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

Title:
  add support for Green Linux, fork linux mint

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Incomplete

Bug description:
  oscillation@oscillation-NEO-M114:~$ ubuntu-bug gnome-software

  *** Collecting information about the problem

  The collected information can be sent to developers
  to improve the application. This may take a few minutes.
  ...

  *** A problem in gnome-software

  Unable to report a problem:

  It looks like this is an unofficial Green package. Try again after
  updating the indexes of available packages. If this does not help,
  then remove the relevant third-party packages and try again.

  To continue, press any key...

  There are no pending crash messages. Try the --help key.

  kolab@kolab-NEO-M114:~$ nala show apart
  Package: import
  Version: 2.20.11-0ubuntu82.5
  koljab@koljab-NEO-M114:~$ cat /etc/os-release 
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2 Cinnamon 64-bit"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/;
  SUPPORT_URL="https://forum.linuxmint.su/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/;
  PRIVACY_POLICY_URL="https://greenlinux.ru/;
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  koljab@koljab-NEO-M114:~$
  --- 
  ProblemType: Bug
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashReports:
   640:1000:1000:88955:2023-06-20 14:14:04.299071363 +0300:2023-06-20 
14:14:04.299071363 
+0300:/var/crash/_usr_share_cinnamon_cinnamon-settings_xlet-settings.py.1000.crash
   640:1000:1000:44330:2023-06-24 09:55:41.470598469 +0300:2023-06-24 
09:55:41.470598469 
+0300:/var/crash/_usr_bin_cinnamon-subprocess-wrapper.1000.crash
  CurrentDesktop: X-Cinnamon
  DistroRelease: Green Linux 21
  InstallationDate: Installed on 2023-06-09 (15 days ago)
  InstallationMedia: Green Linux 21.1.1 "Victoria" (20230512)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: apport 2.20.11-0ubuntu82.5 [origin: Ubuntu]
  PackageArchitecture: all
  Tags: third-party-packages victoria
  Uname: Linux 6.3.9-x64v3-xanmod1 x86_64
  UnreportableReason: Похоже, это неофициальный пакет Green. Повторите попытку 
после обновления индексов доступных пакетов. Если это не помогает, тогда 
удалите соответствующие сторонние пакеты и попробуйте ещё раз.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2024950/+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 1991606] Autopkgtest regression report (dput/1.0.3ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted dput (1.0.3ubuntu1.1) for focal have 
finished running.
The following regressions have been reported in tests triggered by the package:

dgit/9.10 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#dput

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 

Re: [Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[Federico Poloni]

On 05/07/23 16:46, Gunnar Hjalmarsson wrote:
> @Federico: Thanks for testing and reporting that observation!
>
> I can't reproduce it (on mantic), though. Dead keys work as expected for
> me, also with the keyboard layout you mentioned.
>
> Are you sure that the issue is related to the proposed ibus version?
> Does the issue go away if you downgrade to the released version? Are you
> testing on lunar or mantic?

I downgraded and the issue went away so yes, I assume it's related. I'm
on Lunar, apologies if that's the wrong version to test.

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

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1996652/+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 2019212] Re: Backport packages for 22.04.3 HWE stack

[Timo Aaltonen]

mesa tested as described on bug 2021948

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

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  In Progress

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  mesa-amber
  - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
changes to the classic dri drivers
  - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
i915g
  - fixes installation (LP: #2006744) and image build

  [Test case]
  mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  mesa-amber:
  no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Nathan Teodosio]

Marcus, from what I gather, and correct me if I'm wrong, you were able
to fix all your problems in your headless environment with Chromium
edge. Not with Chromium stable?

And hats off to you for responding to the proposed questions and
investigating the issue. That was a great help and much appreciated!

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

[Nathan Teodosio]

To be clear, the reason why this has hit you is that Chromium in the
stable channel switched from Core20 in 114.0.5735.106 to Core22 in
114.0.5735.198 (this is a downstream, in other words Ubuntu
maintainer's, decision, not Chromium's maintainers').

Core20 is a base from Ubuntu 20.04, while core22, from 22.04.

As such, it makes sense that you had no library problems in Focal with
the unconfined command (/snap/chromium/.../chrome) when Core20 was used
— as the base and your system libraries were the same, they were
compatible environments.

Once Core22 is used to build, Chromium is linked against its libraries,
and if you run the unconfined command in 20.04 now, it will find the
host's GLIBC 2.31 instead of the base's 2.35; That aligns with the error
messages.

And that's why we discourage and cannot support unconfined runs.

We are not tempted to switch back to Core20 — unless issues with the
supported run (/snap/bin/chromium, snap run chromium or simply chromium)
are found — because Core22 is the newer base, and actually solves bugs
with hardware acceleration.

I created the stable/core20 channel with the previous snap so you, the
affected users, could confirm the switch was the cause and have time to
adapt. But very importantly: This does not mean that we are going to
actively maintain that new channel, so please don't rely on it for long
term.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 1991606] Please test proposed package

[Timo Aaltonen]

Hello wieczyk, or anyone else affected,

Accepted gpgme1.0 into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gpgme1.0/1.16.0-1.2ubuntu4.1 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
   

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Timo Aaltonen]

Hello wieczyk, or anyone else affected,

Accepted gpgme1.0 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gpgme1.0/1.13.1-7ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: gpgme1.0 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: gpgme1.0 (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env =