[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo

[CH]

The upstream source doesn't have the error: 
https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69

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

Title:
  ifupdown resolved script has typo

Status in ifupdown package in Ubuntu:
  New

Bug description:
  This error happens when you try to run ifup or ifdown:

  ```
  # ifdown enp3s0
  /etc/network/if-down.d/resolved: 12: mystatedir: not found

  # ifup enp3s0
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  ```

  Here's the first 12 lines of those scripts:
  ```
  # head -n 12 /etc/network/if-up.d/resolved

  #!/bin/sh
  #
  # Script fragment to make ifupdown supply DNS infromation to resolved
  #

  case "$ADDRFAM" in
  inet|inet6) : ;;
  *) exit 0 ;;
  esac

  if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
  mystatedir statedir ifindex interface
  ```

  I'm thinking that the word `local` used to appear before `mystatedir`
  on line 12, but that was when it was a function.  When it was
  converted back from being a function, the 'local' keyword was removed,
  but the variables remained.

  Either make it into a function again, or delete line 12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2017840/+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 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Daniel Tang]

Thank you Mr. Eickmeyer for your fix in 23.04.

> notice how the askubuntu question was closed? That's because it was
offtopic/for an unsupported release

AskUbuntu closes questions as off-topic *because* they want those
questions to be *posted here* instead. It says "Bug reports and problems
specific to development version of Ubuntu should be reported on
Launchpad so that developers can see, track and fix these issues."

Anyway, this bug doesn't affect me, and I might as well treat the
Invalid as Fix Committed but not released.

> won't be supported until August 2024 (upon release of 24.04.1)

Interesting! You helped me learn something today after reading
https://ubuntu.com/server/docs/upgrade-introduction . I never noticed
this as I personally upgrade to either latest or dev, never LTS
specifically. I will post a comment on AskUbuntu to relay this
information

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

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Invalid
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

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

  Not my computer.

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

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all -i ./ubuntustudio-default-settings_*

  dpkg --configure -a
  apt --fix-broken install
  apt upgrade
  apt dist-upgrade
  ```

  # Analysis

  Please apply an analogous fix. Where I mentioned `Conflicts:` on
  AskUbuntu, a 

[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Erich Eickmeyer]

Yeah, ok. Ubuntu Studio lead here.

This bug is invalid for two reasons:

1) Upgrades to 24.04 aren't even supported yet and won't be supported until 
August 2024 (upon release of 24.04.1)
2) The exact bug was caught before the release of Lunar Lobster (23.04) and the 
fix is included in that release, but no bug was filed because I was the one who 
found it and didn't need to file it. (see 
https://git.launchpad.net/ubuntustudio-default-settings/commit/?id=7de146f7c74f8c5d73e401513500c700f38f5acf
 if you don't believe me)

Long-story short, NOBODY should be testing upgrades from 22.04 to 24.04
right now, and NOBODY should be expecting support for this. That said,
there *will* be a Conflicts: line in place before 24.04's release, but
this is not something anybody should be expecting now.

Furthermore, notice how the askubuntu question was closed? That's
because it was offtopic/for an unsupported release. I'm treating it the
same here.

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Invalid
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

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

  Not my computer.

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

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all 

[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[dann frazier]

That kernel change doesn't fix the issue:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-
loop/noble/amd64/l/livecd-rootfs/20240125_203808_8b5c9@/log.gz

Which actually didn't surprise me after thinking about it. systemd-udevd
is going to ask for a partition reread when it gets the uevent for loop0
at some point - it doesn't matter if we hold it off until losetup's
reread completes. There will always be a window where the partition
device files disappear and reappear.

Perhaps we just need a `udevadm wait $rootfs_dev_mapper --settle`.

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu (Studio) better.

@Bluesbrother  (or the original posted to askubu..)

Can you please add what your installation media was, ie.

`cat /var/log/installer/media-info`

as your original post on askubu implies you release-upgraded to noble,
and thus this issue may only occur on upgrades, rather than fresh
installs.  Ideally an `apport-collect` would gather this (& more
details), but you aren't the original report of this bug report.

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

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  Confirmed

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

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

  Not my computer.

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

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all -i ./ubuntustudio-default-settings_*

  dpkg --configure -a
  apt --fix-broken install
  apt upgrade
  apt dist-upgrade
  ```

  # Analysis

  Please apply an analogous fix. Where I mentioned `Conflicts:` on
  AskUbuntu, a `Pre-Depends:` may be necessary instead as I read
  somewhere on Launchpad.

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


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

[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Daniel Tang]

Marked as confirmed as the real reporter is the asker on AskUbuntu, and
after my investigation, I confirm that this bug is reasonable.

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

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  Confirmed

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

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

  Not my computer.

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

  Not my computer.

  3) What you expected to happen

  The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
  successfully.

  4) What happened instead

  The upgrade failed and they posted to AskUbuntu.

  # Copy of their question body

  After an upgrade to 
  ```
  Distributor ID: Ubuntu
  Description:Ubuntu Noble Numbat (development branch)
  Release: 24.04
  Codename:noble 

  ```
  apt won't update bcs of unmet dependencies.

  ``` 
  The following packages have unmet dependencies:
   libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
   libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
  ```
  I've tried: 

  ``` 
  apt --fix-broken install

  ```
  ```
  dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
   trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  dpkg-query: package 'fontconfig-config' is not installed
  Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
  Errors were encountered while processing:
   /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ```

  # Copy of workaround in my answer body

  The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
  rgb.conf` out of `ubuntustudio-default-settings`
  ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
  settings/filelist),
  [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
  settings/filelist)) and into [`fontconfig-
  config`](https://packages.ubuntu.com/noble/all/fontconfig-
  config/filelist). The `ubuntustudio-default-settings` package needs to
  be updated first but the maintainers forgot to add an automatic
  `Conflicts:` line.

  You can retry installing the package in the correct order by running
  `sudo apt install --upgrade ubuntustudio-default-settings`. If that
  does not work, you need to forcibly reinstall things in the correct
  order:

  ```bash
  sudo -i

  apt update
  apt download ubuntustudio-default-settings
  apt download fontconfig-config

  # Temporarily force-uninstall only ubuntustudio-default-settings
  # so that we DON'T uninstall ubuntustudio-desktop
  dpkg --force-all -r ubuntustudio-default-settings
  dpkg --force-all -i ./fontconfig-config_*
  dpkg --force-all -i ./ubuntustudio-default-settings_*

  dpkg --configure -a
  apt --fix-broken install
  apt upgrade
  apt dist-upgrade
  ```

  # Analysis

  Please apply an analogous fix. Where I mentioned `Conflicts:` on
  AskUbuntu, a `Pre-Depends:` may be necessary instead as I read
  somewhere on Launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+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 2051313] [NEW] font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04

[Daniel Tang]

Public bug reported:

This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

A nearly identical bug is
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
default-settings`. Please add an analogous fix.

A similar but potentially unrelated bug is
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
settings/+bug/2037471 .

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

Not my computer.

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

Not my computer.

3) What you expected to happen

The AskUbuntu user's upgrade from 22.04 to 24.04 to complete
successfully.

4) What happened instead

The upgrade failed and they posted to AskUbuntu.

# Copy of their question body

After an upgrade to 
```
Distributor ID: Ubuntu
Description:Ubuntu Noble Numbat (development branch)
Release: 24.04
Codename:noble 

```
apt won't update bcs of unmet dependencies.

``` 
The following packages have unmet dependencies:
 libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1)
 libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution). 
```
I've tried: 

``` 
apt --fix-broken install

```
```
dpkg: error processing archive 
/var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack):
 trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also 
in package ubuntustudio-default-settings 22.04.26.3
dpkg-query: package 'fontconfig-config' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
dpkg-query: package 'fontconfig-config' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
dpkg-query: package 'fontconfig-config' is not installed
Use dpkg --contents (= dpkg-deb --contents) to list archive files contents.
Errors were encountered while processing:
 /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
```

# Copy of workaround in my answer body

The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel-
rgb.conf` out of `ubuntustudio-default-settings`
([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default-
settings/filelist),
[after](https://packages.ubuntu.com/noble/all/ubuntustudio-default-
settings/filelist)) and into [`fontconfig-
config`](https://packages.ubuntu.com/noble/all/fontconfig-
config/filelist). The `ubuntustudio-default-settings` package needs to
be updated first but the maintainers forgot to add an automatic
`Conflicts:` line.

You can retry installing the package in the correct order by running
`sudo apt install --upgrade ubuntustudio-default-settings`. If that does
not work, you need to forcibly reinstall things in the correct order:

```bash
sudo -i

apt update
apt download ubuntustudio-default-settings
apt download fontconfig-config

# Temporarily force-uninstall only ubuntustudio-default-settings
# so that we DON'T uninstall ubuntustudio-desktop
dpkg --force-all -r ubuntustudio-default-settings
dpkg --force-all -i ./fontconfig-config_*
dpkg --force-all -i ./ubuntustudio-default-settings_*

dpkg --configure -a
apt --fix-broken install
apt upgrade
apt dist-upgrade
```

# Analysis

Please apply an analogous fix. Where I mentioned `Conflicts:` on
AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere
on Launchpad.

** Affects: fontconfig (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: ubuntustudio-default-settings (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Also affects: fontconfig (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntustudio-default-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  font-config confilcts ubuntustudio-default-settings upgrading from
  22.04 to 24.04

Status in fontconfig package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  Confirmed

Bug description:
  This bug was migrated from https://askubuntu.com/q/1501240/1004020 .

  A nearly identical bug is
  https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It
  fixed things for `kubuntu-settings-desktop` but not `ubuntustudio-
  default-settings`. Please add an analogous fix.

  A similar but potentially unrelated bug is
  https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default-
  settings/+bug/2037471 .

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

  

[Touch-packages] [Bug 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard

[Christopher Barrington-Leigh]

** Description changed:

  Everything's been great for a couple of months on this new machine
  
  Yesterday or the day before it started locking up hard, spontaneously, 
without high load.
  X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.
  
- I accept updates when they arrive. Recently it's been telling me to do
- firmware updates, too.
+ Other context: 
+ I accept OS updates when they arrive. Recently it's been telling me to do 
firmware updates, too.
  
  It's happening frequently enough that it's not safe for me to do anything 
much on the computer.
  I normally use this machine ~14 hours per day.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 19:40:13 2024
  DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
-  virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
+  virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
+  virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
-  Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
+  Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
+    Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
  InstallationDate: Installed on 2022-09-02 (510 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3PET20W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
  dmi.product.family: ThinkPad T14s Gen 4
  dmi.product.name: 21F6CTO1WW
  dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
  dmi.product.version: ThinkPad T14s Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

** Summary changed:

- T14s Gen4 Intel under 23.10 started locking up hard
+ T14s Gen4 Intel under 23.10 started freezing / locking up hard

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

Title:
  T14s Gen4 Intel under 23.10 started freezing / locking up hard

Status in xorg package in Ubuntu:
  New

Bug description:
  Everything's been great for a couple of months on this new machine

  Yesterday or the day before it started locking up hard, spontaneously, 
without high load.
  X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.

  Other context: 
  I accept OS updates when they arrive. Recently it's been telling me to do 
firmware updates, too.

  It's happening frequently enough that it's not safe for me to do anything 
much on the computer.
  I normally use this machine ~14 hours per day.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard

[Christopher Barrington-Leigh]

The last crash before I reported this was just before hard-rebooting
around time 2024-01-25 19:30

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

Title:
  T14s Gen4 Intel under 23.10 started locking up hard

Status in xorg package in Ubuntu:
  New

Bug description:
  Everything's been great for a couple of months on this new machine

  Yesterday or the day before it started locking up hard, spontaneously, 
without high load.
  X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.

  I accept updates when they arrive. Recently it's been telling me to do
  firmware updates, too.

  It's happening frequently enough that it's not safe for me to do anything 
much on the computer.
  I normally use this machine ~14 hours per day.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 19:40:13 2024
  DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
   virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
  InstallationDate: Installed on 2022-09-02 (510 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
  dmi.bios.date: 10/30/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3PET20W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21F6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
  dmi.product.family: ThinkPad T14s Gen 4
  dmi.product.name: 21F6CTO1WW
  dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
  dmi.product.version: ThinkPad T14s Gen 4
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051303/+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 2051303] [NEW] T14s Gen4 Intel under 23.10 started locking up hard

[Christopher Barrington-Leigh]

Public bug reported:

Everything's been great for a couple of months on this new machine

Yesterday or the day before it started locking up hard, spontaneously, without 
high load.
X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.

I accept updates when they arrive. Recently it's been telling me to do
firmware updates, too.

It's happening frequently enough that it's not safe for me to do anything much 
on the computer.
I normally use this machine ~14 hours per day.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux 6.5.0-15-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 19:40:13 2024
DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
 virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b]
InstallationDate: Installed on 2022-09-02 (510 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago)
dmi.bios.date: 10/30/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N3PET20W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21F6CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4:
dmi.product.family: ThinkPad T14s Gen 4
dmi.product.name: 21F6CTO1WW
dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4
dmi.product.version: ThinkPad T14s Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze mantic ubuntu

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

Title:
  T14s Gen4 Intel under 23.10 started locking up hard

Status in xorg package in Ubuntu:
  New

Bug description:
  Everything's been great for a couple of months on this new machine

  Yesterday or the day before it started locking up hard, spontaneously, 
without high load.
  X11 freezes. Keyboard is unresponsive.  Sound still worked for a while once.

  I accept updates when they arrive. Recently it's been telling me to do
  firmware updates, too.

  It's happening frequently enough that it's not safe for me to do anything 
much on the computer.
  I normally use this machine ~14 hours per day.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
  Uname: Linux 6.5.0-15-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 19:40:13 2024
  DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed
   virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed
  

[Touch-packages] [Bug 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Gordon Lack]

This is a problem in Mantic too.

And if you never fix it it will be a problem in the next LTS release.
Just as it is a problem in the current LTS release.

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

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Won't Fix
Status in powermgmt-base source package in Lunar:
  Won't Fix

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 2051292] Re: blutooth

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  blutooth

Status in bluez package in Ubuntu:
  New

Bug description:
  when I connect to my headset it's work couple of seconds or  minutes
  then disconnect  alone

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 22:15:26 2024
  InstallationDate: Installed on 2023-06-27 (211 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Inspiron 3721
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 044D20
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.ec.firmware.release: 1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3721
  dmi.product.sku: Inspiron 3721
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 9C:2A:70:BE:D0:62  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5227 acl:60 sco:0 events:440 errors:0
TX bytes:36549 acl:67 sco:0 commands:391 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2051292/+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 2051292] [NEW] blutooth

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when I connect to my headset it's work couple of seconds or  minutes
then disconnect  alone

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 25 22:15:26 2024
InstallationDate: Installed on 2023-06-27 (211 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: Dell Inc. Inspiron 3721
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 044D20
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 3721
dmi.product.sku: Inspiron 3721
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 9C:2A:70:BE:D0:62  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:5227 acl:60 sco:0 events:440 errors:0
TX bytes:36549 acl:67 sco:0 commands:391 errors:0

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


** Tags: amd64 apport-bug jammy wayland-session
-- 
blutooth
https://bugs.launchpad.net/bugs/2051292
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

-- 
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 2011628] Re: Apparmor Disallows Disabling Dhclient Scripts

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: isc-dhcp (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  Apparmor Disallows Disabling Dhclient Scripts

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  New
Status in isc-dhcp source package in Jammy:
  New
Status in isc-dhcp source package in Lunar:
  Won't Fix
Status in isc-dhcp package in Debian:
  New

Bug description:
  In some cases, it may be desirable to disable dhclient scripts. By
  default /sbin/dhclient-script is used, and some others are allowed by
  the apparmor profile.

  Without Apparmor, disabling hook scripts can be accomplished with
  flags -sf /bin/true, but with apparmor enabled this gets blocked:

  execve (/bin/true, ...): Permission denied

  Unfortunately dhclient doesn't appear to provide any other mechanism
  for disabling hook scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2011628/+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 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: focal (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in focal package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  Confirmed
Status in focal source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  Won't Fix
Status in focal source package in Kinetic:
  New
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in focal source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+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 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: e2fsprogs (Ubuntu Lunar)
   Status: Confirmed => Won't Fix

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in focal package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  Confirmed
Status in focal source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  Won't Fix
Status in focal source package in Kinetic:
  New
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in focal source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: mesa (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  Laptop screen blinked, no tty works and 200 dmesg errors per second

Status in Mesa:
  Fix Released
Status in linux-hwe-6.2 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-hwe-6.2 source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  New
Status in linux-hwe-6.2 source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  Won't Fix
Status in linux-hwe-6.2 source package in Mantic:
  Invalid
Status in mesa source package in Mantic:
  Fix Released

Bug description:
  I was using my laptop and suddenly the screen blinked. After that, all
  I could do was to move the mouse, no interaction worked. Trying to
  change to a TTY would open the black screen but the text cursor wasn't
  blinking and nothing happened.

  I accessed the laptop via SSH and used:

  screen env DISPLAY=:0 xfwm4 --vblank=xpresent --replace

  To reload xfwm4. After that, the graphical interface started working
  again. However, no TTY is accessible and there are 200 dmesg errors
  per second. These are the errors that repeat endlessly:

  [43959.444682] amdgpu :06:00.0: amdgpu: couldn't schedule ib on ring 

  [43959.444688] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs 
(-22)

  And while I was writing this report, another problem happened:

  [44566.016330] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 
timeout, signaled seq=2, emitted seq=6
  [44566.016553] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process obs pid 38687 thread obs:cs0 pid 38694
  [44566.016748] amdgpu :06:00.0: amdgpu: GPU reset begin!
  [44566.317039] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.525640] [drm] Register(0) [mmUVD_RB_RPTR] failed to reach value 
0x0100 != 0x
  [44566.728577] [drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 
0x0001 != 0x0002
  [44566.731204] [ cut here ]
  [44566.731205] WARNING: CPU: 15 PID: 29333 at 
drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:600 amdgpu_irq_put+0xa4/0xc0 [amdgpu]
  [44566.731429] Modules linked in: tls wireguard curve25519_x86_64 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libcurve25519_generic 
libchacha ip6_udp_tunnel udp_tunnel nvme_fabrics veth bridge stp llc zfs(PO) 
zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) 
rfcomm snd_seq_dummy snd_hrtimer vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock cmac algif_hash algif_skcipher af_alg bnep zram 
binfmt_misc nls_iso8859_1 nft_masq snd_sof_amd_rembrandt snd_sof_amd_renoir 
snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci 
ledtrig_audio snd_sof_xtensa_dsp snd_hda_codec_hdmi snd_sof snd_hda_intel 
snd_sof_utils snd_intel_dspcfg snd_soc_core snd_intel_sdw_acpi snd_compress 
nft_limit snd_hda_codec intel_rapl_msr ac97_bus intel_rapl_common snd_hda_core 
snd_pcm_dmaengine snd_hwdep edac_mce_amd snd_pci_ps btusb snd_seq_midi btrtl 
snd_rpl_pci_acp6x kvm_amd snd_seq_midi_event btbcm snd_acp_pci btintel btmtk 
snd_rawmidi uvcvideo
  [44566.731465]  snd_pci_acp6x nf_log_syslog rtw89_8852ae kvm 
videobuf2_vmalloc bluetooth snd_pcm videobuf2_memops snd_seq rtw89_8852a 
irqbypass snd_pci_acp5x videobuf2_v4l2 ecdh_generic snd_seq_device 
snd_rn_pci_acp3x joydev nft_log input_leds rapl videobuf2_common serio_raw 
snd_timer wmi_bmof hid_multitouch ecc snd_acp_config rtw89_pci snd_soc_acpi snd 
k10temp rtw89_core snd_pci_acp3x soundcore ideapad_laptop ccp sparse_keymap 
platform_profile mac_hid nft_ct nvidia_uvm(PO) nft_chain_nat nf_nat 
sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 cuse msr parport_pc 
nf_tables ppdev lp nfnetlink parport ramoops pstore_blk reed_solomon 
pstore_zone efi_pstore autofs4 btrfs blake2b_generic dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear overlay v4l2loopback(O) videodev mc 
virt_wifi virtio_net net_failover failover virtio_gpu virtio_dma_buf 
drm_shmem_helper z3fold rndis_host cdc_ether usbnet bfq at
 h10k_pci
  [44566.731504]  ath10k_core ath mac80211 libarc4 cfg80211 usb_storage nbd mii 
nvidia_drm(PO) nvidia_modeset(PO) usbhid nvidia(PO) amdgpu iommu_v2 drm_buddy 
gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core 
drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul polyval_clmulni 
sysfillrect polyval_generic hid_generic nvme sysimgblt ghash_clmulni_intel drm 
sha512_ssse3 aesni_intel i2c_hid_acpi crypto_simd xhci_pci nvme_core cryptd 
r8169 

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apport (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released
Status in apport source package in Lunar:
  Won't Fix
Status in cloud-init source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a name that no longer has 

[Touch-packages] [Bug 1971425] Re: The "look" cli dictionary only sees capitalized words

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: util-linux (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Triaged
Status in util-linux source package in Jammy:
  Triaged
Status in util-linux source package in Lunar:
  Won't Fix
Status in util-linux package in Debian:
  Confirmed

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: powermgmt-base (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  Triaged
Status in powermgmt-base source package in Kinetic:
  Won't Fix
Status in powermgmt-base source package in Lunar:
  Won't Fix

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1997912] Re: /usr/share/apport/whoopsie-upload-all:binascii.Error:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load:_decompress_line:b64decode

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apport (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:binascii.Error:/usr/share/apport/whoopsie-upload-
  all@249:main:collect_info:process_report:load:_decompress_line:b64decode

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Won't Fix
Status in apport source package in Lunar:
  Won't Fix

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing.

  Test Plan
  =

  1. Create malformed report:
  ```
  printf "CoreDump: base64\n H4sICAAC/0NvcmVEdW1wAA==\n 7Z0LYFPV/cdP0rQ\n" 
> malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  ```
  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 249, in 
  main()
    File "/usr/share/apport/whoopsie-upload-all", line 231, in main
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report
  r.load(f, binary="compressed")
    File "/usr/lib/python3/dist-packages/problem_report.py", line 139, in load
  bd, value = self._decompress_line(line, bd, value)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 276, in 
_decompress_line
  block = base64.b64decode(line)
    File "/usr/lib/python3.10/base64.py", line 87, in b64decode
  return binascii.a2b_base64(s)
  binascii.Error: Incorrect padding
  ```

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1997912/+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 2015380] Re: slapd crash when using pwdMinDelay of ppolicy

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openldap (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  slapd crash when using pwdMinDelay of ppolicy

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Jammy:
  Fix Released
Status in openldap source package in Kinetic:
  Won't Fix
Status in openldap source package in Lunar:
  Won't Fix
Status in openldap source package in Mantic:
  Fix Released

Bug description:
  Bug reported upstream[1], and confirmed in the mailing list[2].

  PR at [3].

  From the mailing list post[2], we can see that slapd crashes:
  """
  But if I test with a wrong password ( yyy) I got:
  root@zeus:/usr/lib/python3/dist-packages# ldapsearch -xLLLZZD
  uid=pauloric,ou=users,dc=contatogs,dc=com,dc=br -w yyy |wc -l
  ldap_result: Can't contact LDAP server (-1)
  0

  my openldap stop working.Active: inactive (dead)

  root@zeus:/usr/lib/python3/dist-packages# systemctl status -l slapd
  ○ slapd.service - LSB: OpenLDAP standalone server (Lightweight Director>
   Loaded: loaded (/etc/init.d/slapd; generated)
  Drop-In: /usr/lib/systemd/system/slapd.service.d
   └─slapd-remain-after-exit.conf
   Active: inactive (dead) since Tue 2023-04-04 14:44:49 -03; 20s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 986673 ExecStart=/etc/init.d/slapd start (code=exited, sta>
  Process: 986688 ExecStop=/etc/init.d/slapd stop (code=exited, statu>
  CPU: 47ms
  """


  1. https://bugs.openldap.org/show_bug.cgi?id=10028
  2. 
https://lists.openldap.org/hyperkitty/list/openldap-techni...@openldap.org/thread/3LYIPMT6TYJM4C7NUFXVYJS7YMODB5ZH/
  3. https://git.openldap.org/openldap/openldap/-/merge_requests/609

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2015380/+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 2018293] Re: [UBUNTU 20.04] Crash in zlib deflateBound() function on s390x

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: zlib (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  [UBUNTU 20.04] Crash in zlib deflateBound() function on s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in zlib package in Ubuntu:
  Fix Released
Status in zlib source package in Focal:
  New
Status in zlib source package in Jammy:
  New
Status in zlib source package in Lunar:
  Won't Fix
Status in zlib source package in Mantic:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [ Impact ]

   * The zlib deflateBound() function can crash on s390x,
     if called before deflateInit().

   * The solution is that zlib on s390x needs to support
     calling deflateBound() always before deflateInit().

  [ Test Plan ]

   * It's suggested to do a more overall or e2e test
 and run the zlib-ng test suite against the system zlib
 as follows:
 $ git clone https://github.com/zlib-ng/zlib-ng.git
 $ cd zlib-ng
 $ cmake -DZLIB_COMPAT=ON -DZLIBNG_ENABLE_TESTS=OFF -DBUILD_SHARED_LIBS=ON 
-DWITH_DFLTCC_DEFLATE=ON -DWITH_DFLTCC_INFLATE=ON .
 $ make gtest_zlib
 $ ldd gtest_zlib
   libz.so.1 => /lib/s390x-linux-gnu/libz.so.1 (0x03fff7e0)
 $ ./gtest_zlib

  [ Where problems could occur ]

   * The only (single line) modification is in the if condition
     of the define DEFLATE_BOUND_ADJUST_COMPLEN statement in
     deflate.c.

   * Things can go wrong if the condition (or logic) is wrong,

   * or if other parts of the code are coded against the old behavior
     and are still expecting it.

   * The likely outcome would be still a crash
     or an unexpected behavior.

  [ Other Info ]

   * Getting this into mantic first,
     before the SRU down to focal is done.
  __

  Problem Description:
  zlib deflateBound() function can crash on s390x when called before 
deflateInit().

  Solution:
  zlib on s390x needs to support calling deflateBound() before deflateInit().

  The fix is squashed into the latest DFLTCC PR:
  https://github.com/madler/zlib/pull/410

  Diff:
  
https://github.com/madler/zlib/compare/113203437eda67261848b14b6c80a33ff7e33d34..f6d382a91a4e7d88b9b12ce0ecdffb1783878160

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2018293/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Lunar:
  Won't Fix

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

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

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openssh (Ubuntu Lunar)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Won't Fix
Status in openssh source package in Lunar:
  Won't Fix

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 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) from gtk_css_value_icon_theme_compute() from gtk_css_static_style_compute_value()

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0) from
  gtk_css_value_icon_theme_compute() from
  gtk_css_static_style_compute_value()

Status in apport package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in apport source package in Focal:
  Invalid
Status in gtk+3.0 source package in Focal:
  Triaged
Status in apport source package in Lunar:
  Invalid
Status in gtk+3.0 source package in Lunar:
  Won't Fix

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Stack trace
  ---

  Python:

  ```
File "apport-gtk", line 703, in 
  app = GTKUserInterface(sys.argv)
File "apport-gtk", line 68, in GTKUserInterface.__init__
  self.widgets.add_from_file(
  os.path.join(os.path.dirname(argv[0]), "apport-gtk.ui")
  )
  ```

  StacktraceTop:
   _gtk_settings_get_screen (settings=0x0) at ../../../../gtk/gtksettings.c:3319
   gtk_css_value_icon_theme_compute (icon_theme=, 
property_id=, provider=, style=, 
parent_style=) at ../../../../gtk/gtkcssiconthemevalue.c:84
   gtk_css_static_style_compute_value (style=0x1e7c320, provider=0x0, 
parent_style=0x0, id=3, specified=0x7f53258b9b20 , section=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:237
   _gtk_css_lookup_resolve (lookup=lookup@entry=0x1e7e790, 
provider=provider@entry=0x0, style=style@entry=0x1e7c320, 
parent_style=parent_style@entry=0x0) at ../../../../gtk/gtkcsslookup.c:122
   gtk_css_static_style_new_compute (provider=provider@entry=0x0, 
matcher=matcher@entry=0x0, parent=parent@entry=0x0) at 
../../../../gtk/gtkcssstaticstyle.c:195

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+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 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Lunar)
   Status: New => Won't Fix

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Kinetic:
  Won't Fix
Status in systemd source package in Lunar:
  Won't Fix

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1992979/+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 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: e2fsprogs (Ubuntu Lunar)
   Status: In Progress => Won't Fix

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Bug Watch Updater]

** Bug watch added: 
github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues #2
   https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues/2

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

[shalokshalom]

I use a Lenovo Slim 7 Carbon with a ALC287 as well.

We have an issue page open for this device/issue as well, and I think we
nailed it down to the pin configurations.

https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-
AMD/issues/2#issuecomment-1615152518

I welcome your thoughts on this. 
hdajackretask seems to be the software for this solution.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2037604] Please test proposed package

[Andreas Hasenack]

Hello Timo, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037604

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Andreas Hasenack]

Hello Lee, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 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 (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Andreas Hasenack]

Please amend the test case to test with both the GA and the (affected)
6.1 OEM kernels.

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  OEM-6.1 kernel is missing support for minimum page size of 64k on DG2
  (gfx12.5). Mesa 23.2 started using that, so it broke initializing the
  gpu on boot, causing a blank screen with no GDM running (with wayland,
  and fallback to X failed too).

  [Fix]

  Revert the commit that allows using 64k page size, since that's what
  the current version in jammy-updates is using. OEM-6.1 kernel is going
  away, no need to patch that anymore. No other kernel is affected, >6.2
  works fine and thus this revert is not necessary in mantic or noble.

  [Test case]

  Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't
  matter). The login screen should appear.

  [Where things could go wrong]
  Hard to see how this could regress anything, as it just restores the limits 
for intel gfx12.5 as they were in the current mesa version in jammy.

  ---

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+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 2048914] Re: System program problem detected at every login Xubuntu Update Notifier

[spicemines]

After installing the Noble Daily ISO (Version 20240125), I did not
receive this error message. I'll keep testing, but hopefully, this is on
its way to being fixed.

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

Title:
  System program problem detected at every login Xubuntu Update Notifier

Status in update-notifier package in Ubuntu:
  New
Status in whoopsie package in Ubuntu:
  Incomplete

Bug description:
  Every time I log in to my new installation of Xubuntu 24.04 (daily
  ISO) after a reboot, I get an error message that says, "System program
  problem detected." Clicking either Cancel or Report Problem only
  dismisses the pop-up without any further action. This has occurred on
  multiple computers. This began with the first boot after installation
  and occurs at each subsequent reboot upon logging in. Logging out and
  back in does not cause the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: update-notifier 3.192.66
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Wed Jan 10 09:57:25 2024
  ExecutablePath: /usr/bin/update-notifier
  InstallationDate: Installed on 2024-01-10 (0 days ago)
  InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110)
  ProcEnviron:
   LANG=C.UTF-8
   LANGUAGE=en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: update-notifier
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

** Changed in: glibc (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: pango1.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Invalid

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2045455] Re: add-apt-repository crashed with --- in _request()

[Julian Andres Klode]

Nevermind, a non-existent or private PPA has been tried to add and
software-properties should properly surface the error to you.

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Triaged

** Tags removed: rls-nn-incoming
** Tags added: foundations-todo

** Also affects: software-properties (Ubuntu Noble)
   Importance: Medium
   Status: Triaged

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Noble:
  Triaged

Bug description:
  Error encountered during first boot after installing ubuntu-unity-
  desktop on Live Server 24.04 Daily Build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 30 02:20:48 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-30 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+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 2045455] Re: add-apt-repository crashed with --- in _request()

[Julian Andres Klode]

Presumably the add-apt-repository command failed while trying to add a
private PPA here due to you not being authorized to access it (maybe not
logged in?), can you tell us which PPA did you try to add?

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  Triaged
Status in software-properties source package in Noble:
  Triaged

Bug description:
  Error encountered during first boot after installing ubuntu-unity-
  desktop on Live Server 24.04 Daily Build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 30 02:20:48 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-30 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Aleksandr Mikhalitsyn]

Huge thanks, Dave!

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2049881] Re: pango1.0: FTBFS against glibc 2.39 snapshot

[Simon Chopin]

So, after some fairly exhausting debugging, I kind of gave up on that
bug, but as a last ditch effort I tried a rebuild against the latest
snapshot (even though the changelog didn't seem particularly relevant),
nd... Now it builds.

I'm so tired.

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

Title:
  pango1.0: FTBFS against glibc 2.39 snapshot

Status in glibc package in Ubuntu:
  Triaged
Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Hi,

  The package pango1.0 failed to build during the recent full archive
  test rebuild against a snapshot of the the development branch for the
  upcoming glibc 2.39, expected to land in Noble. This was subsequently
  confirmed locally against a more recent snapshot.

  Full logs for the FTBFS: 
https://launchpadlibrarian.net/706837188/buildlog_ubuntu-noble-amd64.pango1.0_1.51.0+ds-3_BUILDING.txt.gz
  Full report: 
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html
  PPA with glibc snapshot: 
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc

  Snippet showing the failure:

  === 22/27 
  test: test-fonts
  start time:   10:25:39
  duration: 0.11s
  result:   exit status 1
  command:  G_TEST_SRCDIR=/<>/tests 
srcdir=/<>/tests LC_ALL=en_US.UTF-8 
ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 
LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/pango 
G_TEST_BUILDDIR=/<>/obj-x86_64-linux-gnu/tests 
UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1
 MALLOC_PERTURB_=142 /<>/obj-x86_64-linux-gnu/tests/test-fonts -k 
--tap
  --- stdout ---
  TAP version 13
  # random seed: R02Sd064b2e790c11a865b61afd5b0b7909d
  1..4
  # Start of fontsets tests
  ok 1 /fontsets/cantarell2
  # Contents don't match expected contents
  # --- /tmp/.OQTQH22024-01-19 11:25:39.214546169 +0100
  # +++ /tmp/.OSTQH22024-01-19 11:25:39.214546169 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 2 /fontsets/mono2
  ok 3 /fontsets/cantarell
  # Contents don't match expected contents
  # --- /tmp/.X3URH22024-01-19 11:25:39.234546069 +0100
  # +++ /tmp/.FJURH22024-01-19 11:25:39.234546069 +0100
  # @@ -4,7 +4,7 @@
  #  DejaVu Sans 20
  #  Noto Sans CJK JP 20
  #  Droid Sans Japanese 20
  # -Cantarell 20
  # +Cantarell 20 @wght=400
  #  Amiri 20
  #  DejaVu Sans Bold 20
  #  Font Awesome 5 Free Solid Heavy 20
  #
  not ok 4 /fontsets/mono
  # End of fontsets tests
  --- stderr ---

  (test program exited with status code 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2049881/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

[Julian Andres Klode]

Unsubscribing ubuntu sponsors as already subscribed to the merge

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

  Note: gettext 0.22.4 refactors Java support. This delta can be safely
  dropped after a new upstream release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

[Dave Jones]

Tested on mantic install, and as Robie suggested, performed binary
debdiff against old versions to ensure only change was the version
number. Marking verification done.

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

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

  [Test case]
  No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.

  [Where problems may occur]
  It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 1768088] Re: can't activate 2 independent reachable interface

[Lukas Märdian]

Please reopen if this is still an issue

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

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

Title:
  can't activate 2 independent reachable interface

Status in netplan.io package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ubuntu: 18.04
  systemd:   
  Installed: 237-3ubuntu10
  Candidate: 237-3ubuntu10
  netplan.io:
Installed: 0.36.1
Candidate: 0.36.1

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    addresses: [192.168.3.30/25]
    dhcp4: no
    routes:
     - to: 0.0.0.0/0
   via: 192.168.3.1
   metric: 100
   table: 101

    routing-policy:
     - from: 192.168.3.0/25
   table: 101

  ens7:
    addresses: [192.168.5.24/25]
    dhcp4: no
    gateway4: 192.168.5.1
    nameservers:
  addresses: [1.1.1.1]

  this doesn't activate a proper rule for table 101:
  0:  from all lookup local
  32766:  from all lookup main
  32767:  from all lookup default

  in place of
  0:  from all lookup local
  32765:  from 192.168.3.0/25 lookup 101
  32766:  from all lookup main
  32767:  from all lookup default

  the file in /etc/systemd/network contains the correct information:
  [Match]
  Name=ens3

  [Network]
  Address=192.168.3.30/25

  [Route]
  Destination=0.0.0.0/0
  Gateway=192.168.3.1
  Metric=100
  Table=101

  [RoutingPolicyRule]
  From=192.168.3.0/25
  Table=101

  the ens3 is reachable from 3.0 but not from anywhere else

  with ifupdown on another system both interfaces would be reachable from 
everywhere on the private subnets.
  up ip route add default table 101 dev enp8s0 via 192.168.3.1
  up ip rule add from 192.168.3.0/25 lookup 101
  down ip rule del from 192.168.3.0/25
  down ip route del default table 101 via 192.168.3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768088/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

[Frank Heimes]

Since this bug is fixed with openssl 3.0.8 and newer,
I'm changing the status of the current devel. release to Fix Released too 
(since we are there on 3.0.10).
And with that the affected project status can be set to Fix Released, too.

Thx!

** Changed in: openssl (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Released

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700 

[Touch-packages] [Bug 2023545] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2024-01-25 07:28 EDT---
Thanks everyone for your work.
With the fix being released to -updates, I will close this bug as soon as the 
status in Launchpad changes to "fix released"

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   

[Touch-packages] [Bug 1994165] Update Released

[Łukasz Zemczak]

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

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.2-0ubuntu1.13

---
openssl (3.0.2-0ubuntu1.13) jammy; urgency=medium

  * Fix (upstream): crash when using an engine for ciphers used by DRBG
(LP: #2023545)
- lp2023545/0001-Release-the-drbg-in-the-global-default-context-befor.patch
  * Fix (upstream): do not ignore return values for S/MIME signature
(LP: #1994165)
- lp1994165/0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch
  * Perf (upstream): don't empty method stores and provider synchronization
records when flushing the query cache (LP: #2033422)
- lp2033422/0001-Drop-ossl_provider_clear_all_operation_bits-and-all-.patch
- lp2033422/0002-Refactor-method-construction-pre-and-post-condition.patch
- lp2033422/0003-Don-t-empty-the-method-store-when-flushing-the-query.patch
- lp2033422/0004-Make-it-possible-to-remove-methods-by-the-provider-t.patch
- lp2033422/0005-Complete-the-cleanup-of-an-algorithm-in-OSSL_METHOD_.patch
- lp2033422/0006-For-child-libctx-provider-don-t-count-self-reference.patch
- lp2033422/0007-Add-method-store-cache-flush-and-method-removal-to-n.patch

 -- Adrien Nader   Tue, 09 Jan 2024 11:42:50
+0100

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

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.2-0ubuntu1.13

---
openssl (3.0.2-0ubuntu1.13) jammy; urgency=medium

  * Fix (upstream): crash when using an engine for ciphers used by DRBG
(LP: #2023545)
- lp2023545/0001-Release-the-drbg-in-the-global-default-context-befor.patch
  * Fix (upstream): do not ignore return values for S/MIME signature
(LP: #1994165)
- lp1994165/0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch
  * Perf (upstream): don't empty method stores and provider synchronization
records when flushing the query cache (LP: #2033422)
- lp2033422/0001-Drop-ossl_provider_clear_all_operation_bits-and-all-.patch
- lp2033422/0002-Refactor-method-construction-pre-and-post-condition.patch
- lp2033422/0003-Don-t-empty-the-method-store-when-flushing-the-query.patch
- lp2033422/0004-Make-it-possible-to-remove-methods-by-the-provider-t.patch
- lp2033422/0005-Complete-the-cleanup-of-an-algorithm-in-OSSL_METHOD_.patch
- lp2033422/0006-For-child-libctx-provider-don-t-count-self-reference.patch
- lp2033422/0007-Add-method-store-cache-flush-and-method-removal-to-n.patch

 -- Adrien Nader   Tue, 09 Jan 2024 11:42:50
+0100

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

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

Title:
  openssl: backport to jammy "clear method store / query cache
  confusion"

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [ATTENTION]
  This SRU contains THREE changes which are listed in the section below.

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  This ( #2033422 ) is the "central" bug with the global information and 
debdiff.

  This SRU addresses three issues with Jammy's openssl version:
  - http://pad.lv/1994165: ignored SMIME signature errors
  - http://pad.lv/2023545: imbca engine dumps core
  - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections 
(this one)

  The SRU information has been added to the three bug reports and I am
  attaching the debdiff here only for all three.

  All the patches have been included in subsequent openssl 3.0.x
  releases which in turn have been included in subsequent Ubuntu
  releases. There has been no report of issues when updating to these
  Ubuntu releases.

  I have rebuilt the openssl versions and used abi-compliance-checker to
  compare the ABIs of the libraries in jammy and the one for the SRU.
  Both matched completely (FYI, mantic's matched completely too).

  I have also pushed the code to git (without any attempt to make it
  git-ubuntu friendly).

  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
  sru

  I asked Brian Murray about phasing speed and he concurs a slow roll-out is 
probably better for openssl. There is a small uncertainty because a security 
update could come before the phasing is over, effectively fast-forwarding the 
SRU. Still, unless there is already a current pre-advisory, this is probably 
better than a 10% phasing which is over after only a couple days anyway.
  NB: at the moment openssl doesn't phase slowly so this needs to be 
implemented.

  [Impact]
  Severely degraded performance for concurrent operations compared to openssl 
1.1. The performance is so degraded that some workloads fail due to timeouts or 
insufficient resources (noone magically has 5 times more machines). As a 
consequence, a number of people use openssl 1.1 instead and do not get security 
updates.

  [Test plan]
  Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
 .

  To test, follow these steps:
  - run "time python3 main.py" # using the aforementioned main.py script
  - apt install -t jammy-proposed libssl3
  - run "time python3 main.py"
  - compare the runtimes for the two main.py runs

  You can run this on x86_64, Raspberry Pi 4 or any machine, and get a
  very large speed-up in all cases. The improvements are not
  architecture-dependant.

  Using this changeset, I get the following numbers for ten runs on my
  laptop:

  3.0.2:
  real  2m5.567s
  user  4m3.948s
  sys   2m0.233s

  this SRU:
  real  0m23.966s
  user  2m35.687s
  sys   0m1.920s

  As can be easily seen, the speed-up is massive: system time is divided
  by 60 and overall wall clock time is roughly five times lower.

  In http://pad.lv/2009544 , Rafael also shared his performance numbers
  and they are relatable to these. He used slightly different versions
  (upstreams rather than patched with cherry-picks) but at least one of
  the 

[Touch-packages] [Bug 2023545] Update Released

[Łukasz Zemczak]

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

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
     

[Touch-packages] [Bug 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

[Launchpad Bug Tracker]

This bug was fixed in the package openssl - 3.0.2-0ubuntu1.13

---
openssl (3.0.2-0ubuntu1.13) jammy; urgency=medium

  * Fix (upstream): crash when using an engine for ciphers used by DRBG
(LP: #2023545)
- lp2023545/0001-Release-the-drbg-in-the-global-default-context-befor.patch
  * Fix (upstream): do not ignore return values for S/MIME signature
(LP: #1994165)
- lp1994165/0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch
  * Perf (upstream): don't empty method stores and provider synchronization
records when flushing the query cache (LP: #2033422)
- lp2033422/0001-Drop-ossl_provider_clear_all_operation_bits-and-all-.patch
- lp2033422/0002-Refactor-method-construction-pre-and-post-condition.patch
- lp2033422/0003-Don-t-empty-the-method-store-when-flushing-the-query.patch
- lp2033422/0004-Make-it-possible-to-remove-methods-by-the-provider-t.patch
- lp2033422/0005-Complete-the-cleanup-of-an-algorithm-in-OSSL_METHOD_.patch
- lp2033422/0006-For-child-libctx-provider-don-t-count-self-reference.patch
- lp2033422/0007-Add-method-store-cache-flush-and-method-removal-to-n.patch

 -- Adrien Nader   Tue, 09 Jan 2024 11:42:50
+0100

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

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  

[Touch-packages] [Bug 2033422] Update Released

[Łukasz Zemczak]

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

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

Title:
  openssl: backport to jammy "clear method store / query cache
  confusion"

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [ATTENTION]
  This SRU contains THREE changes which are listed in the section below.

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  This ( #2033422 ) is the "central" bug with the global information and 
debdiff.

  This SRU addresses three issues with Jammy's openssl version:
  - http://pad.lv/1994165: ignored SMIME signature errors
  - http://pad.lv/2023545: imbca engine dumps core
  - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections 
(this one)

  The SRU information has been added to the three bug reports and I am
  attaching the debdiff here only for all three.

  All the patches have been included in subsequent openssl 3.0.x
  releases which in turn have been included in subsequent Ubuntu
  releases. There has been no report of issues when updating to these
  Ubuntu releases.

  I have rebuilt the openssl versions and used abi-compliance-checker to
  compare the ABIs of the libraries in jammy and the one for the SRU.
  Both matched completely (FYI, mantic's matched completely too).

  I have also pushed the code to git (without any attempt to make it
  git-ubuntu friendly).

  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
  sru

  I asked Brian Murray about phasing speed and he concurs a slow roll-out is 
probably better for openssl. There is a small uncertainty because a security 
update could come before the phasing is over, effectively fast-forwarding the 
SRU. Still, unless there is already a current pre-advisory, this is probably 
better than a 10% phasing which is over after only a couple days anyway.
  NB: at the moment openssl doesn't phase slowly so this needs to be 
implemented.

  [Impact]
  Severely degraded performance for concurrent operations compared to openssl 
1.1. The performance is so degraded that some workloads fail due to timeouts or 
insufficient resources (noone magically has 5 times more machines). As a 
consequence, a number of people use openssl 1.1 instead and do not get security 
updates.

  [Test plan]
  Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
 .

  To test, follow these steps:
  - run "time python3 main.py" # using the aforementioned main.py script
  - apt install -t jammy-proposed libssl3
  - run "time python3 main.py"
  - compare the runtimes for the two main.py runs

  You can run this on x86_64, Raspberry Pi 4 or any machine, and get a
  very large speed-up in all cases. The improvements are not
  architecture-dependant.

  Using this changeset, I get the following numbers for ten runs on my
  laptop:

  3.0.2:
  real  2m5.567s
  user  4m3.948s
  sys   2m0.233s

  this SRU:
  real  0m23.966s
  user  2m35.687s
  sys   0m1.920s

  As can be easily seen, the speed-up is massive: system time is divided
  by 60 and overall wall clock time is roughly five times lower.

  In http://pad.lv/2009544 , Rafael also shared his performance numbers
  and they are relatable to these. He used slightly different versions
  (upstreams rather than patched with cherry-picks) but at least one of
  the version used does not include other performance change. He also
  used different hardware and this performance issue seems to depend on
  the number of CPUs available but also obtained a performance several
  times better. Results on a given machine vary also very little across
  runs (less than 2% variation on runs of size 10). They are also very
  similar on a Raspberry Pi 4 (8GB).

  The benchmark uses https://www.google.com/humans.txt which takes
  around 130ms to download on my machine but I modified the script to
  download something only 20ms away. Results are so close to the ones
  using humans.txt that they are within the error margin. This is
  consistent with the high-concurrency in the benchmark which both
  saturates CPU, and "hides" latencies that are relatively low.

  Finally, there are positive reports on 

[Touch-packages] [Bug 2051234] [NEW] old version of e2fsck causes issues on boot

[Matthew]

Public bug reported:

As of writing, the current provided version of e2fsck (provided by
e2fsprogs) is 1.46.5 (2021-12-30). The latest version of e2fsck is
1.47.0 (2023-02-05), which I believe contains a few updates to supported
features.

My older version of fsck failed to run successfully during systemd init
after trying to check a partition in my fstab, which caused the whole
boot process to fail and it dropping me in a root terminal. Upon
manually running `fsck -f /dev/sdxy`, an unsupported FS feature error
was thrown. Upon downloading and `make install`ing the latest release's
source, I was able to successfully run fsck and further boots completed
successfully.

OS: 22.04.3 LTS (jammy)

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

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

Title:
  old version of e2fsck causes issues on boot

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  As of writing, the current provided version of e2fsck (provided by
  e2fsprogs) is 1.46.5 (2021-12-30). The latest version of e2fsck is
  1.47.0 (2023-02-05), which I believe contains a few updates to
  supported features.

  My older version of fsck failed to run successfully during systemd
  init after trying to check a partition in my fstab, which caused the
  whole boot process to fail and it dropping me in a root terminal. Upon
  manually running `fsck -f /dev/sdxy`, an unsupported FS feature error
  was thrown. Upon downloading and `make install`ing the latest
  release's source, I was able to successfully run fsck and further
  boots completed successfully.

  OS: 22.04.3 LTS (jammy)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2051234/+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 2039868] Re: amdgpu reset during usage of firefox

[Timo Aaltonen]

no, -17 does

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2036333]

[dabiswas112]

(In reply to jeff from comment #9)
> (In reply to dabiswas112 from comment #6)
> > Hi, I've fixed this on my copr at hazel-bunny/ports. I have also ported the
> > signon-ui spec from webkit to webengine, because qt5-qtwebkit is a big
> > security hole according to a GNOME guy.
> > 
> > @rdieter could you check if the updates in
> > https://github.com/hazel-bunny/rpm-packaging/tree/master/lib/signon are
> > acceptable?
> 
> Thoughts on becoming maintainer or co-maintainer of this package
> @dabiswas112?

Not opposed to it, but need time. This package needs changes for Qt6 and
Plasma 6, where upstream KDE recommends using Nicolas Fella's fork. My
package uses git master of the original repo and is currently broken on
rawhide. Will look into the requirements for being a maintainer and
negotiations with KDE SIG who currently maintain the stack to take over
maintenance in the future.

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

Title:
  signon-ui no longer works for Google authentication

Status in kio-gdrive package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed
Status in signon-ui package in Fedora:
  Confirmed

Bug description:
  The version of signon-ui from Launchpad no longer works for adding
  Google services in Kubuntu. The login hangs indefinitely after
  entering an email address.

  Apparently, a slightly newer version from its current home on git
  reportedly works, and is what others have been using:

  https://gitlab.com/accounts-sso/signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

[Adrien Nader]

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

** Tags removed: foundations-triage-discuss

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

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