[Touch-packages] [Bug 2011622] Re: rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace interpretation

[Alan Rosenthal]

> Could you try adding --old-args ? That should restore the previous
behaviour you are expecting.

It does indeed.  Thanks for the reply!

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

Title:
  rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace
  interpretation

Status in rsync package in Ubuntu:
  New

Bug description:
  Commands like this:
  rsync -a host.example.org:\{this,that} .
  have worked for decades, in multiple Ubuntu versions, but were broken by the 
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type 
that command).

  (To be clear, the backslash there quotes the '{' so that it is sent to
  the remote rsync rather than being interpreted by the local shell.)

  ("What happens instead?"  It now says "rsync: link_stat
  "/home/flaps/{this,that}" failed: No such file or directory (2)".)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2011622/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[Daniel van Vugt]

Seems like a fix exists, but it got stalled/forgotten:

https://gitlab.gnome.org/GNOME/gsettings-desktop-
schemas/-/merge_requests/55

** No longer affects: curtin (Ubuntu)

** Changed in: gsettings-desktop-schemas (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  In Progress
Status in subiquity package in Ubuntu:
  Won't Fix

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956099] Re: WiFi scan MAC is not randomized

[wontfix]

** Tags added: kinetic lunar

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

Title:
  WiFi scan MAC is not randomized

Status in network-manager package in Ubuntu:
  New

Bug description:
  Every distribution, Gnome itself, and OS are moving or have moved
  forward with this as a basic privacy measure. The old bugs and
  abstractions no longer exist AFAIK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1956099/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[wontfix]

>I would appreciate if you avoided adding uninvolved components to the
bug

What is the correct package for an existing gsetting and GUI selectable
feature that should be a default based purely on install selectable
variables?

>Last I see they are sitting in a "volunteers welcome" state, or
dependencies on things that need further work.

So it will never happen then. It is already a setting based on a
selection that is already done in the installer [timezone based on
area].

>Official time standards for the or one of the largest install bases in
the world is not justification because Ubuntu chose this specific DE?

>This sort of change is really best done in a package in the archive

Something like a gnome-fix-usa-time.deb that adds 12h upon install and
is triggered by selecting a US timezone? Sounds great.

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtin package in Ubuntu:
  Invalid
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  Won't Fix

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 2011622] Re: rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace interpretation

[Marc Deslauriers]

Hi,

The security fix for CVE-2022-29154 unfortunately changed the way
arguments are handled.

Could you try adding --old-args ? That should restore the previous
behaviour you are expecting.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-29154

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

Title:
  rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace
  interpretation

Status in rsync package in Ubuntu:
  New

Bug description:
  Commands like this:
  rsync -a host.example.org:\{this,that} .
  have worked for decades, in multiple Ubuntu versions, but were broken by the 
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type 
that command).

  (To be clear, the backslash there quotes the '{' so that it is sent to
  the remote rsync rather than being interpreted by the local shell.)

  ("What happens instead?"  It now says "rsync: link_stat
  "/home/flaps/{this,that}" failed: No such file or directory (2)".)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2011622/+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 2011622] Re: rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace interpretation

[Athos Ribeiro]

** Tags added: regression-update

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

Title:
  rsync 3.1.3-8ubuntu0.5 (CVE-2022-29154 patch) breaks remote brace
  interpretation

Status in rsync package in Ubuntu:
  New

Bug description:
  Commands like this:
  rsync -a host.example.org:\{this,that} .
  have worked for decades, in multiple Ubuntu versions, but were broken by the 
rsync 3.1.3-8ubuntu0 update (on the client, i.e. the machine on which I type 
that command).

  (To be clear, the backslash there quotes the '{' so that it is sent to
  the remote rsync rather than being interpreted by the local shell.)

  ("What happens instead?"  It now says "rsync: link_stat
  "/home/flaps/{this,that}" failed: No such file or directory (2)".)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2011622/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1949340

** Tags added: iso-testing

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in GTK+:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  Confirmed
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  Confirmed
Status in gtk4 source package in Kinetic:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions


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

[Touch-packages] [Bug 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[Dan Bungert]

Curtin is not the appropriate place to land fixes or even quirk
workarounds for this problem.  I would appreciate if you avoided adding
uninvolved components to the bug, especially when it has already been
pointed out that this is the wrong spot.

The linked threads you mention do not appear to me to have an "all but
refused" stance.  Last I see they are sitting in a "volunteers welcome"
state, or dependencies on things that need further work.

This sort of change is really best done in a package in the archive, and
I'm not hearing appropriate justification for installer quirks.
Declining for Subiquity, thanks.

** Changed in: subiquity (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtin package in Ubuntu:
  Invalid
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  Won't Fix

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

[wontfix]

** Tags added: jammy kinetic lunar

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the Day
  After=network-online.target
  Documentation=man:update-motd(8)

  [Service]
  Type=oneshot
  ExecStart=/etc/update-motd.d/50-motd-news --force

  
  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
    Installed: 10.1ubuntu2.3
    Candidate: 10.1ubuntu2.3
    Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1956109] Re: printer-driver-ptouch is included with metapackages for the minimal install

[wontfix]

** Tags added: kinetic lunar

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

Title:
  printer-driver-ptouch is included with metapackages for the minimal
  install

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  A label printer driver is a recommended dependency of many desktop,
  core, and minimal ubuntu metapackages. It is installed with the
  minimal Ubuntu option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956109/+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 1956110] Re: upower requires libimobiledevice6 as a dependency

[wontfix]

** Tags added: kinetic lunar

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

Title:
  upower requires libimobiledevice6 as a dependency

Status in libimobiledevice package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  An iPhone library is required to have power management required by
  Gnome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1956110/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[Dan Bungert]

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

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtin package in Ubuntu:
  Invalid
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  Incomplete

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[wontfix]

I would point to the new ubuntu-desktop-installer directly but it isn't
listed here. I don't care where in that stack it is done. Gnome has all
but refused to address this. A post-install or live preinstall hook
fixes this. Both linked packages contain one or both of these features
as listed in their documentation.

https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/30
https://gitlab.gnome.org/GNOME/glib/-/issues/2575
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/55
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2422

If it can be handled by simple gsettings or locale defaults, it should
be done until a better fix comes along. It is an option to click on that
should be the default by any official consumer or commercial standard in
the USA.

I don't think this should require justification in 2023.

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2575
   https://gitlab.gnome.org/GNOME/glib/-/issues/2575

** No longer affects: curtain (Ubuntu)

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

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtin package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  Incomplete

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1791691] Re: PATH broken in systemd units

[John Chittum]

** Changed in: cloud-images
   Status: Confirmed => Fix Released

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

Title:
  PATH broken in systemd units

Status in cloud-images:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  New
Status in snapd source package in Bionic:
  In Progress
Status in initramfs-tools source package in Cosmic:
  New
Status in snapd source package in Cosmic:
  Fix Released

Bug description:
  systemd units have broken PATH in recent cloud images.
  The PATH set for them is
    PATH=:/snap/bin.
  Previously value is
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

  # cat /etc/cloud/build.info
  build_name: server
  serial: 20180906

  Booted in lxc that fails like:
  # lxc launch ubuntu-daily:cosmic c3
  # lxc exec c3 cat /run/cloud-init/result.json
  {
   "v1": {
    "datasource": null,
    "errors": [
     "Unexpected error while running command.\nCommand: ['netplan', 
'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: 
b'netplan': b'netplan'\nStdout: -\nStderr: -",
     "Unexpected error while running command.\nCommand: ['netplan', 
'generate']\nExit code: -\nReason: [Errno 2] No such file or directory: 
b'netplan': b'netplan'\nStdout: -\nStderr: -",
     "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: 
ubuntu',))"
    ]
   }
  }

  
  Related bugs:
   * bug 1771382: ds-identify: does not have expected PATH.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1791691/+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 1952899] Re: Upgrade to 3.19.1 for LTS

[Maarten Fonville]

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

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

Title:
  Upgrade to 3.19.1 for LTS

Status in protobuf package in Ubuntu:
  Fix Released

Bug description:
  Woud it please be possible to upgrade Protobuf to 3.19.1 (which is
  already in Debian) for upcoming Ubuntu LTS 22.04 ?

  All packages that use protobuf as dependency (which are quite some)
  will need a rebuild, so it is important to organize a transition on
  time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1952899/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[Dan Bungert]

Curtin (no "a") doesn't manage time settings, so the fix definitely
isn't going there.

Comment #4 though makes this sound like it needs to be in the image, and
isn't installer specific?  Or can you clarify what you'd like the
installer to do here?

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

** Changed in: subiquity (Ubuntu)
   Status: New => Incomplete

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtain package in Ubuntu:
  Invalid
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  Incomplete

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1986619] Re: Fail to install base-passwd

[John]

Traced this down in the base-passwd package to /usr/sbin/update-passwd.
Ran the command with --verbose and it throws the same error.

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

Title:
  Fail to install base-passwd

Status in base-passwd package in Ubuntu:
  Confirmed

Bug description:
  /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb
  (Reading database ... 236425 files and directories currently installed.)
  Preparing to unpack base-passwd_3.5.52build1_amd64.deb ...
  Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ...
  Setting up base-passwd (3.5.52build1) ...
  Changing home-directory of irc from /var/run/ircd to /run/ircd
  1 changes have been made, rewriting files
  Writing passwd-file to /etc/passwd
  Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission 
denied
  dpkg: error processing package base-passwd (--install):
   installed base-passwd package post-installation script subprocess returned 
error exit status 4
  Errors were encountered while processing:
   base-passwd
  root@CNQDSX:/home/frank/Downloads#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+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 1986619] Re: Fail to install base-passwd

[John]

This occurred to me during an apt dist-upgrade.
   The file /etc/passwd.upwd-write does not exist.
   Attempting to "touch /etc/passwd.upwd-write" gives a permission denied error.
   I can write other files to the /etc/ directory.
   Nothing in lsof has and an fd open to this file.
   Forced a file system check made no difference.
   /etc/passwd is not immutable.
   Made a backup and new copy of /etc. No difference.

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

Title:
  Fail to install base-passwd

Status in base-passwd package in Ubuntu:
  Confirmed

Bug description:
  /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb
  (Reading database ... 236425 files and directories currently installed.)
  Preparing to unpack base-passwd_3.5.52build1_amd64.deb ...
  Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ...
  Setting up base-passwd (3.5.52build1) ...
  Changing home-directory of irc from /var/run/ircd to /run/ircd
  1 changes have been made, rewriting files
  Writing passwd-file to /etc/passwd
  Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission 
denied
  dpkg: error processing package base-passwd (--install):
   installed base-passwd package post-installation script subprocess returned 
error exit status 4
  Errors were encountered while processing:
   base-passwd
  root@CNQDSX:/home/frank/Downloads#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM

[wontfix]

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

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

** Tags added: kinetic lunar

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

Title:
  Time for the US is shown in 24h format. It should be 12h with AM/PM

Status in GSettings Desktop Schemas:
  New
Status in curtain package in Ubuntu:
  New
Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed
Status in subiquity package in Ubuntu:
  New

Bug description:
  Source- https://time.gov/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI

[Jeremy Bícha]

I don't want to re-enable this feature until there is a GUI way to turn
it off either altogether or for a particular network. It's nice that it
works in most places but there are still cases where a user may want to
disable it for themselves.

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

Title:
  Allow configuring Wi-Fi MAC Randomization feature from GUI

Status in gnome-control-center:
  Confirmed
Status in NetworkManager:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Recent versions of NetworkManager have a feature enabled by default to
  use a random MAC address when scanning for available Wi-Fi networks
  for privacy. My understanding is that the spoofed MAC address is not
  used when actually connecting to a network.

  This feature was disabled in Ubuntu 17.10 because it broke scanning
  with some Wi-Fi drivers. My understanding is that there is a bug in
  some drivers when attempting to change the MAC address. See LP:
  #1681513.

  The bug might not be as big of an issue with the latest version of 
NetworkManager because
  1) There are helpful commits like this (it was not backported to 17.04):
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1
  2) It is also possible now to selectively disable Wi-Fi MAC Randomization for 
specific drivers.
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9

  However, I'm really hesitant to re-enable this feature as long as
  A) we don't know for sure which drivers are affected,
  B) and more importantly, there is no GUI way to turn the feature on or off. 
Asking users to edit config files isn't very nice.

  The MAC Address Randomization feature is really nice (Windows 10 has a
  similar feature) but I think we need a GUI on/off switch in Settings >
  Wi-Fi or Settings > Privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 1735002] Re: Allow configuring Wi-Fi MAC Randomization feature from GUI

[wontfix]

Has the non-GUI part of issue not been solved through blacklists,
configuration or internal NM bugfixes yet? Most other distributions and
NM themselves have scan randomization enabled as a default.

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

Title:
  Allow configuring Wi-Fi MAC Randomization feature from GUI

Status in gnome-control-center:
  Confirmed
Status in NetworkManager:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Recent versions of NetworkManager have a feature enabled by default to
  use a random MAC address when scanning for available Wi-Fi networks
  for privacy. My understanding is that the spoofed MAC address is not
  used when actually connecting to a network.

  This feature was disabled in Ubuntu 17.10 because it broke scanning
  with some Wi-Fi drivers. My understanding is that there is a bug in
  some drivers when attempting to change the MAC address. See LP:
  #1681513.

  The bug might not be as big of an issue with the latest version of 
NetworkManager because
  1) There are helpful commits like this (it was not backported to 17.04):
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=46d53e1
  2) It is also possible now to selectively disable Wi-Fi MAC Randomization for 
specific drivers.
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b869d9

  However, I'm really hesitant to re-enable this feature as long as
  A) we don't know for sure which drivers are affected,
  B) and more importantly, there is no GUI way to turn the feature on or off. 
Asking users to edit config files isn't very nice.

  The MAC Address Randomization feature is really nice (Windows 10 has a
  similar feature) but I think we need a GUI on/off switch in Settings >
  Wi-Fi or Settings > Privacy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1735002/+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 2011347] Re: language-pack-fr (1:23.04+20230310) breaks at least g-c-c

[Launchpad Bug Tracker]

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

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

** Changed in: language-pack-fr (Ubuntu)
   Status: New => Confirmed

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

Title:
  language-pack-fr (1:23.04+20230310) breaks at least g-c-c

Status in language-pack-fr package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since this update:

  $ gnome-control-center 
  18:44:17.3415   **[27440]: WARNING: Couldn't get locale for 
language: (null)
  Erreur de segmentation (core dumped)

  Was ok in previous one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-fr/+bug/2011347/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/438988

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Incomplete

Bug description:
  [Impact]
  The armhf autopkgtests currently fail in Focal due to this, and failures are 
not marked as regressions. This limits our ability to catch other regressions 
on armhf.

  [Test Plan]
  The boot-and-services autopkgtest should not fail on armhf. Specifically, the 
test_no_failed test should ignore systemd-remount-fs.service failures on armhf 
only.

  [Where problems could occur]
  The fix is limited to the boot-and-services autopkgtest, so there is limited 
risk. Any bugs would show up in that test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/438988

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

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Triaged

Bug description:
  [SRU Impact]

  Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c, 
test_protect_syscall
  sysctl is called with the expectation the error result is EFAULT and not 
ENOSYS.
  This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp, 
oem, gke, oracle).

  [Fix]
  Assertion checks if either EFAULT or ENOSYS is returned. This way it will 
work for focal-5.4 kernels and focal-5.15 kernels.

  [Test to reproduce the issue]
  1. Create a vm and install one of the focal-5.15 kernels (i.e 
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
  2. Run the autotests for upstream and/or root-unittests:
  autopkgtest --test-name=upstream systemd -- qemu 

  [Test to verify the fix]
  1. Same as above
  2. Apply the fix in your local repo and run the tests using your local repo
  autopkgtest --test-name=upstream  -- qemu 

  [Where problems could occur]
  This is not gonna affect end users since it is a change in the test only.
  It may impact autotests, but it's a very low probability.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 2011656] Re: ibus-x11 crashed with SIGSEGV in _int_malloc()

[Gunnar Hjalmarsson]

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+attachment/5654564/+files/CoreDump.gz

** Information type changed from Private to Public

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

Title:
  ibus-x11 crashed with SIGSEGV in _int_malloc()

Status in ibus package in Ubuntu:
  New

Bug description:
  editing python code with idle, doing a select with shift-arrow in prep
  to a cut operation

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: ibus 1.5.28-1
  ProcVersionSignature: Ubuntu 5.19.0-1012.19-raspi 5.19.17
  Uname: Linux 5.19.0-1012-raspi aarch64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 14 23:41:55 2023
  ExecutablePath: /usr/libexec/ibus-x11
  ImageMediaBuild: 20221018.1
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/ibus-x11
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   _int_malloc (av=av@entry=0x892f0b00 , bytes=bytes@entry=48) 
at ./malloc/malloc.c:3923
   __GI___libc_malloc (bytes=48) at ./malloc/malloc.c:3305
   g_malloc () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   g_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
   g_timeout_source_new () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to lunar on 2023-01-31 (42 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2011656/+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 2002445] Re: udev NIC renaming race with mlx5_core driver

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/438988

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

Title:
  udev NIC renaming race with mlx5_core driver

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

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  
  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts
  
  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  client.use_key(pub_path, priv_path)

  base_instance = client.launch(
  image_id=image_id,
  instance_type="Standard_DS1_v2",
  user_data=cloud_config.format(defer="true"),
  )

  LOG.info(f"base instance: ssh ubuntu@{base_instance.ip}")
  base_instance.wait()
  LOG.info(base_instance.execute("apt cache policy systemd"))
  snapshotted_image_id = client.snapshot(base_instance)

  reproducer = False
  tries = 0
  success_count_with_race = 0
  success_count_no_race = 0
  failure_count_network_delay = 0
  failure_count_no_altnames = 0
  TEST_SUMMARY_TMPL = """
  - Test run complete: {tries} attempted -
  Successes without rename race: {success_count_no_race}
  Successes with rename race and preserved altname: 
{success_count_with_race}
  Failures due to network delay: {failure_count_network_delay}
  Failures due to no altnames persisted: {failure_count_no_altnames}
  ===
  """
  while tries < 100 and not reproducer:
  tries += 1
  new_instance = client.launch(
  image_id=snapshotted_image_id,
  

[Touch-packages] [Bug 2011722] [NEW] Move oem-config-setup steps into ubuntu-raspi-settings-desktop

[William Wilson]

Public bug reported:

When building images with livecd-rootfs, there is a hook to set up oem-
config for preinstalled raspi desktop images. As we move away from
livecd-rootfs (and the use of hooks in general), this step should be
moved into a package.

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

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

Title:
  Move oem-config-setup steps into ubuntu-raspi-settings-desktop

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  When building images with livecd-rootfs, there is a hook to set up
  oem-config for preinstalled raspi desktop images. As we move away from
  livecd-rootfs (and the use of hooks in general), this step should be
  moved into a package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2011722/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Benjamin Drung]

Hi Vincent, I uploaded chrony 4.3-1ubuntu3 to add the tzdata-legacy a
few hours ago.

Note: The leap seconds can also be read from /usr/share/zoneinfo/leap-
seconds.list

** Description changed:

  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").
  
  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.
  
  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html
  
  Two packages need to be adjusted:
  
+ * chrony: reads /usr/share/zoneinfo/right/UTC for leap seconds
  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy
  
  Following packages were checked and do not need to be touched:
  
  Only in source code documentation and/or tests suite:
  
  * mariadb
  * mariadb-10.6
  
  Copies of tz soure code:
  
  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)
  
  Referencing only /usr/share/zoneinfo/posixrules:
  
  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  Fix Committed
Status in moment-timezone.js package in Ubuntu:
  Fix Committed
Status in rdate package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * chrony: reads /usr/share/zoneinfo/right/UTC for leap seconds
  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 1965811] Re: software-properties-qt does not load driver information

[Erich Eickmeyer]

Pascal,

This is a very old bug that was closed as fixed and should not be necro-
bumped. If you're noticing something new, open a new bug report.

Furthermore, bug reports are not places for technical support.

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

Title:
  software-properties-qt does not load driver information

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

Bug description:
  Driver information is not being loaded by software-properties-qt. This
  appears to be a python issue, perhaps a python 3.10 compatibility
  issue.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1024, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
  apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
  AttributeError: 'Cache' object has no attribute 'packages'
  Exception ignored in: 

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Mar 21 11:34:54 2022
  InstallationDate: Installed on 2021-03-20 (365 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Vincent Blut]

Hi Benjamin,

chrony reads "/usr/share/zoneinfo/right/UTC" to determine when will the
next leap second occur and what is the current offset between TAI and
UTC. So I’ll have to add "tzdata-legacy" to the list of dependencies.

Cheers,
Vincent

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  Fix Committed
Status in moment-timezone.js package in Ubuntu:
  Fix Committed
Status in rdate package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 2009481] Re: FFE: mesa 23.0.1

[Timo Aaltonen]

** Description changed:

  Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch to
  use for Ubuntu 23.04.
  
  This release includes improvements across the board, and packaging adds
  a package for mesa-drm-shim.
  
  23.0.1 should be released on week 10, so it's a good candidate for an
  upload.
+ 
+ 
+ diffstat:
+ git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1
+  2493 files changed, 710212 insertions(+), 170014 deletions(-)
+ 
+ commits:
+ git log1 mesa-22.3.6..mesa-23.0.0 | wc -l
+3157

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

Title:
  FFE: mesa 23.0.1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch
  to use for Ubuntu 23.04.

  This release includes improvements across the board, and packaging
  adds a package for mesa-drm-shim.

  23.0.1 should be released on week 10, so it's a good candidate for an
  upload.

  
  diffstat:
  git diff mesa-22.3.6..mesa-23.0.0 | diffstat | tail -1
   2493 files changed, 710212 insertions(+), 170014 deletions(-)

  commits:
  git log1 mesa-22.3.6..mesa-23.0.0 | wc -l
 3157

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 1964636] Re: Incorrect handling of apparmor `bpf` capability

[Heather Lemon]

ack thanks!

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

Title:
  Incorrect handling of apparmor `bpf` capability

Status in apparmor package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  Incomplete
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  The apparmor_parser before the 3.0 release would build its capability list 
from the installed kernel headers. The apparmor_parser was built against a 
kernel without support for cap 'bpf'
  This was fixed in 3.0 by having a static caps list (with full mapping info) 
and the dynamic auto-generated list (against the kernel headers) that is used 
to check that the static list has not become stale. In addition the parser can 
pull kernel supported caps straight from the apparmor kernel module (it will 
however be missing the mapping info).
  Backporting the patches from 3.0 fixes the issue.

  [ Test Plan ]

  Before the fix, the following profile fails loading:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  AppArmor parser error, in stdin line 1: Invalid capability bpf.
  # echo $?
  1

  After the fix, it works as expected:

  # echo "profile foo { capability bpf, }" | apparmor_parser -Q
  # echo $?
  0

  [ Where problems could occur ]

  With these changes, the parser can change its behavior based on a few things.
  1. the kernel its built against. This would not change behavior when run in a 
container vs at system level.

  2. If a feature-file is specified, via --features-file, --policy-
  features, or --kernel-features. This allows overriding the normal
  policy and kernel examination that the parser does when compiling
  policy.

  3. If /sys/kernel/security/apparmor/features is not available. The
  parser will fallback to an old set of features available in a kernel
  before the kernel module started exporting what the kernel module
  supports on the running kernel.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  As mentioned before, these patches are already running on apparmor-3.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1964636/+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 1965811] Re: software-properties-qt does not load driver information

[Pascal Tempier]

Hello

@eeickmeyer do you know the status of this issue in ubuntu-drivers-
common ?

This bug is present when installing supplémentary packages and detecting
an nvidia card on 22.04.2.

Here is a workaround we use that sometime works :

sed  -i.orig "s/version = int(package_name.split('-')[-1])/version =
int(package_name.split('-')[-2])/" /usr/lib/python3/dist-
packages/UbuntuDrivers/detect.py

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

Title:
  software-properties-qt does not load driver information

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

Bug description:
  Driver information is not being loaded by software-properties-qt. This
  appears to be a python issue, perhaps a python 3.10 compatibility
  issue.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1024, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
  apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
  AttributeError: 'Cache' object has no attribute 'packages'
  Exception ignored in: 

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Mar 21 11:34:54 2022
  InstallationDate: Installed on 2021-03-20 (365 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 1998321] Re: tzdata 2022g release

[Benjamin Drung]

Attached 2022g-0ubuntu0.14.04+esm1 debdiff for trusty and also pushed to
https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata

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

** Patch added: "tzdata_2022g-0ubuntu0.14.04+esm1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+attachment/5654645/+files/tzdata_2022g-0ubuntu0.14.04+esm1.debdiff

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

Title:
  tzdata 2022g release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Trusty:
  New
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  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 Kinetic:
  Fix Released

Bug description:
  The 2022g release contains the following changes:

  * The northern edge of Chihuahua changes to US timekeeping.
  * Much of Greenland stops changing clocks after March 2023.
  * Fix some pre-1996 timestamps in northern Canada.
  * C89 is now deprecated; please use C99 or later.
  * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
  * In C code, use more C23 features if available.
  * C23 timegm now supported by default
  * Fixes for unlikely integer overflows

  Changes to future timestamps:

  In the Mexican state of Chihuahua, the border strip near the US will
  change to agree with nearby US locations on 2022-11-30. The strip's
  western part, represented by Ciudad Juárez, switches from -06 all year
  to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
  represented by Ojinaga, will observe US DST next year, like Presidio,
  TX.  (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
  splits from America/Ojinaga.

  Much of Greenland, represented by America/Nuuk, stops observing winter
  time after March 2023, so its daylight saving time becomes standard
  time.  (Thanks to Jonas Nyrup and Jürgen Appel.)

  ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
  CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [ Test Case for all releases ]
  1) dpkg -s tzdata | grep ^Version
  2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
    -> should have output, last dates should be in 2499

  
  [Test case for releases >= 20.04 LTS]

  from datetime import datetime, timedelta
  from icu import ICUtzinfo, TimeZone
  tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
  assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))

  [Test Case for releases <= 20.04 LTS]

  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 2002445] Autopkgtest regression report (systemd/249.11-0ubuntu3.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.8) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-intel-iotg/5.15.0-1027.32 (amd64)
linux-lowlatency/5.15.0-68.75 (arm64, amd64)
systemd/249.11-0ubuntu3.8 (arm64, ppc64el)
openrazer/3.2.0+dfsg-3 (i386)
multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x)
netplan.io/0.105-0ubuntu2~22.04.1 (amd64)
fwupd/1.7.9-1~22.04.1 (armhf)
udisks2/2.9.4-1ubuntu2 (amd64)
zfs-linux/unknown (s390x)
dbus/1.12.20-2ubuntu4.1 (s390x)
linux-ibm/5.15.0-1027.30 (amd64)
samba/unknown (s390x)
tang/11-1 (arm64)
gvfs/1.48.2-0ubuntu1 (arm64)
php8.1/unknown (s390x)
linux-nvidia/5.15.0-1018.18 (amd64)
csync2/2.0-25-gc0faaf9-1 (s390x)
tinyssh/20190101-1ubuntu1 (s390x)
mosquitto/2.0.11-1ubuntu1 (amd64)
casync/2+20201210-1build1 (ppc64el)
linux-gke/5.15.0-1029.34 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  udev NIC renaming race with mlx5_core driver

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

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  
  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts
  
  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  client.use_key(pub_path, priv_path)

  base_instance = client.launch(
  

[Touch-packages] [Bug 2004478] Autopkgtest regression report (systemd/249.11-0ubuntu3.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.8) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-intel-iotg/5.15.0-1027.32 (amd64)
linux-lowlatency/5.15.0-68.75 (arm64, amd64)
systemd/249.11-0ubuntu3.8 (arm64, ppc64el)
openrazer/3.2.0+dfsg-3 (i386)
multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x)
netplan.io/0.105-0ubuntu2~22.04.1 (amd64)
fwupd/1.7.9-1~22.04.1 (armhf)
udisks2/2.9.4-1ubuntu2 (amd64)
zfs-linux/unknown (s390x)
dbus/1.12.20-2ubuntu4.1 (s390x)
linux-ibm/5.15.0-1027.30 (amd64)
samba/unknown (s390x)
tang/11-1 (arm64)
gvfs/1.48.2-0ubuntu1 (arm64)
php8.1/unknown (s390x)
linux-nvidia/5.15.0-1018.18 (amd64)
csync2/2.0-25-gc0faaf9-1 (s390x)
tinyssh/20190101-1ubuntu1 (s390x)
mosquitto/2.0.11-1ubuntu1 (amd64)
casync/2+20201210-1build1 (ppc64el)
linux-gke/5.15.0-1029.34 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-networkd's dhcp4 client ignores local subnet routes

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

Bug description:
  [Impact]

  If a DHCP server pushes down a local subnet route with a null gateway,
  the systemd-networkd DHCP client does not correctly install the route.
  Instead, the route is ignored.

  [Test Plan]

  Taken from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2.

  * Start a Jammy LXD container:

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

  * Create a veth pair:

  $ ip link add veth0 up type veth peer name veth1
  $ ip addr add 172.20.0.1/24 dev veth0
  $ cat > /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2000880] Autopkgtest regression report (systemd/249.11-0ubuntu3.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.8) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-intel-iotg/5.15.0-1027.32 (amd64)
linux-lowlatency/5.15.0-68.75 (arm64, amd64)
systemd/249.11-0ubuntu3.8 (arm64, ppc64el)
openrazer/3.2.0+dfsg-3 (i386)
multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x)
netplan.io/0.105-0ubuntu2~22.04.1 (amd64)
fwupd/1.7.9-1~22.04.1 (armhf)
udisks2/2.9.4-1ubuntu2 (amd64)
zfs-linux/unknown (s390x)
dbus/1.12.20-2ubuntu4.1 (s390x)
linux-ibm/5.15.0-1027.30 (amd64)
samba/unknown (s390x)
tang/11-1 (arm64)
gvfs/1.48.2-0ubuntu1 (arm64)
php8.1/unknown (s390x)
linux-nvidia/5.15.0-1018.18 (amd64)
csync2/2.0-25-gc0faaf9-1 (s390x)
tinyssh/20190101-1ubuntu1 (s390x)
mosquitto/2.0.11-1ubuntu1 (amd64)
casync/2+20201210-1build1 (ppc64el)
linux-gke/5.15.0-1029.34 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-networkd: ActivationPolicy ignored in VLANs

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

Bug description:
  [Impact]

  The ActivationPolicy property in .network files is ignored for VLANs.

  [Test Plan]

  * On a Jammy machine with an interface named ens3, create the
  following configs:

  $ cat > /etc/systemd/network/10-vlan18.netdev << EOF
  [NetDev]
  Name=vlan18
  Kind=vlan

  [VLAN]
  Id=18
  EOF

  $ cat > /etc/systemd/network/20-vlan18.network << EOF
  [Match]
  Name=vlan18

  [Network]
  Address=10.10.1.1/24

  [Link]
  ActivationPolicy=manual
  EOF

  $ cat > /etc/systemd/network/30-ens3.network << EOF
  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  VLAN=vlan18
  EOF

  * Reboot the machine
  * On an affected machine, the vlan18@ens3 interface will have a configured IP 
at boot, despite the ActivationPolicy=manual setting in 
/etc/systemd/network/20-vlan18.network. On a patched machine, the interface 
should not have a configured IP.

  [Where problems could occur]

  The patch adds a condition where a netdev is not yet ready to be
  created. Specifically, it makes sure stacked netdevs are not created
  before their underlying link is activated. If we saw any problems, it
  would be related to netdev creation.

  [Original Description]

  This has been fixed upstream, see

  Upstream bug: https://github.com/systemd/systemd/issues/22593

  Any chance of a backport of the fix to 22.04?

  Fix: https://github.com/systemd/systemd-stable/pull/211

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2009502] Autopkgtest regression report (systemd/249.11-0ubuntu3.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.8) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

linux-intel-iotg/5.15.0-1027.32 (amd64)
linux-lowlatency/5.15.0-68.75 (arm64, amd64)
systemd/249.11-0ubuntu3.8 (arm64, ppc64el)
openrazer/3.2.0+dfsg-3 (i386)
multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x)
netplan.io/0.105-0ubuntu2~22.04.1 (amd64)
fwupd/1.7.9-1~22.04.1 (armhf)
udisks2/2.9.4-1ubuntu2 (amd64)
zfs-linux/unknown (s390x)
dbus/1.12.20-2ubuntu4.1 (s390x)
linux-ibm/5.15.0-1027.30 (amd64)
samba/unknown (s390x)
tang/11-1 (arm64)
gvfs/1.48.2-0ubuntu1 (arm64)
php8.1/unknown (s390x)
linux-nvidia/5.15.0-1018.18 (amd64)
csync2/2.0-25-gc0faaf9-1 (s390x)
tinyssh/20190101-1ubuntu1 (s390x)
mosquitto/2.0.11-1ubuntu1 (amd64)
casync/2+20201210-1build1 (ppc64el)
linux-gke/5.15.0-1029.34 (arm64, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
   Enable /dev/sgx_vepc access for the group 'sgx'

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

Bug description:
  [ Impact ]

  On systems where Intel SGX is available, access to a specific device
  node (/dev/sgx_vepc) must be enforced, with a specific permission
  (0660) and group (sgx).

  This allows KVM-based virtual machines to use such feature (the SGX
  "enclaves") in a proper fashion.  Without this, a manual udev rule
  needs to be created.

  [ Test Plan ]

  As the patch itself only tailors the permissions/group to the device
  node, in a system with Intel-SGX enabled, merely `ls -la` against the
  device node should show if the permissions and group are seen as
  expected.

  [ Where problems could occur ]

  N/A.  This seems to be a very straightforward inclusion, very specific
  to access enablement to the SGX reserved memory used for hosting
  enclaves.

  [ Other Info ]

  N/A.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+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 2011697] Re: [FFe] Ubuntu Pro integration outside of the LTS

[Sebastien Bacher]

Screenshot showing the corresponding tab

** Attachment added: "softwarepro.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011697/+attachment/5654639/+files/softwarepro.png

** Description changed:

  The Ubuntu Pro tab of software-properties-gtk is currently only enabled
  on LTS series. We would like to activate with a modified UI (to match
  the restricted set of services available on the serie) for Lunar.
  
- The corresponding code changes can be found on
- https://code.launchpad.net/~nteodosio/software-properties/+git/software-
- properties/+merge/438549
+ There are no changes to the existing backend code compared to what is
+ currently being used in LTS series and the action are done through the
+ 'pro' client so the 'new code' is limited to the UI layout tweaks.
  
- A ppa is available which includes a package build with the changes on
- https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro
+ The corresponding code changes can be found on 
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549
+ and ppa is available which includes a package build with the changes on 
https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro

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

Title:
  [FFe] Ubuntu Pro integration outside of the LTS

Status in software-properties package in Ubuntu:
  New

Bug description:
  The Ubuntu Pro tab of software-properties-gtk is currently only
  enabled on LTS series. We would like to activate with a modified UI
  (to match the restricted set of services available on the serie) for
  Lunar.

  There are no changes to the existing backend code compared to what is
  currently being used in LTS series and the action are done through the
  'pro' client so the 'new code' is limited to the UI layout tweaks.

  The corresponding code changes can be found on 
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549
  and ppa is available which includes a package build with the changes on 
https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011697/+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 2011697] [NEW] [FFe] Ubuntu Pro integration outside of the LTS

[Sebastien Bacher]

Public bug reported:

The Ubuntu Pro tab of software-properties-gtk is currently only enabled
on LTS series. We would like to activate with a modified UI (to match
the restricted set of services available on the serie) for Lunar.

There are no changes to the existing backend code compared to what is
currently being used in LTS series and the action are done through the
'pro' client so the 'new code' is limited to the UI layout tweaks.

The corresponding code changes can be found on 
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549
and ppa is available which includes a package build with the changes on 
https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro

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

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

Title:
  [FFe] Ubuntu Pro integration outside of the LTS

Status in software-properties package in Ubuntu:
  New

Bug description:
  The Ubuntu Pro tab of software-properties-gtk is currently only
  enabled on LTS series. We would like to activate with a modified UI
  (to match the restricted set of services available on the serie) for
  Lunar.

  There are no changes to the existing backend code compared to what is
  currently being used in LTS series and the action are done through the
  'pro' client so the 'new code' is limited to the UI layout tweaks.

  The corresponding code changes can be found on 
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/438549
  and ppa is available which includes a package build with the changes on 
https://launchpad.net/~nteodosio/+archive/ubuntu/ubuntu-pro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2011697/+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 2009481] Re: FFE: mesa 23.0.1

[Łukasz Zemczak]

I think it makes sense to go with 23.0.1 indeed, we'll probably update
it regardless. A bit unfortunate that this didn't happen earlier, but
it's outside of our control. I'd still like to see the list of changes
for 23.0.0 + 23.0.1, but let's consider this a pre-ACK for the FFe.

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

Title:
  FFE: mesa 23.0.1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Mesa 23.0.0 was released on Feb 23rd, and this is the planned branch
  to use for Ubuntu 23.04.

  This release includes improvements across the board, and packaging
  adds a package for mesa-drm-shim.

  23.0.1 should be released on week 10, so it's a good candidate for an
  upload.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2009481/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Benjamin Drung]

** Changed in: chrony (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: moment-timezone.js (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  Fix Committed
Status in moment-timezone.js package in Ubuntu:
  Fix Committed
Status in rdate package in Ubuntu:
  Fix Committed
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 2002445] Autopkgtest regression report (systemd/251.4-1ubuntu7.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (251.4-1ubuntu7.2) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

openrazer/3.4.0+dfsg-1ubuntu1 (i386)
asterisk/1:18.14.0~dfsg+~cs6.12.40431414-1 (arm64)
network-manager/1.40.0-1ubuntu2 (amd64)
gvfs/1.50.2-2 (amd64)
freedombox/unknown (armhf)
php8.1/unknown (s390x)
lemonldap-ng/2.0.14+ds-1 (s390x, arm64)
udisks2/2.9.4-3 (amd64)
mandos/1.8.15-1 (arm64)
libsoup3/3.2.0-1 (ppc64el)
postgresql-common/242ubuntu1 (s390x)
nftables/1.0.5-1 (arm64)
mutter/43.0-1ubuntu4 (amd64)
ostree/2022.5-3 (s390x)
dropbear/2022.82-4 (armhf)
lighttpd/1.4.65-2ubuntu1.1 (s390x)
exim4/4.96-3ubuntu1.1 (ppc64el)
resource-agents/unknown (amd64)
liblinux-systemd-perl/1.201600-3build1 (s390x, arm64)
tinyssh/20190101-1ubuntu1 (s390x)
linux-lowlatency/5.19.0-1020.21 (amd64, arm64)
mediawiki/1:1.35.7-1 (s390x)
linux-oem-5.17/5.17.0-1003.3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  udev NIC renaming race with mlx5_core driver

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

Bug description:
  [Impact]
  On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core 
driver's own configuration of subordinate interfaces. When the kernel wins this 
race, the device cannot be renamed as udev has attempted, and this causes 
systemd-network-online.target to timeout waiting for links to be configured. 
This ultimately results in boot being delayed by about 2 minutes.

  [Test Plan]
  Repeated launches of Standard_D8ds_v5 instance types will generally hit this 
race around 1 in 10 runs. Create a vm snapshot with updated systemd from 
ppa:enr0n/systemd-245. Launch 100 Standard_D8ds_v5 instances with updated 
systemd. Assert not failure in cloud-init status and no 2 minute delay in 
network-online.target.

  To check for failure symptom:
    - Assert that network-online.target isn't the longest pole from 
systemd-analyze blame.

  To assert success condition during net rename busy race:
    - assert when "eth1" is still the primary device name, that two altnames 
are listed (preserving the altname due to the primary NIC rename being hit.

  Sample script uses pycloudlib to create modified base image for test
  and launches 100 VMs of type Standard_D8ds_v5, counting both successes
  and any failures seen.

  
  #!/usr/bin/env python3
  # This file is part of pycloudlib. See LICENSE file for license information.
  """Basic examples of various lifecycle with an Azure instance."""

  import logging
  import json

  import pycloudlib
  LOG = logging.getLogger()

  base_cfg = """#cloud-config
  ssh-import-id: [chad.smith, enr0n]
  """

  apt_cfg = """
  # Add developer PPA
  apt:
   sources:
 systemd-testing:
   source: "deb [allow-insecure=yes] 
https://ppa.launchpadcontent.net/enr0n/systemd-245/ubuntu focal main"
  # upgrade systemd after cloud-init is nearly done
  runcmd:
   - apt install systemd udev -y --allow-unauthenticated
  """

  debug_systemd_cfg = """
  # Create systemd-udev debug override.conf in base image
  write_files:
  - path: /etc/systemd/system/systemd-networkd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  
  - path: /etc/systemd/system/systemd-udevd.service.d/override.conf
owner: root:root
defer: {defer}
content: |
  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug
  LogRateLimitIntervalSec=0
  """

  cloud_config = base_cfg + apt_cfg + debug_systemd_cfg
  cloud_config2 = base_cfg + debug_systemd_cfg

  
  def debug_systemd_image_launch_overlake_v5_with_snapshot():
  """Test overlake v5 timeouts
  
  test procedure:
  - Launch base focal image
  - enable ppa:enr0n/systemd-245 and systemd/udev debugging
  - cloud-init clean --logs && deconfigure waalinux agent before shutdown
  - snapshot a base image
  - launch v5 system from snapshot
  - check systemd-analyze for expected timeout
  """
  client = pycloudlib.Azure(tag="azure")

  image_id = client.daily_image(release="focal")
  pub_path = "/home/ubuntu/.ssh/id_rsa.pub"
  priv_path = "/home/ubuntu/.ssh/id_rsa"

  

[Touch-packages] [Bug 2004478] Autopkgtest regression report (systemd/251.4-1ubuntu7.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (251.4-1ubuntu7.2) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

openrazer/3.4.0+dfsg-1ubuntu1 (i386)
asterisk/1:18.14.0~dfsg+~cs6.12.40431414-1 (arm64)
network-manager/1.40.0-1ubuntu2 (amd64)
gvfs/1.50.2-2 (amd64)
freedombox/unknown (armhf)
php8.1/unknown (s390x)
lemonldap-ng/2.0.14+ds-1 (s390x, arm64)
udisks2/2.9.4-3 (amd64)
mandos/1.8.15-1 (arm64)
libsoup3/3.2.0-1 (ppc64el)
postgresql-common/242ubuntu1 (s390x)
nftables/1.0.5-1 (arm64)
mutter/43.0-1ubuntu4 (amd64)
ostree/2022.5-3 (s390x)
dropbear/2022.82-4 (armhf)
lighttpd/1.4.65-2ubuntu1.1 (s390x)
exim4/4.96-3ubuntu1.1 (ppc64el)
resource-agents/unknown (amd64)
liblinux-systemd-perl/1.201600-3build1 (s390x, arm64)
tinyssh/20190101-1ubuntu1 (s390x)
linux-lowlatency/5.19.0-1020.21 (amd64, arm64)
mediawiki/1:1.35.7-1 (s390x)
linux-oem-5.17/5.17.0-1003.3 (amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-networkd's dhcp4 client ignores local subnet routes

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

Bug description:
  [Impact]

  If a DHCP server pushes down a local subnet route with a null gateway,
  the systemd-networkd DHCP client does not correctly install the route.
  Instead, the route is ignored.

  [Test Plan]

  Taken from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/comments/2.

  * Start a Jammy LXD container:

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

  * Create a veth pair:

  $ ip link add veth0 up type veth peer name veth1
  $ ip addr add 172.20.0.1/24 dev veth0
  $ cat > /etc/netplan/60-veth1.yaml 

[Touch-packages] [Bug 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Benjamin Drung]

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

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in chrony package in Ubuntu:
  New
Status in moment-timezone.js package in Ubuntu:
  New
Status in rdate package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy

[Benjamin Drung]

** Summary changed:

- Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into 
tzdata-right
+ Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into 
tzdata-legacy

** Description changed:

  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").
  
  Drop /usr/share/zoneinfo/right from tzdata and move
- /usr/share/zoneinfo/right into separate tzdata-right package.
+ /usr/share/zoneinfo/right into separate tzdata-legacy package.
  
  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html
  
  Two packages need to be adjusted:
  
  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
- * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-right
+ * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy
  
  Following packages were checked and do not need to be touched:
  
  Only in source code documentation and/or tests suite:
  
  * mariadb
  * mariadb-10.6
  
  Copies of tz soure code:
  
  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)
  
  Referencing only /usr/share/zoneinfo/posixrules:
  
  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

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

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-legacy

Status in moment-timezone.js package in Ubuntu:
  New
Status in rdate package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-legacy package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moment-timezone.js/+bug/2008076/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface

[Timo Aaltonen]

so this is not fixed in lunar yet?

and Debian seems to have fixed it in mdadm instead?

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

Title:
  initramfs need to mount efivarfs because kernel 6.0 deprecated
  'efivars' sysfs interface

Status in OEM Priority Project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  [ Impact ]

  kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC
  RAID, mdadm needs initramfs to mount efivarfs instead.

  [1] The commit:
  commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741
  Author: Ard Biesheuvel 
  Date: Mon Jun 20 13:34:03 2022 +0200

  efi: vars: Remove deprecated 'efivars' sysfs interface

  [ Test Plan ]

  1. Install initramfs-tools
  2. update-initramfs -u
  3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs
  4. Check if boot script 00_mount_efivarfs exists in directory 
/tmp/extract-initramfs/main/scripts/init-top/
  5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot 
script 00_mount_efivarfs will be execute before udev.

  [ Where problems could occur ]

  Not sure if there any other tools/utilities also need to mount efivarfs as 
early as mdadm but the probability of file conflict should be very low.
  Also, there are no impact mounting efivarfs multiple times.
  mount: /sys/firmware/efi/efivars: efivarfs already mounted on 
/sys/firmware/efi/efivars.

  [ Scope ]

  Jammy, Kinetic

  [ Other Info ]

  The private bug link
  https://bugs.launchpad.net/somerville/+bug/1990231

  debian MR:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

[Ravi Prakash Joshi]

I am facing exactly the same issue. I have tried using 2-3 headphones
(having inbuilt microphone as wel), but the OS is not recognizing any,
as if the headphone jack is broken/faulty. These headpones are working
well on another PC (Dell) though.

ravi@razer:~$ sudo hdajacksensetest -a //without plugging the headphone
Pin 0x12 (Internal Mic, Mobile-In): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Black Mic, Right side): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = Yes
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Right side): present = No

ravi@razer:~$ sudo hdajacksensetest -a //with plugging the headhone
Pin 0x12 (Internal Mic, Mobile-In): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Black Mic, Right side): present = No
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = Yes
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Right side): present = No

Under the "Output Devices" tab in the pavucontrol, it shows "Headphones
(unplugged)". Strangely, selecting "Headphones (unplugged)" from the
dropdown menu makes sound in my headphone. In summary, headphones are
not detected automatically. I can hear using headphones after selecting
them inside pavucontrol, but even inside pavucontrol, headphones are
shown as "Headphones (unplugged)"

I reported at AskUbuntu (https://askubuntu.com/q/1454505) but no
response.

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

Title:
  [ALC256 - Razer Blade 15 2018] Headphones not automatically detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running the command alsamixer allows me to manually increase the sound levels 
for the headset, and sound plays properly through them. This requires me to 
disable the auto-mute feature.
  I haven't rebooted my system yet to see if this is permanent.
  But the UI doesn't show the heaphones at all and only sends sound through the 
main speakers of the laptop.

  ➜  ~ lspci -nnk | grep -i -A7 audio
  00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
Subsystem: Razer USA Ltd. Device [1a58:2001]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801

  ➜  ~ cat /proc/asound/card0/codec* | grep Codec 
  Codec: Realtek ALC256
  Codec: Intel Kabylake HDMI

  Using for example pavucontrol allows me to select the headphone, which are 
marked as unplugged, and I can play audio through them as long as I keep the 
application open.
  If I reboot or close pavucontrol, everything is back to the original state 
and only the speakers work.

  Additional Information:

  ➜  ~ lsb_release -rd 
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  What I expect to happen:

  When I plug in my headphones, Ubuntu and the UI should see them and
  automatically redirect all sound through them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   olivar 8320 F...m pulseaudio
   /dev/snd/controlC0:  olivar 8320 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec  6 13:02:14 2018
  InstallationDate: Installed on 2018-11-21 (15 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Razer
  dmi.bios.version: 01.01
  dmi.board.name: DANA_MB
  dmi.board.vendor: Razer
  dmi.chassis.type: 10
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr:
  dmi.product.family: 1A582001 Razer Blade
  dmi.product.name: Blade