date:20220712

[Touch-packages] [Bug 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy

2022-07-12 Thread Launchpad Bug Tracker

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Confirmed

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

Title:
  dhclient overriding stub-resolv.conf file on Jammy

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  [Issue]
  On Jammy, the stub-resolv.conf file on /run/systemd/resolve gets overwritten 
if dhclient is executed.

  While debugging this, I found the reference on LP#1889068 [0] of the
  move of `resolved` hook from dhclient-enter-hooks.d/ to dhclient-exit-
  hooks.d/, and this new hook [2] has no reference of make_resolv_conf()
  being called.

  [Reproducer]
  -
  I used a cloud-image based Jammy installation (uvt-kvm).  Once in:

  $ cat /run/system/resolve/stub-resolv.conf

  And one will see:

  nameserver 127.0.0.53
  options edns0 trust-ad
  search .

  Then:

  $ sudo dhclient
  $ cat /run/system/resolve/stub-resolv.conf

  You'll see the definition of the nameserver(s) in, and the stub IP
  address no longer there.  To revert this, a `systemctl restart
  systemd-resolved` is needed.

  [Impact]

  This is an improper way to keep nameserver(s) in *resolv* files; the
  override of the file should never happen in these circumstances.

  [Extra]
  -
  As a minor test, I copied over the dhclient-enter-hooks.d/resolved file from 
a Focal installation to a Jammy one, and the problem _does not happen_ when 
such hook is in place.

  [ . . . ]

  Let me know if further clarification is needed to proceed.  Thank you.

  BR,
  pprincipeza

  [0] https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1889068
  [1] https://paste.ubuntu.com/p/bvqPZXZZ8w/
  [2] https://paste.ubuntu.com/p/YQdG6z4WS7/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1972029/+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 1980679] Re: Suspend on focal takes 30s.

2022-07-12 Thread Kai-Heng Feng

Doesn't seem to be a kernel issue.

** Package changed: linux (Ubuntu) => systemd (Ubuntu)

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

Title:
  Suspend on focal takes 30s.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Just upgrades my NUC from Bionic to Focal and suspend went from
  immediate (within a couple seconds) to taking a whole 30 seconds.
  While suspend is happening, the machine is still usable, mouse moves,
  applications respond, all the way until the machine actually goes to
  sleep. I don't see anything strange in kern.log that would explain the
  slowness:

  Jul  4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
  Jul  4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
  Jul  4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
  Jul  4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
  Jul  4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
  Jul  4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle)
  Jul  4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds
  Jul  4 08:45:32 domi kernel: [342410.751470] Freezing user space processes 
... (elapsed 0.002 seconds) done.
  Jul  4 08:45:32 domi kernel: [342410.753907] OOM killer disabled.
  Jul  4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jul  4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) 
(use no_console_suspend to debug)
  Jul  4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 
0011
  Jul  4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing 
SCSI cache
  Jul  4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing 
SCSI cache
  Jul  4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk
  Jul  4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk
  Jul  4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked
  Jul  4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked

  There does look to be 30s between the last "Lockdown: systemd-logind:
  hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend
  entry (s2idle)"

  This is mostly a frustration, but could be a security issue for some
  if they suspend the machine and walk away thinking it would be locked
  but is usable for another 30s.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-121-generic 5.4.0-121.137
  ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189
  Uname: Linux 5.4.0-121-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1033 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Jul  4 08:43:09 2022
  InstallationDate: Installed on 2019-02-09 (1241 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-121-generic N/A
   linux-backports-modules-5.4.0-121-generic  N/A
   linux-firmware 1.187.31
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1980679/+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 1980679] [NEW] Suspend on focal takes 30s.

2022-07-12 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Just upgrades my NUC from Bionic to Focal and suspend went from
immediate (within a couple seconds) to taking a whole 30 seconds. While
suspend is happening, the machine is still usable, mouse moves,
applications respond, all the way until the machine actually goes to
sleep. I don't see anything strange in kern.log that would explain the
slowness:

Jul  4 08:44:55 domi kernel: [342379.045479] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
Jul  4 08:44:55 domi kernel: [342379.048878] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
Jul  4 08:44:55 domi kernel: [342379.049670] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
Jul  4 08:44:56 domi kernel: [342379.966129] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
Jul  4 08:44:56 domi kernel: [342379.971410] Lockdown: systemd-logind: 
hibernation is restricted; see man kernel_lockdown.7
Jul  4 08:45:27 domi kernel: [342410.725869] PM: suspend entry (s2idle)
Jul  4 08:45:32 domi kernel: [342410.749912] Filesystems sync: 0.024 seconds
Jul  4 08:45:32 domi kernel: [342410.751470] Freezing user space processes ... 
(elapsed 0.002 seconds) done.
Jul  4 08:45:32 domi kernel: [342410.753907] OOM killer disabled.
Jul  4 08:45:32 domi kernel: [342410.753907] Freezing remaining freezable tasks 
... (elapsed 0.001 seconds) done.
Jul  4 08:45:32 domi kernel: [342410.755259] printk: Suspending console(s) (use 
no_console_suspend to debug)
Jul  4 08:45:32 domi kernel: [342410.755948] e1000e: EEE TX LPI TIMER: 0011
Jul  4 08:45:32 domi kernel: [342410.812587] sd 2:0:0:0: [sdb] Synchronizing 
SCSI cache
Jul  4 08:45:32 domi kernel: [342410.812607] sd 1:0:0:0: [sda] Synchronizing 
SCSI cache
Jul  4 08:45:32 domi kernel: [342410.812708] sd 2:0:0:0: [sdb] Stopping disk
Jul  4 08:45:32 domi kernel: [342410.816870] sd 1:0:0:0: [sda] Stopping disk
Jul  4 08:45:32 domi kernel: [342411.080056] ACPI: EC: interrupt blocked
Jul  4 08:45:32 domi kernel: [342415.597918] ACPI: EC: interrupt unblocked

There does look to be 30s between the last "Lockdown: systemd-logind:
hibernation is restricted; see man kernel_lockdown.7" and "PM: suspend
entry (s2idle)"

This is mostly a frustration, but could be a security issue for some if
they suspend the machine and walk away thinking it would be locked but
is usable for another 30s.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-121-generic 5.4.0-121.137
ProcVersionSignature: Ubuntu 5.4.0-121.137-generic 5.4.189
Uname: Linux 5.4.0-121-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bbogart1033 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Mon Jul  4 08:43:09 2022
InstallationDate: Installed on 2019-02-09 (1241 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: Intel(R) Client Systems NUC8i3BEH
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-121-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-121-generic N/A
 linux-backports-modules-5.4.0-121-generic  N/A
 linux-firmware 1.187.31
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2022-06-30 (4 days ago)
dmi.bios.date: 10/15/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72693-304
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i3BEH
dmi.product.sku: BOXNUC8i3BEH
dmi.product.version: J72753-303
dmi.sys.vendor: Intel(R) Client Systems

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


** Tags: amd64 apport-bug focal
-- 
Suspend on focal takes 30s.
https://bugs.launchpad.net/bugs/1980679
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

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

2022-07-12 Thread Brian Murray

Looking at the package, it hasn't been updated in 3 years in Debian.

** Tags added: rls-kk-incoming

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

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

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  Good afternoon, folks.

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

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

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

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

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

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"

2022-07-12 Thread Launchpad Bug Tracker

This bug was fixed in the package qtbase-opensource-src -
5.15.3+dfsg-2ubuntu0.1

---
qtbase-opensource-src (5.15.3+dfsg-2ubuntu0.1) jammy; urgency=medium

  * Backport upstream patch to remove limit on the number of HTTP/2 streams.
Fixes https://bugs.kde.org/455540. (LP: #1980210)

 -- Rik Mills   Sat, 18 Jun 2022 14:22:24 +0100

** Changed in: qtbase-opensource-src (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Unable download from store.kde.org with error "invalid number of
  concurrent streams"

Status in qtbase-opensource-src package in Ubuntu:
  Triaged
Status in qtbase-opensource-src source package in Jammy:
  Fix Released

Bug description:
  Version: 5.15.3+dfsg-2
  Release: Jammy 22.04

  In KDE systemsettings or Discover, trying to download new plasma
  themes or similar assets from store.kde.org results in an error
  dialogue stating "invalid number of concurrent streams".

  KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540

  Fixed in KDE Qt patch collection with:
  
https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f

  Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase-
  opensource-src/5.15.4+dfsg-3ubuntu1

  Also fixed in Debian experimental as part on the planned Qt 5.15.5
  transition: https://metadata.ftp-
  master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase-
  opensource-src_5.15.5+dfsg-2_changelog

  The update has also been shipped to our updates and backports PPA, and
  confirmed to be working by users.

  [Impact]

   * Users are unable to download new assets from store.kde.org. This is
  an important feature for users to be able to easily and safely
  customise their systems.

  [Test Plan]

   * Confirm that you can reproduce the bug with the unpatched Qtbase in the 
main archive.
   * Apply the update and test.
   * Confirm that assets now download without error.
   * Check a selection of other Qt based applications that access the internet 
to confirm as mush as is practical that there are not adverse consequences to 
the update.

  [Where problems could occur]

   * We are changing somewhat how Qt responds to these http requests, so
  some testing of other Qt based applications is desirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+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 1980210] Update Released

2022-07-12 Thread Brian Murray

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

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

Title:
  [SRU] Unable download from store.kde.org with error "invalid number of
  concurrent streams"

Status in qtbase-opensource-src package in Ubuntu:
  Triaged
Status in qtbase-opensource-src source package in Jammy:
  Fix Released

Bug description:
  Version: 5.15.3+dfsg-2
  Release: Jammy 22.04

  In KDE systemsettings or Discover, trying to download new plasma
  themes or similar assets from store.kde.org results in an error
  dialogue stating "invalid number of concurrent streams".

  KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540

  Fixed in KDE Qt patch collection with:
  
https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f

  Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase-
  opensource-src/5.15.4+dfsg-3ubuntu1

  Also fixed in Debian experimental as part on the planned Qt 5.15.5
  transition: https://metadata.ftp-
  master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase-
  opensource-src_5.15.5+dfsg-2_changelog

  The update has also been shipped to our updates and backports PPA, and
  confirmed to be working by users.

  [Impact]

   * Users are unable to download new assets from store.kde.org. This is
  an important feature for users to be able to easily and safely
  customise their systems.

  [Test Plan]

   * Confirm that you can reproduce the bug with the unpatched Qtbase in the 
main archive.
   * Apply the update and test.
   * Confirm that assets now download without error.
   * Check a selection of other Qt based applications that access the internet 
to confirm as mush as is practical that there are not adverse consequences to 
the update.

  [Where problems could occur]

   * We are changing somewhat how Qt responds to these http requests, so
  some testing of other Qt based applications is desirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+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 1970634] Update Released

2022-07-12 Thread Brian Murray

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

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in mariadb-10.6 source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Jammy's MariaDB will fail to build, and also fail to start, if the
  underlying kernel is 5.4.x (focal's) and if it's running in an
  unprivileged container (lxd, docker). It will also fail to build in
  launchpad builders.

  Common scenarios where this combination exists is a focal host,
  running an unprivileged jammy container (lxd or docker), or even a
  chroot (the launchpad builders).

  Jammy's MariaDB was built with io_uring support, and it tries to
  enable it at runtime if it deems it's running on a supported kernel.
  There is a range of kernel versions it checks, but of interest for
  this SRU, the Focal (5.4.x) kernel is inside this range and io_uring
  will be enabled. The jammy kernel (5.15) is not, so io_uring will not
  be enabled there, and thus the bug is not manifested in that case.

  If io_uring is enabled, a higher MEMLOCK limit is required than what
  is set by default in focal or jammy (64Mb is what we get, 256Mb or
  more is required).

  The systemd unit file for mariadb tries to raise this limit, but in an
  unprivileged container this won't work.

  MariaDB has checks in place to catch when MEMLOCK is too low, in which
  case it will not use io_uring, but these checks are failing because of
  the LTO build flags that were used in the jammy build of mariadb. It's
  unclear if it's a bug in gcc or something else. There is more
  information in comment #1, comment #5 and later.

  The suggested fix here is to disable LTO for the jammy build. This has
  been done for kinetic already, and is also applied to the debian
  packaging (inside a distro-specific conditional).

  [Test Plan]
  The test plan is to launch mariadb in a jammy lxd container running on a 
focal host.

  lxc launch ubuntu:focal f --vm
  lxc shell f
  lxd init # just hit enter for all questions
  lxc launch ubuntu:jammy j
  lxc shell j
  ulimit -l # confirm it's less than 256
  apt update && apt install mariadb-server -y

  After the installation, mariadb will not be running, and this can be
  checked with:

  systemctl status mariadb.service

  or

  journalctl -u mariadb.server

  You will see something like this:
  Jun 17 18:32:01 jammy-mariadb systemd[1]: Starting MariaDB 10.6.7 database 
server...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
/usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 1864 ...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be 
created!
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Compressed tables use zlib 1.2.11
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using transactional memory
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Number of pools: 1
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using crc32 + pclmulqdq instructions
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Warning] 
mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked 
limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 220617 18:32:01 [ERROR] mysqld 
got signal 6 ;

  And a crash dump.

  With the fixed version, the service will be running normally after
  installation.

  [Where problems could occur]
  The proposed fix is not a surgical strike. It's unfortunate that we didn't 
get to the bottom of why LTO is causing this behavior. Reverting it is still 
the quickest and less risky change at the moment, though. This gets us on par 
with upstream binary builds, and debian builds, and these also have wide test 
coverage and ample user base.

  The other regression possibility is that this is a rebuild of mariadb
  in the current jammy environment, and the package that is currently in

[Touch-packages] [Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

2022-07-12 Thread Launchpad Bug Tracker

This bug was fixed in the package mariadb-10.6 - 1:10.6.7-2ubuntu1.1

---
mariadb-10.6 (1:10.6.7-2ubuntu1.1) jammy; urgency=medium

  * d/rules: disable LTO on Ubuntu so a low MEMLOCK_LIMIT can be
properly caught and dealt with (LP: #1970634)

 -- Andreas Hasenack   Fri, 17 Jun 2022 10:03:50
-0300

** Changed in: mariadb-10.6 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in mariadb-10.6 source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  Jammy's MariaDB will fail to build, and also fail to start, if the
  underlying kernel is 5.4.x (focal's) and if it's running in an
  unprivileged container (lxd, docker). It will also fail to build in
  launchpad builders.

  Common scenarios where this combination exists is a focal host,
  running an unprivileged jammy container (lxd or docker), or even a
  chroot (the launchpad builders).

  Jammy's MariaDB was built with io_uring support, and it tries to
  enable it at runtime if it deems it's running on a supported kernel.
  There is a range of kernel versions it checks, but of interest for
  this SRU, the Focal (5.4.x) kernel is inside this range and io_uring
  will be enabled. The jammy kernel (5.15) is not, so io_uring will not
  be enabled there, and thus the bug is not manifested in that case.

  If io_uring is enabled, a higher MEMLOCK limit is required than what
  is set by default in focal or jammy (64Mb is what we get, 256Mb or
  more is required).

  The systemd unit file for mariadb tries to raise this limit, but in an
  unprivileged container this won't work.

  MariaDB has checks in place to catch when MEMLOCK is too low, in which
  case it will not use io_uring, but these checks are failing because of
  the LTO build flags that were used in the jammy build of mariadb. It's
  unclear if it's a bug in gcc or something else. There is more
  information in comment #1, comment #5 and later.

  The suggested fix here is to disable LTO for the jammy build. This has
  been done for kinetic already, and is also applied to the debian
  packaging (inside a distro-specific conditional).

  [Test Plan]
  The test plan is to launch mariadb in a jammy lxd container running on a 
focal host.

  lxc launch ubuntu:focal f --vm
  lxc shell f
  lxd init # just hit enter for all questions
  lxc launch ubuntu:jammy j
  lxc shell j
  ulimit -l # confirm it's less than 256
  apt update && apt install mariadb-server -y

  After the installation, mariadb will not be running, and this can be
  checked with:

  systemctl status mariadb.service

  or

  journalctl -u mariadb.server

  You will see something like this:
  Jun 17 18:32:01 jammy-mariadb systemd[1]: Starting MariaDB 10.6.7 database 
server...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
/usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 1864 ...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be 
created!
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Compressed tables use zlib 1.2.11
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using transactional memory
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Number of pools: 1
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using crc32 + pclmulqdq instructions
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Warning] 
mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked 
limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 220617 18:32:01 [ERROR] mysqld 
got signal 6 ;

  And a crash dump.

  With the fixed version, the service will be running normally after
  installation.

  [Where problems could occur]
  The proposed fix is not a surgical strike. It's unfortunate that we didn't 
get to the bottom of why LTO is causing this behavior. Reverting it is still 
the quickest and less risky change at the moment, though. This gets us on par 
with upstream binary builds, and debian builds, and these also have wide test 
coverage and ample user base.

  The other regression possibility is that this is a rebuild of mariadb
  in the current jammy environment, and the package that is currently in
  jammy was built on March 10th, 2022. Most likely the reverse
  de

[Touch-packages] [Bug 1958019]

2022-07-12 Thread belozyorcev

Hi guys!

I also have problem with subwoofers (like in comment #559) on Lenovo
Yoga Slim 7 Carbon 14ACN6.

https://psref.lenovo.com/Detail/Yoga/Yoga_Slim_7_Carbon_14ACN6?M=82L0005PRK

I tried kernels 5.18.10, 5.17.15 (and 5.17.0-1012-oem on Ubuntu).

The sound is bad everywhere :(

alsa-info: http://alsa-
project.org/db/?f=be90ab6208aa1484ed902f5bf89612219f634980

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1981488] [NEW] presistent reoccuring error message: wrapper-2.0

2022-07-12 Thread Andrew Cochrane

Public bug reported:

After an update there is a reoccuring system message saying there is an
error in wrapper-2.0 it doesn't seem to affect any of my processes,
except it steals cursor focus when it occurs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul 12 14:43:28 2022
ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2021-04-06 (462 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** 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/1981488

Title:
  presistent reoccuring error message: wrapper-2.0

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After an update there is a reoccuring system message saying there is
  an error in wrapper-2.0 it doesn't seem to affect any of my processes,
  except it steals cursor focus when it occurs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 12 14:43:28 2022
  ErrorMessage: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-04-06 (462 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package nvidia-kernel-common-470 470.129.06-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-kernel-common-470 package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981488/+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 1980238] Re: apport-gtk: AssertionError when importing Gdk

2022-07-12 Thread Brian Murray

I also ran into this during an upgrade from Ubuntu 20.04 to Ubuntu
22.04.

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

Title:
  apport-gtk: AssertionError when importing Gdk

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

Bug description:
  Latest occurrence on Ubuntu 22.04 with apport 2.20.11-0ubuntu82.1

  Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 19, in 
  from gi.repository import GLib, Wnck, GdkX11, Gdk
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in 
load_module
  importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 145, in 
load_module
  importlib.import_module('gi.repository.' + dep.split("-")[0])
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 655, in _load_unlocked
File "", line 618, in _load_backward_compatible
File "/usr/lib/python3/dist-packages/gi/importer.py", line 146, in 
load_module
  dynamic_module = load_overrides(introspection_module)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 118, 
in load_overrides
  override_mod = importlib.import_module(override_package_name)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
File "/usr/lib/python3/dist-packages/gi/overrides/Gdk.py", line 83, in 

  Color = override(Color)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 195, 
in override
  assert g_type != TYPE_NONE
  AssertionError

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1980238/+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 1979347] Re: SRU pygobject 3.42.1, including fix for the append function

2022-07-12 Thread Jeremy Bicha

I also verified the fix. Before I installed python3-gi 3.42.1-0ubuntu1,
when I ran the script, I only got errors on the command line. After
installing the update, the window showed and there were no errors on the
command line.

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

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

Title:
  SRU pygobject 3.42.1, including fix for the append function

Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject source package in Jammy:
  Fix Committed

Bug description:
  >> Impact <<

  Applications crash when they call the append function to append data
  to stores.

  >> Test plan <<

  When executing the attached bug.py script,

  - With the fix: A dummy window with a text field is mapped.

  - Without the fix: An error message is raised and no window is mapped.

  >> Regression potential <<

  Since this includes a new upstream release, by looking at the NEWS
  file ,
  regressions could show up:

  - On programs which use ListStore and Treeview. Additionally, those
  changes should not affect GTK2 or GTK3.

  - As leaks, given the replace of g_error by g_critical by
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1979347/+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 1981362] Re: rehash command not working on armhf architecture inside chroot

2022-07-12 Thread Oscar Diaz

Hi Seth, AFAIK systemd-nspawn uses qemu--static to run those
executables, and that's the way I use to run, for instance, Raspberry Pi
images in my host PC.

In fact one test I did was to run two debootstraps with focal (openssl
1.1.1): one with armhf architecture and one with arm64 architecture, and
only the armhf has the issue mentioned in this bug report.

I rerun the debootstraps with jammy (openssl 3.0.2) with both armhf and
arm64, and it worked fine in both runs.

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

Title:
  rehash command not working on armhf architecture inside chroot

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  Hi, I found a possible bug in the `openssl rehash` command: it won't
  do anything while running inside a armhf chroot with an amd64 host
  architecture.

  How to reproduce (confirmed on focal and hirsute):

  1. Build a armhf chroot environment: `debootstrap --arch armhf --foreign 
focal `
  2. Go inside chroot (using systemd-nspawn): `systemd-nspawn -D `
  3. Complete debootstrap second stage: `/debootstrap/debootstrap 
--second-stage`
  4. Run rehash in system certs dir: `openssl rehash -n -v /etc/ssl/certs`
  5. Rehash shows nothing was done

  ```
  root@ubuntuarm:~# openssl rehash -n -v /etc/ssl/certs
  Doing /etc/ssl/certs
  root@ubuntuarm:~#
  ```

  In jammy there is no problem (openssl 3.0.2).

  $ lsb_release -rd
  Description:Ubuntu 20.04.4 LTS
  Release:20.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1f-1ubuntu2.16
Candidate: 1.1.1f-1ubuntu2.16
Version table:
   *** 1.1.1f-1ubuntu2.16 500
  500 http://co.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1f-1ubuntu2 500
  500 http://co.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Full console session (on an armhf chroot, arm64 host arch):

  root@ubuntuarm:~# openssl rehash -n -v /etc/ssl/certs
  Doing /etc/ssl/certs
  root@ubuntuarm:~# openssl version -a
  OpenSSL 1.1.1f  31 Mar 2020
  built on: Mon Apr 20 11:53:50 2020 UTC
  platform: debian-armhf
  options:  bn(64,32) rc4(char) des(long) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 
-fdebug-prefix-map=/build/openssl-uC90dH/openssl-1.1.1f=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM 
-DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DAES_ASM -DBSAES_ASM -DGHASH_ASM 
-DECP_NISTZ256_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/arm-linux-gnueabihf/engines-1.1"
  Seeding source: os-specifi
  root@ubuntuarm:~# uname -a
  Linux ubuntuarm 5.4.0-117-generic #132-Ubuntu SMP Thu Jun 2 00:39:06 UTC 2022 
armv7l armv7l armv7l GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1981362/+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 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"

2022-07-12 Thread Rik Mills

In testing on hardware and VM, this fixes the issue for me. No adverse
impact observed.

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

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

Title:
  [SRU] Unable download from store.kde.org with error "invalid number of
  concurrent streams"

Status in qtbase-opensource-src package in Ubuntu:
  Triaged
Status in qtbase-opensource-src source package in Jammy:
  Fix Committed

Bug description:
  Version: 5.15.3+dfsg-2
  Release: Jammy 22.04

  In KDE systemsettings or Discover, trying to download new plasma
  themes or similar assets from store.kde.org results in an error
  dialogue stating "invalid number of concurrent streams".

  KDE Bug: https://bugs.kde.org/show_bug.cgi?id=455540

  Fixed in KDE Qt patch collection with:
  
https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f

  Fixed in Kinetic with: https://launchpad.net/ubuntu/+source/qtbase-
  opensource-src/5.15.4+dfsg-3ubuntu1

  Also fixed in Debian experimental as part on the planned Qt 5.15.5
  transition: https://metadata.ftp-
  master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase-
  opensource-src_5.15.5+dfsg-2_changelog

  The update has also been shipped to our updates and backports PPA, and
  confirmed to be working by users.

  [Impact]

   * Users are unable to download new assets from store.kde.org. This is
  an important feature for users to be able to easily and safely
  customise their systems.

  [Test Plan]

   * Confirm that you can reproduce the bug with the unpatched Qtbase in the 
main archive.
   * Apply the update and test.
   * Confirm that assets now download without error.
   * Check a selection of other Qt based applications that access the internet 
to confirm as mush as is practical that there are not adverse consequences to 
the update.

  [Where problems could occur]

   * We are changing somewhat how Qt responds to these http requests, so
  some testing of other Qt based applications is desirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1980210/+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 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

2022-07-12 Thread Łukasz Zemczak

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

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

** Changed in: ubuntu-meta (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1

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

Title:
  autoinstall ssh:install-server:false is misleading in 22.04

Status in subiquity:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  With 22.04, openssh-server is baked into the image curtin copies to
  the target.  The ssh:install-server key no longer controls whether
  openssh-server gets installed.  It should be easy enough to have the
  bit of code that installs openssh-server when the key is true also
  remove it when the key is false.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1974483/+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 1981431] [NEW] systemd-resolved: DNSSEC validation failed: incompatible-server

2022-07-12 Thread Jan-Otto Kröpke

Public bug reported:

Hi,

I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4.

2 days ago, I enabled DNSSEC=true through:

# grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf
DNSSEC=yes

After running some hours, systemd-resolved stop working. Log lines like
incompatible-server starts to spam.

Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution...
Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors:
Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: 
int.creativesandbox.de
Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 'htdocs'.
Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution.
Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 214.162.in-addr.arpa IN SOA: no-signature
Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 76.214.162.in-addr.arpa IN DS: no-signature
Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 126.76.214.162.in-addr.arpa IN DS: no-signature
Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 126.76.214.162.in-addr.arpa IN SOA: no-signature
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question . IN SOA: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question de IN DS: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question de IN SOA: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question your-server.de IN DS: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question your-server.de IN SOA: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question clients.your-server.de IN DS: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 201.138.clients.your-server.de IN DS: incompatible-server
Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question static.237.11.201.138.clients.your-server.de IN : 
incompatible-server

Mention here, I'm running multiple machines with the same config against
the same upstream DNS server. From time to time, only one instance is
stop working here.

Running a manual query also fails here, for example:

# resolvectl query noc3.wordfence.com
noc3.wordfence.com: resolve call failed: DNSSEC validation failed: 
incompatible-server

Running 'resolvectl reset-server-features' helps here and can be
considered as workaround.

# resolvectl query noc3.wordfence.com
noc3.wordfence.com: resolve call failed: DNSSEC validation failed: 
incompatible-server
# resolvectl reset-server-features
# resolvectl query noc3.wordfence.com
noc3.wordfence.com: 35.155.126.231 -- link: eth0

-- Information acquired via protocol DNS in 26.5ms.
-- Data is authenticated: no; Data was acquired via local or encrypted 
transport: no
-- Data from: network

By reading issues upstream looks like
https://github.com/systemd/systemd/issues/6490.

A fix is implemented (https://github.com/systemd/systemd/pull/18624) and
released in 248 which is included in Ubuntu 22.04.

But there is another fix around this issue
(https://github.com/systemd/systemd/pull/20214) which is released in
systemd 250.

I would like to know if it's possible to backport this fix into Ubuntu
22.04.

Thanks.

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


** Tags: systemd-resolved

** Description changed:

  Hi,
  
  I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4.
  
  2 days ago, I enabled DNSSEC=true through:
  
  # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf
  DNSSEC=yes
  
  After running some hours, systemd-resolved stop working. Log lines like
  incompatible-server starts to spam.
  
  Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution...
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors:
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: 
int.creativesandbox.de
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 
'htdocs'.
  Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution.
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 214.162.in-addr.arpa IN SOA: no-signature
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 76.214.162.in-addr.arpa IN DS: no-signature
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation

[Touch-packages] [Bug 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

2022-07-12 Thread Olivier Gayot

Based on my tests, the patch
1-1.1ubuntu1.18.04.14__1.1ubuntu1.18.04.15.debdiff for bionic is still
relevant.

unattended-upgrades FTBFS in bionic ; and the patch fixes it:

https://launchpad.net/~ogayot/+archive/ubuntu/bionic-
proposed/+build/24162373

During autopkgtest run, the error described in comment #9 is not
reproduced in the bionic series so there should be no need for clearing
__pycache__.

https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-ogayot-bionic-
proposed/bionic/amd64/u/unattended-
upgrades/20220712_094142_9df41@/log.gz

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Incomplete => Confirmed

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

Title:
  FTBFS and autopkgtest failure since changes in apt for automatic
  kernel removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed
Status in unattended-upgrades source package in Focal:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]
  Since the following changes in apt have landed in focal-updates (and is 
currently in bionic-proposed), unattended-upgrades FTBFS and fails autopkgtest 
on both series:

    * Revert "Protect currently running kernel at run-time"
    * Backport Determine autoremovable kernels at run-time (LP: #1615381) as of
  2.4.5; including the change to only protect two kernels, not last 
installed
  one (LP: #1968154)

  ==
  FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
  --
  Traceback (most recent call last):
    File "./test_remove_unused.py", line 165, in 
test_remove_unused_dependencies_new_unused_only
  haystack))
  AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm

  [Test plan]
  1. focal:
* run autopkgtest against -updates:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=updates 
--test-name run-tests -- 
* try to build the package
  2. bionic:
* run autopkgtest against -proposed:
  $ autopkgtest unattended-upgrades --apt-upgrade --apt-pocket=proposed 
--test-name run-tests -- 
* try to build the package

  [Where problems could occur]
* The fix only affects the test-suite (that runs both at build time & 
autopkgtest time) so the impact should be minimal. Something wrong in the patch 
would make the unattended package FTBFS or fail autopkgtest but it is already 
failing ATM.
* The new tests dependency on apt can trigger more autopkgtest runs. Since 
unattended-upgrades has a non-trivial autopkgtest suite, this can have a slight 
impact on the queues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1974223/+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 1959469] Comment bridged from LTC Bugzilla

2022-07-12 Thread bugproxy

An updated test package was created for kinetic and build with the help of this 
PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1959469
for the major architectures.

This incl. building and executing the testsuite too, which results in all tests 
passed:
...

All 112 tests passed

...
PASS: rsa-sign
PASS: rsa-verify
PASS: rsa-encrypt
==
All 3 tests passed
==

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-12 Thread Simon Chopin

** Tags added: fr-2537

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  New
Status in nettle package in Ubuntu:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-07-12 Thread Dustin Utecht

I tried to connect to the AP on 07:49:xx.

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  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
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-07-12 Thread Sebastien Bacher

Thanks, that's the complete log though and not the part from -f when a
client tried to connect right? Did you maybe note down the time when you
tried to connect?

The log has nl80211 warnings similar to bug #1886169 , unsure if that
could be the issue though

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  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
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1972790] Re: Can't connect to hotspot created on ubuntu

2022-07-12 Thread Dustin Utecht

1. yes.
2. currently to busy, sorry!
3. uploaded a log

I tried to connect via MacBook (macOS Monterey 12.4), Iphone (iOS 15.5),
Android (Version unknown).

** Attachment added: "wpa.log"
   
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+attachment/5602531/+files/wpa.log

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

Title:
  Can't connect to hotspot created on ubuntu

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  We currently have older systems (18.04) with hotspot's and we will migrate to 
22.04.
  Anything work's fine, expect the hotspot.
  The Hotspot will be created and is visible in the WLAN-List, but if the 
security is set to "WPA & WPA2 Personal" we get the error message "Failed to 
connect to the network".
  If we change the Security to "WPA3 Personal" we get the error message 
"Invalid Password", even if the password is correct.
  As soon we remove the security (change it to "none"), we can connect with out 
any problems.

  We can reproduce it with a fresh installtion of the Ubuntu Server
  22.04 and the following two commands:

  apt install network-manager

  nmcli c add type wifi ifname wlp3s0 con-name Hotspot autoconnect yes
  ssid test-ap 802-11-wireless.mode ap 802-11-wireless.band bg
  802-11-wireless.mac-address "80:45:dd:f0:27:ba" wifi-sec.group ccmp
  wifi-sec.key-mgmt wpa-psk wifi-sec.pairwise ccmp wifi-sec.proto rsn
  wifi-sec.psk "test12345" ipv4.addresses 192.168.60.1/24 ipv4.method
  shared && nmcli connection up Hotspot

  
  We thought it could be similar to this issue: 
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267
  Because if we test it with 20.04 it worked fine, because 20.04 uses the 
Version 2:2.9.0-21build1 as described in the Ticket.

  As @Sebastian Bacher suggested 
(https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/comments/58), i 
created a own report.
  In the attachment is the requested log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6 [modified: 
lib/systemd/system/wpa_supplicant.service]
  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
  Date: Tue May 10 07:24:15 2022
  InstallationDate: Installed on 2022-05-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1972790/+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 1978307] Re: gwenview aborts with a std::out_of_range exception raised in libexiv2

2022-07-12 Thread Arrigo Marchiori

Here is a more detailed gdb output

terminate called after throwing an instance of 'std::out_of_range'  

 
  what():  basic_string::at: __n (which is 19) >= this->size() (which is 19)

 

Thread 1 "gwenview" received signal SIGABRT, Aborted.   

 
0xf7fd5079 in __kernel_vsyscall ()  

 
(gdb) bt

 
#0  0xf7fd5079 in __kernel_vsyscall ()  

 
#1  0xf5d1ea02 in __libc_signal_restore_set (set=0xc0cc) at 
../sysdeps/unix/sysv/linux/nptl-signals.h:80
 
#2  __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 

 
#3  0xf5d1fe91 in __GI_abort () at abort.c:79   

 
#4  0xf5f3b97d in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 

 
#5  0xf5f43174 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 

 
#6  0xf5f431dd in std::terminate() () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6  
  
#7  0xf5f434dc in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6

 
#8  0xf5f6defa in std::__throw_out_of_range_fmt(char const*, ...) () from 
/usr/lib/i386-linux-gnu/libstdc++.so.6  
   
#9  0xf5881da3 in std::__cxx11::basic_string, 
std::allocator >::at (__n=19, this=0xc67c)
  
at /usr/include/c++/7/bits/basic_string.h:1098  

 
#10 Exiv2::Internal::printXmpDate (os=..., value=...) at tags.cpp:2774  

 
#11 0xf58c3aff in Exiv2::Xmpdatum::write (this=0xe7016260, os=...) at 
xmp.cpp:281 
   
#12 0xf7d870af in Exiv2::operator<< (md=..., os=...) at 
/usr/include/exiv2/metadatum.hpp:305
 
#13 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup > > > (this=, parent=..., 
group=, container=...) at ./lib/imagemetainfomodel.cpp:284   

#14 0xf7d8212f in Gwenview::ImageMetaInfoModel::setExiv2Image (this=, image=) at ./lib/imagemetainfomodel.cpp:454
  
#15 0xf7d2fa54 in Gwenview::Document::setExiv2Image (this=0x56ad70b0, 
image=...) at ./lib/document/document.cpp:395   
   
#16 0xf7d2e7f0 in Gwenview::AbstractDocumentImpl::setDocumentExiv2Image 
(this=0x56b73570, image=...) at ./lib/document/abstractdocumentimpl.cpp:82  
 
#17 0xf7d434b3 in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded 
(this=0x56b73570) at ./lib/document/loadingdocumentimpl.cpp:491 
 
#18 0xf7debf44 in Gwenview::LoadingDocumentImpl::qt_static_metacall 
(_o=0x56b73570, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xcb78) 
 
at 
./obj-i686-linux-gnu/lib/gwenviewlib_autogen/DV7UALDUNI/moc_loadingdocumentimpl.cpp:85

#19 0xf6303c6e in QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
[...]

I hope this helps.

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

Title:
  gwenview aborts with a std::out_of_range exception raised in libexiv2

Status in exiv2 package in Ubuntu:
  New
Status in gwenview package in Ubuntu:
  New

Bug description:
  This bug seems to be a regression of KDE bug 441121:
  https://bugs.kde.org/show_bug.cgi?id=441121

  When opening certain JPG files, gwenview aborts with an uncaught C++
  exception std::out_of_range

  System is Ubuntu 18.04.6 LTS x86 with up-to-dat

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

2022-07-12 Thread Launchpad Bug Tracker

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

** Changed in: powermgmt-base (Ubuntu)
   Status: New => Confirmed

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

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

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  Good afternoon, folks.

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

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

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

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

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

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+subscriptions


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

[Touch-packages] [Bug 1981383] Re: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2022-07-12 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1901115, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1901115
   package bluez failed to install/upgrade: installed bluez package 
post-installation script subprocess returned error exit status 1 [Failed to 
start Bluetooth service.]

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

Title:
  package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Unable to use or turn on bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 12 04:11:50 2022
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-02-06 (155 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_F543MA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=a1980608-1f3e-4705-9432-421aa3851fe6 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: bluez
  Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540MA.314
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540MA.314:bd10/01/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_F543MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 15_ASUS Laptop X540MA_F543MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C0:E4:34:24:68:A6  ACL MTU: 820:8  SCO MTU: 255:12
DOWN 
RX bytes:1154613008 acl:1610113 sco:0 events:493522 errors:0
TX bytes:35384460 acl:492878 sco:0 commands:420 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981383/+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 1972029] Re: dhclient overriding stub-resolv.conf file on Jammy

[Touch-packages] [Bug 1980679] Re: Suspend on focal takes 30s.

[Touch-packages] [Bug 1980679] [NEW] Suspend on focal takes 30s.

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

[Touch-packages] [Bug 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"

[Touch-packages] [Bug 1980210] Update Released

[Touch-packages] [Bug 1970634] Update Released

[Touch-packages] [Bug 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Touch-packages] [Bug 1958019]

[Touch-packages] [Bug 1981488] [NEW] presistent reoccuring error message: wrapper-2.0

[Touch-packages] [Bug 1980238] Re: apport-gtk: AssertionError when importing Gdk

[Touch-packages] [Bug 1979347] Re: SRU pygobject 3.42.1, including fix for the append function

[Touch-packages] [Bug 1981362] Re: rehash command not working on armhf architecture inside chroot

[Touch-packages] [Bug 1980210] Re: [SRU] Unable download from store.kde.org with error "invalid number of concurrent streams"

[Touch-packages] [Bug 1974483] Re: autoinstall ssh:install-server:false is misleading in 22.04

[Touch-packages] [Bug 1981431] [NEW] systemd-resolved: DNSSEC validation failed: incompatible-server

[Touch-packages] [Bug 1974223] Re: FTBFS and autopkgtest failure since changes in apt for automatic kernel removal

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

[Touch-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Touch-packages] [Bug 1972790] Re: Can't connect to hotspot created on ubuntu

[Touch-packages] [Bug 1978307] Re: gwenview aborts with a std::out_of_range exception raised in libexiv2

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

[Touch-packages] [Bug 1981383] Re: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

25 matches

Site Navigation

Mail list logo

Footer information