[Touch-packages] [Bug 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

[Bug Watch Updater]

** Changed in: debug-me (Debian)
   Status: Unknown => New

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

Title:
  debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

Status in binutils package in Ubuntu:
  New
Status in debug-me package in Ubuntu:
  Triaged
Status in debug-me package in Debian:
  New

Bug description:
  debug-me 1.20221231-1 fails to build from source on ppc64el due to
  internal ld.gold error (binutils 2.41-4ubuntu1):

  ```
  Linking dist/build/debug-me/debug-me ...
  /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050
  collect2: error: ld returned 1 exit status
  `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
  ```

  Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu-
  mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz

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

[Nick Rosbrook]

** Description changed:

  [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 supported network stack.
+ 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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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.

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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 

[Touch-packages] [Bug 2036998] Re: Xorg freeze

[Daniel van Vugt]

** Tags added: amdgpu

** Summary changed:

- Xorg freeze
+ [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu]

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)

** Summary changed:

- [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu]
+ [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0

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

Title:
  [amdgpu] Oops in dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0

Status in linux-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
  May have reported this earlier myself. Details to be filled later.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 21 20:20:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (512 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  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/linux-hwe-6.2/+bug/2036998/+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 2037012] Re: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1 [Fail

[Daniel van Vugt]

** Summary changed:

- package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
+ package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1 [Failed to restart bluetooth.service: Unit bluetooth.service failed 
to load properly: File exists.]

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

Title:
  package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
  instalado paquete bluez script post-installation devolvió el código de
  salida de error 1 [Failed to restart bluetooth.service: Unit
  bluetooth.service failed to load properly: File exists.]

Status in bluez package in Ubuntu:
  New

Bug description:
  no se está ejecutando el sevico Bluez

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep 21 13:30:47 2023
  ErrorMessage: el subproceso instalado paquete bluez script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-09-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 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: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F7
  dmi.board.vendor: Compal
  dmi.board.version: 99.80
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv4 Notebook PC
  dmi.product.sku: FR922UA#ABA
  dmi.product.version: F.22
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037012/+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 2036956] Re: Problems in browing like firefox, and chromium and some other application

[Daniel van Vugt]

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

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 2012388, 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.


** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator
(Ubuntu)

** This bug has been marked a duplicate of bug 2012388
   X11 window (usually AnyDesk) at top-right of the screen is invisible and 
steals mouse clicks

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

Title:
  Problems in browing like firefox, and chromium and some other
  application

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  Whenever I open the browser and some other application, My cursor
  doesn't work here at the top right side of the screen. Usually, it
  happens only when I open browser or few of the application, with that
  problem I cannot close the tab button, minimize, maximize, can't use
  some of the menu buttons on the top right side of the browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-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 Sep 21 16:59:55 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb]
  InstallationDate: Installed on 2023-09-07 (13 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Latitude E7440
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=ba68d84a-c8cc-4d13-839b-42fed52c8449 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2016
  dmi.bios.release: 65.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 091TRH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd12/22/2016:br65.20:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn091TRH:rvrA00:cvnDellInc.:ct9:cvr:sku05CB:
  dmi.product.name: Latitude E7440
  dmi.product.sku: 05CB
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  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/gnome-shell-extension-appindicator/+bug/2036956/+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

[Nick Rosbrook]

Tais - you should not have both services running. For you the solution
should be:

$ systemctl disable --now systemd-networkd.service

This will also disable associated units, including systemd-networkd-
wait-online.service.

** Description changed:

+ [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 supported 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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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.

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

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 supported 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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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. 

[Touch-packages] [Bug 2037022] [NEW] logrotate systemd timer should run hourly rather than daily

[Todd Jacobsen]

Public bug reported:

Logrotate supports "hourly rotation, however the Ubuntu logrotate
systemd Timer runs "daily" - so "hourly" logrotate jobs are still only
run daily.

Updating /etc/systemd/system/timers.target.wants/logrotate.timer:
...
[Timer]
OnCalendar=hourly
...

should allow "logrotate hourly" to work as expected.

See related comment at 
https://github.com/logrotate/logrotate/issues/249#issuecomment-485829363
"The tricky part is that one needs to change the default cron hook
(or systemd timer) to make hourly actually work as expected."

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: logrotate 3.21.0-1
ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Sep 21 22:11:04 2023
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

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

Title:
  logrotate systemd timer should run hourly rather than daily

Status in logrotate package in Ubuntu:
  New

Bug description:
  Logrotate supports "hourly rotation, however the Ubuntu logrotate
  systemd Timer runs "daily" - so "hourly" logrotate jobs are still only
  run daily.

  Updating /etc/systemd/system/timers.target.wants/logrotate.timer:
  ...
  [Timer]
  OnCalendar=hourly
  ...

  should allow "logrotate hourly" to work as expected.

  See related comment at 
https://github.com/logrotate/logrotate/issues/249#issuecomment-485829363
  "The tricky part is that one needs to change the default cron hook
  (or systemd timer) to make hourly actually work as expected."

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: logrotate 3.21.0-1
  ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16
  Uname: Linux 6.2.0-32-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Sep 21 22:11:04 2023
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/2037022/+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 2037012] [NEW] package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete bluez script post-installation devolvió el código de salida de error 1

[James Bonilla]

Public bug reported:

no se está ejecutando el sevico Bluez

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Sep 21 13:30:47 2023
ErrorMessage: el subproceso instalado paquete bluez script post-installation 
devolvió el código de salida de error 1
InstallationDate: Installed on 2023-09-18 (2 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
InterestingModules: bluetooth
MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 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: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30F7
dmi.board.vendor: Compal
dmi.board.version: 99.80
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv4 Notebook PC
dmi.product.sku: FR922UA#ABA
dmi.product.version: F.22
dmi.sys.vendor: Hewlett-Packard
hciconfig:

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2037012

Title:
  package bluez 5.53-0ubuntu3.6 failed to install/upgrade: el subproceso
  instalado paquete bluez script post-installation devolvió el código de
  salida de error 1

Status in bluez package in Ubuntu:
  New

Bug description:
  no se está ejecutando el sevico Bluez

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Sep 21 13:30:47 2023
  ErrorMessage: el subproceso instalado paquete bluez script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-09-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  InterestingModules: bluetooth
  MachineType: Hewlett-Packard HP Pavilion dv4 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=e02ac370-977e-4bed-840d-5a24e2e5b288 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: el subproceso 
instalado paquete bluez script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F7
  dmi.board.vendor: Compal
  dmi.board.version: 99.80
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd10/17/2008:svnHewlett-Packard:pnHPPaviliondv4NotebookPC:pvrF.22:rvnCompal:rn30F7:rvr99.80:cvnCompal:ct10:cvrN/A:skuFR922UA#ABA:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv4 Notebook PC
  dmi.product.sku: FR922UA#ABA
  dmi.product.version: F.22
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037012/+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 2035337] Re: dh-python: Cannot exclude deliberately embedded .egg-info from the clean step

[Simon Chopin]

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

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

Title:
  dh-python: Cannot exclude deliberately embedded .egg-info from the
  clean step

Status in dh-python package in Ubuntu:
  New
Status in pastedeploy package in Ubuntu:
  New
Status in pastescript package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  New

Bug description:
  Imported from Debian bug http://bugs.debian.org/1051837:

  Source: dh-python
  Version: 6.20230825
  Severity: normal
  X-Debbugs-Cc: scho...@ubuntu.com

  We have a FTBFS on src:pastescript because its test suite embeds a
  FakePlugin Python package, including its .egg-info, and the recent
  change to the dh-python clean: target breaks that package.

  While we can work around it by temporarily renaming the problematic
  directory before the dh_clean call, it would be nicer to have an
  explicit mechanism to exclude some paths from the clean analysis.

  -- System Information:
  Debian Release: bookworm/sid
APT prefers lunar-updates
APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 
'lunar'), (100, 'lunar-proposed'), (100, 'lunar-backports')
  Architecture: amd64 (x86_64)
  Foreign Architectures: i386

  Kernel: Linux 6.2.0-32-generic (SMP w/8 CPU threads; PREEMPT)
  Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE
  Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
set
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  -- no debconf information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2035337/+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 2034656] Re: Update Ubuntu ESM cache only once daily?

[Julian Andres Klode]

Yes so esm archive is contacted whenever main archive is, as the service
is started by a hook to apt update to run an apt update on a subcache.

And APT daily only runs once on a given calendar day, even if you
configure lower intervals.

So this seems to me like misconfiguration of those systems and not a pro
issue. Adding checks to pro would be dangerous, it's easy to get this
wrong in the current architecture, it may then only run every 2 days if
done the wrong way (you can't just check if you last checked 24 hours
ago, because if the daily run runs 22 hours due to randomisation you
wouldn't run, hence why apt normalizes the time stamps to midnight so it
sees if the date is different).

And really we want you to get the up-to-date information for your ESM
too if you run apt update (also when ESM is actually enrolled, it runs
in the main update anyhow).

Azure has its own update management solution afaik, which will do its
own update checks and update management, it's possible it checks
multiple times per day and should be relying on the randomised once a
day apt-daily instead.

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

Title:
  Update Ubuntu ESM cache only once daily?

Status in cloud-images:
  New
Status in apt package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We're seeing frequent alerts on the Ubuntu ESM archive servers due to
  surges in requests. On two systems, I'm seeing this:

  | Sep  6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches.

  On another:

  | Sep  6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.

  This is all from `/usr/lib/systemd/system/esm-cache.service` which
  calls `/usr/lib/ubuntu-advantage/esm_cache.py`.

  Can we please have this run less frequent? Perhaps only once daily
  which aligns with APT and apt-daily-upgrade.service / unattended-
  upgrades?

  Perhaps check existence of a file and run if not, then age of that
  same file and only run if it's older than a day?

  I think, from what I can see, this may be triggered from
  /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm-
  hook.conf?

  See also LP:1554848 which was for APT.

  On Trusty and Xenial clients we only seem to update daily, but the
  problem is worse as it's a cron.daily job, so all clients fire
  simultaneously - could we get this changed to a cron.d job with a
  randomised firing time instead?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2034656/+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 2036885] Re: please add API to exclude things

[Benjamin Drung]

A single dracut-install call is unrealistic, but those --mod-filter-
nopath and --mod-filter-noname parameters could be constructed and added
to all dracut-install calls.

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

Title:
  please add API to exclude things

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Please add API to exclude things

  It would be useful on Pi to say "yes include all graphics" but do
  exclude "amdgpu, nvidia" drivers and firmware related to those.

  Something along the lines of a "exclude filter list" for drivers &
  firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036885/+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 2036886] Re: please add api to repack initramfs

[Benjamin Drung]

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

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

Title:
  please add api to repack initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  please add api to repack initramfs

  from the results of unpackinitramfs, including all early & main dirs.

  Userstory: i want to tweak my initrd in-place by replacing broken
  libc.so.6 with a patched one, I want to use unmkinitramfs, modify
  files in main, repack it and boot it.

  CLI:

  $ unmkinitramfs /boot/initrd.img unpacked-initrd
  $ ls unpacked-initrd/
  early  early2  main
  $ (edit things in unpacked-initrd/main/)
  $ remkinitramfs unpacked-initrd patched-initrd.img

  Where patched-initrd.img is now similar to /boot/initrd.img, apart
  from the changed things.

  I expect remkinitramfs like functionality that will take the output of
  unmkinitramfs (e.g. unpacked-initrd/) directory as input, do
  uncompressed cpio archives out of all the subdirs, make compressed
  cpio archive out of main, and produce a patched-initrd.img that is
  ready for booting.

  It is very close to what mkinitramfs does, but skip calling all the
  hooks to create things a fresh, and just do the final assembly step of
  cpio and compression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036886/+subscriptions


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

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

[Steve Langasek]

** Tags added: foundations-todo

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

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

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

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


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

[Touch-packages] [Bug 1978079] Re: EFI pstore not cleared on boot

[Launchpad Bug Tracker]

This bug was fixed in the package linux-bluefield - 5.4.0-1070.76

---
linux-bluefield (5.4.0-1070.76) focal; urgency=medium

  * focal/linux-bluefield: 5.4.0-1070.76 -proposed tracker (LP:
#2030986)

  * EFI pstore not cleared on boot (LP: #1978079)
- [Config] bluefield: Enable CONFIG_EFI_VARS_PSTORE as build-in
- [Config] bluefield: Remove efi-pstore from modules list

  * Focal update: v5.4.246 upstream stable release (LP: #2028981)
- [Config] bluefield: updateconfigs for SCSI_DPT_I2O
- SAUCE: xfrm: Check if_id in xfrm full offload

  * rshim console truncates dmesg output due to tmfifo issue (LP: #2028197)
- SAUCE: mlxbf-tmfifo.c: Fix rhsim console w/ truncated dmesg output

  * mlxbf-gige: Fix kernel panic after reboot (LP: #2030765)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 1/2)
- SAUCE: mlxbf-gige: Fix kernel panic after reboot (part 2/2)

  [ Ubuntu: 5.4.0-162.179 ]

  * focal/linux: 5.4.0-162.179 -proposed tracker (LP: #2031128)
  * libgnutls report "trap invalid opcode" when trying to install packages over
https (LP: #2031093)
- [Config]: disable CONFIG_GDS_FORCE_MITIGATION

  [ Ubuntu: 5.4.0-160.177 ]

  * focal/linux: 5.4.0-160.177 -proposed tracker (LP: #2031017)
  * Fix boot test warning for log_check "CPU: 0 PID: 0 at
arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0" (LP: #2031022)
- x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to 
init_fpstate")

  [ Ubuntu: 5.4.0-158.175 ]

  * focal/linux: 5.4.0-158.175 -proposed tracker (LP: #2030466)
  * CVE-2022-40982
- x86/mm: Initialize text poking earlier
- x86/mm: fix poking_init() for Xen PV guests
- x86/mm: Use mm_alloc() in poking_init()
- mm: Move mm_cachep initialization to mm_init()
- init: Provide arch_cpu_finalize_init()
- x86/cpu: Switch to arch_cpu_finalize_init()
- ARM: cpu: Switch to arch_cpu_finalize_init()
- sparc/cpu: Switch to arch_cpu_finalize_init()
- um/cpu: Switch to arch_cpu_finalize_init()
- init: Remove check_bugs() leftovers
- init: Invoke arch_cpu_finalize_init() earlier
- init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
- x86/fpu: Remove cpuinfo argument from init functions
- x86/fpu: Mark init functions __init
- x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
- x86/xen: Fix secondary processors' FPU initialization
- x86/speculation: Add Gather Data Sampling mitigation
- x86/speculation: Add force option to GDS mitigation
- x86/speculation: Add Kconfig option for GDS
- KVM: Add GDS_NO support to KVM
- Documentation/x86: Fix backwards on/off logic about YMM support
- [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT and
  CONFIG_GDS_FORCE_MITIGATION
  * CVE-2023-3609
- net/sched: cls_u32: Fix reference counter leak leading to overflow
  * CVE-2023-20593
- x86/cpu/amd: Move the errata checking functionality up
- x86/cpu/amd: Add a Zenbleed fix
  * CVE-2023-3611
- net/sched: sch_qfq: account for stab overhead in qfq_enqueue
  * stacked overlay file system mounts that have chroot() called against them
appear to be getting locked (by the kernel most likely?) (LP: #2016398)
- SAUCE: overlayfs: fix reference count mismatch
  * Focal update: v5.4.246 upstream stable release (LP: #2028981)
- RDMA/efa: Fix unsupported page sizes in device
- RDMA/bnxt_re: Enable SRIOV VF support on Broadcom's 57500 adapter series
- RDMA/bnxt_re: Refactor queue pair creation code
- RDMA/bnxt_re: Fix return value of bnxt_re_process_raw_qp_pkt_rx
- iommu/rockchip: Fix unwind goto issue
- iommu/amd: Don't block updates to GATag if guest mode is on
- dmaengine: pl330: rename _start to prevent build error
- net/mlx5: fw_tracer, Fix event handling
- netrom: fix info-leak in nr_write_internal()
- af_packet: Fix data-races of pkt_sk(sk)->num.
- amd-xgbe: fix the false linkup in xgbe_phy_status
- mtd: rawnand: ingenic: fix empty stub helper definitions
- af_packet: do not use READ_ONCE() in packet_bind()
- tcp: deny tcp_disconnect() when threads are waiting
- tcp: Return user_mss for TCP_MAXSEG in CLOSE/LISTEN state if user_mss set
- net/sched: sch_ingress: Only create under TC_H_INGRESS
- net/sched: sch_clsact: Only create under TC_H_CLSACT
- net/sched: Reserve TC_H_INGRESS (TC_H_CLSACT) for ingress (clsact) Qdiscs
- net/sched: Prohibit regrafting ingress or clsact Qdiscs
- net: sched: fix NULL pointer dereference in mq_attach
- ocfs2/dlm: move BITS_TO_BYTES() to bitops.h for wider use
- net/netlink: fix NETLINK_LIST_MEMBERSHIPS length report
- udp6: Fix race condition in udp6_sendmsg & connect
- net: dsa: mv88e6xxx: Increase wait after reset deactivation
- mtd: rawnand: marvell: ensure timing values are written
- mtd: rawnand: marvell: don't set the NAND frequency select
- watchdog: menz069_wdt: fix watchdog 

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

[Gunnar Hjalmarsson]

@Steve: I made such a change to the MR.

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

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

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

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


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

[Touch-packages] [Bug 2033949] Re: Does not work with sources in deb822 format

[Julian Andres Klode]

For 23.10, we will support deb822 sources for third party sources,
especially PPAs, but due to complex interactions did not fully manage to
create a decent experience for ubuntu.sources so far..

So in my local git branches:

The bits I got working correctly still ended up splitting paragraphs
into multiple ones and not merging them back again, so if you enabled a
component and disabled it again, you suddenly had two paragraphs.

There's missing bits still were it writes to sources.list if you edit
ubuntu.sources, actually generates duplicate entries and then stops
working.

** Changed in: software-properties (Ubuntu Mantic)
   Status: Fix Released => In Progress

** Summary changed:

- Does not work with sources in deb822 format
+ Does not work with Ubuntu sources in deb822 format

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

Title:
  Does not work with Ubuntu sources in deb822 format

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Mantic:
  In Progress

Bug description:
  On my Mantic I have sources in new deb822 format.
  Starting software-properties-gtk seems my server is Main server, but from 
/etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I 
software-properties-gtk seems unable to change.

  corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources
  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic mantic-updates mantic-backports
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic-security
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  corrado@corrado-n16-mm-0901:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 10:33:12 2023
  InstallationDate: Installed on 2023-09-01 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+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 2037007] Re: Checked for apps to update in the new software app

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2036460, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2037007/+attachment/5703318/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2037007/+attachment/5703320/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2037007/+attachment/5703321/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2036460

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Checked for apps to update in the new software app

Status in packagekit package in Ubuntu:
  New

Bug description:
  Checked for apps to update in the new software app

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: packagekit 1.2.7-1
  Uname: Linux 6.5.0-5-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 21 21:04:51 2023
  ExecutablePath: /usr/libexec/packagekitd
  ExecutableTimestamp: 1693144014
  ProcCmdline: /usr/libexec/packagekitd
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: packagekit
  UserGroups: N/A

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

[Tais P. Hansen]

Tested 252.5-2ubuntu3.2 on Ubuntu 23.04 (lunar) and it still hangs for 2
minutes during boot.

$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 7
Found link 6
Found link 5
Found link 4
Found link 3
Found link 2
Found link 1
lo: link is ignored
wlp6s0: link is not managed by networkd (yet?).
virbr2: link is not managed by networkd (yet?).
enp5s0: link is not managed by networkd (yet?).
enp4s0: link is not managed by networkd (yet?).
virbr0: link is not managed by networkd (yet?).
tailscale0: link is not managed by networkd (yet?).
Timeout occurred while waiting for network connectivity.

Desktop system.

Both systemd-networkd and NetworkManager services are running and
active.

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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 2037004] [NEW] warnings in terminal with software-properties-gtk

[Brian Murray]

Public bug reported:

When running software-properties-gtk and switching to the "Additional
Drivers" tab I saw the following warnings in my terminal:

 $ software-properties-gtk 
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
...

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: software-properties-gtk 0.99.39
ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
Uname: Linux 6.5.0-4-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 11:49:24 2023
InstallationDate: Installed on 2018-08-10 (1868 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: software-properties
UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug mantic rls-nn-incoming

** Tags added: rls-nn-incoming

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  warnings in terminal with software-properties-gtk

Status in software-properties package in Ubuntu:
  New

Bug description:
  When running software-properties-gtk and switching to the "Additional
  Drivers" tab I saw the following warnings in my terminal:

   $ software-properties-gtk 
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  udevadm hwdb is deprecated. Use systemd-hwdb instead.
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 11:49:24 2023
  InstallationDate: Installed on 2018-08-10 (1868 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2037004/+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 2033949] Re: Does not work with sources in deb822 format

[Alexander Bejarano]

** Changed in: software-properties (Ubuntu Mantic)
   Status: Confirmed => Fix Released

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

Title:
  Does not work with sources in deb822 format

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Mantic:
  Fix Released

Bug description:
  On my Mantic I have sources in new deb822 format.
  Starting software-properties-gtk seems my server is Main server, but from 
/etc/apt/sources.list.d/ubuntu.sources I see server from Italy and I 
software-properties-gtk seems unable to change.

  corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources
  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic mantic-updates mantic-backports
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  Types: deb
  URIs: http://it.archive.ubuntu.com/ubuntu
  Suites: mantic-security
  Components: main restricted universe multiverse
  Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

  corrado@corrado-n16-mm-0901:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: software-properties-gtk 0.99.39
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 10:33:12 2023
  InstallationDate: Installed on 2023-09-01 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2033949/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop

[Leó Kolbeinsson]

Confirm I have not seen this again after 18/08.

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

Title:
  File system layers missing - unable to boot live cd Ubuntu Mantic
  Desktop

Status in ubuntu-desktop-installer:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error
  reported when attempting to boot live installation media -

  File system layers missing:\n
  '/cdrom/casper/minimal.standard.live.squashfs .. see attached
  screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2031899/+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 2031899] Re: File system layers missing - unable to boot live cd Ubuntu Mantic Desktop

[Brian Murray]

This was sorted out a few weeks ago, but I don't have the primary bug at
hand.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-desktop-installer
   Status: New => Invalid

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

Title:
  File system layers missing - unable to boot live cd Ubuntu Mantic
  Desktop

Status in ubuntu-desktop-installer:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Testing Ubuntu Mantic desktop daily iso 18-08-2023 the folling error
  reported when attempting to boot live installation media -

  File system layers missing:\n
  '/cdrom/casper/minimal.standard.live.squashfs .. see attached
  screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2031899/+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 2036611] Re: FFe: Mesa 23.2.0

[Timo Aaltonen]

https://tracker.debian.org/pkg/mesa

shows that mutter autopkgtest is failing for some reason on arm64, but
seems otherwise fine

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)

  xnox: Separately to amd64, this new mesa would also be useful on many
  arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu
  Concept X13s, and Apple / Asahi hardware.

  I strongly request that upgrade of mesa is also considered because of
  the Arm platform improvements in Mesa 23.2.0.

  The request is to ship rc, SRU upto final upstream GA .0 release, and
  enforce SRU policy after that.

  Other distributions are also shipping this Mesa RC largely due to the
  very same reasons, thus this will align hardware compatiblity and
  performance with other distributions launching this autumn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2036998] [NEW] Xorg freeze

[Tuomas Heino]

Public bug reported:

Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
May have reported this earlier myself. Details to be filled later.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Thu Sep 21 20:20:00 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2022-04-27 (512 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
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/2036998

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
  May have reported this earlier myself. Details to be filled later.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 21 20:20:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (512 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: 

[Touch-packages] [Bug 2036885] Re: please add API to exclude things

[Dimitri John Ledkov]

dracut-install has these options:
  -P --mod-filter-nopathExclude kernel modules by path regexp
  -N --mod-filter-nonameExclude kernel modules by name regexp

I'm more thinking along the lines of:

rm_modules_dir()
rm_modules()

Which would apply mod-filter-nopath / mod-filter-noname, after the full
list of modules to include has been assembled.

I am assuming that any add module requests are bundled together into a
single dracut-install call, such that rm_modules()/rm_modules_dir() call
will be effective.

Then raspberri pi hook may have a list of things to exclude, which can
then be optionally disabled based on the toggles it would have.

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

Title:
  please add API to exclude things

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Please add API to exclude things

  It would be useful on Pi to say "yes include all graphics" but do
  exclude "amdgpu, nvidia" drivers and firmware related to those.

  Something along the lines of a "exclude filter list" for drivers &
  firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036885/+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 2036886] Re: please add api to repack initramfs

[Dimitri John Ledkov]

** Description changed:

  please add api to repack initramfs
  
- from the results of unpackinitramfs, including all early & main dirs
+ from the results of unpackinitramfs, including all early & main dirs.
+ 
+ Userstory: i want to tweak my initrd in-place by replacing broken
+ libc.so.6 with a patched one, I want to use unmkinitramfs, modify files
+ in main, repack it and boot it.
+ 
+ CLI:
+ 
+ $ unmkinitramfs /boot/initrd.img unpacked-initrd
+ $ ls unpacked-initrd/
+ early  early2  main
+ $ (edit things in unpacked-initrd/main/)
+ $ remkinitramfs unpacked-initrd patched-initrd.img
+ 
+ Where patched-initrd.img is now similar to /boot/initrd.img, apart from
+ the changed things.
+ 
+ I expect remkinitramfs like functionality that will take the output of
+ unmkinitramfs (e.g. unpacked-initrd/) directory as input, do
+ uncompressed cpio archives out of all the subdirs, make compressed cpio
+ archive out of main, and produce a patched-initrd.img that is ready for
+ booting.
+ 
+ It is very close to what mkinitramfs does, but skip calling all the
+ hooks to create things a fresh, and just do the final assembly step of
+ cpio and compression.

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

Title:
  please add api to repack initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  please add api to repack initramfs

  from the results of unpackinitramfs, including all early & main dirs.

  Userstory: i want to tweak my initrd in-place by replacing broken
  libc.so.6 with a patched one, I want to use unmkinitramfs, modify
  files in main, repack it and boot it.

  CLI:

  $ unmkinitramfs /boot/initrd.img unpacked-initrd
  $ ls unpacked-initrd/
  early  early2  main
  $ (edit things in unpacked-initrd/main/)
  $ remkinitramfs unpacked-initrd patched-initrd.img

  Where patched-initrd.img is now similar to /boot/initrd.img, apart
  from the changed things.

  I expect remkinitramfs like functionality that will take the output of
  unmkinitramfs (e.g. unpacked-initrd/) directory as input, do
  uncompressed cpio archives out of all the subdirs, make compressed
  cpio archive out of main, and produce a patched-initrd.img that is
  ready for booting.

  It is very close to what mkinitramfs does, but skip calling all the
  hooks to create things a fresh, and just do the final assembly step of
  cpio and compression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036886/+subscriptions


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

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

[Steve Langasek]

Gunnar, one concern raised is that 'Sans 11' may be a different font
size than is used for the current interface font, so setting this may
cause legibility problems for users who have intentionally configured
larger fonts.  Can you suggest a workaround that's font-size-neutral?

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

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

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

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


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

[Touch-packages] [Bug 2036611] Re: FFe: Mesa 23.2.0

[Dimitri John Ledkov]

** Description changed:

  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we have
  an rc3 which is "only" two weeks old. Yes, we are getting close to
  mantic release but this series is something we want for Intel Meteor
  Lake support.
  
  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.
  
  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)
  
- 
- xnox: Separately to amd64, this new mesa would also be useful on many arm64 
platforms with a lot of improvements for RaspberryPi, Ubuntu Concept X13s, and 
Apple / Asahi hardware.
+ xnox: Separately to amd64, this new mesa would also be useful on many
+ arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu
+ Concept X13s, and Apple / Asahi hardware.
  
  I strongly request that upgrade of mesa is also considered because of
  the Arm platform improvements in Mesa 23.2.0.
+ 
+ The request is to ship rc, SRU upto final upstream GA .0 release, and
+ enforce SRU policy after that.
+ 
+ Other distributions are also shipping this Mesa RC largely due to the
+ very same reasons, thus this will align hardware compatiblity and
+ performance with other distributions launching this autumn.

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)

  xnox: Separately to amd64, this new mesa would also be useful on many
  arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu
  Concept X13s, and Apple / Asahi hardware.

  I strongly request that upgrade of mesa is also considered because of
  the Arm platform improvements in Mesa 23.2.0.

  The request is to ship rc, SRU upto final upstream GA .0 release, and
  enforce SRU policy after that.

  Other distributions are also shipping this Mesa RC largely due to the
  very same reasons, thus this will align hardware compatiblity and
  performance with other distributions launching this autumn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2036611] Re: FFe: Mesa 23.2.0

[Dimitri John Ledkov]

** Description changed:

  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we have
  an rc3 which is "only" two weeks old. Yes, we are getting close to
  mantic release but this series is something we want for Intel Meteor
  Lake support.
  
  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.
  
  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)
+ 
+ 
+ xnox: Separately to amd64, this new mesa would also be useful on many arm64 
platforms with a lot of improvements for RaspberryPi, Ubuntu Concept X13s, and 
Apple / Asahi hardware.
+ 
+ I strongly request that upgrade of mesa is also considered because of
+ the Arm platform improvements in Mesa 23.2.0.

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Critical

** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-23.10

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)

  xnox: Separately to amd64, this new mesa would also be useful on many
  arm64 platforms with a lot of improvements for RaspberryPi, Ubuntu
  Concept X13s, and Apple / Asahi hardware.

  I strongly request that upgrade of mesa is also considered because of
  the Arm platform improvements in Mesa 23.2.0.

  The request is to ship rc, SRU upto final upstream GA .0 release, and
  enforce SRU policy after that.

  Other distributions are also shipping this Mesa RC largely due to the
  very same reasons, thus this will align hardware compatiblity and
  performance with other distributions launching this autumn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2036611/+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 2034656] Re: Update Ubuntu ESM cache only once daily?

[Grant Orndorff]

pro-client doesn't run apt upgrade in any scenario or configure the
system to do so.

Do we have control over any of the offending machines? I'd still like to
see a `pro collect-logs` from one of them to be sure nothing unexpected
is happening pro-client related.

That the major offending package is azure-specific may be a clue that it
could be something happening only on Azure. We can talk to the cloud
team about it. We would only see the spike on esm.ubuntu.com because
clouds use mirrors for the main archive. Adding cloud-images here which
I think will notify them.

I went ahead and checked default apt configuration on a couple machines and 
found the following:
on Azure Bionic Pro:
$ apt-config dump | grep Periodic
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "1";

on GCP Bionic Pro:
$ apt-config dump | grep Periodic
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "1";
APT::Periodic::Unattended-Upgrade "1";

So at least in those two places, "Download-Upgradeable-Packages" is
disabled ("0"), which I believe is what corresponds to the apt upgrade
--download-only in apt.daily, but I'm out of my depth here. Just to be
sure though, I'm also adding this bug to apt in case this is a problem
with default configuration there.




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

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Update Ubuntu ESM cache only once daily?

Status in cloud-images:
  New
Status in apt package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We're seeing frequent alerts on the Ubuntu ESM archive servers due to
  surges in requests. On two systems, I'm seeing this:

  | Sep  6 05:47:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 05:47:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 10:49:35 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 10:49:35 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 17:17:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 17:17:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  6 23:47:16 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 23:47:17 machine-2 systemd[1]: Finished Update the local ESM caches.
  | Sep  7 01:55:02 machine-2 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  7 01:55:02 machine-2 systemd[1]: Finished Update the local ESM caches.

  On another:

  | Sep  6 02:41:02 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 02:41:03 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 09:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 09:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 15:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 15:32:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  6 22:02:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  6 22:02:41 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.
  | Sep  7 04:32:40 is-bastion-ps5 systemd[1]: Starting Update the local ESM 
caches...
  | Sep  7 04:32:42 is-bastion-ps5 systemd[1]: Finished Update the local ESM 
caches.

  This is all from `/usr/lib/systemd/system/esm-cache.service` which
  calls `/usr/lib/ubuntu-advantage/esm_cache.py`.

  Can we please have this run less frequent? Perhaps only once daily
  which aligns with APT and apt-daily-upgrade.service / unattended-
  upgrades?

  Perhaps check existence of a file and run if not, then age of that
  same file and only run if it's older than a day?

  I think, from what I can see, this may be triggered from
  /lib/systemd/system/ua-timer.timer and /etc/apt/apt.conf.d/20apt-esm-
  hook.conf?

  See also LP:1554848 which was for APT.

  On Trusty and Xenial clients we only seem to update daily, but the
  problem is worse as it's a cron.daily job, so all clients fire
  simultaneously - could we get this changed to a cron.d job with a
  randomised firing time instead?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2034656/+subscriptions


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

[Touch-packages] [Bug 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds

[Julian Andres Klode]

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

** Also affects: software-properties (Ubuntu Mantic)
   Importance: Undecided
   Status: Confirmed

** Also affects: ppa-purge (Ubuntu Mantic)
   Importance: High
   Status: Triaged

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

Title:
  [mantic] ppa-purge no longer purges what add-apt-repository adds

Status in ppa-purge package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Confirmed
Status in ppa-purge source package in Mantic:
  Triaged
Status in software-properties source package in Mantic:
  Confirmed

Bug description:
  Test Case
  -
  From Ubuntu 23.10:

  sudo apt install hello
  sudo add-apt-repository ppa:jbicha/temp
  sudo apt upgrade

  apt policy hello

  sudo ppa-purge ppa:jbicha/temp

  apt policy hello
  reveals that the PPA version of hello is still installed

  Also /etc/apt/sources.list.d/jbicha-ubuntu-temp-mantic.sources
  is still present and active

  What Should Happen
  --
  ppa-purge should disable the PPA and reinstall any PPA packages with the 
version apt currently sees.

  Background
  --
  add-apt-repository creates deb822 sources lists, starting in Ubuntu 23.10

  https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-
  default/29333

  Other Info
  --
  add-apt-repository has a --remove option

  But it does not do the reinstall part which is important
  Honestly, that feature is so important, I suggest that add-apt-repository 
take over the functionality of ppa-purge so that we always get the ppa-purge 
behavior

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/2036761/+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 2033440] Re: ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"

[Julian Andres Klode]

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

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

Title:
  ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Lunar:
  Won't Fix
Status in ubuntu-meta source package in Mantic:
  New

Bug description:
  Recommend demoting pipewire-audio from Depends: to Recommends:.

  Reason: While it's not ideal, the Ubuntu Desktop can still function on
  the pulseaudio backend rather than using the direct pipewire-alsa
  backend which conflicts with the pulseaudio package. This would help
  people who wish to have a more traditional JACK setup that is bridged
  to pulseaudio. Right now, this setup is incompatible.

  
  Original description:

  I have installed successfully the standard Ubuntu 23.04 (on a 500 GB
  external USB drive). Immediately after the installation, I have also
  installed with apt the "ubuntustudio-installer" package.

  In the dialog provided by the ubuntustudio-installer, I have selected
  the following metapackages:

  - linux-lowlatency
  - ubuntustudio-lowlatency-settings
  - ubuntustudio-performance-tweaks
  - ubuntustudio-audio
  - ubuntu-pulseaudio-config

  and pressed "Modify installed Package Selection"

  After a while a "qaptbatch" dialog has appeared with title

  "Commit Error"

  and message

  "An error occurred while applying changes"

  So the installation has failed. Then I have tried to manually install
  each metapackage in the list above with apt and every package was
  installed successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2033440/+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 2036441] Re: whoopsie cannot report crash reports from live environment

[Julian Andres Klode]

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

** Also affects: whoopsie (Ubuntu Mantic)
   Importance: High
   Status: New

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

Title:
  whoopsie cannot report crash reports from live environment

Status in whoopsie package in Ubuntu:
  New
Status in whoopsie source package in Mantic:
  New

Bug description:
  The .uploaded file corresponding to a crash report had NULL for its
  contents so I used journalctl to find information about whoopsie and
  saw the following:

  Sep 18 15:28:42 ubuntu systemd[1]: Started whoopsie.service - crash report 
submission.
  Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Using lock path: 
/var/lock/whoopsie/lock
  Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Parsing 
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash.
  Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Unable to parse report 
(/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash): 
/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash could not be opened.
  Sep 18 15:28:42 ubuntu systemd[1]: whoopsie.service: Deactivated successfully.

  This was on an Ubuntu daily-legacy image dated 20230918.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: whoopsie 0.2.77
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.482
  CrashReports:
   600:109:116:5:2023-09-18 15:28:42.434625080 +:2023-09-18 
15:30:28.058067902 +:/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.uploaded
   644:1000:1000:0:2023-09-18 15:28:11.774841581 +:2023-09-18 
15:28:11.774841581 +:/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.upload
   640:1000:1000:650635:2023-09-18 15:25:02.717362880 +:2023-09-18 
15:28:42.410625168 +:/var/crash/_usr_lib_ubiquity_bin_ubiquity.0.crash
   640:1000:116:181411:2023-09-18 15:21:05.423967599 +:2023-09-18 
15:21:06.423967599 +:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 18 15:31:48 2023
  LiveMediaBuild: Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20230918)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Gunnar Hjalmarsson]

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

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

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

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

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


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

[Touch-packages] [Bug 1923052] Re: screen reader does not read ubiquity window after it is launched in "Try Ubuntu" session

[Tim Holmes-Mitra]

Not a release blocker.

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  screen reader does not read ubiquity window after it is launched in
  "Try Ubuntu" session

Status in at-spi2-core package in Ubuntu:
  Incomplete
Status in orca package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Confirmed
Status in at-spi2-core source package in Jammy:
  Incomplete
Status in orca source package in Jammy:
  Incomplete
Status in ubiquity source package in Jammy:
  Confirmed
Status in at-spi2-core source package in Mantic:
  Incomplete
Status in orca source package in Mantic:
  Incomplete
Status in ubiquity source package in Mantic:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run Ubuntu MATE 21.04 installation media
  2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info 
testcase by pressing ++ to activate screenreader with shown 
Ubiquity window, press  to select some button

  Expected result:
  * screen reader reads ubiquity window

  Actual result:
  * screen reader does not read ubiquity window

  Note: screen reader actually works, it reads other windows - for
  example the terminal opened by ++.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.14
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  8 13:01:30 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions


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

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

[Tim Holmes-Mitra]

** Tags removed: rls-mm-incoming

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

Title:
  some text became unreadable during a distribution upgrade

Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in ubuntu-meta source package in Mantic:
  Confirmed
Status in ubuntu-release-upgrader source package in Mantic:
  Confirmed

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

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

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


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

[Touch-packages] [Bug 2019939] Re: Outdated documentation about NetworkManager keyfiles

[Tim Holmes-Mitra]

** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing

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

Title:
  Outdated documentation about NetworkManager keyfiles

Status in debian-handbook package in Ubuntu:
  Won't Fix
Status in dhcpcanon package in Ubuntu:
  Won't Fix
Status in fai package in Ubuntu:
  New
Status in gnome-user-docs package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  Fix Committed
Status in scap-security-guide package in Ubuntu:
  New
Status in wifi-qr package in Ubuntu:
  New

Bug description:
  The affected packages contain documentation or examples about
  NetworkManager keyfiles, which might not be appropriate anymore on
  Ubuntu, since the Netplan integration was enabled in NetworkManager
  (starting with Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-handbook/+bug/2019939/+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 2029049] Re: NetworkManager crashed with SIGABRT in g_mutex_clear()

[Sebastien Bacher]

The issue was fixed in
https://launchpad.net/ubuntu/+source/glib2.0/2.78.0-2

** Changed in: network-manager (Ubuntu)
   Importance: Medium => High

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  NetworkManager crashed with SIGABRT in g_mutex_clear()

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  instant crash every 5 minutes

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.6-2ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sun Jul 30 12:49:16 2023
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2023-07-29 (1 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230729)
  IpRoute:
   default via 192.168.179.94 dev wlo1 proto dhcp src 192.168.179.174 metric 
600 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 
   192.168.179.0/24 dev wlo1 proto kernel scope link src 192.168.179.174 metric 
600
  JournalErrors:
   juil. 30 12:49:18 hostname systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
   juil. 30 12:49:18 hostname systemd[1]: NetworkManager.service: Failed with 
result 'core-dump'.
   juil. 30 12:49:19 hostname generate[7708]: Permissions for 
/etc/netplan/00-installer-config.yaml are too open. Netplan configuration 
should NOT be accessible by others.
   juil. 30 12:49:19 hostname generate[7708]: Permissions for 
/etc/netplan/01-network-manager-all.yaml are too open. Netplan configuration 
should NOT be accessible by others.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: NetworkManager crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.42.6   connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2029049/+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 2033639] Re: debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

[Julian Andres Klode]

** Also affects: debug-me (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052313
   Importance: Unknown
   Status: Unknown

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

Title:
  debug-me 1.20221231-1 FTBFS on ppc64el due to internal ld.gold error

Status in binutils package in Ubuntu:
  New
Status in debug-me package in Ubuntu:
  Triaged
Status in debug-me package in Debian:
  Unknown

Bug description:
  debug-me 1.20221231-1 fails to build from source on ppc64el due to
  internal ld.gold error (binutils 2.41-4ubuntu1):

  ```
  Linking dist/build/debug-me/debug-me ...
  /usr/bin/ld.gold: internal error in set_xindex, at ../../gold/object.h:1050
  collect2: error: ld returned 1 exit status
  `powerpc64le-linux-gnu-gcc' failed in phase `Linker'. (Exit code: 1)
  ```

  Full log: https://launchpadlibrarian.net/684538812/buildlog_ubuntu-
  mantic-ppc64el.debug-me_1.20221231-1_BUILDING.txt.gz

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

[Nick Rosbrook]

Robert - are you on on desktop or server? If the links are not managed
by systemd-networkd, it seems like you would be running NetworkManager?
What does this show for you?

$ systemctl status systemd-networkd
$ systemctl status NetworkManager

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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 2036956] [NEW] Problems in browing like firefox, and chromium and some other application

[Muhammad Yahya Butt]

Public bug reported:

Whenever I open the browser and some other application, My cursor
doesn't work here at the top right side of the screen. Usually, it
happens only when I open browser or few of the application, with that
problem I cannot close the tab button, minimize, maximize, can't use
some of the menu buttons on the top right side of the browser.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-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 Sep 21 16:59:55 2023
DistUpgraded: Fresh install
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb]
InstallationDate: Installed on 2023-09-07 (13 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Dell Inc. Latitude E7440
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=ba68d84a-c8cc-4d13-839b-42fed52c8449 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2016
dmi.bios.release: 65.20
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A20
dmi.board.name: 091TRH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd12/22/2016:br65.20:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn091TRH:rvrA00:cvnDellInc.:ct9:cvr:sku05CB:
dmi.product.name: Latitude E7440
dmi.product.sku: 05CB
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
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 corruption 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/2036956

Title:
  Problems in browing like firefox, and chromium and some other
  application

Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever I open the browser and some other application, My cursor
  doesn't work here at the top right side of the screen. Usually, it
  happens only when I open browser or few of the application, with that
  problem I cannot close the tab button, minimize, maximize, can't use
  some of the menu buttons on the top right side of the browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
  Uname: Linux 6.2.0-33-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 Sep 21 16:59:55 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05cb]
  InstallationDate: Installed on 2023-09-07 (13 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: Dell Inc. Latitude E7440
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=ba68d84a-c8cc-4d13-839b-42fed52c8449 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2016
  dmi.bios.release: 65.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 091TRH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 2036887] Re: package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1

[Paul White]

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

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

Title:
  package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso
  instalado paquete cups script post-installation devolvió el código de
  salida de error 1

Status in cups package in Ubuntu:
  New

Bug description:
  No details.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  Date: Thu Sep 21 11:59:31 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  ErrorMessage: el subproceso instalado paquete cups script post-installation 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2021-12-21 (639 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6d1a Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
   Bus 001 Device 004: ID 0bda:c829 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 3511
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 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
  Snap: cups 2.4.6-4 (latest/stable)
  Title: package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso 
instalado paquete cups script post-installation devolvió el código de salida de 
error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2021
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 06F315
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd10/07/2021:br1.6:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn06F315:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 3511
  dmi.product.sku: 0AB0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2036887/+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 2036887] [NEW] package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso instalado paquete cups script post-installation devolvió el código de salida de error 1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

No details.

ProblemType: Package
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
CasperMD5CheckResult: skip
CupsErrorLog:
 
Date: Thu Sep 21 11:59:31 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ErrorMessage: el subproceso instalado paquete cups script post-installation 
devolvió el código de salida de error 1
InstallationDate: Installed on 2021-12-21 (639 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:6d1a Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
 Bus 001 Device 004: ID 0bda:c829 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15 3511
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic 
root=UUID=53ec6836-3cb0-4e0d-b3b3-346372cfdc51 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
Snap: cups 2.4.6-4 (latest/stable)
Title: package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso 
instalado paquete cups script post-installation devolvió el código de salida de 
error 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2021
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 06F315
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd10/07/2021:br1.6:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn06F315:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15 3511
dmi.product.sku: 0AB0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal
-- 
package cups 2.3.1-9ubuntu1.6 failed to install/upgrade: el subproceso 
instalado paquete cups script post-installation devolvió el código de salida de 
error 1
https://bugs.launchpad.net/bugs/2036887
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups 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 2036611] Re: FFe: Mesa 23.2.0

[Timo Aaltonen]

** Description changed:

  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we have
  an rc3 which is "only" two weeks old. Yes, we are getting close to
  mantic release but this series is something we want for Intel Meteor
  Lake support.
  
  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.
  
  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
- (status: i386/riscv64 build failed due to an upstream bug, but should be 
fixed by latest upload)
+ (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)

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

Title:
  FFe: Mesa 23.2.0

Status in mesa package in Ubuntu:
  New

Bug description:
  Upstream still hasn't released Mesa 23.2.0 (as of Sep 19th) which is
  almost seven weeks past it's original release date. But at least we
  have an rc3 which is "only" two weeks old. Yes, we are getting close
  to mantic release but this series is something we want for Intel
  Meteor Lake support.

  This is now fresh in Debian unstable, and has been in Fedora 39 for a
  month already without any apparent drama.

  Build available at the x-staging ppa
  https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging/+packages
  (status: i386 build failed due to an upstream bug, which requires 
llvmspirvlib headers to exist even if rusticl OpenCL driver is not enabled)

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

[Julian Andres Klode]

Just continue appending packages that APT would install until it stops
trying to install new stuff.

-- 
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 Released
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 2036885] Re: please add API to exclude things

[Benjamin Drung]

Yes, we do not have an easy way to exclude kernel modules. A workaround
would be to add a hook in /etc/initramfs-tools/hooks to remove those
modules, but this is ugly.

We could add another option to `MODULES` (besides `most`, `dep`,
`netboot`, `list`) to exclude the amdgpu+nvidia drivers.

Please suggest how the API could look like.

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

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

Title:
  please add API to exclude things

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Please add API to exclude things

  It would be useful on Pi to say "yes include all graphics" but do
  exclude "amdgpu, nvidia" drivers and firmware related to those.

  Something along the lines of a "exclude filter list" for drivers &
  firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036885/+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 2036885] Re: please add API to exclude things

[Dimitri John Ledkov]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  please add API to exclude things

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please add API to exclude things

  It would be useful on Pi to say "yes include all graphics" but do
  exclude "amdgpu, nvidia" drivers and firmware related to those.

  Something along the lines of a "exclude filter list" for drivers &
  firmware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036885/+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 2036886] [NEW] please add api to repack initramfs

[Dimitri John Ledkov]

Public bug reported:

please add api to repack initramfs

from the results of unpackinitramfs, including all early & main dirs

** Affects: initramfs-tools (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  please add api to repack initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  please add api to repack initramfs

  from the results of unpackinitramfs, including all early & main dirs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036886/+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 2036885] [NEW] please add API to exclude things

[Dimitri John Ledkov]

Public bug reported:

Please add API to exclude things

It would be useful on Pi to say "yes include all graphics" but do
exclude "amdgpu, nvidia" drivers and firmware related to those.

Something along the lines of a "exclude filter list" for drivers &
firmware.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: raspi

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

Title:
  please add API to exclude things

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please add API to exclude things

  It would be useful on Pi to say "yes include all graphics" but do
  exclude "amdgpu, nvidia" drivers and firmware related to those.

  Something along the lines of a "exclude filter list" for drivers &
  firmware.

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

[Robert Hrovat]

Tested 249.11-0ubuntu3.11 on Ubuntu 22.04 (jammy) and system still wait
for network to be configured

$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 3
Found link 2
Found link 1
enp2s0: link is not managed by networkd (yet?).
wlp3s0: link is not managed by networkd (yet?).
lo: link is ignored
enp2s0: link is not managed by networkd (yet?).
wlp3s0: link is not managed by networkd (yet?).
lo: link is ignored
Timeout occurred while waiting for network connectivity.

-- 
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 Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [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/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.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 2032379] Re: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Benjamin Drung]

Marking this bug as invalid in favour of bug #2032577.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  looks like an issue with compression/decompression?

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.4
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Aug 21 01:19:18 2023
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-04-09 (863 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.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379/+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 2032577] Re: xz segfault error in liblzma.so.5.2.5

[Benjamin Drung]

Attached is the retraced crash.

** Attachment added: "retraced_usr_bin_xz.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+attachment/5702596/+files/retraced_usr_bin_xz.0.crash

** Changed in: xz-utils (Ubuntu)
   Status: Incomplete => New

** Description changed:

- xz segfaults. More details in 
+ xz segfaults. More details in
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379
- 
  
  From Dmesg.txt on that report
  
  [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a
  sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000]
+ 
+ ProblemType: Crash
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ ExecutablePath: /usr/bin/xz
+ ExecutableTimestamp: 1649422298
+ InstallationDate: Installed on 2021-04-09 (863 days ago)
+ InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ Package: xz-utils 5.2.5-2ubuntu1
+ ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9
+ ProcCwd: /
+ ProcEnviron:
+  LC_CTYPE=C.UTF-8
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+ ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
+ SegvAnalysis:
+  Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d
+  PC (0x7f9b3f780c1a) ok
+  source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 
0x7f9a90021000-0x7f9a9400 ---p None
+  destination "%r10d" ok
+  Stack memory exhausted (SP below stack segment)
+ SegvReason: reading VMA None
+ Signal: 11
+ SourcePackage: xz-utils
+ Title: xz crashed with SIGSEGV
+ Uname: Linux 5.19.0-38-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago)
+ UserGroups: N/A

** Description changed:

  xz segfaults. More details in
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379
  
  From Dmesg.txt on that report
  
  [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a
  sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000]
  
  ProblemType: Crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  ExecutablePath: /usr/bin/xz
  ExecutableTimestamp: 1649422298
  InstallationDate: Installed on 2021-04-09 (863 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Package: xz-utils 5.2.5-2ubuntu1
  ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9
  ProcCwd: /
  ProcEnviron:
-  LC_CTYPE=C.UTF-8
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
+  LC_CTYPE=C.UTF-8
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  SegvAnalysis:
-  Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d
-  PC (0x7f9b3f780c1a) ok
-  source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 
0x7f9a90021000-0x7f9a9400 ---p None
-  destination "%r10d" ok
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d
+  PC (0x7f9b3f780c1a) ok
+  source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 
0x7f9a90021000-0x7f9a9400 ---p None
+  destination "%r10d" ok
+  Stack memory exhausted (SP below stack segment)
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: xz-utils
  Title: xz crashed with SIGSEGV
  Uname: Linux 5.19.0-38-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago)
  UserGroups: N/A
+ StacktraceTop:
+  bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", 
cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, 
cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at 
../../../../src/liblzma/lz/lz_encoder_mf.c:483
+  lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at 
../../../../src/liblzma/lz/lz_encoder_mf.c:721
+  lzma_mf_find (mf=mf@entry=0x7f9a9c70, 
count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) 
at ../../../../src/liblzma/lz/lz_encoder_mf.c:28
+  lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846
+  lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804

** Summary changed:

- xz segfault error in liblzma.so.5.2.5
+ xz crashed with SIGSEGV in lzma_lzma_optimum_normal

** Description changed:

  xz segfaults. More details in
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379
  
  From Dmesg.txt on that report
  
  [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a
  sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000]
  
  ProblemType: Crash
  ApportVersion: 2.20.11-0ubuntu82.5