[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen

[Leó Kolbeinsson]

Tested Ubuntu Noble Desktop daily ISO dated 16-01-2024 and bug was not
present

Fix confirmed

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  New
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049352] Re: Package BlueZ 5.72 for Noble

[Daniel van Vugt]

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

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

Title:
  Package BlueZ 5.72 for Noble

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  ver 5.72:
  Fix issue with BAP and handling stream IO linking.
  Fix issue with BAP and setup of multiple streams per endpoint.
  Fix issue with AVDTP and potential incorrect transaction label.
  Fix issue with A2DP and handling crash on suspend.
  Fix issue with GATT database and an invalid pointer.
  Add support for AICS service.

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2043915] Re: Booting into live session results in try/install page white screen

[Daniel van Vugt]

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

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  New
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2045621] Re: Improve power consumption on Framework systems

[Artur Pak]

** Changed in: oem-priority
   Status: In Progress => Fix Released

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

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2049352] Re: Package BlueZ 5.72 for Noble

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  Package BlueZ 5.72 for Noble

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  ver 5.72:
  Fix issue with BAP and handling stream IO linking.
  Fix issue with BAP and setup of multiple streams per endpoint.
  Fix issue with AVDTP and potential incorrect transaction label.
  Fix issue with A2DP and handling crash on suspend.
  Fix issue with GATT database and an invalid pointer.
  Add support for AICS service.

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2045668] Re: Please merge dbus 1.14.10-3 (main) from Debian unstable

[Launchpad Bug Tracker]

This bug was fixed in the package dbus - 1.14.10-3ubuntu1

---
dbus (1.14.10-3ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2045668). Remaining changes:
- Add aa-get-connection-apparmor-security-context.patch: This is not
  intended for upstream inclusion. It implements a bus method
  (GetConnectionAppArmorSecurityContext) to get a connection's AppArmor
  security context but upstream D-Bus has recently added a generic way of
  getting a connection's security credentials (GetConnectionCredentials).
  Ubuntu should carry this patch until packages in the archive are moved
  over to the new, generic method of getting a connection's credentials.
  (LP #1489489).
- Add dont-stop-dbus.patch: Don't stop D-Bus in the service unit
  (LP #1438612)
  - Reworked to actually make dbus.service _and_ dbus.socket to not
be part of the shutdown transaction. And yet make it possible
to still stop/kill/restart dbus.service if one really
wants to, because it is stuck and stopped responding to any
commands. This allows allows to restart dbus.service with
needrestart. However a finalrd hook might still be needed, to kill
dbus-daemon for good, once we pivot off rootfs.
  - Reworked to avoid a deadlock during boot (LP #1936948)
- debian/dbus.postinst, debian/rules: Don't start D-Bus on package
  installation, as that doesn't work any more with dont-stop-dbus.patch.
  Instead, start dbus.socket in postinst, which will then start D-Bus
  on demand after package installation.
  - Prevent dbus from being restarted on upgrade (LP #1962036)
  * Drop dependency on usr-is-merged; this transition is long completed
in Ubuntu.

dbus (1.14.10-3) unstable; urgency=medium

  * d/control: dbus Depends on usr-is-merged (>= 38~).
Non-merged /usr has been unsupported since Debian 12, as per Technical
Committee resolutions #978636 and #994388 (please see the Debian 12
release notes for details).
The version of usr-is-merged shipped in Debian 12 had an undocumented
opt-out mechanism intended for use on buildds and QA systems targeting
Debian 12 (piuparts, reproducible-builds, autopkgtest and similar),
to ensure that the upgrade path from Debian 11 to 12 will continue
to work and continue to undergo automated tests. That opt-out is
no longer applicable or available in trixie/sid, and was removed in
usrmerge version 38.
Since version 1.14.10-2, dbus ships its systemd units in
/usr/lib/systemd/system, as part of the distro-wide transition
away from making use of "aliased" paths. This is entirely valid on
merged-/usr systems, but will no longer work in the unsupported
filesystem layout with non-merged /usr, because for historical
reasons, current versions of systemd on non-merged-/usr systems will
only read units from /lib/systemd/system.
In the case of dbus, the symptom when this assumption is broken is
particularly bad (various key system services will not start, with
long delays during boot, login and shutdown), so let's hold back
this upgrade on unsupported non-merged-/usr systems until they have
completed the switch to merged-/usr and can install
usr-is-merged (>= 38~).
(Closes: #1054650)

dbus (1.14.10-2) unstable; urgency=low

  * Backport packaging changes from experimental:
- Install systemd system units into /usr/lib/systemd/system.
  This was allowed by TC resolution #1053901. The shared library is
  still in /lib, for now.
  Build-depend on debhelper 13.11.6~ to ensure that the units are still
  picked up by dh_installsystemd.
- Build-depend on pkgconf rather than pkg-config
- dbus-x11: Don't copy XDG_SEAT_PATH, XDG_SESSION_PATH to activation
  environment. These variables are specific to a single login session.
  * d/copyright: Drop unused entry for pkg.m4.
This is no longer included in the upstream source release since 1.14.6.
  * d/dbus-tests.lintian-overrides: Drop unused overrides.
Lintian no longer flags our RUNPATH as problematic.

 -- Olivier Gayot   Tue, 05 Dec 2023
16:36:45 +0100

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

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

Title:
  Please merge dbus 1.14.10-3 (main) from Debian unstable

Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  1.14.10-3
  Published in sid-release on 2023-10-30

  dbus (1.14.10-3) unstable; urgency=medium

* d/control: dbus Depends on usr-is-merged (>= 38~).
  Non-merged /usr has been unsupported since Debian 12, as per Technical
  Committee resolutions #978636 and #994388 (please see the Debian 12
  release notes for details).
  The version of usr-is-merged shipped in Debian 

[Touch-packages] [Bug 2049424] Re: Grayscreen

[Daniel van Vugt]

Xorg itself doesn't paint anything, it will start with a black window.
So it's likely to be a Xubuntu bug. Since it can't be reproduced then
let's leave it Incomplete and it will close automatically after two
months of inactivity.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Grayscreen

Status in Ubuntu:
  Incomplete

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Mon Jan 15 10:37:25 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
 Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
  InstallationDate: Installed on 2023-10-14 (93 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2024
  dmi.bios.release: 2.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.1
  dmi.board.name: 0KM9JV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
  dmi.product.family: Precision
  dmi.product.name: Precision 3660
  dmi.product.sku: 0A9F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  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/+bug/2049424/+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 2049318] Re: [SRU] free(): double free detected in tcache 2

[Jo Rhett]

According to the versions listed for the package, Lunar would have the
same bug. I don't run Lunar so have no personal investment, just FYI.

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

Title:
  [SRU] free(): double free detected in tcache 2

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Jammy:
  Confirmed

Bug description:
  [ Impact ]

  iptables is unable to list the iptables rules or save the iptables
  rules if a nftables ruleset is defined which iptables does not
  recognize.

  [ Test Plan ]

  * Add an iptables rule.
- sudo iptables -A OUTPUT -p tcp --dport   -j REJECT

  * save the rules in a file
- sudo iptables-save > rules.txt

  * Convert the rule to nftables ruleset
- sudo iptables-nft-restore < rules.txt

  * List the nftables ruleset
- sudo nft list ruleset

  * Also confirm that iptables can list the old rule
- sudo iptables -L

  * Now add another nftables rule (this rule is taken from upstream test
  case)

  sudo nft -f - 

[Touch-packages] [Bug 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2023d-0ubuntu0.20.04

---
tzdata (2023d-0ubuntu0.20.04) focal; urgency=medium

  * New upstream version (LP: #2047314):
- Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
- Vostok, Antarctica changed time zones on 2023-12-18.
- Casey, Antarctica changed time zones five times since 2020.
- Code and data fixes for Palestine timestamps starting in 2072.
- A new data file zonenow.tab for timestamps starting now.
  * No ICU data update yet as none is yet available upstream.
  * Install zonenow.tab in tzdata
  * Add autopkgtest test case for 2023d release
  * Refresh make-systemv.patch

 -- Benjamin Drung   Tue, 02 Jan 2024 21:08:29 +0100

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2023d-0ubuntu0.22.04

---
tzdata (2023d-0ubuntu0.22.04) jammy; urgency=medium

  * New upstream version (LP: #2047314):
- Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
- Vostok, Antarctica changed time zones on 2023-12-18.
- Casey, Antarctica changed time zones five times since 2020.
- Code and data fixes for Palestine timestamps starting in 2072.
- A new data file zonenow.tab for timestamps starting now.
  * No ICU data update yet as none is yet available upstream.
  * Install zonenow.tab in tzdata
  * Add autopkgtest test case for 2023d release

 -- Benjamin Drung   Tue, 02 Jan 2024 20:37:09 +0100

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2023d-0ubuntu0.23.04

---
tzdata (2023d-0ubuntu0.23.04) lunar; urgency=medium

  * New upstream version (LP: #2047314):
- Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
- Vostok, Antarctica changed time zones on 2023-12-18.
- Casey, Antarctica changed time zones five times since 2020.
- Code and data fixes for Palestine timestamps starting in 2072.
- A new data file zonenow.tab for timestamps starting now.
  * No ICU data update yet as none is yet available upstream.
  * Install zonenow.tab in tzdata
  * Add autopkgtest test case for 2023d release

 -- Benjamin Drung   Tue, 02 Jan 2024 20:10:22 +0100

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

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

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

[Brian Murray]

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Launchpad Bug Tracker]

This bug was fixed in the package tzdata - 2023d-0ubuntu0.23.10

---
tzdata (2023d-0ubuntu0.23.10) mantic; urgency=medium

  * New upstream version (LP: #2047314):
- Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
- Vostok, Antarctica changed time zones on 2023-12-18.
- Casey, Antarctica changed time zones five times since 2020.
- Code and data fixes for Palestine timestamps starting in 2072.
- A new data file zonenow.tab for timestamps starting now.
  * No ICU data update yet as none is yet available upstream.
  * Install zonenow.tab in tzdata
  * Add autopkgtest test case for 2023d release

 -- Benjamin Drung   Tue, 02 Jan 2024 19:28:21 +0100

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Brian Murray]

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

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released
Status in tzdata source package in Lunar:
  Fix Released
Status in tzdata source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 1982693] Re: USB-Audio device UMC204HD disappears after suspend

[Charly Boy]

I'm facing the same problem that you describe.
Were you able to figure out a solution to your problem?

I noticed that the command "usbreset" before going to sleep would show
the USB audio interface. After coming back from sleep, the same command
doesn't show the interface anymore.

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

Title:
  USB-Audio device UMC204HD disappears after suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Coming back from sleep, Behringer UMC204HD is not in the list of
  devices in Settings > Sound. It comes back if I unplug and plug back
  in.

  I tried with/without a USB hub in between, I tried setting
  "usbcore.autosuspend=-1". No help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 24 15:04:57 2022
  InstallationDate: Installed on 2022-04-21 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful
  Symptom_Card: HD Webcam C525 - HD Webcam C525
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - UMC204HD 192k, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/16/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M PRO-VH (MS-7996)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.H0:bd06/16/2018:br5.12:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VH(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7996
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1982693/+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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian

[Heinrich Schuchardt]

** Bug watch added: Debian Bug tracker #1060868
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060868

** Also affects: rsyslog via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060868
   Importance: Unknown
   Status: Unknown

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

Title:
  Merge rsyslog 8.2312.0-2 from Debian

Status in Rsyslog:
  Unknown
Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  Debian has released rsyslog 8.2310.0-4. Merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/rsyslog/+bug/2045033/+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 2049433] [NEW] [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6

[Shahbaz Youssefi]

Public bug reported:

Hi, Chrome/ANGLE developer here.

We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so
since December 5, 2023. So far, all crashes seem to come from that
specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV
developer, that version hasn't had an update since Nov 2021.

While there's always a chance that an update in ANGLE has hit a bug, the
timing does not work out (Chrome Beta has been fine since November 1,
but the crashes started happening on Dec 5).

Has there been an update to this driver around Dec 5, 2023 in Ubuntu
specifically? I'm wondering if there has been a (security) update done
by the Ubuntu team that upstream mesa may not be aware of. I can't find
a public history of updates to ubuntu packages (with associated dates),
is it possible to look at / provide that info and see what happened
around Dec 5?

Additional context is crbug.com/1508940, but I'm afraid not much is
visible publicly. The crash stack is nonsense unfortunately.

Cheers

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

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

Title:
  [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi, Chrome/ANGLE developer here.

  We've started observing crashes on Ubuntu 20.04.6 in
  libvulkan_radeon.so since December 5, 2023. So far, all crashes seem
  to come from that specific Ubuntu version, and with RADV 21.2.6.
  Speaking with a mesa RADV developer, that version hasn't had an update
  since Nov 2021.

  While there's always a chance that an update in ANGLE has hit a bug,
  the timing does not work out (Chrome Beta has been fine since November
  1, but the crashes started happening on Dec 5).

  Has there been an update to this driver around Dec 5, 2023 in Ubuntu
  specifically? I'm wondering if there has been a (security) update done
  by the Ubuntu team that upstream mesa may not be aware of. I can't
  find a public history of updates to ubuntu packages (with associated
  dates), is it possible to look at / provide that info and see what
  happened around Dec 5?

  Additional context is crbug.com/1508940, but I'm afraid not much is
  visible publicly. The crash stack is nonsense unfortunately.

  Cheers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2049433/+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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian

[Heinrich Schuchardt]

Upstream merge request created
https://github.com/rsyslog/rsyslog/pull/5310

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

Title:
  Merge rsyslog 8.2312.0-2 from Debian

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  Debian has released rsyslog 8.2310.0-4. Merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian

[Heinrich Schuchardt]

The failure of rsyslog-mysql is due to the hostname in Launchpad having 64 
characters while the FromHost column only has 60 columns.
https://github.com/rsyslog/rsyslog/issues/5309

** Bug watch added: github.com/rsyslog/rsyslog/issues #5309
   https://github.com/rsyslog/rsyslog/issues/5309

** Changed in: rsyslog (Ubuntu)
 Assignee: (unassigned) => Heinrich Schuchardt (xypron)

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

Title:
  Merge rsyslog 8.2312.0-2 from Debian

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  Debian has released rsyslog 8.2310.0-4. Merge it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2045033/+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 2047314] Re: tzdata 2023d release (leap-second.list expiring this week)

[Chris Peterson]

Hi, I can confirm the autopkgtests for all releases (Mantic, Lunar, Jammy, and 
Focal) are passing and all listed regressions are fixed.
 
The listed regression for systemd/253.5-1ubuntu6.1 (arm64) in Mantic appears to 
be resolved on a retest. See: 

https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/arm64/s/systemd/20240108_213105_c65e8@/log.gz


The listed regression for chrony/4.3-1ubuntu4 (armhf) in Lunar appears to be 
resolved on a retest. See:

https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lunar/armhf/c/chrony/20240107_161911_97f61@/log.gz


The listed regression for mtail/3.0.0~rc50-1 (arm64) in Lunar appears to be 
resolved on a retest. see:

https://autopkgtest.ubuntu.com/results/autopkgtest-
lunar/lunar/arm64/m/mtail/20240107_151954_b45f2@/log.gz


The listed regression for python-tz/2022.7.1-3 (amd64, arm64, armhf, ppc64el, 
s390x) in Lunar resolved by the release of 2022.7.1-3ubuntu0.1 .

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

Title:
  tzdata 2023d release (leap-second.list expiring this week)

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  leap-seconds.list shipped by tzdata 2023c expired on Dec 28th 2023.

  The 2023d release contains the following changes:

     Briefly:
   Ittoqqortoormiit, Greenland changes time zones on 2024-03-31.
   Vostok, Antarctica changed time zones on 2023-12-18.
   Casey, Antarctica changed time zones five times since 2020.
   Code and data fixes for Palestine timestamps starting in 2072.
   A new data file zonenow.tab for timestamps starting now.

     Changes to future timestamps

   Ittoqqortoormiit, Greenland (America/Scoresbysund) joins most of
   the rest of Greenland's timekeeping practice on 2024-03-31, by
   changing its time zone from -01/+00 to -02/-01 at the same moment
   as the spring-forward transition.  Its clocks will therefore not
   spring forward as previously scheduled.  The time zone change
   reverts to its common practice before 1981.

   Fix predictions for DST transitions in Palestine in 2072-2075,
   correcting a typo introduced in 2023a.

     Changes to past and future timestamps

   Vostok, Antarctica changed to +05 on 2023-12-18.  It had been at
   +07 (not +06) for years.  (Thanks to Zakhary V. Akulov.)

   Change data for Casey, Antarctica to agree with timeanddate.com,
   by adding five time zone changes since 2020.  Casey is now at +08
   instead of +11.

     Changes to past tm_isdst flags

   Much of Greenland, represented by America/Nuuk, changed its
   standard time from -03 to -02 on 2023-03-25, not on 2023-10-28.
   This does not affect UTC offsets, only the tm_isdst flag.
   (Thanks to Thomas M. Steenholdt.)

     New data file

   A new data file zonenow.tab helps configure applications that use
   timestamps dated from now on.  This simplifies configuration,
   since users choose from a smaller Zone set.  The file's format is
   experimental and subject to change.

  [ Test Plan ]

  Test cases were added to autopkgtest to cover the testing:

  * python: test_2023d

  So the test plan is to check that all autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047314/+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 2049318] Re: [SRU] free(): double free detected in tcache 2

[Sudip Mukherjee]

debdiff for Jammy attached.


** Summary changed:

- free(): double free detected in tcache 2
+ [SRU] free(): double free detected in tcache 2

** Description changed:

+ [ Impact ]
+ 
+ iptables is unable to list the iptables rules or save the iptables rules
+ if a nftables ruleset is defined which iptables does not recognize.
+ 
+ [ Test Plan ]
+ 
+ * Add an iptables rule.
+   - sudo iptables -A OUTPUT -p tcp --dport   -j REJECT
+ 
+ * save the rules in a file
+   - sudo iptables-save > rules.txt
+ 
+ * Convert the rule to nftables ruleset
+   - sudo iptables-nft-restore < rules.txt
+ 
+ * List the nftables ruleset
+   - sudo nft list ruleset
+ 
+ * Also confirm that iptables can list the old rule
+   - sudo iptables -L
+ 
+ * Now add another nftables rule (this rule is taken from upstream test
+ case)
+ 
+ sudo nft -f -  Confirmed

** Changed in: iptables (Ubuntu Jammy)
 Assignee: Sudip Mukherjee (sudipmuk) => (unassigned)

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

Title:
  [SRU] free(): double free detected in tcache 2

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Jammy:
  Confirmed

Bug description:
  [ Impact ]

  iptables is unable to list the iptables rules or save the iptables
  rules if a nftables ruleset is defined which iptables does not
  recognize.

  [ Test Plan ]

  * Add an iptables rule.
- sudo iptables -A OUTPUT -p tcp --dport   -j REJECT

  * save the rules in a file
- sudo iptables-save > rules.txt

  * Convert the rule to nftables ruleset
- sudo iptables-nft-restore < rules.txt

  * List the nftables ruleset
- sudo nft list ruleset

  * Also confirm that iptables can list the old rule
- sudo iptables -L

  * Now add another nftables rule (this rule is taken from upstream test
  case)

  sudo nft -f - 

[Touch-packages] [Bug 2040011] Re: [SRU] Ensure supported codenames are accurate

[Simon Quigley]

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

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

Title:
  [SRU] Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  Fix Released
Status in vim source package in Focal:
  In Progress
Status in vim source package in Jammy:
  In Progress
Status in vim source package in Lunar:
  In Progress
Status in vim source package in Mantic:
  In Progress

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  and sources.list is supported or not. Any regression would present
  itself in external tooling that detects text highlighting, which is
  not a case I think we support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "noble") showing as red, it should show as
  blue. I would also suggest editing sources.list, to ensure e.g. Eoan
  shows as EOL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2049318] Re: free(): double free detected in tcache 2

[Sudip Mukherjee]

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

** Changed in: iptables (Ubuntu Jammy)
 Assignee: (unassigned) => Sudip Mukherjee (sudipmuk)

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

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

Title:
  free(): double free detected in tcache 2

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

Bug description:
  nftables is being used successfully with no difficulty.

  Running iptables on my node receives a crash:

  $ sudo iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  without sudo

  # iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  This bug is known and was fixed in version 1.8.8 of iptables
  
https://git.netfilter.org/iptables/commit/?id=4318961230bce82958df82b57f1796143bf2f421

  
  1) The release of Ubuntu

  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2) The version of the package

  $ apt info iptables
  Package: iptables
  Version: 1.8.7-1ubuntu5.1

  3) What you expected to happen

  not to crash with valid, working nftables rules

  4) What happened instead

  crash

  
  A plausible workaround could be a backport of iptables 1.8.9 from mantic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iptables 1.8.7-1ubuntu5.1
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Sun Jan 14 20:36:59 2024
  InstallationDate: Installed on 2021-11-23 (782 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iptables
  UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2049318/+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 2049318] Re: free(): double free detected in tcache 2

[Simon Quigley]

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

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

Title:
  free(): double free detected in tcache 2

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

Bug description:
  nftables is being used successfully with no difficulty.

  Running iptables on my node receives a crash:

  $ sudo iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  without sudo

  # iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  This bug is known and was fixed in version 1.8.8 of iptables
  
https://git.netfilter.org/iptables/commit/?id=4318961230bce82958df82b57f1796143bf2f421

  
  1) The release of Ubuntu

  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2) The version of the package

  $ apt info iptables
  Package: iptables
  Version: 1.8.7-1ubuntu5.1

  3) What you expected to happen

  not to crash with valid, working nftables rules

  4) What happened instead

  crash

  
  A plausible workaround could be a backport of iptables 1.8.9 from mantic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iptables 1.8.7-1ubuntu5.1
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Sun Jan 14 20:36:59 2024
  InstallationDate: Installed on 2021-11-23 (782 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iptables
  UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2049318/+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 2049424] Re: Grayscreen

[Jim Roberts]

How frustrating I have spent hours researching this issue including
numerous reboots and logins.

After opening this bug I logged in to get my processes started expecting
the frozen gray screen and the display came up without an issue.

If there is anything that can be gained by further examination of this
issue please let me know how I can help.  If not, please close this bug.

Thank you

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

Title:
  Grayscreen

Status in xorg package in Ubuntu:
  New

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Mon Jan 15 10:37:25 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
 Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
  InstallationDate: Installed on 2023-10-14 (93 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2024
  dmi.bios.release: 2.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.1
  dmi.board.name: 0KM9JV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
  dmi.product.family: Precision
  dmi.product.name: Precision 3660
  dmi.product.sku: 0A9F
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

[Jim Roberts]

Public bug reported:

Dell Precision 3660

I upgraded BIOS to 2.11.1 which also upgraded some other things.

When I login into Xubuntu I get a frozen gray screen


jim@jim:~/Scripts$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10

jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

jim@jim:~/Scripts$ uname -r
6.5.0-14-generic


I can boot into the install flashdrive under Try Xubuntu and the display
works fine.

Flash Drive:
xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
:00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 
0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
xubuntu@xubuntu:~$ uname -r
6.5.0-9-generic

Please provide a workaround as this is my primary workstation.

Let me know if you need any additional information.

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Mon Jan 15 10:37:25 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) (prog-if 00 [VGA 
controller])
   Subsystem: Dell AlderLake-S GT1 [1028:0a9f]
InstallationDate: Installed on 2023-10-14 (93 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/03/2024
dmi.bios.release: 2.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.1
dmi.board.name: 0KM9JV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.1:bd01/03/2024:br2.11:efr1.7:svnDellInc.:pnPrecision3660:pvr:rvnDellInc.:rn0KM9JV:rvrA00:cvnDellInc.:ct3:cvr:sku0A9F:
dmi.product.family: Precision
dmi.product.name: Precision 3660
dmi.product.sku: 0A9F
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
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 mantic ubuntu

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

Title:
  Grayscreen

Status in xorg package in Ubuntu:
  New

Bug description:
  Dell Precision 3660

  I upgraded BIOS to 2.11.1 which also upgraded some other things.

  When I login into Xubuntu I get a frozen gray screen

  
  jim@jim:~/Scripts$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.10
  Release:  23.10

  jim@jim:~/Scripts$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915

  jim@jim:~/Scripts$ uname -r
  6.5.0-14-generic


  I can boot into the install flashdrive under Try Xubuntu and the
  display works fine.

  Flash Drive:
  xubuntu@xubuntu:~$ lspci -k | grep -EA3 'VGA|3D|Display'
  :00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 
(rev 0c)
Subsystem: Dell AlderLake-S GT1
Kernel driver in use: i915
Kernel modules: i915
  xubuntu@xubuntu:~$ uname -r
  6.5.0-9-generic

  Please provide a workaround as this is my primary workstation.

  Let me know if you need any additional information.

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission 

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Confirmed

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

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

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

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

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

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

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

  Issue/Bug Description:

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

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

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


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

[Touch-packages] [Bug 2049312] Re: Dnsmasq in jammy-updates and lacks .orig.tar.gz

[Athos Ribeiro]

Thank you for taking the time to report bugs and help make Ubuntu
better.

This package is a native package in the (old) 1.0 source format.

$ cat debian/source/format 
1.0

Please see: https://manpages.debian.org/unstable/dpkg-dev/dpkg-
source.1.en.html#Format:_1.0

"A source package in this format consists either of a .orig.tar.gz
associated to a .diff.gz or a single .tar.gz (in that case the package
is said to be native)."

I'm marking this "Invalid" because it doesn't appear to be a bug, but if
I'm wrong, please change it back to "New" and add some more info to
point me in the right direction. Use this link as a guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

** Changed in: dnsmasq (Ubuntu)
   Status: New => Invalid

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

Title:
  Dnsmasq in jammy-updates and  lacks .orig.tar.gz

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  Source code package of dnsmasq in jammy-updates (version 2.86-1.1ubuntu0.4) 
and proposed lacks dnsmasq_2.89.orig.tar.gz.
  This causes debuild to show warning and asks for confirmation to build 
packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2049312/+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 2049352] Re: Package BlueZ 5.72 for Noble

[Gianfranco Costamagna]

and it migrated!

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

Title:
  Package BlueZ 5.72 for Noble

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  ver 5.72:
  Fix issue with BAP and handling stream IO linking.
  Fix issue with BAP and setup of multiple streams per endpoint.
  Fix issue with AVDTP and potential incorrect transaction label.
  Fix issue with A2DP and handling crash on suspend.
  Fix issue with GATT database and an invalid pointer.
  Add support for AICS service.

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72

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


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

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Sebastien Bacher]

Speaking from a Desktop perspective, it's difficult to have a strong
opinion without data to backup the decision but it does feel like that
in the light of what other distributions/upstream are doing we should
reverse the default and go with option A and not have it by default but
an opt-in instead.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

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

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

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

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

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

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

  Issue/Bug Description:

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

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

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


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

[Touch-packages] [Bug 2049312] Re: Dnsmasq in jammy-updates and lacks .orig.tar.gz

[Athos Ribeiro]

** Summary changed:

- Dnsmasq in jummy-updates and  lacks .orig.tar.gz
+ Dnsmasq in jammy-updates and  lacks .orig.tar.gz

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

Title:
  Dnsmasq in jammy-updates and  lacks .orig.tar.gz

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Source code package of dnsmasq in jammy-updates (version 2.86-1.1ubuntu0.4) 
and proposed lacks dnsmasq_2.89.orig.tar.gz.
  This causes debuild to show warning and asks for confirmation to build 
packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2049312/+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 2041491] Re: Provide an option to avoid the yaml NM backend

[Lukas Märdian]

Another option/idea I'd like to provide here is the migration script
used by NetworkManager [1], to transfer NM keyfiles from
/etc/NetworkManager/system-conncetions/ into /etc/netplan. This script
is automatically run on package upgrade of NetworkManager. I understand
this does not exactly fit the usecase described by alkisg, as you'd go
from debian-box:/etc/NetworkManager/system-connections -> ubuntu-
box:/etc/NetworkManager/system-connections -> migrate.sh -> ubuntu-
box:/run/NetworkManager/system-connections

Running "./migrate.sh configure" would transfer your copied original NM
keyfiles from a different box into Netplan and re-generate them in
/run/NetworkManager/system-connections:

```bash
# Run "Netplan Everywhere" migration after debhelper (re-)started
# NetworkManager.service for us. On every package upgrade.
DIR="/etc/NetworkManager/system-connections"
if [ "$1" = "configure" ] && [ -d "$DIR" ]; then
mkdir -p /run/netplan/nm-migrate
for CON in /etc/NetworkManager/system-connections/*; do
TYPE=$(file -bi "$CON" | cut -s -d ";" -f 1)
[ "$TYPE" = "text/plain" ] || continue # skip non-keyfiles
UUID=$(grep "^uuid=" "$CON" | cut -c 6-)
if [ -n "$UUID" ]
then
# Wait for NetworkManager startup to complete,
# so we can safely use nmcli. Wait in every interation to handle
# a crashed NetworkManager in the previous migraiton step.
if ! nm-online -qs; then
echo "SKIP: NetworkManager is not ready ..." 1>&2
continue
fi
BACKUP="/run/netplan/nm-migrate/"$(basename "$CON")
ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID") || \
{ echo "SKIP: $(basename "$CON") ($UUID) unknown to 
NetworkManager." 1>&2 && \
  continue; }
cp "$CON" "$BACKUP"
echo "Migrating $ORIG_NAME ($UUID) to /etc/netplan" 1>&2
# Touch the connection's ID (con-name) to trigger its migration.
# The Netplan integration will translate the original NM keyfile 
from
# /etc/NetworkManager/system-connections/* to a YAML file located in
# /etc/netplan/90-NM-*.yaml and re-generate a corresponding keyfile 
in
# /run/NetworkManager/system-connections/netplan-NM-*.nmconnection
nmcli con mod "$UUID" con-name "$ORIG_NAME" || \
(echo "FAILED. Restoring backup ..." 1>&2 && mv "$BACKUP" 
"$CON" && \
 rm -f "/etc/netplan/90-NM-$UUID"*.yaml)
rm -f "$BACKUP" # clear backup (if it still exists)
   fi
done
rm -rf /run/netplan/nm-migrate # cleanup after ourselves
(nm-online -qs && nmcli con reload) || echo "WARNING: NetworkManager could 
not reload connections ..." 1>&2
fi
```

[1] https://git.launchpad.net/network-manager/tree/debian/network-
manager.postinst#n62

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

Title:
  Provide an option to avoid the yaml NM backend

Status in netplan.io package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi, recently netplan added support for a yaml NM backend:

  https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-
  settings/32420

  The rationale is that "the descriptive YAML layer is especially useful
  in cloud environments":

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556

  It's great that you care about that user group!
  Please also care for the rest of us that do not use cloud environments!

  For example, I routinely review, clone, backup or even directly edit
  the /etc/NetworkManager/system-connections files in my desktops and
  servers, in all distributions.

  Having an Ubuntu-specific way to do things will make things harder for
  me. I will have to learn a new Ubuntu-specific syntax, develop scripts
  and methods to convert my connections between distributions, I will
  need to discover and report bugs in the netplan <=> nm mapping etc...

  I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide 
a unified yaml-based experience for cloud-init etc.
  But Ubuntu is also great outside the cloud; please allow us to continue 
having a unified experience between distributions (i.e. directly using nm or 
systemd-networkd) without enforcing an Ubuntu-specific way of doing things 
(netplan) to us.

  For Ubuntu 24.04+, please provide an option to avoid the yaml NM
  backend, thank you very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+subscriptions


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

[Touch-packages] [Bug 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

[Sergio Costas]

Would this Qemu capture from a Core Desktop terminal be enough? There
you can see that the installed .deb for systemd is 249.11-0ubuntu3.12,
that /etc/default/keyboard and /etc/default/locale are soft links to the
same files at /etc/writable/default, that /etc/writable/default/keyboard
file doesn't exist and /etc/writable/default/locale contains C.UTF-8.
And after following the test protocol, locale now contains es_ES.UTF-8,
and keyboard file exists with es layout and pc105 model.

** Attachment added: "Window capture"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+attachment/5739596/+files/Captura%20desde%202024-01-15%2014-00-43.png

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *sudo localectl set-locale xx_YY.UTF-8* in an Ubuntu Core or
  Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the
  */etc/default/locale* file. Also, *localectl* must return the new
  locale.

  Using *sudo dbus-send --system --print-reply
  --dest=org.freedesktop.locale1 /org/freedesktop/locale1
  org.freedesktop.locale1.SetX11Keyboard string:XX string:pc10Y string:
  string: boolean:true boolean:false" must change the
  */etc/default/keyboard* file to layout XX and model PC10Y (being Y
  either 1, 2, 4 or 5). Reading the file allows to check it. Also,
  *localectl status* must return the layout and model values in "X11
  Layout" and "X11 Model" entries.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2049392] [NEW] Symlink for resolv.conf not working with F5 vpn

[christophe hubert]

Public bug reported:

Hi,

I create this bug issue following an advice from Nick Rosbrook in this
bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234


May be it's a F5 VPN. I haven't found such a bug anywhere. 

I have an issue when connection to a F5 VPN when  /etc/resolv.conf is
the symbolic link of ../run/systemd/resolve/stub-resolv.conf

➜ ~ sudo ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

When F5 is launched, /etc/resolv.conf is not changed. I have to manually
set resolv.conf to change the nameserver(s).


When I change the symbolic link /etc/resolv.conf to
/run/systemd/resolve/resolv.conf

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

When F5 is launched, /etc/resolv.conf is  updated whith vpn
nameserver(s).

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

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

Title:
   Symlink for resolv.conf not working with F5 vpn

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I create this bug issue following an advice from Nick Rosbrook in this
  bug : https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2043234

  
  May be it's a F5 VPN. I haven't found such a bug anywhere. 

  I have an issue when connection to a F5 VPN when  /etc/resolv.conf is
  the symbolic link of ../run/systemd/resolve/stub-resolv.conf

  ➜ ~ sudo ls -la /etc/resolv.conf
  lrwxrwxrwx 1 root root 39 juin 23 12:37 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  When F5 is launched, /etc/resolv.conf is not changed. I have to
  manually set resolv.conf to change the nameserver(s).


  
  When I change the symbolic link /etc/resolv.conf to 
/run/systemd/resolve/resolv.conf

  sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

  When F5 is launched, /etc/resolv.conf is  updated whith vpn
  nameserver(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049392/+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 2049318] Re: free(): double free detected in tcache 2

[Sudip Mukherjee]

I can reproduce the segfault in Jammy using the testcase that the
upstream as added. Also tested on other releases to confirm they are not
affected.

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

Title:
  free(): double free detected in tcache 2

Status in iptables package in Ubuntu:
  New

Bug description:
  nftables is being used successfully with no difficulty.

  Running iptables on my node receives a crash:

  $ sudo iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  without sudo

  # iptables -nL
  free(): double free detected in tcache 2
  Aborted (core dumped)

  This bug is known and was fixed in version 1.8.8 of iptables
  
https://git.netfilter.org/iptables/commit/?id=4318961230bce82958df82b57f1796143bf2f421

  
  1) The release of Ubuntu

  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  2) The version of the package

  $ apt info iptables
  Package: iptables
  Version: 1.8.7-1ubuntu5.1

  3) What you expected to happen

  not to crash with valid, working nftables rules

  4) What happened instead

  crash

  
  A plausible workaround could be a backport of iptables 1.8.9 from mantic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: iptables 1.8.7-1ubuntu5.1
  ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131
  Uname: Linux 5.15.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Sun Jan 14 20:36:59 2024
  InstallationDate: Installed on 2021-11-23 (782 days ago)
  InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210824)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: iptables
  UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago)

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


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

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

[bugproxy]

--- Comment From cborn...@de.ibm.com 2024-01-15 06:46 EDT---
Just a statement from s390x/IBM Z. For our platform irqbalance makes no sense 
as our interrupt handling works differently. So we do not need it.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

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

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

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

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

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

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

  Issue/Bug Description:

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

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

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


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

[Touch-packages] [Bug 2049352] Re: Package BlueZ 5.72 for Noble

[Gianfranco Costamagna]

Bluez should migrate next run, and then you can do the update if you
want, is it ok for you?

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

Title:
  Package BlueZ 5.72 for Noble

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  ver 5.72:
  Fix issue with BAP and handling stream IO linking.
  Fix issue with BAP and setup of multiple streams per endpoint.
  Fix issue with AVDTP and potential incorrect transaction label.
  Fix issue with A2DP and handling crash on suspend.
  Fix issue with GATT database and an invalid pointer.
  Add support for AICS service.

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2046356] Re: Update URL for Support information in MOTD message

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 12.3ubuntu2.1

---
base-files (12.3ubuntu2.1) lunar; urgency=medium

  * motd/10-help-text: Update support url for new Ubuntu Pro webpage
(LP: #2046356)

 -- Lucas Moura   Tue, 02 Jan 2024 14:37:38
-0300

** Changed in: base-files (Ubuntu Lunar)
   Status: Fix Committed => Fix Released

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

Title:
  Update URL for Support information in MOTD message

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Committed
Status in base-files source package in Lunar:
  Fix Released
Status in base-files source package in Mantic:
  Fix Released
Status in base-files source package in Noble:
  Fix Released

Bug description:
  
  [Impact]
  When users see the MOTD message, they are currently seeing an outdated url 
under the support information.
  Even though the outdated url redirects to new Ubuntu Pro webpage, we believe 
the users should still see
  the correct url from the start

  [Test Case]

  - Launch a LXD container for any of the affected releases
  - Install the package with this fix applied
  - Install `update-motd` package
  - Run `update-motd` and confirm the Support url is now the correct one

  [Regression Potential]
  If users are parsing MOTD for some reason, the url change might break that 
logic now. However, parsing MOTD messages is not a supported flow, so we 
believe regression potential is low here.

  [Discussion]
  Since we want users to be aware of what Ubuntu Pro is, we should highlight 
the right product name on any place that is still using the old "advantage" 
name. Updating the support URL here is a step into this direction

  [Original Bug Description]
  On the file 10-help-text, we are printing the following line on MOTD:

  * Support: https://ubuntu.com/advantage

  We should update the url to https://ubuntu.com/pro instead, as this
  will the default url for support information now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2046356] Re: Update URL for Support information in MOTD message

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 13ubuntu2.1

---
base-files (13ubuntu2.1) mantic; urgency=medium

  * motd/10-help-text: Update support url for new Ubuntu Pro webpage
(LP: #2046356)

 -- Lucas Moura   Tue, 02 Jan 2024 10:25:08
-0300

** Changed in: base-files (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Update URL for Support information in MOTD message

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Committed
Status in base-files source package in Lunar:
  Fix Released
Status in base-files source package in Mantic:
  Fix Released
Status in base-files source package in Noble:
  Fix Released

Bug description:
  
  [Impact]
  When users see the MOTD message, they are currently seeing an outdated url 
under the support information.
  Even though the outdated url redirects to new Ubuntu Pro webpage, we believe 
the users should still see
  the correct url from the start

  [Test Case]

  - Launch a LXD container for any of the affected releases
  - Install the package with this fix applied
  - Install `update-motd` package
  - Run `update-motd` and confirm the Support url is now the correct one

  [Regression Potential]
  If users are parsing MOTD for some reason, the url change might break that 
logic now. However, parsing MOTD messages is not a supported flow, so we 
believe regression potential is low here.

  [Discussion]
  Since we want users to be aware of what Ubuntu Pro is, we should highlight 
the right product name on any place that is still using the old "advantage" 
name. Updating the support URL here is a step into this direction

  [Original Bug Description]
  On the file 10-help-text, we are printing the following line on MOTD:

  * Support: https://ubuntu.com/advantage

  We should update the url to https://ubuntu.com/pro instead, as this
  will the default url for support information now

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

[Łukasz Zemczak]

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

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

Title:
  Update URL for Support information in MOTD message

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Committed
Status in base-files source package in Lunar:
  Fix Released
Status in base-files source package in Mantic:
  Fix Released
Status in base-files source package in Noble:
  Fix Released

Bug description:
  
  [Impact]
  When users see the MOTD message, they are currently seeing an outdated url 
under the support information.
  Even though the outdated url redirects to new Ubuntu Pro webpage, we believe 
the users should still see
  the correct url from the start

  [Test Case]

  - Launch a LXD container for any of the affected releases
  - Install the package with this fix applied
  - Install `update-motd` package
  - Run `update-motd` and confirm the Support url is now the correct one

  [Regression Potential]
  If users are parsing MOTD for some reason, the url change might break that 
logic now. However, parsing MOTD messages is not a supported flow, so we 
believe regression potential is low here.

  [Discussion]
  Since we want users to be aware of what Ubuntu Pro is, we should highlight 
the right product name on any place that is still using the old "advantage" 
name. Updating the support URL here is a step into this direction

  [Original Bug Description]
  On the file 10-help-text, we are printing the following line on MOTD:

  * Support: https://ubuntu.com/advantage

  We should update the url to https://ubuntu.com/pro instead, as this
  will the default url for support information now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 2045621] Re: Improve power consumption on Framework systems

[Launchpad Bug Tracker]

This bug was fixed in the package systemd-hwe - 249.11.5

---
systemd-hwe (249.11.5) jammy; urgency=medium

  [ Artur Pak ]
  * Add autosuspend rules for Framework (LP: #2045621)
  * Add three Dell platforms to sensor accel location base (LP: #2046687)

 -- Nick Rosbrook   Fri, 05 Jan 2024 10:29:41 -0500

** Changed in: systemd-hwe (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Update Released

[Łukasz Zemczak]

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

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

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2045621] Re: Improve power consumption on Framework systems

[Launchpad Bug Tracker]

This bug was fixed in the package systemd-hwe - 253.5.3

---
systemd-hwe (253.5.3) mantic; urgency=medium

  [ Artur Pak ]
  * Add autosuspend rules for Framework (LP: #2045621)
  * Add three Dell platforms to sensor accel location base (LP: #2046687)

 -- Nick Rosbrook   Fri, 05 Jan 2024 10:40:58 -0500

** Changed in: systemd-hwe (Ubuntu Mantic)
   Status: Fix Committed => Fix Released

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

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Released
Status in systemd source package in Noble:
  Fix Committed
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2015243] Re: py3versions doesn't follow symlinks (like realpath)

[Matthias Klose]

The python3 symlink is not meant to be handled by alternatives.

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

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

Title:
  py3versions doesn't follow symlinks (like realpath)

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  In case if we have more than one python version and manage them by 
update-alternatives, the path to the python binary looks like:
  root@devvm-14-143:~# ls -la /usr/bin/python3
  lrwxrwxrwx 1 root root 25 Apr  4 08:11 /usr/bin/python3 -> 
/etc/alternatives/python3
  root@devvm-14-143:~# ls -la /etc/alternatives/python3
  lrwxrwxrwx 1 root root 18 Apr  4 08:11 /etc/alternatives/python3 -> 
/usr/bin/python3.8

  So even we use the correct default version of python3 (like in Focal
  it is python3.8) py3version will fail

  root@devvm-14-143:~# py3versions -d
  py3versions: the symlink /usr/bin/python3 does not point to the python3 
default version. It must be reset to point to python3.8

  This caused due to os.readlink doesn't follow multiply symlinks, so I
  suggest to use Path from pathlib.

  I have attached patch with suggested changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2015243/+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 2049369] [NEW] autopkg tests ignored for migration of python3-defaults adding 3.12

[Matthias Klose]

Public bug reported:

autopkg tests ignored for migration of python3-defaults adding 3.12:

These are the autopkg tests for packages, which we'll ignore for the
initial migration of python3-defaults adding 3.12.

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

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


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

[Touch-packages] [Bug 1958019]

[attitokes]

(In reply to August Wikerfors from comment #781)
> (In reply to Christian G. Semke from comment #780)
> > Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> > worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> > can resolve this? I'm a bit of a beginner
> > 
> > Alsa:
> http://alsa-project.org/db/?f=24e78ce46f588c8a681c092c24e05811a4f42f77
> > Kernel: 6.5.2-arch1-1
> 
> I've submitted this patch which should fix it:
> https://lore.kernel.org/all/20230911213409.6106-1-...@augustwikerfors.se/

Hey! Looks like this acp6x-mach/yc_acp_quirk_table workaround would also
be needed for Yoga Slim 7 Pro 14ARH7 (LENOVO/82UU). I have one, and the
microphone does not works.

ALSA info:
https://alsa-project.org/db/?f=77e94edfeb14c5e3bf3ffb9524fb5d8390e1b722

>From the kernel logs looks like snd_pci_acp6x detects and enables a device:
```
[7.120140] snd_pci_acp6x :32:00.5: enabling device ( -> 0002)
```
but then there is nothing acp_yc_mach related in the logs.

I would appreciate if you could make a patch. Thanks!

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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

[Touch-packages] [Bug 2049353] Re: wayland XWarpPointer backwards compability

[Bug Watch Updater]

** Changed in: wayland
   Status: Unknown => New

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

Title:
  wayland XWarpPointer backwards compability

Status in wayland:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  I'm not sure how to report this really as it's not a bug but still
  quite severe. Bear with me as I'm a Unity dev mainly.

  Unity uses function calls to X11 for setting mouse cursor positions.
  Many games use this to lock the cursor to a certain position.

  With no backwards compatibility to XWarpPointer these games will be broken in 
Wayland.
  As there's little chance these games will be updated, the only possibility 
here is that Wayland supports this in some way.

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