[Touch-packages] [Bug 2063200] [NEW] useradd --extrausers --groups tries to lock /etc/group

[Valentin David]

Public bug reported:

On Ubuntu Core 24 calling the command line

useradd --extrausers --groups somegroup somenewuser

... fails with:

useradd: cannot lock /etc/group; try again later.

It worked on 22.04. /etc is not writable. It also fails if somegroup is
a group in extrausers.

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

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

Title:
  useradd --extrausers --groups tries to lock /etc/group

Status in shadow package in Ubuntu:
  New

Bug description:
  On Ubuntu Core 24 calling the command line

  useradd --extrausers --groups somegroup somenewuser

  ... fails with:

  useradd: cannot lock /etc/group; try again later.

  It worked on 22.04. /etc is not writable. It also fails if somegroup
  is a group in extrausers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+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 2063003] Re: package manager could not make changes to the installed system

[David Kalnischkies]

As the requirement for reproducing is "being offline" it could be that
this remove command wants to download packages, which fails.

Yes, remove can install packages – specifically the problem resolver can
try to fix a broken dependency by installing another provider/or-group
member. Controlled by `pkgProblemResolver::FixByInstall` which is
enabled by default. Once in a while I wonder if that should have been
disabled for remove commands. Or if it was a mistake to resolve an
upgrade problem 14y ago with this. Hard to tell if it does more good
than bad as that highly depends on the situation.

The other "obvious" possibility is that a maintainer script is trying to
access the network. Perhaps its intended only on install, but not
correctly guarded for the removal case.

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

Title:
  package manager could not make changes to the installed system

Status in apt package in Ubuntu:
  New

Bug description:
  This is the cause of Ubuntu Unity failing to install. Test case
  requires system to be offline.

  The full error message is:
  The package manager could not make changes to the installed system. The 
command apt-get --purge -q -y remove ^live-* 
calamares-settings-ubuntu-unity calamares zram-config cifs-utils returned 
error code 100.

  There are no logs in /var/log/installer or /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063003/+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 2061834] Re: apt build-dep . fails to parse build dependencies

[David Kalnischkies]

https://salsa.debian.org/apt-
team/apt/-/commit/633f6d67a28b375cf1f225f14d3c926e618d46af

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

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => David Kalnischkies (donkult)

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

Title:
  apt build-dep . fails to parse build dependencies

Status in apt package in Ubuntu:
  Fix Committed

Bug description:
  seen in trantor 1.5.12+ds-1ubuntu3:

  Build-Depends: cmake, debhelper-compat (=13), dh-cmake, dh-cmake-
  compat (=1)

  replacing (=1) with (= 1) lets the parsing succeed.

  $ sudo apt build-dep .
  Note, using directory '.' to get the build dependencies
  Reading package lists... Done
  E: Problem parsing dependency: Build-Depends
  E: Unable to get build-dependency information for .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2061834/+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 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately

[David Kalnischkies]

Not sure who all the upstream(s) involved might be, but from my personal
PoV at least you can add all the options you like… the topic gets harder
if we talk defaults & changing (e.g.) the lists completely (like that
tabular verbose-explosion thingy from apk or whatever it was). At some
point it might make sense to extended apt-patterns so that current (and
future) lists can be expressed in them and then add some more options to
format those lists/tables/… at which point we could have different
templates and so options/choices galore. I think aptitude has formatting
to some extend of its lists. One of my first apt patches that was never
merged was actually about reordering/coloring the lists… that failed, so
I am very positive that a much bigger yak will be shaved more easily and
faster many years later. ;)

Precedence of the initial ask is 'can be autoremoved' btw, which is not
displayed, displays a full list, an even fuller list in version mode or
displays a single line with how many packages could be autoremoved
depending on config.

P.S.: On a multi-arch system nearly every Depends is a choice even
without or-groups: given that you e.g. pick banana:amd64 or banana:i386
for an M-A:foreign banana. And the t64 transition added a quadrillion of
real vs. virtual bananas at least until everyone depends on bananat64.

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

Title:
  When apt keeps back packages due to phased updates, it should list
  them separately

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 2057822] Re: Removing irqbalance disables power button on Raspberry Pi 5

[David Myers]

** Description changed:

  As discussed in Bug #1833322: "Please consider no more having irqbalance
  enabled by default (per image/use-case/TBD)"
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322) the
  irqbalance package will no longer be installed by default in Noble. So
- as a test I removed the package from my Raspberry Pi 5 running Mantic,
- after which the Pi 5's power button no longer worked to poweroff the
- system. Re-installing irqbalance caused the button to work again.
+ as a test I removed the package from my Raspberry Pi 5 running Mantic
+ Server, after which the Pi 5's power button no longer worked to poweroff
+ the system. Re-installing irqbalance caused the button to work again.
  
  With irqbalance installed I see these messages at boot time:
  
  kernel: input: pwr_button as /devices/platform/pwr_button/input/input1
  systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button)
  
  Without irqbalance I see this:
  
  kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0, error
  -6
  
  So the Raspberry Pi 5 might still need irqbalance installed, or perhaps
  there's a better solution for enabling the button.
  
  I have the following appended to the Mantic default
  /boot/firmware/config.txt:
  
  # Trickle charge the RTC battery (default: don't charge)
  dtparam=rtc_bbat_vchg=300
  # Enable the PCIe external connector
  dtparam=nvme
  # Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0)
  # dtparam=pciex1_gen=3
  # Enable second serial port on GPIO 14 & 15 (default: disabled)
  dtparam=uart0
  # Change activity LED behavior (default: blink for MMC access)
  dtparam=act_led_trigger=heartbeat
  # Disable Bluetooth (not wanted on a server)
  dtoverlay=disable-bt-pi5
  # Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT
  dtoverlay=pps-gpio,gpiopin=18,capture_clear

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

Title:
  Removing irqbalance disables power button on Raspberry Pi 5

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As discussed in Bug #1833322: "Please consider no more having
  irqbalance enabled by default (per image/use-case/TBD)"
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322)
  the irqbalance package will no longer be installed by default in
  Noble. So as a test I removed the package from my Raspberry Pi 5
  running Mantic Server, after which the Pi 5's power button no longer
  worked to poweroff the system. Re-installing irqbalance caused the
  button to work again.

  With irqbalance installed I see these messages at boot time:

  kernel: input: pwr_button as /devices/platform/pwr_button/input/input1
  systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button)

  Without irqbalance I see this:

  kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0,
  error -6

  So the Raspberry Pi 5 might still need irqbalance installed, or
  perhaps there's a better solution for enabling the button.

  I have the following appended to the Mantic default
  /boot/firmware/config.txt:

  # Trickle charge the RTC battery (default: don't charge)
  dtparam=rtc_bbat_vchg=300
  # Enable the PCIe external connector
  dtparam=nvme
  # Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0)
  # dtparam=pciex1_gen=3
  # Enable second serial port on GPIO 14 & 15 (default: disabled)
  dtparam=uart0
  # Change activity LED behavior (default: blink for MMC access)
  dtparam=act_led_trigger=heartbeat
  # Disable Bluetooth (not wanted on a server)
  dtoverlay=disable-bt-pi5
  # Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT
  dtoverlay=pps-gpio,gpiopin=18,capture_clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2057822/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

[David Myers]

I filed Bug #2057822: "Removing irqbalance disables power button on
Raspberry Pi 5" (https://bugs.launchpad.net/ubuntu/+source/ubuntu-
meta/+bug/2057822).

Thanks.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2057822] [NEW] Removing irqbalance disables power button on Raspberry Pi 5

[David Myers]

Public bug reported:

As discussed in Bug #1833322: "Please consider no more having irqbalance
enabled by default (per image/use-case/TBD)"
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322) the
irqbalance package will no longer be installed by default in Noble. So
as a test I removed the package from my Raspberry Pi 5 running Mantic,
after which the Pi 5's power button no longer worked to poweroff the
system. Re-installing irqbalance caused the button to work again.

With irqbalance installed I see these messages at boot time:

kernel: input: pwr_button as /devices/platform/pwr_button/input/input1
systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button)

Without irqbalance I see this:

kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0, error
-6

So the Raspberry Pi 5 might still need irqbalance installed, or perhaps
there's a better solution for enabling the button.

I have the following appended to the Mantic default
/boot/firmware/config.txt:

# Trickle charge the RTC battery (default: don't charge)
dtparam=rtc_bbat_vchg=300
# Enable the PCIe external connector
dtparam=nvme
# Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0)
# dtparam=pciex1_gen=3
# Enable second serial port on GPIO 14 & 15 (default: disabled)
dtparam=uart0
# Change activity LED behavior (default: blink for MMC access)
dtparam=act_led_trigger=heartbeat
# Disable Bluetooth (not wanted on a server)
dtoverlay=disable-bt-pi5
# Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT
dtoverlay=pps-gpio,gpiopin=18,capture_clear

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Removing irqbalance disables power button on Raspberry Pi 5

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As discussed in Bug #1833322: "Please consider no more having
  irqbalance enabled by default (per image/use-case/TBD)"
  (https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322)
  the irqbalance package will no longer be installed by default in
  Noble. So as a test I removed the package from my Raspberry Pi 5
  running Mantic, after which the Pi 5's power button no longer worked
  to poweroff the system. Re-installing irqbalance caused the button to
  work again.

  With irqbalance installed I see these messages at boot time:

  kernel: input: pwr_button as /devices/platform/pwr_button/input/input1
  systemd-logind[694]: Watching system buttons on /dev/input/event0 (pwr_button)

  Without irqbalance I see this:

  kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0,
  error -6

  So the Raspberry Pi 5 might still need irqbalance installed, or
  perhaps there's a better solution for enabling the button.

  I have the following appended to the Mantic default
  /boot/firmware/config.txt:

  # Trickle charge the RTC battery (default: don't charge)
  dtparam=rtc_bbat_vchg=300
  # Enable the PCIe external connector
  dtparam=nvme
  # Force PCIe Gen 3.0 (default: Gen 2.0; not certified for Gen 3.0)
  # dtparam=pciex1_gen=3
  # Enable second serial port on GPIO 14 & 15 (default: disabled)
  dtparam=uart0
  # Change activity LED behavior (default: blink for MMC access)
  dtparam=act_led_trigger=heartbeat
  # Disable Bluetooth (not wanted on a server)
  dtoverlay=disable-bt-pi5
  # Enable PPS on GPIO 18 for MAX-M8Q GNSS HAT
  dtoverlay=pps-gpio,gpiopin=18,capture_clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2057822/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

[David Myers]

Since I saw that irqbalance was not going to be installed by default in
Noble I removed it from my Raspberry Pi 5 running Mantic, and as a
result the power button stopped working. The error is:

kernel: gpio-keys pwr_button: Unable to get irq number for GPIO 0, error
-6

Reinstalling irqbalance made the power button work again.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

Trusty would require a significant backport, marking it as won't fix to
prevent possible regressions.

** Changed in: openssl (Ubuntu Trusty)
 Assignee: David Fernandez Gonzalez (litios) => (unassigned)

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  Won't Fix
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Mantic:
  Fix Released
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

Fixed released for Xenial ESM: 1.0.2g-1ubuntu4.20+esm12

https://ubuntu.com/security/notices/USN-6663-2

** Changed in: openssl (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: openssl (Ubuntu Trusty)
   Status: New => Won't Fix

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  Won't Fix
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Mantic:
  Fix Released
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054864] Re: Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

[David]

Just ran Ubuntu Updater today. It included a bunch of updates including
Linux Image 3.26 > 3.29. After reboot I now have IPv6 addresses again
and mDNS6 hostnames are correctly working on the local network.

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

Title:
  Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I ran the updater last week, my computer could only have a Link
  Local address for IPv6. I have now confirmed that IPv6 works normally
  when I install a fresh copy of 22.04.3 LTS and has the bug even after
  a fresh install of 22.04.4 LTS. Previous data and fault finding on
  this fault can be found on 2 Ask Ubuntu Posts I made regarding this
  fault during the last week (Note: Originally I thought that this was
  just an mDNS6 fault, hence the inaccurate title on the first post):

  First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
  ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

  Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
  ipv6-link-local-address-after-ubuntu-update

  The Ubuntu Release I am currently using is:
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  network-manager version reports as:
Installed: 1.36.6-0ubuntu2
Candidate: 1.36.6-0ubuntu2
Version table:
   *** 1.36.6-0ubuntu2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 24 16:02:45 2024
  InstallationDate: Installed on 2024-02-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 
600
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054864/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

https://ubuntu.com/security/notices/USN-6663-1

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  New
Status in openssl source package in Xenial:
  New
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Mantic:
  Fix Released
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

Bionic released in ESM Infra, version 1.1.1-1ubuntu2.1~18.04.23+esm5

** Changed in: openssl (Ubuntu Bionic)
   Status: New => 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/2054090

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  New
Status in openssl source package in Xenial:
  New
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Mantic:
  Fix Released
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054864] [NEW] Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

[David]

Public bug reported:

After I ran the updater last week, my computer could only have a Link
Local address for IPv6. I have now confirmed that IPv6 works normally
when I install a fresh copy of 22.04.3 LTS and has the bug even after a
fresh install of 22.04.4 LTS. Previous data and fault finding on this
fault can be found on 2 Ask Ubuntu Posts I made regarding this fault
during the last week (Note: Originally I thought that this was just an
mDNS6 fault, hence the inaccurate title on the first post):

First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
ipv6-link-local-address-after-ubuntu-update

The Ubuntu Release I am currently using is:
Description:Ubuntu 22.04.4 LTS
Release:22.04

network-manager version reports as:
  Installed: 1.36.6-0ubuntu2
  Candidate: 1.36.6-0ubuntu2
  Version table:
 *** 1.36.6-0ubuntu2 500

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 24 16:02:45 2024
InstallationDate: Installed on 2024-02-24 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
IpRoute:
 default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 600
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug jammy

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

Title:
  Only Link Local IPv6 after upgrading to 22.04.4 LTS from 22.04.3

Status in network-manager package in Ubuntu:
  New

Bug description:
  After I ran the updater last week, my computer could only have a Link
  Local address for IPv6. I have now confirmed that IPv6 works normally
  when I install a fresh copy of 22.04.3 LTS and has the bug even after
  a fresh install of 22.04.4 LTS. Previous data and fault finding on
  this fault can be found on 2 Ask Ubuntu Posts I made regarding this
  fault during the last week (Note: Originally I thought that this was
  just an mDNS6 fault, hence the inaccurate title on the first post):

  First Ask Ubuntu Post: https://askubuntu.com/questions/1503895/cant-
  ping-dynamic-ipv6-xubuntu-hostname-from-kubuntu-laptop

  Second Ask Ubuntu Post: https://askubuntu.com/questions/1504030/only-
  ipv6-link-local-address-after-ubuntu-update

  The Ubuntu Release I am currently using is:
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  network-manager version reports as:
Installed: 1.36.6-0ubuntu2
Candidate: 1.36.6-0ubuntu2
Version table:
   *** 1.36.6-0ubuntu2 500

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 24 16:02:45 2024
  InstallationDate: Installed on 2024-02-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.203 metric 
600
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054864/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

** Changed in: openssl (Ubuntu Bionic)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Focal)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Jammy)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Mantic)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Noble)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Xenial)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Trusty)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  New
Status in openssl source package in Xenial:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Jammy:
  New
Status in openssl source package in Mantic:
  New
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Also affects: openssl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: openssl (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: openssl (Ubuntu Noble)
   Importance: Undecided
 Assignee: David Fernandez Gonzalez (litios)
   Status: New

** Also affects: openssl (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: openssl (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: openssl (Ubuntu Noble)
 Assignee: David Fernandez Gonzalez (litios) => (unassigned)

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  New
Status in openssl source package in Xenial:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Jammy:
  New
Status in openssl source package in Mantic:
  New
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2054090] [NEW] Implicit rejection of PKCS#1 v1.5 RSA

[David Fernandez Gonzalez]

Public bug reported:

OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
output instead of an exception when detecting wrong padding
(https://github.com/openssl/openssl/pull/13817).

There are available backports already:

* 3.0 https://gitlab.com/redhat/centos-
stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
rejection.patch?ref_type=heads

* 1.1.1 https://gitlab.com/redhat/centos-
stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
rejection.patch?ref_type=heads


This change is needed to fix CVE-2023-50782.

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

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

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

[David Perry]

Verified on a few different reference boards internally by running a set
of 3 Unigine benchmarks with the updated mesa on the following:

Stormpeak W/Radeon 7900 XTX

Stormpeak W/Radeon Pro W7500

Stormpeak W/Radeon Pro W7900

Phoenix AMD Ryzen 7 7840U W/AMD Radeon™ 780M

Phoenix2 AMD Ryzen 5 7545U W/AMD Radeon™ 740M

verified also on a couple different pre-production platforms.

-- 
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/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 2037281] Re: Shutdown when triggering daemon-reload early in boot

[Valentin David]

I have done manual tests with jammy-proposed and focal-proposed.

I have added in /etc/systemd/system, the following service and enabled it. Then 
rebooted.
```
[Unit]
DefaultDependencies=no
Before=systemd-udev-trigger.service

[Service]
Type=oneshot
ExecStart=systemctl daemon-reload

[Install]
WantedBy=multi-user.target
```

If the bug was present, it would not complete the boot and have
filesystems unmounted. When the fix is working, the boot would complete
and it is possible to ssh to it.

Results of the test:

Ubuntu Core 22
Without jammy-proposed: systemd 249.11-0ubuntu3.11 -> broken
With jammy-proposed: systemd 249.11-0ubuntu3.12 -> fixed

Ubuntu Core 20, with pc-kernel 22/beta
Without focal-proposed: systemd 245.4-4ubuntu3.22 -> broken
With focal-proposed: systemd 245.4-4ubuntu3.23 -> fixed

So I confirm the systemd packages in jammy-proposed and focal-proposed
are fixing this issue.


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

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

Title:
  Shutdown when triggering daemon-reload early in boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  [ Impact ]

  If a user adds a service that calls `systemctl daemon-reload`, and if
  this service is started before systemd-udevd. And if the initrd is
  systemd (the case of Ubuntu Core), then most service will be stopped
  or cancel, and the machine will mostly shutdown everything and hang.

  The fix has been backported down to 250 upstream. It is already on
  kinetic and later.

  The fix only affects systems where systemd is used in initrd.

  [ Test Plan ]

  On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
  any system that uses systemd in initrd.

  Add a systemd service that calls `systemctl daemon-reload`.
  The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.

  Restart the machine.

  If fix is not applied, after the service is started, most of units
  with be shutdown, and the system will be unusable.

  [ Where problems could occur ]

  This should affect systems with systemd in initrd.

  There are risks on systems that have an udev rule in initrd not
  present in the main system.

  There are risks on systems that use db_persist in initrd where the
  device can potentially get dead state. Though this does not seem to
  happen on Ubuntu Core 22, even though we use db_persist for dev mapper
  devices. Regression is upstream bug #23429. Commits named
  "core/device: device_coldplug(): don't set DEVICE_DEAD" and
  "core/device: do not downgrade device state if it is already
  enumerated" could be applied as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

Fantastic! I can confirm that this is fixed on Ubuntu 23.10.

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

Title:
  Apple pages file type should be added to MIME types

Status in shared-mime-info:
  Fix Released
Status in mime-support package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Fix Released

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 2009544] Re: OpenSSL 3 performance regression

[David Leadbeater]

We came across this and noticed the CA certificates parsing itself is
one of the biggest slowdowns. One of the reasons OpenSSL ends up doing
that parsing is ca-certificates puts the same certificates in
/etc/ssl/certs/*.pem ("CApath") and /etc/ssl/certs/ca-certificates.crt
("CAfile"):

$ wc -l /etc/ssl/certs/ca-certificates.crt <(cat /etc/ssl/certs/*.pem)
   3431 /etc/ssl/certs/ca-certificates.crt
   3431 /dev/fd/63

On a mantic system, as a baseline:

$ time python3.11 main.py
Distro: Ubuntu 23.10
Python Version: 3.11.6 (main, Oct  8 2023, 05:06:43) [GCC 13.2.0]
OpenSSL Version: OpenSSL 3.0.10 1 Aug 2023
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
real0m2.768s
user0m9.666s
sys 0m0.124s

If I replace /etc/ssl/certs/ca-certificates.crt with a random one of the
certificates (sadly an empty file results in errors), so there's much
less parsing to be done, things are much faster:

$ sudo sh -c 'cat /etc/ssl/certs/002c0b4f.0 > 
/etc/ssl/certs/ca-certificates.crt'
$ time python3.11 main.py
Distro: Ubuntu 23.10
Python Version: 3.11.6 (main, Oct  8 2023, 05:06:43) [GCC 13.2.0]
OpenSSL Version: OpenSSL 3.0.10 1 Aug 2023
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
real0m0.675s
user0m0.781s
sys 0m0.059s

This also reproduces as a visible difference in user CPU time when
simply running curl against a HTTPS site.

I do wonder if somehow it would be possible to disable the CA file and
only rely on the CA path. Likely easier said than done, particularly
with the API changes in 3.x (splitting out the file loading into
SSL_CTX_load_verify_file).

There's also some Python specific discussion in
https://github.com/python/cpython/issues/95031 too, I did try setting
requests.get(..., verify='/etc/ssl/certs/') in the test script to
attempt to get requests to read only the directory per[1] but that
didn't seem to work.

[1]: https://requests.readthedocs.io/en/latest/user/advanced/#ssl-cert-
verification

** Bug watch added: github.com/python/cpython/issues #95031
   https://github.com/python/cpython/issues/95031

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

Title:
  OpenSSL 3 performance regression

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Hello, it sounds like there's some significant performance regressions
  in OpenSSL 3:

  https://github.com/openssl/openssl/issues/20286#issuecomment-1438826816

  Some we might be able to address with:
  https://github.com/openssl/openssl/pull/18151

  Some of the performance differences may be subject to ongoing work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+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 2044034] Re: /etc/security/limits.conf memlock changes have no effect

[David Favor]

This ticket can be closed.

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

Title:
  /etc/security/limits.conf memlock changes have no effect

Status in pam package in Ubuntu:
  New

Bug description:
  APT reports package as libpam-modules + launchpad says pam is the
  closest package. Please change package name, if required.

  Summary says it all.

  Default of memlock seems to be 64 (which limits.conf suggests means
  64k). Changing this setting seems to have no effect.

  The following entry seems to be correct, and has no effect after
  reboot, meaning ulimit -l still reports 64. I've tried 128, -1,
  unlimited, nothing seems to work.

  Maybe I just misunderstand the correct settings or maybe Ubuntu
  overrides limits.conf at boot time.

  My entry...

  *-   memlock unlimited

  Be great if someone can help me fixing this, as likely it's a simple
  config file fix somewhere.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+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 2044034] Re: /etc/security/limits.conf memlock changes have no effect

[David Favor]

Looks like the problem was UsePAM=yes in /etc/ssh/sshd_config.

So system wide memlock is effected + ssh logins only effected if PAM is
enabled to set limits.

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

Title:
  /etc/security/limits.conf memlock changes have no effect

Status in pam package in Ubuntu:
  New

Bug description:
  APT reports package as libpam-modules + launchpad says pam is the
  closest package. Please change package name, if required.

  Summary says it all.

  Default of memlock seems to be 64 (which limits.conf suggests means
  64k). Changing this setting seems to have no effect.

  The following entry seems to be correct, and has no effect after
  reboot, meaning ulimit -l still reports 64. I've tried 128, -1,
  unlimited, nothing seems to work.

  Maybe I just misunderstand the correct settings or maybe Ubuntu
  overrides limits.conf at boot time.

  My entry...

  *-   memlock unlimited

  Be great if someone can help me fixing this, as likely it's a simple
  config file fix somewhere.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+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 2035644] Re: apt status not updated ubuntu 20 LTS

[David Kalnischkies]

Looks like third-party packages are involved, so details on where to
find them would be good.

I presume the formatting of the data is different in dpkg/status vs. the
Packages file in the repo as libapt does string comparisons rather than
very costly fully parsed, transformed & cleaned comparisons and whatever
tool is used to create the Packages file might or might not do the same
transformations dpkg does. apt-ftparchive for example mostly doesn't.

dpkg e.g. has the tendency to remove 0-epochs from version numbers which
might be included in a dependency. Wild guess only – we would need the
actual data to know.

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

Title:
  apt status not updated ubuntu 20 LTS

Status in apt package in Ubuntu:
  New

Bug description:
  Hi,

  is this a cache bug? The packages are installed, but "apt list
  --upgradable" say's no, the are not installed.

  root@minion:~# apt list --upgradable
  Listing... Done
  uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 
[upgradable from: 3.15-7ubuntu20]
  venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 
[upgradable from: 3006.0-2.35.1]

  root@minion:~# apt install uls-client
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-5.4.0-153 linux-headers-5.4.0-153-generic 
linux-image-5.4.0-153-generic linux-modules-5.4.0-153-generic 
linux-modules-extra-5.4.0-153-generic
  Use 'apt autoremove' to remove them.
  Recommended packages:
libncursesw5
  The following packages will be upgraded:
uls-client
  1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  Need to get 0 B/194 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 177475 files and directories currently installed.)
  Preparing to unpack .../uls-client_3.15-7ubuntu20_amd64.deb ...
  redirecting to systemd
  Unpacking uls-client (3.15-7ubuntu20) over (3.15-7ubuntu20) ...
  Setting up uls-client (3.15-7ubuntu20) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for systemd (245.4-4ubuntu3.22) ...

  root@minion:~# apt list --upgradable
  Listing... Done
  uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 
[upgradable from: 3.15-7ubuntu20]
  venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 
[upgradable from: 3006.0-2.35.1]

  root@minion:~# apt update
  Hit:12 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-dp-tserver/ 
Release
  Hit:13 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-dp-tserver/ Release
  Hit:14 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-res-suma-dp-tserver/ Release
  Hit:15 https://SuMa:443/rhn/manager/download 
luxux-puppet-ubuntu20-x-amd64-dp-tserver/ Release
  Hit:16 https://SuMa:443/rhn/manager/download 
tvm-standard-ubuntu20-x-amd64-dp-tserver/ Release
  Hit:17 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-updates-dp-tserver/ Release
  Hit:18 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-security-dp-tserver/ Release
  Hit:19 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-universe-dp-tserver/ Release
  Hit:20 https://SuMa:443/rhn/manager/download 
luxux-standard-ubuntu20-x-amd64-dp-tserver/ Release
  Hit:21 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-updates-universe-dp-tserver/ Release
  Hit:22 https://SuMa:443/rhn/manager/download 
ubuntu20-x-amd64-main-security-universe-dp-tserver/ Release

  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  2 packages can be upgraded. Run 'apt list --upgradable' to see them.

  root@minion:~# apt list --upgradable
  Listing... Done
  uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 
[upgradable from: 3.15-7ubuntu20]
  venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 
[upgradable from: 3006.0-2.35.1]

  root@minion:~# apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-5.4.0-153 linux-headers-5.4.0-153-generic 
linux-image-5.4.0-153-generic linux-modules-5.4.0-153-generic 
linux-modules-extra-5.4.0-153-generic
  Use 'apt autoremove' to remove them.
  The following packages will be upgraded:
uls-client venv-salt-minion
  2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 22.7 MB/22.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 https://SuMa:443/rhn/manager/download 

[Touch-packages] [Bug 2044034] Re: /etc/security/limits.conf memlock changes have no effect

[David Favor]

This also fails... meaning... ulimit -l as root still shows 64...

*-   memlock unlimited
root -   memlock unlimited

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

Title:
  /etc/security/limits.conf memlock changes have no effect

Status in pam package in Ubuntu:
  New

Bug description:
  APT reports package as libpam-modules + launchpad says pam is the
  closest package. Please change package name, if required.

  Summary says it all.

  Default of memlock seems to be 64 (which limits.conf suggests means
  64k). Changing this setting seems to have no effect.

  The following entry seems to be correct, and has no effect after
  reboot, meaning ulimit -l still reports 64. I've tried 128, -1,
  unlimited, nothing seems to work.

  Maybe I just misunderstand the correct settings or maybe Ubuntu
  overrides limits.conf at boot time.

  My entry...

  *-   memlock unlimited

  Be great if someone can help me fixing this, as likely it's a simple
  config file fix somewhere.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+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 2044034] [NEW] /etc/security/limits.conf memlock changes have no effect

[David Favor]

Public bug reported:

APT reports package as libpam-modules + launchpad says pam is the
closest package. Please change package name, if required.

Summary says it all.

Default of memlock seems to be 64 (which limits.conf suggests means
64k). Changing this setting seems to have no effect.

The following entry seems to be correct, and has no effect after reboot,
meaning ulimit -l still reports 64. I've tried 128, -1, unlimited,
nothing seems to work.

Maybe I just misunderstand the correct settings or maybe Ubuntu
overrides limits.conf at boot time.

My entry...

*-   memlock unlimited

Be great if someone can help me fixing this, as likely it's a simple
config file fix somewhere.

Thanks!

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

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

Title:
  /etc/security/limits.conf memlock changes have no effect

Status in pam package in Ubuntu:
  New

Bug description:
  APT reports package as libpam-modules + launchpad says pam is the
  closest package. Please change package name, if required.

  Summary says it all.

  Default of memlock seems to be 64 (which limits.conf suggests means
  64k). Changing this setting seems to have no effect.

  The following entry seems to be correct, and has no effect after
  reboot, meaning ulimit -l still reports 64. I've tried 128, -1,
  unlimited, nothing seems to work.

  Maybe I just misunderstand the correct settings or maybe Ubuntu
  overrides limits.conf at boot time.

  My entry...

  *-   memlock unlimited

  Be great if someone can help me fixing this, as likely it's a simple
  config file fix somewhere.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/2044034/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[David Bürgin]

I think this bug should be reopened.

The timeout error still happens even after installing the stable release
update.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot

[Valentin David]

Just adding a comment on how to reproduce the bug, because I have lost a
day trying to figure it out again. This fails only when not using secure
boot because the device mapper state is kept from initrd to main boot.

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

Title:
  Shutdown when triggering daemon-reload eary in boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  [ Impact ]

  If a user adds a service that calls `systemctl daemon-reload`, and if
  this service is started before systemd-udevd. And if the initrd is
  systemd (the case of Ubuntu Core), then most service will be stopped
  or cancel, and the machine will mostly shutdown everything and hang.

  The fix has been backported down to 250 upstream. It is already on
  kinetic and later.

  The fix only affects systems where systemd is used in initrd.

  [ Test Plan ]

  On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
  any system that uses systemd in initrd.

  Add a systemd service that calls `systemctl daemon-reload`.
  The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.

  Restart the machine.

  If fix is not applied, after the service is started, most of units
  with be shutdown, and the system will be unusable.

  [ Where problems could occur ]

  This should affect systems with systemd in initrd.

  There are risks on systems that have an udev rule in initrd not
  present in the main system.

  There are risks on systems that use db_persist in initrd where the
  device can potentially get dead state. Though this does not seem to
  happen on Ubuntu Core 22, even though we use db_persist for dev mapper
  devices. Regression is upstream bug #23429. Commits named
  "core/device: device_coldplug(): don't set DEVICE_DEAD" and
  "core/device: do not downgrade device state if it is already
  enumerated" could be applied as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2041722] [NEW] Duplex printing error on Brother MFC-J825DW

[David Tombs]

Public bug reported:

Using the default "implicitclass" printer setup by Ubuntu, trying to do
Duplex printing does not function properly. E.g., printing a four page
document will result in the printer printing pages 4, 3, 2, and 1 in
that order on four separate sheets of paper. Note that pages 3 and 1
print upside-down.

As in bug #2041721, manually adding the printer using "dnssd" and using
that one resolves the issue. I am opening a separate bug in case this is
a different root cause, though.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.7
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog:
 W [28/Oct/2023:09:27:48 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
 W [28/Oct/2023:10:00:49 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 10:33:50 2023
InstallationDate: Installed on 2023-01-22 (278 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lpstat:
 device for Brother_MFC_J825DW: implicitclass://Brother_MFC_J825DW/
 device for MFC-J825DW-2: 
dnssd://Brother%20MFC-J825DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-001ba9a45fbe
MachineType: Dell Inc. Inspiron 3537
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_MFC_J825DW.ppd', '/etc/cups/ppd/MFC-J825DW-2.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Brother_MFC_J825DW.ppd: Permission 
denied
 grep: /etc/cups/ppd/MFC-J825DW-2.ppd: Permission denied
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=2b653741-a62a-4f80-8671-24ffbfe5cd2c ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0MJNYC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron3537:pvrA12:rvnDellInc.:rn0MJNYC:rvrA00:cvnDellInc.:ct8:cvrA12:skuInspiron3537:
dmi.product.family: 00
dmi.product.name: Inspiron 3537
dmi.product.sku: Inspiron 3537
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Duplex printing error on Brother MFC-J825DW

Status in cups package in Ubuntu:
  New

Bug description:
  Using the default "implicitclass" printer setup by Ubuntu, trying to
  do Duplex printing does not function properly. E.g., printing a four
  page document will result in the printer printing pages 4, 3, 2, and 1
  in that order on four separate sheets of paper. Note that pages 3 and
  1 print upside-down.

  As in bug #2041721, manually adding the printer using "dnssd" and
  using that one resolves the issue. I am opening a separate bug in case
  this is a different root cause, though.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [28/Oct/2023:09:27:48 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [28/Oct/2023:10:00:49 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 10:33:50 2023
  InstallationDate: Installed on 2023-01-22 (278 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lpstat:
   device for Brother_MFC_J825DW: implicitclass://Brother_MFC_J825DW/
   device for MFC-J825DW-2: 
dnssd://Brother%20MFC-J825DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-001ba9a45fbe
  MachineType: Dell Inc. Inspiron 3537
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_MFC_J825DW.ppd', '/etc/cups/ppd/MFC-J825DW-2.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Brother_MFC_J825DW.ppd: Permission 
denied
   grep: /etc/cups/ppd/MFC-J825DW-2.ppd: Permission denied
  

[Touch-packages] [Bug 2041721] [NEW] Brother MFC-J825DW squares copy number when printing

[David Tombs]

Public bug reported:

Using the default "implicitclass" printer setup by Ubuntu, printing to
my Brother MFC-J825DW "squares" the number of copies. E.g., trying to do
2 copies prints 4 and trying to do 3 copies prints 9.

I manually added the printer using the "dnssd" connection instead, and
using that one resolves the issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.7
ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CupsErrorLog:
 W [28/Oct/2023:09:27:48 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
 W [28/Oct/2023:10:00:49 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 10:29:52 2023
InstallationDate: Installed on 2023-01-22 (278 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lpstat:
 device for Brother_MFC_J825DW: implicitclass://Brother_MFC_J825DW/
 device for MFC-J825DW-2: 
dnssd://Brother%20MFC-J825DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-001ba9a45fbe
MachineType: Dell Inc. Inspiron 3537
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_MFC_J825DW.ppd', '/etc/cups/ppd/MFC-J825DW-2.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Brother_MFC_J825DW.ppd: Permission 
denied
 grep: /etc/cups/ppd/MFC-J825DW-2.ppd: Permission denied
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=2b653741-a62a-4f80-8671-24ffbfe5cd2c ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0MJNYC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.ec.firmware.release: 1.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron3537:pvrA12:rvnDellInc.:rn0MJNYC:rvrA00:cvnDellInc.:ct8:cvrA12:skuInspiron3537:
dmi.product.family: 00
dmi.product.name: Inspiron 3537
dmi.product.sku: Inspiron 3537
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  Brother MFC-J825DW squares copy number when printing

Status in cups package in Ubuntu:
  New

Bug description:
  Using the default "implicitclass" printer setup by Ubuntu, printing to
  my Brother MFC-J825DW "squares" the number of copies. E.g., trying to
  do 2 copies prints 4 and trying to do 3 copies prints 9.

  I manually added the printer using the "dnssd" connection instead, and
  using that one resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4.7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   W [28/Oct/2023:09:27:48 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
   W [28/Oct/2023:10:00:49 -0400] Printer drivers are deprecated and will stop 
working in a future version of CUPS. See 
https://github.com/OpenPrinting/cups/issues/103
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 10:29:52 2023
  InstallationDate: Installed on 2023-01-22 (278 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lpstat:
   device for Brother_MFC_J825DW: implicitclass://Brother_MFC_J825DW/
   device for MFC-J825DW-2: 
dnssd://Brother%20MFC-J825DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-001ba9a45fbe
  MachineType: Dell Inc. Inspiron 3537
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_MFC_J825DW.ppd', '/etc/cups/ppd/MFC-J825DW-2.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Brother_MFC_J825DW.ppd: Permission 
denied
   grep: /etc/cups/ppd/MFC-J825DW-2.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-35-generic 
root=UUID=2b653741-a62a-4f80-8671-24ffbfe5cd2c ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen artifacts/UI oddities on Wayland

[Antoine DAVID]

I'm experiencing the same issue as well.

I'm using an Asus TUF A15 with an RTX 4050.

Gnome crashes when using multiple screens with Firefox and the file
explorer.

One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.

Best regards,

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

Title:
  [amdgpu] Screen artifacts/UI oddities on Wayland

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

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 21A00068US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A00068US:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A00068US:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A00068US
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  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
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
  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/linux/+bug/2038998/+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 2037281] Re: Shutdown when triggering daemon-reload eary in boot

[Valentin David]

** Description changed:

  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by udev,
  does `systemctl daemon-reload`, the system shuts down. This is due to
  devices for mounted filesystem temporarily taken dead, which pulls most
  units down.
  
  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.
  
  But this was not backported to the versions used by Ubuntu packages for
  focal and jammy. The needed commit from that PR is the one with message
  `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.
  
  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed.
  And I suppose it does also for jammy.
  
  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.
  
  We would like this patch to be backported to focal-updates and jammy-
  updates.
  
  Thank you in advance.
  
+ [ Impact ]
  
- [ Impact ] 
-  * An explanation of the effects of the bug on users and
-  * justification for backporting the fix to the stable release.
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ If a user adds a service that calls `systemctl daemon-reload`, and if
+ this service is started before systemd-udevd. And if the initrd is
+ systemd (the case of Ubuntu Core), then most service will be stopped or
+ cancel, and the machine will mostly shutdown everything and hang.
+ 
+ The fix has been backported down to 250 upstream. It is already on
+ kinetic and later.
+ 
+ The fix only affects systems where systemd is used in initrd.
  
  [ Test Plan ]
-  * detailed instructions how to reproduce the bug
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
-  * if other testing is appropriate to perform before landing this update,
-this should also be described here.
+ 
+ On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on any
+ system that uses systemd in initrd.
+ 
+ Add a systemd service that calls `systemctl daemon-reload`.
+ The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.
+ 
+ Restart the machine.
+ 
+ If fix is not applied, after the service is started, most of units with
+ be shutdown, and the system will be unusable.
  
  [ Where problems could occur ]
-  * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
  
- [ 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
+ This should affect systems with systemd in initrd.
+ 
+ There are risks on systems that have an udev rule in initrd not present
+ in the main system.
+ 
+ There are risks on systems that use db_persist in initrd where the
+ device can potentially get dead state. Though this does not seem to
+ happen on Ubuntu Core 22, even though we use db_persist for dev mapper
+ devices. Regression is upstream bug #23429. Commits named "core/device:
+ device_coldplug(): don't set DEVICE_DEAD" and "core/device: do not
+ downgrade device state if it is already enumerated" could be applied as
+ well.

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

Title:
  Shutdown when triggering daemon-reload eary in boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without 

[Touch-packages] [Bug 2037281] [NEW] Shutdown when triggering daemon-reload eary in boot

[Valentin David]

Public bug reported:

In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
where if a service, started earlier than devices are processed by udev,
does `systemctl daemon-reload`, the system shuts down. This is due to
devices for mounted filesystem temporarily taken dead, which pulls most
units down.

This was fixed by upstream in
https://github.com/systemd/systemd/pull/23218.

But this was not backported to the versions used by Ubuntu packages for
focal and jammy. The needed commit from that PR is the one with message
`core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing needed.
And I suppose it does also for jammy.

I have manually tested the fix with Ubuntu Core 20, and this fixes our
issue.

We would like this patch to be backported to focal-updates and jammy-
updates.

Thank you in advance.

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

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

Title:
  Shutdown when triggering daemon-reload eary in boot

Status in systemd package in Ubuntu:
  New

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2036427] Re: Upgrade to version 249.11-0ubuntu3.10 breaks 12d1:15c1 Huawei ME906s LTE M.2 Module

[David Bürgin]

I am also seeing this on Ubuntu 20.04.3 LTS Server. apt upgrade of systemd
"(249.11-0ubuntu3.9, 249.11-0ubuntu3.10)" results in:

Sep 22 22:25:27 mail systemd-networkd-wait-online[420]: Timeout occurred while 
waiting for network connectivity.
Sep 22 22:25:27 mail systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Sep 22 22:25:27 mail systemd[1]: systemd-networkd-wait-online.service: Failed 
with result 'exit-code'.
Sep 22 22:25:27 mail systemd[1]: Failed to start Wait for Network to be 
Configured.

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

Title:
  Upgrade to version 249.11-0ubuntu3.10 breaks 12d1:15c1 Huawei  ME906s
  LTE M.2 Module

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  After the latest upgrade our Huawei LTE modem is not working anymore.
  We can see the modem wie lsusb, but no interfaces gets activated and 
systemd-networkd-wait-online gets a timeout.

  The following packages have been upgraded:
  Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 
249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), 
systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), thermald:amd64 
(2.4.9-1ubuntu0.3, 2.4.9-1ubuntu0.4)

  When we switch back to an older version the modem is working again!

  Downgrade: systemd-timesyncd:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7), libpam-systemd:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7), libsystemd0:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7), libnss-systemd:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7), systemd:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7), systemd-sysv:amd64 (249.11-0ubuntu3.10,
  249.11-0ubuntu3.7)

  So the latest update breaks anything with that modem.

  The output of lsusb stays the same with both versions:
  Bus 001 Device 003: ID 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 
Module

  With old packages "ip link" looks like that:
  9: wwan0:  mtu 1500 qdisc fq_codel 
state UNKNOWN mode DEFAULT group default qlen 1000
  link/ether 2e:c4:ac:0a:11:f2 brd ff:ff:ff:ff:ff:ff

  With new packages "ip link" does not show any wwan0 or similar interface.
  Other network interfaces are avaiable.

  The network interfaces are configured with /etc/network/interfaces:
  allow-hotplug wwan0
  iface wwan0 inet dhcp
   apn a1.net
   metric 100

  We use modemmanager to connect:
  /usr/bin/mmcli --modem 0 --simple-connect="apn=a1.net"

  "mmcli -L" can't find any modems on a upgraded system.
  With the previous version we see the Huawei modem:
  /org/freedesktop/ModemManager1/Modem/0 [Huawei Technologies Co., Ltd.] 
HUAWEI Mobile V7R11

  
  We have a lot of systems with Huawei LTE modems and that's a serious problem 
for us!
  Do you need more information to debug that problem?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036427/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

[serck david]

I confirm workaround mentioned in #32 works on debian 12 with
GlobalProtect UI version 6.1.2-82

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  Expired

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

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


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

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

[David Venz]

Thanks Nathan,

I finally lined up all the ducks, and it appears to have worked.

- The dir I'm building in has to be in my home dir
- the xvfb-run seems necessary
- don't attempt to use --headless
- both --user-data-dir=/tmp/ChrUnsnapped   and   --class="ChrUnsnapped"  seem 
unnecessary

So,

user@host:~/tmp/ChromeExtensions$ 
   xvfb-run /snap/bin/chromium --pack-extension=MyExt 
--pack-extension-key=MyExt.pem

Tested with chromium snap v2556 (115.0.5790.102).

I'll have to update our build system to copy files to somewhere in
/home/, build there, and copy the results back.

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

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

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

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

  Issue appears to only impact 20.04.
  chrome snap version 2529

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

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

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

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

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

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

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


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

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

[David Venz]

This breaks our command-line pack of an in-house extension, under Ubuntu 20.04.
Is there a way to do this using the confined run?

Our current unconfined run build command-line (please excuse legacy from
years ago, eg --headless might be more appropriate now):

xvfb-run /snap/chromium/current/usr/lib/chromium-browser/chrome --user-
data-dir=/tmp/ChrUnsnapped --class="ChrUnsnapped" --pack-extension=MyExt
--pack-extension-key=MyExt.pem

This understandably gets libm GLIBC version errors with a core22
dependent chromium snap.

Trying with confinement and --headless (and files moved to a subdirectory of 
/home/):
user@host:~/tmp/ChromeExtensions$ /snap/bin/chromium --headless 
--enable-logging=stderr --pack-extension=MyExt --pack-extension-key=MyExt.pem 
[0726/200919.476268:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called 
with multiple threads in process gpu-process.
[0726/200919.543209:WARNING:bluez_dbus_manager.cc(247)] Floss manager not 
present, cannot set Floss enable/disable.

user@host:~/tmp/ChromeExtensions$ echo $?
0

Sadly no .crx comes out that I can find.

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

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

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

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

  Issue appears to only impact 20.04.
  chrome snap version 2529

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2028124] Re: apt dist-upgrade does not restart package qemu-guest-agent

[David Kalnischkies]

APT itself is not involved with (re)starting services. The individual
packages do this in their maintainer scripts, so reassigning to qemu
(which contains qemu-guest-agent).

** Package changed: apt (Ubuntu) => qemu (Ubuntu)

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

Title:
  apt dist-upgrade does not restart package qemu-guest-agent

Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  When my system Ubuntu 22.04.2 LTS performs apt dist-upgrade (manually or from 
unattended upgrades) and there is an upadte on package qemu-guest-agent, the 
agent gets stopped, updated, but is not started.
  I observed this behaviour on two machines with same result.

  After I run the apt I see this in syslog, no errors:
  Jul 19 07:04:02 micro systemd[1]: Stopping QEMU Guest Agent...
  Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Deactivated 
successfully.
  Jul 19 07:04:02 micro systemd[1]: Stopped QEMU Guest Agent.
  Jul 19 07:04:02 micro systemd[1]: qemu-guest-agent.service: Consumed 31min 
49.962s CPU time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2028124/+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 2028170] Re: curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt-name

[David Renshaw]

This bug is causing breakage in the Lean 4 build cache infrastructure:
https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/leantar.20too.20old.20.28lean.20exe.20cache.20get.20not.20working.29/near/376686259

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

Title:
  curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt-
  name

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  With the latest curl 7.81.0-1ubuntu1.11 on ubuntu 22.04, I'm getting
  the following:

  curl -v https://raw.githubusercontent.com

  *   Trying 185.199.108.133:443...
  * Connected to raw.githubusercontent.com (185.199.108.133) port 443 (#0)
  [...]
  * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  * ALPN, server accepted to use h2
  * Server certificate:
  *  subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; 
CN=*.github.io
  *  start date: Feb 21 00:00:00 2023 GMT
  *  expire date: Mar 20 23:59:59 2024 GMT
  *  subjectAltName does not match raw.githubusercontent.com
  * SSL: no alternative certificate subject name matches target host name 
'raw.githubusercontent.com'
  curl: (60) SSL: no alternative certificate subject name matches target host 
name 'raw.githubusercontent.com'
  More details here: https://curl.se/docs/sslcerts.html

  curl failed to verify the legitimacy of the server and therefore could not
  establish a secure connection to it. To learn more about this situation and
  how to fix it, please visit the web page mentioned above.

  --
  The alt name looks proper when looking at the cert w/ s_client:

  openssl s_client -connect raw.githubusercontent.com:443 /dev/null | openssl x509 -noout -text

  X509v3 Subject Alternative Name:
  DNS:*.github.io, DNS:github.io, DNS:*.github.com, 
DNS:github.com, DNS:www.github.com, DNS:*.githubusercontent.com, 
DNS:githubusercontent.com

  Previous versions of curl work as intended.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028170/+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 2013128] Re: mesa: set info.separate_shader for ARB programs

[David Vereb]

The fix seems to be in 23.1
(https://gitlab.freedesktop.org/mesa/mesa/-/blob/23.1/src/mesa/program/prog_to_nir.c?ref_type=heads#L1039).
For anyone else with the issue, there are PPAs that have been updated
with the code that fixes this issue.  I'm using this while waiting for
the official release:
https://launchpad.net/~kisak/+archive/ubuntu/kisak-
mesa?field.series_filter=jammy.  Not the "correct" solution, I suppose,
but it got me back up and running until the fix comes through.

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

Title:
  mesa: set info.separate_shader for ARB programs

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Jammy:
  In Progress
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Triaged
Status in mesa source package in Mantic:
  In Progress

Bug description:
  [Impact]
  There's a shader bug in 22.2.x, fixed upstream in commit

  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  but since 22.2.x is already EOL, we need to backport it.

  [Test case]

  Install update, check that the application from the submitter works.

  
  [Where things could go wrong]
  This is a oneliner that flips a bool, but it's hard to imagine use-cases 
which would expect the old value.

  
  --

  
  I have a bug that occurs in Ubuntu 22.04's most up to date libmesa related 
packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in =22.0.1-1ubuntu2. 
It has since been solved in mesa's repo and pulled into debian's repo. I do not 
know the proper way to request an updated version be made for Ubuntu. I've 
manually installed many different versions of libmesa to test on my own that it 
was working in an older version, is broken in this update, and was fixed again 
in 22.3.4 and 22.3.5.

  The one-line fix is implemented here in libmesa's repo:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782

  Unfortunately I'm not using libmesa directly. I'm programming an
  application using fox-toolkit which interfaces with libmesa behind the
  scenes for me. I reported my issue to them first, and they stated it
  appears to be in the mesa library, which is what ultimately led me
  down the path to their repo, debian's repo, and here. Please let me
  know if I'm in the right spot, and, if so, what my next step is to
  properly report this.

  --

  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

   > lsb_release -rd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
    Installed: 22.2.5-0ubuntu0.1~22.04.1
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+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 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS

[David Wilian Oliveira de Sousa]

This bug affects me too.

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

Title:
  cannot install libegl-mesa0 on 22.04.2 LTS

Status in mesa package in Ubuntu:
  New

Bug description:
  # Summary

  `apt install libegl-mesa0` does not install it due to a dependency
  conflict in the apt repo.

  libegl-mesa0 has dependency to explicit versions of:
  * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
  * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)

  But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2.

  # Expected behavior

  These closely linked packages to be up-to-date in the Ubuntu repo.

  
  # Workaround

  It is possible to install libegl-mesa0 by first downgrading the
  conflicting package versions:

  apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1
  apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1

  and then installing it normally:

  apt install libegl-mesa0

  # Details

  ```
  # apt install libegl-mesa0
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.`
  ```

  1) Is the hard dependency (=) really necessary?

  2) Or should I just downgrade existing libglapi-mesa and libgbm1
  installs? The difference is minor patch version only so I am hesitant
  to do so (there must have been a reasons for the .2 patch).

  # Environment

  ## cat /etc/lsb-release
  ```
  cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
  ```

  # apt-cache policy

  ```
  apt-cache policy  libegl-mesa0
  libegl-mesa0:
    Installed: (none)
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   22.2.5-0ubuntu0.1~22.04.1 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
   22.0.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2023008/+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 2020251] [NEW] cannot install both libcurl4-gnutls-dev x64 and i386

[David Daynard]

Public bug reported:

sudo aptitude install libcurl4-gnutls-dev:i386
The following NEW packages will be installed:
  libcurl4-gnutls-dev:i386
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/455 kB of archives. After unpacking 1653 kB will be used.
Selecting previously unselected package libcurl4-gnutls-dev:i386.
(Reading database ... 66367 files and directories currently installed.)
Preparing to unpack .../libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb ...
Unpacking libcurl4-gnutls-dev:i386 (7.88.1-9ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb (--unpack):
 trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-gnutls-dev:i386
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libcurl4-gnutls-dev:i386 7.88.1-9ubuntu1
Uname: Linux 5.15.90.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat May 20 18:01:39 2023
PackageArchitecture: i386
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: curl
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  cannot install both libcurl4-gnutls-dev x64 and i386

Status in curl package in Ubuntu:
  New

Bug description:
  sudo aptitude install libcurl4-gnutls-dev:i386
  The following NEW packages will be installed:
libcurl4-gnutls-dev:i386
  0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/455 kB of archives. After unpacking 1653 kB will be used.
  Selecting previously unselected package libcurl4-gnutls-dev:i386.
  (Reading database ... 66367 files and directories currently installed.)
  Preparing to unpack .../libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb ...
  Unpacking libcurl4-gnutls-dev:i386 (7.88.1-9ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb (--unpack):
   trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-gnutls-dev:i386
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libcurl4-gnutls-dev_7.88.1-9ubuntu1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: libcurl4-gnutls-dev:i386 7.88.1-9ubuntu1
  Uname: Linux 5.15.90.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat May 20 18:01:39 2023
  PackageArchitecture: i386
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: curl
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Touch-packages] [Bug 2020127] Re: x apps fail to launch from terminal shell

[David Prout]

Brilliant!

grep XAUTHORITY ~/.*

found

/home/dave/.bashrc: export XAUTHORITY=~/.Xauthority

and commenting the line out in .bashrc fixed the problem

I don't know how the export got into my .bashrc

Possibly to do with me recently upgrading to 23.04 from 22.04 via 22.10, 
without checking 22.10 in any detail.   Or, it took two attempts to 
download 23.04 due to slow network and repositories timing out and 
something glitched.  More likely it could have been me fiddling with X 
in the past.

Whatever the cause, many thanks for your help

Cheers,

Dave

On 19/05/2023 02:59, Daniel van Vugt wrote:
> Thanks for the bug report.
>
> I can't seem to reproduce the issue here. Perhaps you just need to
> delete ~/.Xauthority or perhaps there's something in your local config
> setting it? Try:
>
>grep XAUTHORITY ~/.*
>

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

Title:
  x apps fail to launch from terminal shell

Status in xorg package in Ubuntu:
  New

Bug description:
  New upgrade to 23.04

  In terminal typing xeyes, idle or other X app including ubuntu-bug
  fails to launch with error Invalid MIT-MAGIC-COOKIE-1 keyError: cannot
  open display: :0

  Desktop and remote access from another machine to a shell on this host
  with ssh -X work correctly

  echo $XAUTHORITY is /home/dave/.Xauthority   File exists and contains
  2 cookies

  Clue:

  export XAUTHORITY=$(ls /run/user/1000/.mutter-Xwayland*) ubuntu-bug

  links to a working per session cookie, and I'm able to type this.

  Expected behaviour: display just works when an X application is
  started from a shell.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 18 18:44:46 2023
  DistUpgraded: 2023-05-16 20:52:31,229 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.6, 5.19.0-42-generic, x86_64: installed
   virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz 
Edition] [1002:6818] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Pitcairn XT [Radeon HD 7870 
GHz Edition] [1787:2321]
  InstallationDate: Installed on 2021-03-06 (802 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Gigabyte Technology Co., Ltd. Z490 AORUS ELITE AC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=c3300897-9f55-4525-91f6-ac8cfbe405f3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-05-16 (1 days ago)
  dmi.bios.date: 08/28/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z490 AORUS ELITE AC
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd08/28/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490AORUSELITEAC:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ490AORUSELITEAC:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Z490 MB
  dmi.product.name: Z490 AORUS ELITE AC
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  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/2020127/+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 1771041] Re: Remove gconf from Ubuntu

[David D Lowe]

ooo-thumbnailer is an abandoned project and is being removed from
Debian. Project link: https://launchpad.net/ooo-thumbnailer

** Changed in: ooo-thumbnailer (Ubuntu)
   Status: New => Invalid

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Released
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  Invalid
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Fix Released

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+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 2018233] [NEW] Xorg crash / Wayland

[David]

Public bug reported:

I'm not sure if it's Xorg crashing, i'm using wayland. 
Clean installation Ubuntu 22.10 and upgraded to 23.04.

The bug can be re-produced.

Symptom:
Moving firefox with ongoing video for example Youtube. Moving the firefox 
window from screen 2 or 3 to screen1 then it crashes 100% of times.

Screen 1 is in vertical view mode.
Screen 2 and 3 landscape.

##

unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May  1 15:17:51 2023
DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
InstallationDate: Installed on 2023-03-22 (39 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: LENOVO 21CB00AYMX
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to lunar on 2023-04-23 (7 days ago)
dmi.bios.date: 03/02/2023
dmi.bios.release: 1.37
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET72W (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CB00AYMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 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.18
dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET72W(1.37):bd03/02/2023:br1.37:efr1.18:svnLENOVO:pn21CB00AYMX:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CB00AYMX:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CB00AYMX
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
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 crash lunar ubuntu wayland-session

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

Title:
  Xorg crash / Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure if it's Xorg crashing, i'm using wayland. 
  Clean installation Ubuntu 22.10 and upgraded to 23.04.

  The bug can be re-produced.

  Symptom:
  Moving firefox with ongoing video for example Youtube. Moving the firefox 
window from screen 2 or 3 to screen1 then it crashes 100% of times.

  Screen 1 is in vertical view mode.
  Screen 2 and 3 landscape.

  ##

  unk@unk-ThinkPad-X1-Carbon-Gen-10:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  1 15:17:51 2023
  DistUpgraded: 2023-04-23 20:27:46,523 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7]
  InstallationDate: Installed on 2023-03-22 (39 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: LENOVO 21CB00AYMX
  

[Touch-packages] [Bug 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used

[David Fernandez Gonzalez]

Thanks for the heads up Alejandro!

A fix was committed and merged for the CIS/USG tooling.

We are preparing a new version but we are still working on some other
fixes to include. I'll update the thread when it comes out.

** Changed in: pam (Ubuntu)
   Status: New => Fix Committed

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

** Changed in: usg
   Status: In Progress => Fix Committed

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in Ubuntu Security Guide:
  Fix Committed
Status in pam package in Ubuntu:
  In Progress

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/usg/+bug/1989731/+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 2013128] Re: [feature request] Upgrade libglx-mesa0

[David Vereb]

Sorry about that, I thought linking the bugfix to the question would
show the question post more prominently.  I'll keep that in mind for
next time.

Is there a way to see when this fix will make its way to the 22.04
repositories?  I'm just curious how to follow along with the progress of
the bugfix being applied.  Is this something that's done on a schedule,
or is it just when the package maintainer has time?  I don't mean to
rush, I'm just curious!

Thanks.

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

Title:
  [feature request] Upgrade libglx-mesa0

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New

Bug description:
  I have a bug that occurs in Ubuntu 22.04's most up to date libmesa
  related packages (=22.2.5-0ubuntu0.1~22.04.1) that was not there in
  =22.0.1-1ubuntu2. It has since been solved in mesa's repo and pulled
  into debian's repo. I do not know the proper way to request an updated
  version be made for Ubuntu. I've manually installed many different
  versions of libmesa to test on my own that it was working in an older
  version, is broken in this update, and was fixed again in 22.3.4 and
  22.3.5.

  The one-line fix is implemented here in libmesa's repo:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/7e68cf91d74e6bd9a88c2b52417451d9afec4782/pipelines

  --

  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

   > lsb_release -rd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
    Installed: 22.2.5-0ubuntu0.1~22.04.1
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

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


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

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

[David]

Hello, I experienced this issue as well (EOG 42 on Pop!_OS/Ubuntu 22.04
LTS). I just described it here:
https://gitlab.gnome.org/GNOME/eog/-/issues/289

I solved the issue by disabling the auto-generated colour profile in the
gnome settings.

As I said in the description, I can't assess if this issue is related to
some specific monitors (I have a ThinkPad T480 monitor), or it's a
common problem.

** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #289
   https://gitlab.gnome.org/GNOME/eog/-/issues/289

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

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

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

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

  Workaround:

  1. Settings > Colour > turn off the toggle switch for your monitor.

  2. Restart any affected apps.

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

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


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

[Touch-packages] [Bug 2013128] [NEW] [feature request] Upgrade libglx-mesa0

[David Vereb]

Public bug reported:

Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

I was directed to report this bug via my question at
answers.launchpad.net/ubuntu:
https://answers.launchpad.net/ubuntu/+question/705988

Please let me know if you need further information.  Thanks!


 > lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

 > apt-cache policy libglx-mesa0
libglx-mesa0:
  Installed: 22.2.5-0ubuntu0.1~22.04.1
  Candidate: 22.2.5-0ubuntu0.1~22.04.1
  Version table:
 *** 22.2.5-0ubuntu0.1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: i3
Date: Tue Mar 28 15:30:59 2023
InstallationDate: Installed on 2022-04-28 (334 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

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


** Tags: amd64 apport-bug jammy

** Summary changed:

- Upgrade libglx-mesa0
+ [feature request] Upgrade libglx-mesa0

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

Title:
  [feature request] Upgrade libglx-mesa0

Status in mesa package in Ubuntu:
  New

Bug description:
  Feature Request: Upgrade mesa libraries to apply upstream bugfix to a
  bug introduced in 22.2.5-0ubuntu0.1~22.04.1.

  I was directed to report this bug via my question at
  answers.launchpad.net/ubuntu:
  https://answers.launchpad.net/ubuntu/+question/705988

  Please let me know if you need further information.  Thanks!

  
   > lsb_release -rd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

   > apt-cache policy libglx-mesa0
  libglx-mesa0:
Installed: 22.2.5-0ubuntu0.1~22.04.1
Candidate: 22.2.5-0ubuntu0.1~22.04.1
Version table:
   *** 22.2.5-0ubuntu0.1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libglx-mesa0 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: i3
  Date: Tue Mar 28 15:30:59 2023
  InstallationDate: Installed on 2022-04-28 (334 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2022-04-29T14:47:14.568862

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2013128/+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 1404635] Re: rsync: recv_generator: mkdir error with folder ending with space

[RICQ David]

Yes, I understand. I would just confirm it was not a rsync bug but just
a FAT32 feature.

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

Title:
  rsync: recv_generator: mkdir error with folder ending with space

Status in rsync package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I notice what rsync is not able to copy folder which ending with space :

  Example which not working : 
  rsync: recv_generator: mkdir "/var/Janji feat. T.R. " failed: Invalid 
argument (22)
  *** Skipping any contents from this failed directory ***

  If I remove space at the end, it works.

  mkdir can create folder with space at the end.


  rsync  version 3.1.0  protocol version 31

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1404635/+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 1404635] Re: rsync: recv_generator: mkdir error with folder ending with space

[RICQ David]

Hi,

Thanks for the response.

I don't remember the context but maybe the destination was a FAT32 device.
And FAT32 doesn't support folder ending with space.

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

Title:
  rsync: recv_generator: mkdir error with folder ending with space

Status in rsync package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I notice what rsync is not able to copy folder which ending with space :

  Example which not working : 
  rsync: recv_generator: mkdir "/var/Janji feat. T.R. " failed: Invalid 
argument (22)
  *** Skipping any contents from this failed directory ***

  If I remove space at the end, it works.

  mkdir can create folder with space at the end.


  rsync  version 3.1.0  protocol version 31

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1404635/+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 2007381] Re: Xorg freeze

[David Scott]

Additional info, not sure if it has any relivance but the last update
installed a new wi fi driver for RTL8821CE card. It seemed to take a
very long time to install.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and 
flashing cursor in top corner then stopped and started again with log in 
screen. As duel boot started laptop in Windows 10 and no problems so software 
problem. Reseached and found a fix which was putting in file,
1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf"

  Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "TearFree" "true"
  EndSection  

  This seems to have fixed the problem. I was running System Profile to watch 
Temps and also Mate System monitor with Firefox in the background. It did for a 
moment give a black screen but recovered so not sure if this was the problem 
resurfacing.
  Without this being a duel boot I would have had great difficulty identifying 
if it was software or a overheating/grapics card problem. Most users would 
scrap their hardware if they were presented with this problem. Hopefully my 
problem is fixed but if not could you please advise me further.
  All the Best
  DAvid

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Wed Feb 15 12:00:06 2023
  DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed
   bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed
   rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1179:ff50]
 Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1179:ff50]
  InstallationDate: Installed on 2021-08-21 (542 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: TOSHIBA Satellite M300
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago)
  dmi.bios.date: 03/13/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.80
  dmi.board.name: Satellite M300
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku:
  dmi.product.name: Satellite M300
  dmi.product.version: PSMD0L-01N00M
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/2007381/+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 2007381] [NEW] Xorg freeze

[David Scott]

Public bug reported:

Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and 
flashing cursor in top corner then stopped and started again with log in 
screen. As duel boot started laptop in Windows 10 and no problems so software 
problem. Reseached and found a fix which was putting in file,
  1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf"

Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "TearFree" "true"
EndSection  

This seems to have fixed the problem. I was running System Profile to watch 
Temps and also Mate System monitor with Firefox in the background. It did for a 
moment give a black screen but recovered so not sure if this was the problem 
resurfacing.
Without this being a duel boot I would have had great difficulty identifying if 
it was software or a overheating/grapics card problem. Most users would scrap 
their hardware if they were presented with this problem. Hopefully my problem 
is fixed but if not could you please advise me further.
All the Best
DAvid

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: MATE
Date: Wed Feb 15 12:00:06 2023
DistUpgraded: 2022-08-17 16:23:45,139 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 bcmwl/6.30.223.271+bdcom, 5.15.0-58-generic, x86_64: installed
 bcmwl/6.30.223.271+bdcom, 5.15.0-60-generic, x86_64: installed
 rtl8821ce/5.5.2.1, 5.15.0-60-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Continuously
GpuHangReproducibility: I don't know
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1179:ff50]
   Subsystem: Toshiba Corporation Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1179:ff50]
InstallationDate: Installed on 2021-08-21 (542 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
MachineType: TOSHIBA Satellite M300
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=UUID=98dc102b-f3cc-4067-b9a3-75250f24163c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-08-17 (181 days ago)
dmi.bios.date: 03/13/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.80
dmi.board.name: Satellite M300
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.80:bd03/13/2008:svnTOSHIBA:pnSatelliteM300:pvrPSMD0L-01N00M:rvnTOSHIBA:rnSatelliteM300:rvrNotApplicable:cvnTOSHIBA:ct1:cvrN/A:sku:
dmi.product.name: Satellite M300
dmi.product.version: PSMD0L-01N00M
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
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 jammy 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/2007381

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and 
flashing cursor in top corner then stopped and started again with log in 
screen. As duel boot started laptop in Windows 10 and no problems so software 
problem. Reseached and found a fix which was putting in file,
1 - Creating a file "/etc/X11/xorg.conf.d/20-intel.conf"

  Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "TearFree" "true"
   

[Touch-packages] [Bug 2003785] Re: apt source exact-source-package doesn't download the requested source package

[David Kalnischkies]

The idea is that a user will want to request the sources for a given
binary package – after all, that is the promise of GPL and co that you
can easily get the source for the binary you have installed. So for me
at least this binary-to-source mapping is very intuitive and I would be
very confused about your intuitive non-mapping.

Any way of handling can result in confusion every time a source and
binary package have the same name, but produce/include packages with
other names. A prime example used to be 'automake', but nowadays at
least that mess was cleaned up.

I don't think changing defaults would help here, especially not after ~25 years 
of operating in this way. I guess it might be more helpful to detect these 
collisions and have apt-get print/apt ask the user about it rather than 
assuming that one way or the other and an option to change it is intuitive for 
all users at all times.
Or, well, teach package maintainers that these collisions are a horrible idea. 
Preferably both. (Personally not going to work on either through in the 
foreseeable future.)

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

Title:
  apt source exact-source-package doesn't download the requested source
  package

Status in apt package in Ubuntu:
  New

Bug description:
  apt source exact-source-package doesn't download the right source
  package

  
  when specifying source package, i expect the exact source package to be 
downloaded.

  
  example:

  $ apt source linux-lowlatency => incorrectly downloads linux-meta-lowlatency
  $ apt source --only-source linux-lowlatency => is very counter intuitive but 
downloads linux-lowlatency source package

  Please default to downloading exact source package by default first,
  and offer binary->source resolution separately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003785/+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 1999981] [NEW] package libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1 failed to install/upgrade: triggers looping, abandoned

[David Brown]

Public bug reported:

System crash with several notifications during upgrade

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1
ProcVersionSignature: Ubuntu 5.17.0-1015.16-oem 5.17.15
Uname: Linux 5.17.0-1015-oem x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Dec 17 06:00:14 2022
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2021-08-14 (489 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to kinetic on 2022-12-17 (0 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kinetic

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

Title:
  package libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  System crash with several notifications during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1
  ProcVersionSignature: Ubuntu 5.17.0-1015.16-oem 5.17.15
  Uname: Linux 5.17.0-1015-oem x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Dec 17 06:00:14 2022
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2021-08-14 (489 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:amd64 2.42.9+dfsg-1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to kinetic on 2022-12-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/181/+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 1999979] [NEW] package ca-certificates 20211016ubuntu0.22.10.1 failed to install/upgrade: triggers looping, abandoned

[David Brown]

Public bug reported:

System crash with several notifications

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: ca-certificates 20211016ubuntu0.22.10.1
ProcVersionSignature: Ubuntu 5.17.0-1015.16-oem 5.17.15
Uname: Linux 5.17.0-1015-oem x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Dec 17 06:00:14 2022
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2021-08-14 (489 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: ca-certificates
Title: package ca-certificates 20211016ubuntu0.22.10.1 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to kinetic on 2022-12-17 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kinetic

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

Title:
  package ca-certificates 20211016ubuntu0.22.10.1 failed to
  install/upgrade: triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  System crash with several notifications

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: ca-certificates 20211016ubuntu0.22.10.1
  ProcVersionSignature: Ubuntu 5.17.0-1015.16-oem 5.17.15
  Uname: Linux 5.17.0-1015-oem x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sat Dec 17 06:00:14 2022
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2021-08-14 (489 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: ca-certificates
  Title: package ca-certificates 20211016ubuntu0.22.10.1 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to kinetic on 2022-12-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/179/+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 1998444] Re: Backport security fix for CVE-2022-3970

[David Fernandez Gonzalez]

The fix for CVE-2022-3970 has been released in the following versions:

Ubuntu 22.10: 4.4.0-4ubuntu3.2

Ubuntu 22.04 LTS: 4.3.0-6ubuntu0.3

Ubuntu 20.04 LTS: 4.1.0+git191117-2ubuntu0.20.04.7

Ubuntu 18.04 LTS: 4.0.9-5ubuntu0.9


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

** Changed in: tiff (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: tiff (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: tiff (Ubuntu Jammy)
   Status: New => Fix Released

** Changed in: tiff (Ubuntu Kinetic)
   Status: New => Fix Released

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

Title:
  Backport security fix for CVE-2022-3970

Status in tiff package in Ubuntu:
  Fix Released
Status in tiff source package in Bionic:
  Fix Released
Status in tiff source package in Focal:
  Fix Released
Status in tiff source package in Jammy:
  Fix Released
Status in tiff source package in Kinetic:
  Fix Released

Bug description:
  This CVE patch is desperately needed to fix a build failure caused by
  a crash in the testsuite of the current libreoffice/kinetic SRU

  Testing load 
file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff:
  *** stack smashing detected ***: terminated

  Fatal exception: Signal 6
  Stack:
  /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2]
  /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0]
  /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc]
  /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be]
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386]
  
/lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1]
  
/lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10]
  
/<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b]
  /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6]
  
/<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5]
  Aborted (core dumped)
  

[Touch-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970

[David Fernandez Gonzalez]

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

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

Title:
  Backport security fix for CVE-2022-3970

Status in tiff package in Ubuntu:
  In Progress
Status in tiff source package in Bionic:
  New
Status in tiff source package in Focal:
  New
Status in tiff source package in Jammy:
  New
Status in tiff source package in Kinetic:
  New

Bug description:
  This CVE patch is desperately needed to fix a build failure caused by
  a crash in the testsuite of the current libreoffice/kinetic SRU

  Testing load 
file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff:
  *** stack smashing detected ***: terminated

  Fatal exception: Signal 6
  Stack:
  /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2]
  /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0]
  /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc]
  /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be]
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386]
  
/lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1]
  
/lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10]
  
/<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b]
  /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6]
  
/<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5]
  Aborted (core dumped)
  make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: 
/<>/workdir/CppunitTest/vcl_filters_test.test] Error 134

  
  For the log of the failed amd64 kinetic archive build, see
  
https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181

  For the log of the successful amd64 kinetic PPA build with the updated tiff 
present, see
  
https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085


  Lunar already includes this fix with the last merge from debian
  

[Touch-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970

[David Fernandez Gonzalez]

** Changed in: tiff (Ubuntu)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

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

Title:
  Backport security fix for CVE-2022-3970

Status in tiff package in Ubuntu:
  New
Status in tiff source package in Bionic:
  New
Status in tiff source package in Focal:
  New
Status in tiff source package in Jammy:
  New
Status in tiff source package in Kinetic:
  New

Bug description:
  This CVE patch is desperately needed to fix a build failure caused by
  a crash in the testsuite of the current libreoffice/kinetic SRU

  Testing load 
file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff:
  *** stack smashing detected ***: terminated

  Fatal exception: Signal 6
  Stack:
  /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2]
  /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0]
  /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b]
  /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46]
  /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc]
  /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be]
  /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a]
  /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386]
  
/lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc]
  /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1]
  
/lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10]
  
/<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479]
  
/<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6]
  
/<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b]
  /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6]
  
/<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077]
  
/lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f]
  /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9]
  
/<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5]
  Aborted (core dumped)
  make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: 
/<>/workdir/CppunitTest/vcl_filters_test.test] Error 134

  
  For the log of the failed amd64 kinetic archive build, see
  
https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181

  For the log of the successful amd64 kinetic PPA build with the updated tiff 
present, see
  
https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/2488608

[Touch-packages] [Bug 1998169] Re: useradd command does not copy all of /etc/skel

[David Fernandez Gonzalez]

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

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

Title:
  useradd command does not copy all of /etc/skel

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  
  I know the useradd command is discouraged, but I wanted to report the bug to 
make the maintainers of the package aware.

  Recently there was an update of Ubuntu's passwd package which is
  sourced from shadow from version 4.8.1-1ubuntu5.20.04.2 to version
  4.8.1-1ubuntu5.20.04.3

  When using the useradd command, the /etc/skel directory with contents
  below, an only copies in one empty folder.

  
  ls -lah /etc/skel
  total 60K
  drwxrwxrwx  10 root user 4.0K Nov 28 18:33 .
  drwxr-xr-x 155 root root  12K Nov 28 19:12 ..
  drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .backgrounds
  -rwxrwxrwx   1 root user  220 Nov 28 18:23 .bash_logout
  -rwxrwxrwx   1 root user 3.7K Nov 28 18:23 .bashrc
  drwxrwxrwx   6 root user 4.0K Nov 28 18:23 .config
  drwxrwxrwx   3 root user 4.0K Nov 28 18:23 Desktop
  drwxrwxrwx   2 root user 4.0K Nov 28 18:30 .fonts_stuff
  drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .icons
  -rwxrwxrwx   1 root user  765 Nov 28 18:23 .profile
  drwxrwxrwx   2 root root 4.0K Nov 28 18:32 testfolderempty
  drwxrwxrwx   3 root user 4.0K Nov 28 18:23 .themes
  drwxrwxrwx  14 root user 4.0K Nov 28 18:23 WinAte
  
  ls -lah /home/user20
  total 12K
  drwx--  3 user20 user 4.0K Nov 28 19:12 .
  drwxr-xr-x 18 root   root 4.0K Nov 28 19:12 ..
  drwx--  2 user20 user 4.0K Nov 28 19:12 WinAte

  ls -lah /home/user20/WinAte/
  total 8.0K
  drwx-- 2 user20 user 4.0K Nov 28 19:12 .
  drwx-- 3 user20 user 4.0K Nov 28 19:12 ..

  
  I noticed in the strace calls for useradd that the kernel is returning the 
correct count of directories, but the useradd is clearly not copying all of 
them. Below is the strace output.
  

  strace useradd -k /etc/skel -g 900 -m -s /bin/bash -p a_password -c User20 
user20
  execve("/usr/sbin/useradd", ["useradd", "-k", "/etc/skel", "-g", "900", "-m", 
"-s", "/bin/bash", "-p", "P@ssw0rd!", "-c", "User20", "user20"], 0x7fffe10eba10 
/* 24 vars */) = 0
  brk(NULL)   = 0x5631ba1c2000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7fff0e47bab0) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=98383, ...}) = 0
  mmap(NULL, 98383, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fea9b7bf000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libaudit.so.1", O_RDONLY|O_CLOEXEC) = 
3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3407\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=133200, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fea9b7bd000
  mmap(NULL, 176296, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fea9b791000
  mprotect(0x7fea9b794000, 118784, PROT_NONE) = 0
  mmap(0x7fea9b794000, 32768, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fea9b794000
  mmap(0x7fea9b79c000, 81920, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0xb000) = 0x7fea9b79c000
  mmap(0x7fea9b7b1000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0x7fea9b7b1000
  mmap(0x7fea9b7b3000, 37032, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b7b3000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) 
= 3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@p\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=163200, ...}) = 0
  mmap(NULL, 174600, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fea9b766000
  mprotect(0x7fea9b76c000, 135168, PROT_NONE) = 0
  mmap(0x7fea9b76c000, 102400, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fea9b76c000
  mmap(0x7fea9b785000, 28672, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x1f000) = 0x7fea9b785000
  mmap(0x7fea9b78d000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26000) = 0x7fea9b78d000
  mmap(0x7fea9b78f000, 6664, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b78f000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libsemanage.so.1", 
O_RDONLY|O_CLOEXEC) = 3
  read(3, 

[Touch-packages] [Bug 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used

[David Fernandez Gonzalez]

** Changed in: usg
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: usg
   Status: New => In Progress

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in Ubuntu Security Guide:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/usg/+bug/1989731/+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 1965535] Re: Stop recommending snap

[David Megginson]

Please either stop using snap, or find a way to get the snap folder out
of my home directory.

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

Title:
  Stop recommending snap

Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Currently, ubuntu recommends installing snap by default, and some apps
  are slowly transitioning from DEB-based installation to Snap-based
  installation.

  APT is great, and facilitates having a clean, maintainable system.

  The snap project is not very well designed or engineered (just
  changing the location of where snap data is located is taking the
  project more than 5 years because it was hardcoded:
  https://bugs.launchpad.net/snapd/+bug/1575053). Snaps are large and
  VERY slow. The design of snap, as well as the way that decisions are
  made, are very questionable, and are receiving increasing amounts of
  criticism.

  I'd like to request that Ubuntu stops recommending snap, stops
  transitioning towards snaps, and we come back to defaulting to
  DEB/APT-based installation for all apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[David Kowis]

https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273

This one seems to have the full patch repair in the bug description.
None of the other bugs I've found relating to this have the full
solution.

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

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

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1981103] Re: System with DNS server in /etc/network/interfaces has bogus systemd-resolved config after upgrade to 22.04

[David Kowis]

https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273

This one seems to have the full patch repair in the bug description.
None of the other bugs I've found relating to this have the full
solution.

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

Title:
  System with DNS server in /etc/network/interfaces has bogus systemd-
  resolved config after  upgrade to 22.04

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  ifupdown:
Installed: 0.8.36+nmu1ubuntu3
Candidate: 0.8.36+nmu1ubuntu3
Version table:
   *** 0.8.36+nmu1ubuntu3 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  After upgrading a server with classic ifupdown configuration after
  reboot the machine had no valid dns servers anymore.

  The problem is that the state file created by ifupdown using
  /etc/network/if-up.d/resolved looks like this:

  root@pangaea-pm:~# cat /run/network/ifupdown-inet-ens13
  "DNS"="134.102.20.20 134.102.200.14"
  "DOMAINS"="marum.de"

  The script later sources this file and causes the following errors,
  easy to see when you execute this:

  root@pangaea-pm:~# ifdown ens13; ifup ens13
  /etc/network/if-down.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 12: mystatedir: not found
  /etc/network/if-up.d/resolved: 71: DNS: not found
  /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-ens13: 
DNS=134.102.20.20 134.102.200.14: not found
  /etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-ens13: 
DOMAINS=marum.de: not found
  Failed to parse DNS server address: DNS
  Failed to set DNS configuration: Invalid argument

  This happened to me on three different servers, so this is a serious
  bug and should be fixed before 22.04 upgrades are allowed for
  everybody. Most servers provided by data centers like Hetzner
  (Germany) are configure like that. After a do-release-upgrade you have
  no working DNS anymore, unless you disable systemd-resolved. I don't
  want to use netplan, so changing to this is no option.

  The fix is easy - remove the quotes in the script on the left side
  "$DNS" => $DNS; same for DOMAINS:

  if  [ -n "$NEW_DNS" ]; then
  cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DNS="$NEW_DNS"
  EOF
  if  [ -n "$NEW_DOMAINS" ]; then
  cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
  $DOMAINS="$NEW_DOMAINS"
  EOF
  fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1981103/+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 1993084] Re: libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

[Keith David Bershatsky]

Thank you both for helping me to create a more detailed report of the
issue.  I was unable to duplicate the error using a fresh installation
of Ubuntu 22.04.1 LTS; i.e., using a fresh install of the OS, `sudo apt
install libkrb5-dev` succeeded without any issue.  Using a current
installation with lots of other stuff, however, still refuses to
install.  The output from the terminal and also from
`/var/log/apt/term.log` combined is only about 77 lines, so I'm just
pasting the combined output here:

{{{
### Output from the terminal:

Preparing to unpack .../2-libkadm5srv-mit12_1.19.2-2_amd64.deb ...
Unpacking libkadm5srv-mit12:amd64 (1.19.2-2) ...
Selecting previously unselected package libkadm5clnt-mit12:amd64.
Preparing to unpack .../3-libkadm5clnt-mit12_1.19.2-2_amd64.deb ...
Unpacking libkadm5clnt-mit12:amd64 (1.19.2-2) ...
Selecting previously unselected package comerr-dev:amd64.
Preparing to unpack .../4-comerr-dev_2.1-1.46.5-2ubuntu1.1_amd64.deb ...
Unpacking comerr-dev:amd64 (2.1-1.46.5-2ubuntu1.1) ...
Selecting previously unselected package krb5-multidev:amd64.
Preparing to unpack .../5-krb5-multidev_1.19.2-2_amd64.deb ...
Unpacking krb5-multidev:amd64 (1.19.2-2) ...
dpkg: error processing archive /tmp/apt-dpkg-install-UsJRPe/5-krb5-multidev_1.19
.2-2_amd64.deb (--unpack):
 trying to overwrite shared '/usr/bin/krb5-config.mit', which is different from 
other instances of package krb5-multidev:amd64
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package libkrb5-dev:amd64.
Preparing to unpack .../6-libkrb5-dev_1.19.2-2_amd64.deb ...
Unpacking libkrb5-dev:amd64 (1.19.2-2) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-UsJRPe/5-krb5-multidev_1.19.2-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
lawlist@lawlist-VirtualBox:~$ 

==
### excerpt from /var/log/apt/term.log

Log started: 2022-10-17  14:25:29
Selecting previously unselected package libgssrpc4:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 286291 files and directories currently installed.)
Preparing to unpack .../0-libgssrpc4_1.19.2-2_amd64.deb ...
Unpacking libgssrpc4:amd64 (1.19.2-2) ...
Selecting previously unselected package libkdb5-10:amd64.
Preparing to unpack .../1-libkdb5-10_1.19.2-2_amd64.deb ...
Unpacking libkdb5-10:amd64 (1.19.2-2) ...
Selecting previously unselected package libkadm5srv-mit12:amd64.
Preparing to unpack .../2-libkadm5srv-mit12_1.19.2-2_amd64.deb ...
Unpacking libkadm5srv-mit12:amd64 (1.19.2-2) ...
Selecting previously unselected package libkadm5clnt-mit12:amd64.
Preparing to unpack .../3-libkadm5clnt-mit12_1.19.2-2_amd64.deb ...
Unpacking libkadm5clnt-mit12:amd64 (1.19.2-2) ...
Selecting previously unselected package comerr-dev:amd64.
Preparing to unpack .../4-comerr-dev_2.1-1.46.5-2ubuntu1.1_amd64.deb ...
Unpacking comerr-dev:amd64 (2.1-1.46.5-2ubuntu1.1) ...
Selecting previously unselected package krb5-multidev:amd64.
Preparing to unpack .../5-krb5-multidev_1.19.2-2_amd64.deb ...
Unpacking krb5-multidev:amd64 (1.19.2-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-UsJRPe/5-krb5-multidev_1.19.2-2_amd64.deb (--unpack):
 trying to overwrite shared '/usr/bin/krb5-config.mit', which is different from 
other instances of package krb5-multidev:amd64
dpkg-deb: error: paste subprocess was killed by signal 
(Broken pipe)
Selecting previously unselected package libkrb5-dev:amd64.
Preparing to unpack .../6-libkrb5-dev_1.19.2-2_amd64.deb ...
Unpacking libkrb5-dev:amd64 (1.19.2-2) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-UsJRPe/5-krb5-multidev_1.19.2-2_amd64.deb
Log ended: 2022-10-17  14:25:31
}}}

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

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this 

[Touch-packages] [Bug 1993084] [NEW] libkrb5-dev: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

[Keith David Bershatsky]

Public bug reported:

Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

Installation fails with this message:

dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

I had tried to install this package as a dependency of building Wine
from source:

configure: libkrb5 32-bit/64-bit development files not found (or too
old), Kerberos won't be supported.

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

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

Title:
  libkrb5-dev:  dpkg-deb: error: paste subprocess was killed by signal
  (Broken pipe)

Status in krb5 package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.1 LTS:  sudo apt install libkrb5-dev

  Installation fails with this message:

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  I had tried to install this package as a dependency of building Wine
  from source:

  configure: libkrb5 32-bit/64-bit development files not found (or too
  old), Kerberos won't be supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1993084/+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 1979352] Re: system frozen after sleep

[David Iterton]

Maybe related to this https://github.com/mate-desktop/mate-
desktop/issues/519

** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519
   https://github.com/mate-desktop/mate-desktop/issues/519

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

Title:
  system frozen after sleep

Status in Ubuntu MATE:
  Confirmed
Status in acpid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Linux V330 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC
  2022 x86_64 x86_64 x86_64 GNU/Linux

  This is a bug that I reported with Ubuntu Mate 20.04 if I remember correctly 
but, at that time it was only apparent when I was using video ripping software 
on separate laptops and only when the machines became idle once the ripping 
program had finished.
  I don't think this bug was ever fixed and so I'm returning to it because I 
left my laptop in sleep mode over meal time to come back to a frozen system. I 
was not using the video ripping program this time, just surfing the Net. No 
other program was open.

  I run a Lenovo i7 V330-151KB and a Lenovo i5 Z50 but, the bug has
  happened when using an old Dell 1530 laptop.

  I do not believe I am unique in having this bug as someone has a
  similar bug when they have minimised Google Chrome and their system
  had went to sleep. I was also using Chrome this time but, as I have
  already said I was having this happen using another program and not
  using Chrome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1979352/+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 1981622] Re: mtd device must be supplied (device name is empty)

[David Robert Lewis]

Same here, recent upgrade message appears.

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy

[David Fernandez Gonzalez]

New security versions of tiff have been released for focal and bionic.
These versions provide the corresponding fixes for CVE-2022-0907,
CVE-2022-0908, CVE-2022-0909, CVE-2022-0924 and CVE-2022-22844.

https://ubuntu.com/security/notices/USN-5523-2

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

Title:
  Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy

Status in tiff package in Ubuntu:
  In Progress

Bug description:
  The versions in Trusty, Xenial, Bionic, Focal and Jammy may be
  vulnerable to all CVEs below.

  Debian released an advisory on March 24.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[David Zuelke]

Does this mean the fix will remain in Kinetic, though?

Should it not be reverted there, then?

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

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

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1979639/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[David Fontenot]

I forgot to add SYSTEM INFO:

$ cat /proc/version
Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 
11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP 
Thu Aug 4 18:03:25 UTC 2022

$ uname -r
5.15.0-46-generic

$ hostnamectl | grep Kernel
Kernel: Linux 5.15.0-46-generic

$ sudo lscpu
Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 39 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  8
  On-line CPU(s) list:   0-7
Vendor ID:   GenuineIntel
  Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[David Fontenot]

I upgraded to Ubuntu 22.04 yesterday and this bug now affects me.

Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and
its been like that since day 1 of the install.

In both versions of the operating system, when using a browser to right-
click a file and "save as", the Save As Dialogue box does not get focus.
This means, you can't just type the name of the file you want, you have
to force focus on the Save As Dialogue box to use it by clicking it.

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 1986480] [NEW] package linux-firmware 1.187.33 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[David Martelle]

Public bug reported:

Terminal copy;

(1) david@FPA-Admin2:~$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

(2) david@FPA-Admin2:~$ apt-cache policy pkgname
N: Unable to locate package pkgname

(3) What I expected was; the update to complete successfully
(4) What happened instead was; it failed  

Terminal Log follows:

David@FPA-Admin2:~$ sudo apt update
[sudo] password for david: 
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease  
Hit:3 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease   
Hit:5 http://archive.canonical.com/ubuntu focal InRelease
Reading package lists... Done
Building dependency tree   
Reading state information... Done
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
david@FPA-Admin2:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-5.15.0-46-generic linux-hwe-5.15-headers-5.15.0-46
  linux-image-5.15.0-46-generic linux-modules-5.15.0-46-generic
  linux-modules-extra-5.15.0-46-generic
The following packages will be upgraded:
  isc-dhcp-client isc-dhcp-common libnetplan0 linux-firmware
  linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04
  linux-image-generic-hwe-20.04 linux-libc-dev netplan.io unattended-upgrades
  update-notifier update-notifier-common
12 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
4 standard security updates
Need to get 231 MB of archives.
After this operation, 586 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
update-notifier amd64 3.192.30.11 [56.6 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
update-notifier-common all 3.192.30.11 [133 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
isc-dhcp-client amd64 4.4.1-2.1ubuntu5.20.04.3 [246 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
isc-dhcp-common amd64 4.4.1-2.1ubuntu5.20.04.3 [44.9 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 netplan.io 
amd64 0.104-0ubuntu2~20.04.2 [88.0 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 libnetplan0 
amd64 0.104-0ubuntu2~20.04.2 [82.5 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-firmware all 1.187.33 [125 MB]
Get:8 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-5.15.0-46-generic amd64 5.15.0-46.49~20.04.1 [20.5 MB]
Get:9 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-5.15.0-46-generic amd64 5.15.0-46.49~20.04.1 [11.3 MB]
Get:10 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-modules-extra-5.15.0-46-generic amd64 5.15.0-46.49~20.04.1 [57.8 MB]
Get:11 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-generic-hwe-20.04 amd64 5.15.0.46.49~20.04.16 [1,928 B]
Get:12 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-image-generic-hwe-20.04 amd64 5.15.0.46.49~20.04.16 [2,700 B]
Get:13 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-hwe-5.15-headers-5.15.0-46 all 5.15.0-46.49~20.04.1 [12.0 MB]
Get:14 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-5.15.0-46-generic amd64 5.15.0-46.49~20.04.1 [2,776 kB]
Get:15 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-headers-generic-hwe-20.04 amd64 5.15.0.46.49~20.04.16 [2,592 B]
Get:16 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
linux-libc-dev amd64 5.4.0-124.140 [1,104 kB]
Get:17 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
unattended-upgrades all 2.3ubuntu0.3 [48.5 kB]
Fetched 231 MB in 44s (5,289 kB/s) 
Requesting to save current system state
ERROR couldn't save system state: Minimum free space to take a snapshot and 
preserve ZFS performance is 20%.
Free space on pool "bpool" is 13%.
Please remove some states manually to free up space. 
Preconfiguring packages ...
(Reading database ... 190357 files and directories currently installed.)
Preparing to unpack .../00-update-notifier_3.192.30.11_amd64.deb ...
Unpacking update-notifier (3.192.30.11) over (3.192.30.10) ...
Preparing to unpack .../01-update-notifier-common_3.192.30.11_all.deb ...
Unpacking update-notifier-common (3.192.30.11) over (3.192.30.10) ...
Preparing to unpack .../02-isc-dhcp-client_4.4.1-2.1ubuntu5.20.04.3_amd64.deb ..
.
Unpacking isc-dhcp-client (4.4.1-2.1ubuntu5.20.04.3) over (4.4.1-2.1ubuntu5.20.0
4.2) ...
Preparing to unpack .../03-isc-dhcp-common_4.4.1-2.1ubuntu5.20.04.3_amd64.deb ..
.
Unpacking isc-dhcp-com

[Touch-packages] [Bug 1969709] Re: libreoffice font selection unusably slow

[David White]

I have a feeling this is something to do with the Nvidia driver. I first
noticed this on my desktop PC which was using Mint 20 (based on Ubuntu
20.04), and the "Fresh" PPA of Libreoffice 7.3. I recently moved to Mint
21, based on Ubuntu 22.04. Mindful of this lagging issue in the font
selection box, I tested the Mint 21 live USB, which comes with
Libreoffice 21. There was no lag when booting from the USB; the font
selection box scrolled normally. However, once Mint 21 was installed,
and the Nvidia driver was installed from Driver Manager and used instead
of Nouveau, then sure enough the font selection box started lagging
again.

I also experience no lagging on Mint 21 on my laptop, which is using the
built-in Intel graphics chip. So I think this is some sort of rendering
issue caused by Nvidia. Try it yourself; try booting into a Live USB of
Ubuntu 22.04, make sure the graphics driver is still just Nouveau, and
you should find the font selection box works normally.

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

Title:
  libreoffice font selection unusably slow

Status in fontconfig package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[David Zuelke]

(older Node.js versions didn't get updates, but they're all EOL).

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1979639/+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 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[David Zuelke]

It's fixed upstream in Node.js already; versions 14.20 and 16.16 (18.x
was never affected).

I'm now inclined to agree this shouldn't be ported from Debian (and
reverted in Kinetic).

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  While the default configuration works fine for every package that uses the 
system libssl3, libssl1.1.1 (which implicitly loads the configuration on 
OPENSSL_crypto_init()) fails to parse it.

  Our nodejs package vendors openssl 1.1.1, which means it will trigger this 
bug. In addition, upstream NodeJS explicitly points their statically-linked 
OpenSSL to this file as well, and ships 1.1.1 in their current LTS (branch 
16.x).
  Finally, we can also expect breakage for third-party packages that still 
depends on libssl1.1.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1979639/+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 1982563] [NEW] sbat-distro should be set

[Valentin David]

Public bug reported:

-Dsbat-distro should be set so that the systemd efi stub gets a .sbat
section. This is needed for secure boot.

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

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

Title:
  sbat-distro should be set

Status in systemd package in Ubuntu:
  New

Bug description:
  -Dsbat-distro should be set so that the systemd efi stub gets a .sbat
  section. This is needed for secure boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982563/+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 1928733] Re: Starting systemd Network Service fails with "Invalid argument"

[David Cunningham]

What version is this fix in please? Just asking as i was reported back
in May 2021. Thanks.

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

Title:
  Starting systemd Network Service fails with "Invalid argument"

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Triaged
Status in systemd source package in Focal:
  Triaged
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  This server has a new install of Ubuntu 18.04 server. Sometimes
  (around 50% of the time) when it boots systemd-networkd.service
  initially fails to start with an error as below. It then tries again
  and succeeds, however other services which depend on systemd-networkd
  have already failed on the dependency by then.

  From the output of "journalctl -u systemd-networkd":

  -- Reboot --
  May 17 19:44:28 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to 
set up mount namespacing: Invalid argument
  May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at 
step NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process 
exited, code=exited, status=226/NAMESPACE
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with 
result 'exit-code'.
  May 17 19:44:30 server1 systemd[1]: Failed to start Network Service.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
  May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled 
restart job, restart counter is at 1.
  May 17 19:44:30 server1 systemd[1]: Stopped Network Service.
  May 17 19:44:30 server1 systemd[1]: Starting Network Service...
  May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed
  May 17 19:44:30 server1 systemd[1]: Started Network Service.
  May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by 
us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully 
enabled
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
  May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
  May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP
  May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP
  May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier
  May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL
  May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL
  May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.46
  ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon May 17 19:53:11 2021
  InstallationDate: Installed on 2021-03-18 (60 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1604:10c0 Tascam 
   Bus 001 Device 003: ID 1604:10c0 Tascam 
   Bus 001 Device 002: ID 1604:10c0 Tascam 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 
transparent_hugepage=never
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.9.3
  dmi.board.name: 04JN2K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R440
  dmi.sys.vendor: Dell 

[Touch-packages] [Bug 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[David Zuelke]

So I think a big class of programs to consider that are affected by this
potentially are those that use a statically linked OpenSSL v1, not just
Node.js or any leftover programs that dynamically link against
libssl1.1.

And that's... a lot of software off the internet ;)

If it indeed is the case that OpenSSL falls back to the exact default
behavior the current config specifies in its sections if those sections
aren't there, then IMO the backport still makes a lot of sense.

Anyway... it appears as though Node.js have fixed this as a side-effect
of their recent update:
https://nodejs.org/en/blog/vulnerability/july-2022-security-
releases/#dll-hijacking-on-windows-high-cve-2022-32223

I was able to verify that the latest 14.20 and 16.16 releases work fine.

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

Status in nodejs package in Ubuntu:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in nodejs source package in Jammy:
  Confirmed
Status in openssl source package in Jammy:
  Incomplete
Status in nodejs source package in Kinetic:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact] 
  While the default configuration works fine for every package that uses the 
system libssl3, any software that uses libssl1.1, either separately packaged 
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive) 
will fail to load the configuration as they don't have any notion of providers.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

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


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

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

[David Röthlisberger]

@seb128 Does this still need additional testing? See comments #11 & #12.

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

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

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

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

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

  [Test case]

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

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

  for example, on focal:

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

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

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

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

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

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

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

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

  It works with apt 2.0.6.

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


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

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

[David Röthlisberger]

P.S. I have worked around this in my build system (by creating an empty
executable script at the location that apt.postinst is expecting before
I call dpkg --configure) so I'm not worried. When I reported this I
didn't realise it wouldn't affect debootstrap.

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

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

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

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

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

  [Test case]

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

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

  for example, on focal:

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

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

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

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

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

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

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

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

  It works with apt 2.0.6.

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


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

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

[David Röthlisberger]

> Which tool were you using to bootstrap your system?

My own build system (which I wrote about for LWN:
https://lwn.net/Articles/821367/ ).

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

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

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

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

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

  [Test case]

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

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

  for example, on focal:

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

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

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

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

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

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

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

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

  It works with apt 2.0.6.

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


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

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

[David Kalnischkies]

jftr: I removed this if in git commit
938889b20268ec92be1bff67750f7adf03f52c1b, which was shipped with 2.1.12
– that might explain why it isn't effecting releases with later versions
and why it was missed.

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

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

Status in apt package in Ubuntu:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New

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

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

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

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

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

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

  It works with apt 2.0.6.

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


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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

[David Röthlisberger]

Raised #1974456.

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

Title:
  Only keep 2 kernels

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

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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


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

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

[David Röthlisberger]

Public bug reported:

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

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

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

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

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

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

It works with apt 2.0.6.

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

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

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

Status in apt package in Ubuntu:
  New

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

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

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

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

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

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

  It works with apt 2.0.6.

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


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

[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

[David Röthlisberger]

This is causing me trouble building a focal (20.04) userspace from
scratch:

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

It works with apt 2.0.6.

I think it's because the patch[1] removes `/etc/kernel/postinst.d/apt-
auto-removal`:

diff --git a/debian/rules b/debian/rules
index 7997739..8a110f7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -29,7 +29,6 @@ override_dh_install-arch:
dh_install -papt -Xmethods/curl -Xmethods/curl+https -Xmethods/curl+http
dh_install --remaining
install -m 644 debian/apt.conf.autoremove 
debian/apt/etc/apt/apt.conf.d/01autoremove
-   install -m 755 debian/apt.auto-removal.sh 
debian/apt/etc/kernel/postinst.d/apt-auto-removal
 
 override_dh_gencontrol:
dh_gencontrol -- -Vapt:keyring="$(shell ./vendor/getinfo 
keyring-package)"

...but `apt.postinst` still contains this:

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

Since I'm building this from scratch, "$2" (the most-recently-
configured-version) is empty, and `dpkg --compare-versions lt` returns
true.


[1]: 
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

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

Title:
  Only keep 2 kernels

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

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+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 1878617] Re: Apple pages file type should be added to MIME types

[David D Lowe]

A fix was released upstream in shared-mime-info 2.2 (2022-03-27). Sadly,
this didn't make it to Ubuntu 22.04 LTS.

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

Title:
  Apple pages file type should be added to MIME types

Status in shared-mime-info:
  Unknown
Status in mime-support package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1878617/+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 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and Jammy

[David Fernandez Gonzalez]

Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562,
CVE-2022-0865 and CVE-2022-0891 are now released and available.
(https://ubuntu.com/security/notices/USN-5421-1).

Jammy is currently at version 4.3.0-6 which includes the patch for
CVE-2022-0865 as it was introduced in 4.3.0-5.

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

Title:
  Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal, Impish and
  Jammy

Status in tiff package in Ubuntu:
  In Progress

Bug description:
  The versions in Trusty, Xenial, Bionic, Focal and Impish may be
  vulnerable to all CVEs below.

  The version in Jammy is vulnerable to CVE-2022-0865.

  Debian released an advisory on March 24.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+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 349943] Re: Screen blinks randomly on external monitor

[David Johnston]

Adding 
GRUB_GFXMODE=1920x1080
to /etc/default/grub, running update-grub, and rebooting fixed this for me.

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

Title:
  Screen blinks randomly on external monitor

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  Hardware: Asus F8Va laptop (Core 2 Duo P8600, ATI HD3650, 1440x900)
  OS: Ubuntu 9.04 beta x64 (Wubi installation inside Windows Vista Home Premium 
x64 SP1)

  External monitor (Samsung SyncMaster 2493HM, 1920x1200), connected via HDMI, 
blinks several times a minute, randomly. When there is no user activity, it 
doesn't seem to blink however.
  By "blinking" I mean, the monitor goes off and then on, like it usually does 
when it changes resolution, only resolution doesn't change. Also, when I move 
windows around, thin horizontal stripes flash in fraction of second from time 
to time (only on external monitor).

  Screen configuration:

  Samsung 24": On
  Resolution: 1920x1200
  Refresh rate: 60 Hz
  Rotation: Normal

  Laptop 14": On
  Resolution: 1440x900
  Refresh rate: 67 Hz
  Rotation: Normal

  Mirror screens: unchecked

  Relative position of screens (physical and in Display Preferences)
  laptop screen below the external screen, centred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/349943/+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 1968876] Re: ssh-agent: Error connecting to agent: Connection refused

[David Michael Pick]

I have been having the same problem without the involvement of git.

Raspberry Pi 4, 4GB, upgraded to Ubuntu 22.04 from 21.10. Same commands 
worked with 21.10 that fail with 22.04.

Boot machine. Login, and this starts an agent, but I'm not sure if it's 
actually ssh-agent or if it's the Gnome version. Open terminal window. 
add keys to the agent using ssh-add. Open another terminal window and 
try to use slogin to another machine. Get the eerror message.

The very first time it happened a popup appeared about the ssh-agent 
crashing and asking if I wanted to send a diagnostic dump to Ububtu. I 
dis. Didn't get asked this subsequent times.

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

Title:
  ssh-agent: Error connecting to agent: Connection refused

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh 1:8.9p1-3
  Architecture: arm64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE

  raspberry pi 4. The keys are added, but for example, when cloning a
  repository via ssh, the ssh agent crashes, restarting does not help,
  the repository is not cloned. When launch the command ssh-add -L Error
  connecting to agent: Connection refused. I rolled back to the package
  version 1: 8.8p1-1 and everything works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+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 1970110] Re: downloaded packages are removed just after installation

[David Kalnischkies]

apt 1.2~exp1 came with the follow NEWS entry:
  [ Automatic removal of debs after install ]
  After packages are successfully installed by apt(8),
  the corresponding .deb package files will be
  removed from the /var/cache/apt/archives cache directory.

  This can be changed by setting the apt configuration option
"Binary::apt::APT::Keep-Downloaded-Packages" to "true". E.g:

  # echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \
  > /etc/apt/apt.conf.d/01keep-debs

  Please note that the behavior of apt-get is unchanged. The
  downloaded debs will be kept in the cache directory after they
  are installed. To enable the behavior for other tools, you can set
  "APT::Keep-Downloaded-Packages" to false.

If you have disabled this feature you can do manual maintenance with the
`autoclean` and `clean` commands. More automatic maintenance can be
achieved with our cronjob, see `/usr/lib/apt/apt.systemd.daily`for
details, which can e.g. be configured to remove files after a few days
as you seem to prefer here.

As this default behavior is a deliberate choice and there are various
options to change this I am closing this report as not a bug.

** Changed in: apt (Ubuntu)
   Status: New => Opinion

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

Title:
  downloaded packages are removed just after installation

Status in apt package in Ubuntu:
  Opinion

Bug description:
  When installing a package with 'apt install [package name]', I see the deb 
files which appear in /var/cache/apt/archives.
  However, just after installation, the deb file are deleted from this 
directory.
  I would prefer a deletion after a few days. Sometimes, we install/uninstall 
and reinstall.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.5
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Apr 24 16:10:48 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1970110/+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 1952107] Re: Google Contacts API Deprecated

[David Johnston]

Any chance this will get fixed in focal?

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1959508] Re: enable BMFF support in exiv2

[David H]

Many thanks!

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

Title:
  enable BMFF support in exiv2

Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that
  Ubuntu 22.04 currently includes exiv2 0.27.3

  Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3
  file format has been the Canon camera-raw file format since mid 2018,
  and is probably one of the most common raw image file formats today.
  Applications such as darktable, amongst others, use exiv2 to extract
  image metadata, thumbnails and previews, and can only open CR3 files
  when linked with exiv2 0.27.5 or later.

  Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On
  to enable *.CR3 support.

  Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled
  included in Ubuntu 22.04?

  Note that a similar request exists for Debian in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788

  References
  https://github.com/exiv2/exiv2#2-19
  https://github.com/Exiv2/exiv2/issues/1229
  https://github.com/darktable-org/darktable/pull/10332
  https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918
  https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+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 1967651] [NEW] jammy beta xorg no kb / mouse

[David Lang]

Public bug reported:

after updating to jammy beta, xorg does not work for any desktop, in
every case the desktop comes up, but there is no response to keyboard or
mouse (not even numlock). I tried unplugging and replugging the devices
with no luck.

All desktops do 'work' in the wayland version, but the display flashes
frequently, showing parts of other windows

ubuntu=bug gathers information, but does not open the browser window
after reporting that it's uploaded the data.

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

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

Title:
  jammy beta xorg no kb / mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  after updating to jammy beta, xorg does not work for any desktop, in
  every case the desktop comes up, but there is no response to keyboard
  or mouse (not even numlock). I tried unplugging and replugging the
  devices with no luck.

  All desktops do 'work' in the wayland version, but the display flashes
  frequently, showing parts of other windows

  ubuntu=bug gathers information, but does not open the browser window
  after reporting that it's uploaded the data.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967651/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

[David Ober]

Following instruction in forwarded email after appling the alsa-ucm-
conf=1.2.2-1ubuntu0.12sutton1 package the rear microphone jack works
correctly

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Confirmed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1965960] Re: apt installs snap packages

[David Kalnischkies]

fwiw it is "invalid" here as apt has nothing to do with it, as it did
what it is supposed to do, upgrade a package: It has no business in the
contents, similar to a parcel deliverer. It is probably more productive
you figure out what exactly is not working in foo.deb vs. foo.snap and
report this to foo (or snap) so it can be worked on and perhaps fixed.
Currently, you are angrily complaining to your old parcel deliverer that
they brought you a letter informing you that the next letter will come
with a different parcel deliverer.

(Disclaimer: Not an Ubuntu dev, not even a user, but one of the devs of
apt itself reading "downstream" bug reports)

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

Title:
  apt installs snap packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  $ apt-cache policy apt
  apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
   *** 2.4.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) I expected to dist-upgrade my system, running apt-get dist-upgrade

  4) apt tried to install firefox from snap. I naturally aborted the upgrade, 
if I want a snap package I install it with snap, I use apt to install 
debian/apt packages.
  Aborting the install essentially broke my system. Trying to repair it, and 
installing firefox using apt again, hence getting force-fed the snap of 
firefox, broke my install, too, as the snap cannot access my firefox 
configuration files (for good reasons).
  It took me half a day to repair the system and switch to a PPA to keep the 
system (and Ubuntu with its intended processes - apt for deb, snap for snap, 
probably flatpaks and whatever for other stuff  - for that matter) running.

  In summary: We know you love snap. We use snap for certain purposes, and apt 
for others. Please don't force your love for snap on us, snaps constantly break 
long-running systems and require careful introduction.
   
  The proper solution could have been to stop supporting firefox from apt, so 
we have to consciously deal with the situation - without getting our systems 
broken.

  Thanks ❤️

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 22 16:26:47 2022
  InstallationDate: Installed on 2022-03-07 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1965960/+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 1965820] [NEW] Screen goes black when opening Settings, following error appears

[David]

Public bug reported:

Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: Unhandled promise rejection. 
To suppress this warning, add an error handler to your promise chain with 
.catch() or a try-catch block around your await expression. Stack trace of the 
failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34#012  
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14
Mar 21 20:56:03 Ubuntu-desktop gnome-shell[2287]: message repeated 8 times: [ 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:#012  
_loadFile@resource:///org/gnome/shell/ui/background.js:503:20#012  
_load@resource:///org/gnome/shell/ui/background.js:533:14#012  
_init@resource:///org/gnome/shell/ui/background.js:282:14#012  
Background@resource:///org/gnome/shell/ui/background.js:237:4#012  
getBackground@resource:///org/gnome/shell/ui/background.js:624:30#012  
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49#012  
BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37#012  
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25#012  
_updateBackgrounds@resource:///o]

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  470.103.01  Thu Jan  6 
12:10:04 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 21 20:57:30 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GA104 [GeForce RTX 3070 Lite Hash 
Rate] [1458:404c]
InstallationDate: Installed on 2022-03-16 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
MachineType: Gigabyte Technology Co., Ltd. B550 AORUS MASTER
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=f0d454f1-0a2b-48a3-b6ff-6ba06e951a1b ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F13h
dmi.board.asset.tag: Default string
dmi.board.name: B550 AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF13h:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSMASTER:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B550 MB
dmi.product.name: B550 AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.3.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Touch-packages] [Bug 1965683] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[David Martelle]

Public bug reported:

Processing triggers for initramfs-tools (0.136ubuntu6.7) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-104-generic
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-104-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Processing triggers for libc-bin (2.31-0ubuntu9.7) ...
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
Uname: Linux 5.4.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Mar 20 11:55:14 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-09-19 (1643 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-07-10 (618 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Processing triggers for initramfs-tools (0.136ubuntu6.7) ...
  update-initramfs: Generating /boot/initrd.img-5.4.0-104-generic
  Error 24 : Write error : cannot write compressed block 
  E: mkinitramfs failure cpio 141 lz4 -9 -l 24
  update-initramfs: failed for /boot/initrd.img-5.4.0-104-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned 
  error exit status 1
  Processing triggers for libc-bin (2.31-0ubuntu9.7) ...
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
  Uname: Linux 5.4.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Mar 20 11:55:14 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-09-19 (1643 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-07-10 (618 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1965683/+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 236956] Re: sane devices should not be managed by consolekit

[David Ward]

https://jff.email/cgit/sane-
backends.git/tree/debian/libsane1.README.Debian (under "SETUP")

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

Title:
  sane devices should not be managed by consolekit

Status in consolekit package in Ubuntu:
  Invalid
Status in sane-backends package in Ubuntu:
  Fix Released

Bug description:
  In hardy, USB scanners are managed differently than in previous
  releases of Ubuntu.

  Before hardy, there was a udev rules assigning to the "scanner" group
  all the usb devices that appeared to be scanners under comparison to
  the /etc/udev/rules.d/45-libsane.rules.

  Now, that file is no more, and the access to the usb scanners is
  controlled by HAL+Consolekit.

  The result is that only the user who is sitting at the console has
  permission to use the scanner, since the usb devices now get owned by
  root, with a special ACL allowing access to the console user.

  This is a very very wrong thing to do.

  The beauty of sane is that it can work over the network.  But with
  "hardy" it cannot anymore: there is no possibility to set up a scanner
  server.

  Saned is supposed to be run via xinetd as the saned user. But with the 
current setup, the saned user cannot access the scanner, since only the current 
console user and root can. It is not possible to tell xinetd that saned should 
be run as "the current console user". And in fact there might be no current 
console user at all.
  Nor it is possible to tell xinetd that saned should be run as root, because 
this is just too bad from a security point of view.

  What makes the matter worse is that putting the 45-libsane.rules from
  gutsy back in place does not help.

  So, with the current consolekit thing, sane is not sane anymore, and
  can only be run from the console (a la Twain) and not as a server.

  Please, rethink about console kit and scanners.  Consolekit is a very
  desktop-centric thing, assuming that most pluggable peripherals should
  be owned by the person at the console. But this is generally not true
  of anything that can be shared on the network. Things that can be
  shared should be independent from the console user. Please go back to
  treating scanners with a dedicated system user or group owning them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/236956/+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 236956] Re: sane devices should not be managed by consolekit

[David Ward]

https://jff.email/cgit/sane-
backends.git/tree/debian/libsane1.README.Debian (under "SETUP")

** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  sane devices should not be managed by consolekit

Status in consolekit package in Ubuntu:
  Invalid
Status in sane-backends package in Ubuntu:
  Fix Released

Bug description:
  In hardy, USB scanners are managed differently than in previous
  releases of Ubuntu.

  Before hardy, there was a udev rules assigning to the "scanner" group
  all the usb devices that appeared to be scanners under comparison to
  the /etc/udev/rules.d/45-libsane.rules.

  Now, that file is no more, and the access to the usb scanners is
  controlled by HAL+Consolekit.

  The result is that only the user who is sitting at the console has
  permission to use the scanner, since the usb devices now get owned by
  root, with a special ACL allowing access to the console user.

  This is a very very wrong thing to do.

  The beauty of sane is that it can work over the network.  But with
  "hardy" it cannot anymore: there is no possibility to set up a scanner
  server.

  Saned is supposed to be run via xinetd as the saned user. But with the 
current setup, the saned user cannot access the scanner, since only the current 
console user and root can. It is not possible to tell xinetd that saned should 
be run as "the current console user". And in fact there might be no current 
console user at all.
  Nor it is possible to tell xinetd that saned should be run as root, because 
this is just too bad from a security point of view.

  What makes the matter worse is that putting the 45-libsane.rules from
  gutsy back in place does not help.

  So, with the current consolekit thing, sane is not sane anymore, and
  can only be run from the console (a la Twain) and not as a server.

  Please, rethink about console kit and scanners.  Consolekit is a very
  desktop-centric thing, assuming that most pluggable peripherals should
  be owned by the person at the console. But this is generally not true
  of anything that can be shared on the network. Things that can be
  shared should be independent from the console user. Please go back to
  treating scanners with a dedicated system user or group owning them.

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