From 1861524 at bugs.launchpad.net  Sat Feb  1 23:51:10 2020
From: 1861524 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 01 Feb 2020 23:51:10 -0000
Subject: [Bug 1861524] Re: Sync libsbml 5.18.0+dfsg-1 (universe) from Debian
 unstable (main)
References: <158049790720.19181.9740766373873744684.malonedeb@gac.canonical.com>
Message-ID: <158060107112.18703.652944875557661192.launchpad@gac.canonical.com>

** Changed in: libsbml (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861524

Title:
  Sync libsbml 5.18.0+dfsg-1 (universe) from Debian unstable (main)

Status in libsbml package in Ubuntu:
  New

Bug description:
  Please sync libsbml 5.18.0+dfsg-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Build-depend on dh-python.
    * Rebuild against new liboctave7.
    * No-change rebuild for the perl update.

  The Debian package added the build dependency as well.

  Changelog entries since current focal version 5.17.2+dfsg-3ubuntu1:

  libsbml (5.18.0+dfsg-1) unstable; urgency=medium

    * New upstream version
    * Standards-Version: 4.5.0 (routine-update)
    * debhelper-compat 12 (routine-update)
    * Remove obsolete fields Contact, Name from debian/upstream/metadata
      (already present in machine-readable debian/copyright).
    * Build-Depends: dh-python
      Closes: #949195
    * Fix installation path of Python modules
      Closes: #922486
    * Enforce Python3 interpreter in examples

   -- Andreas Tille <tille at debian.org>  Thu, 30 Jan 2020 19:10:49 +0100

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


From 1860845 at bugs.launchpad.net  Sat Feb  1 23:51:24 2020
From: 1860845 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 01 Feb 2020 23:51:24 -0000
Subject: [Bug 1860845] Re: Sync python-concurrent.futures 3.3.0-3 (universe)
 from Debian unstable (main)
References: <157994016259.5059.1256274147338832036.malonedeb@wampee.canonical.com>
Message-ID: <158060108571.8594.6822445931502195053.launchpad@chaenomeles.canonical.com>

** Changed in: python-concurrent.futures (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860845

Title:
  Sync python-concurrent.futures 3.3.0-3 (universe) from Debian unstable
  (main)

Status in python-concurrent.futures package in Ubuntu:
  New

Bug description:
  Please sync python-concurrent.futures 3.3.0-3 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Call python2 in the build and the autopkg test command.

  The Debian package now call python2 as well.

  Changelog entries since current focal version 3.3.0-1ubuntu2:

  python-concurrent.futures (3.3.0-3) unstable; urgency=medium

    * Reupload as source-only upload.

   -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 11:47:15 +0100

  python-concurrent.futures (3.3.0-2) unstable; urgency=medium

    * Bump Standards-Version to 4.4.1.
    * Call python2 in the build and the autopkg test command.
    * d/copyright: Bump my copyright year.

   -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 08:07:33 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-concurrent.futures/+bug/1860845/+subscriptions


From 1860839 at bugs.launchpad.net  Sat Feb  1 23:51:42 2020
From: 1860839 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 01 Feb 2020 23:51:42 -0000
Subject: [Bug 1860839] Re: Sync python-multipletau 0.3.3+ds-3 (universe) from
 Debian unstable (main)
References: <157993962160.5441.15096718876626558857.malonedeb@chaenomeles.canonical.com>
Message-ID: <158060110403.9005.2006544172232154951.launchpad@chaenomeles.canonical.com>

** Changed in: python-multipletau (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860839

Title:
  Sync python-multipletau 0.3.3+ds-3 (universe) from Debian unstable
  (main)

Status in python-multipletau package in Ubuntu:
  New

Bug description:
  Please sync python-multipletau 0.3.3+ds-3 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Do not test dropped Python2 libraries in autopkgtest.

  The Debian package has dropped the Python2 tests as well.

  Changelog entries since current focal version 0.3.3+ds-2ubuntu1:

  python-multipletau (0.3.3+ds-3) unstable; urgency=medium

    * Team upload

    [ Michael Hudson-Doyle ]
    * Do not test dropped Python2 libraries in autopkgtest.
      Closes: #944700

    [ Andreas Tille ]
    * Standards-Version: 4.4.1
    * Remove trailing whitespace in debian/changelog

   -- Andreas Tille <tille at debian.org>  Fri, 06 Dec 2019 13:49:14 +0100

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


From 1762391 at bugs.launchpad.net  Sun Feb  2 00:00:19 2020
From: 1762391 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 02 Feb 2020 00:00:19 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158060161911.8770.16894957432625337589.launchpad@chaenomeles.canonical.com>

** Bug watch removed: github.com/systemd/systemd/issues #14567
   https://github.com/systemd/systemd/issues/14567

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1859627 at bugs.launchpad.net  Sun Feb  2 00:19:01 2020
From: 1859627 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 02 Feb 2020 00:19:01 -0000
Subject: [Bug 1859627] Re: Firefox 72 regression - HTML5 games do not load
References: <157901118020.3421.14884327325588278772.malonedeb@soybean.canonical.com>
Message-ID: <158060274266.19022.13811797427119270866.launchpad@gac.canonical.com>

** Tags added: regression-update

** Changed in: firefox (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1859627

Title:
  Firefox 72 regression - HTML5 games do not load

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu the following URL:

  https://game-launcher-
  lux.isoftbet.com/255/904612?lang=en&cur=EUR&mode=0&user=fun

  * loads fine with Chrome
  * loads fine with Firefox 71
  * shows only a black page with Firefox 72

  However Firefox 72 on Windows and OSX loads correctly.

  All the HTML5 games from this provider are affected.

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


From 1852599 at bugs.launchpad.net  Sun Feb  2 00:25:28 2020
From: 1852599 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 02 Feb 2020 00:25:28 -0000
Subject: [Bug 1852599] Re: Cannot delete TLS Terminated listener if container
 has been deleted in barbican
References: <157374528757.6370.13569343319335325172.malonedeb@gac.canonical.com>
Message-ID: <158060312983.19098.1124307114325610099.launchpad@gac.canonical.com>

** Project changed: charm-octavia => octavia

** Changed in: octavia
       Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1852599

Title:
  Cannot delete TLS Terminated listener if container has been deleted in
  barbican

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Triaged
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in octavia:
  Fix Released
Status in octavia package in Ubuntu:
  Fix Released
Status in octavia source package in Disco:
  Won't Fix
Status in octavia source package in Eoan:
  Triaged
Status in octavia source package in Focal:
  Fix Released

Bug description:
  [Impact]
  octavia lb's listener can't be delete when there is no secret container which is already deleted.

  
  [Test Case]

  1. deploy and setup octavia env
  2. run below script
  - https://pastebin.ubuntu.com/p/xPWKnPqFhw/
  3. check if there is listener-1 is there or not ( in this case, there is )

  [Regression]

  This fix needs restarting octavia services. so downtime will be there
  shortly.

  [Others]

  After patching with https://review.opendev.org/#/c/691693/,

  I Was able to see the same error , but listener is actually deleted.

  
  [Original Description]

  There seems to be a fault condition in amphora builds that can lead to
  not being able to delete a failed loadbalancer/listener.

  If the barbican container for a tls terminated endpoint listener is
  deleted before the listener/amphora is deleted, the query to update to
  the listener's tls certificates fails during the delete_pools flow.

  It exhibits the following in the client:

  DELETE call to None for https://octavia.mysite:9876/v2.0/lbaas/listeners/4f46a6a3-a756-41b2-9148-c060bf28e621 used request id req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf
  Request returned failure status: 500
  Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 29, in wrapper
      response = func(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 204, in listener_delete
      response = self.delete(url)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 185, in delete
      return self._request('DELETE', url, **params)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 141, in _request
      return session.request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/osc_lib/session.py", line 40, in request
      resp = super(TimingSession, self).request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/keystoneauth1/session.py", line 737, in request
      raise exceptions.from_response(resp, method, url)
  keystoneauth1.exceptions.http.InternalServerError: Internal Server Error (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand
      result = cmd.run(parsed_args)
    File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run
      return super(Command, self).run(parsed_args)
    File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run
      return_code = self.take_action(parsed_args) or 0
    File "/usr/lib/python3/dist-packages/octaviaclient/osc/v2/listener.py", line 152, in take_action
      listener_id=listener_id)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 38, in wrapper
      request_id=e.request_id)
  octaviaclient.api.v2.octavia.OctaviaClientException: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  clean_up DeleteListener: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 29, in wrapper
      response = func(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 204, in listener_delete
      response = self.delete(url)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 185, in delete
      return self._request('DELETE', url, **params)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 141, in _request
      return session.request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/osc_lib/session.py", line 40, in request
      resp = super(TimingSession, self).request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/keystoneauth1/session.py", line 737, in request
      raise exceptions.from_response(resp, method, url)
  keystoneauth1.exceptions.http.InternalServerError: Internal Server Error (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 134, in run
      ret_val = super(OpenStackShell, self).run(argv)
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 279, in run
      result = self.run_subcommand(remainder)
    File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 169, in run_subcommand
      ret_value = super(OpenStackShell, self).run_subcommand(argv)
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand
      result = cmd.run(parsed_args)
    File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run
      return super(Command, self).run(parsed_args)
    File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run
      return_code = self.take_action(parsed_args) or 0
    File "/usr/lib/python3/dist-packages/octaviaclient/osc/v2/listener.py", line 152, in take_action
      listener_id=listener_id)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 38, in wrapper
      request_id=e.request_id)
  octaviaclient.api.v2.octavia.OctaviaClientException: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  The server side log shows:

  2019-11-05 14:41:48.288 2020577 WARNING octavia.controller.worker.controller_worker [req-046fe879-63c2-4804-9732-9985faf380e6 - ef8b2568c694461499c074c641a57a14 - - -] Task 'octavia.controller.worker.tasks.amphora_driver_tasks.ListenersUpdate' (1e77205e-486a-432b-b236-8e806c3c2b7e) transitioned into state 'FAILURE' from state 'RUNNING'
  5 predecessors (most recent first):
    Atom 'octavia.controller.worker.tasks.model_tasks.DeleteModelObject' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'object': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': None}
    |__Atom 'octavia.controller.worker.tasks.database_tasks.CountPoolChildrenForQuota' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': {'HM': 1, 'member': 3}}
       |__Atom 'octavia.controller.worker.tasks.database_tasks.MarkPoolPendingDeleteInDB' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': None}
          |__Atom 'octavia.controller.worker.tasks.lifecycle_tasks.PoolToErrorOnRevertTask' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>, 'listeners': [<octavia.common.data_models.Listener object at 0x7fd217b7f400>], 'loadbalancer': <octavia.common.data_models.LoadBalancer object at 0x7fd216dc6550>}, 'provides': None}
             |__Flow 'octavia-delete-pool-flow': barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker Traceback (most recent call last):
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican.py", line 114, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return pkcs12.PKCS12Cert(cert_secret.payload)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 193, in payload
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._fetch_payload()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 261, in _fetch_payload
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     if not self.payload_content_type and not self.content_types:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 184, in payload_content_type
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     if not self._payload_content_type and self.content_types:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 34, in wrapper
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._fill_lazy_properties()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 414, in _fill_lazy_properties
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     result = self._api.get(self._secret_ref)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 70, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return super(_HTTPClient, self).get(*args, **kwargs).json()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 375, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return self.request(url, 'GET', **kwargs)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 63, in request
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._check_status_code(resp)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 107, in _check_status_code
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     status
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker During handling of the above exception, another exception occurred:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker Traceback (most recent call last):
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/executor.py", line 53, in _execute_task
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     result = task.execute(**arguments)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/controller/worker/tasks/amphora_driver_tasks.py", line 78, in execute
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.amphora_driver.update(listener, loadbalancer.vip)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 162, in update
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     certs = self._process_tls_certificates(listener)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 284, in _process_tls_certificates
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.cert_manager, listener)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/common/tls_utils/cert_parser.py", line 353, in load_certificates_data
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     check_only=True))
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican.py", line 122, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     check_only=check_only, service_name=service_name
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican_legacy.py", line 160, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     LOG.error('Error getting cert %s: %s', cert_ref, str(e))
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.force_reraise()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     six.reraise(self.type_, self.value, self.tb)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     raise value
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican_legacy.py", line 138, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     container_ref=cert_ref
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/containers.py", line 540, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     response = self._api.get(container_ref)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 70, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return super(_HTTPClient, self).get(*args, **kwargs).json()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 375, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return self.request(url, 'GET', **kwargs)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 63, in request
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._check_status_code(resp)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 107, in _check_status_code
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     status
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.

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


From 1861524 at bugs.launchpad.net  Sun Feb  2 07:19:47 2020
From: 1861524 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sun, 02 Feb 2020 07:19:47 -0000
Subject: [Bug 1861524] Re: Sync libsbml 5.18.0+dfsg-1 (universe) from Debian
 unstable (main)
References: <158049790720.19181.9740766373873744684.malonedeb@gac.canonical.com>
Message-ID: <158062798822.8211.14459524781773899221.malone@chaenomeles.canonical.com>

Synced, though currently waiting in -proposed.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861524

Title:
  Sync libsbml 5.18.0+dfsg-1 (universe) from Debian unstable (main)

Status in libsbml package in Ubuntu:
  Fix Released

Bug description:
  Please sync libsbml 5.18.0+dfsg-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Build-depend on dh-python.
    * Rebuild against new liboctave7.
    * No-change rebuild for the perl update.

  The Debian package added the build dependency as well.

  Changelog entries since current focal version 5.17.2+dfsg-3ubuntu1:

  libsbml (5.18.0+dfsg-1) unstable; urgency=medium

    * New upstream version
    * Standards-Version: 4.5.0 (routine-update)
    * debhelper-compat 12 (routine-update)
    * Remove obsolete fields Contact, Name from debian/upstream/metadata
      (already present in machine-readable debian/copyright).
    * Build-Depends: dh-python
      Closes: #949195
    * Fix installation path of Python modules
      Closes: #922486
    * Enforce Python3 interpreter in examples

   -- Andreas Tille <tille at debian.org>  Thu, 30 Jan 2020 19:10:49 +0100

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


From 1860839 at bugs.launchpad.net  Sun Feb  2 07:17:57 2020
From: 1860839 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sun, 02 Feb 2020 07:17:57 -0000
Subject: [Bug 1860839] Re: Sync python-multipletau 0.3.3+ds-3 (universe) from
 Debian unstable (main)
References: <157993962160.5441.15096718876626558857.malonedeb@chaenomeles.canonical.com>
Message-ID: <158062787741.26327.10292632889553437296.malone@soybean.canonical.com>

Already synced :)

** Changed in: python-multipletau (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860839

Title:
  Sync python-multipletau 0.3.3+ds-3 (universe) from Debian unstable
  (main)

Status in python-multipletau package in Ubuntu:
  Fix Released

Bug description:
  Please sync python-multipletau 0.3.3+ds-3 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Do not test dropped Python2 libraries in autopkgtest.

  The Debian package has dropped the Python2 tests as well.

  Changelog entries since current focal version 0.3.3+ds-2ubuntu1:

  python-multipletau (0.3.3+ds-3) unstable; urgency=medium

    * Team upload

    [ Michael Hudson-Doyle ]
    * Do not test dropped Python2 libraries in autopkgtest.
      Closes: #944700

    [ Andreas Tille ]
    * Standards-Version: 4.4.1
    * Remove trailing whitespace in debian/changelog

   -- Andreas Tille <tille at debian.org>  Fri, 06 Dec 2019 13:49:14 +0100

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


From 1842167 at bugs.launchpad.net  Sun Feb  2 23:40:56 2020
From: 1842167 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 02 Feb 2020 23:40:56 -0000
Subject: [Bug 1842167] Re: Default list of stations entry for "WSUM 91.7 FM
 (University of Wisconsin) has an outdated URL
References: <156723706522.6124.12294142371125705385.malonedeb@soybean.canonical.com>
Message-ID: <158068685700.26233.18166699324071968373.malone@soybean.canonical.com>

rhythmbox (3.4.4-1ubuntu1) focal; urgency=medium

  * debian/patches/restore-traditional-menubar.patch:
    - removed, the menu code the change was built on was dropped
      and we removed similar patches from other applications with GNOME
  * Merge with Debian. Remaining changes:
    + Split out zeitgeist plugin
    + debian/control.in:
      - Allow unity-control-center as alternate dependency
      - Suggest instead of recommend gst-plugins-ugly
      - Suggest rhythmbox-plugin-zeitgeist
      - Recommends rhythmbox-plugin-alternative-toolbar. It improves the
        user interface and makes it fit better with GNOME.
    + debian/rhythmbox-plugins.install, debian/control{,.in}: Drop context
      plugin - it's mostly broken and would need porting to webkit2 anyway.
    + debian/patches/02_use_escaped_podcast_uri.patch
      - Handle podcasts that have sound files with the same basename
    + debian/patches/03_magnatune_partner.patch:
      - Change magnatune partner ID to 'ubuntu'.
    + debian/patches/05_hide_on_quit.patch
      - Hide (not quit) if RB is playing when closed.
    + debian/patches/07_quicklists.patch
      - Add quicklists.
    + debian/patches/08_stop_quit.patch:
      - Add a "Stop & Quit"-option to the quickmenu (via .desktop)
      - Add new symbol to librhythmbox-core10.symbols
    + debian/patches/make-shuffle-repeat-proper-toggle-actions.patch,
      debian/patches/restore-traditional-menubar.patch: Add a traditional
      menubar back when we want it, and fix the shuffle/repeat actions so
      they work correctly there.
    + debian/patches/0002-grilo-container-max-tracks.patch:
      increase CONTAINER_MAX_TRACKS to 15000
    + debian/patches/10_encoding_use_ubuntu_profiles.patch, debian/*.prs,
      debian/rhythmbox-data.install:
      - Add Ubuntu encoding presets and use them by default.
    + debian/source_rhythmbox.py: Add an apport hook.
    + Add breaks/replaces since we moved plugins from rhythmbox and rhythmbox-
      plugins-magnatune back to rhythmbox-plugins

 -- Sebastien Bacher <seb128 at ubuntu.com>  Wed, 16 Jan 2019 13:50:24
+0100

** Changed in: rhythmbox (Ubuntu)
       Status: Confirmed => Fix Released

** Tags removed: patch-forwarded-upstream
** Tags added: patch-accepted-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842167

Title:
  Default list of stations entry for "WSUM 91.7 FM (University of
  Wisconsin) has an outdated URL

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Update:  A patch has been posted - who can apply it?

  The stock URL does no longer have an DNS-record.

  (Stock URL is "http://vu.wsum.wisc.edu/wsumlive.m3u").

  The new URL appears to be:

  http://stream.studio.wsum.wisc.edu/wsum128

  A workaround, is to rightclick the station, choose "properties", which
  will popup a window with information about the station. Click the
  "details" tab in the popup window, and replace the URL with the one
  above, and close the the popup window.

  I think at least one of the other URL's might need an update, but I
  haven't looked into that yet.

  Additional information per request:

  (1)
  $ lsb_release -rd
  Description:	Ubuntu 19.04
  Release:	19.04

  (2)
  $ rhythmbox --version
  rhythmbox 3.4.3

  $ apt-cache policy rhythmbox
  rhythmbox:
    Installeret: 3.4.3-1ubuntu1
    Kandidat:    3.4.3-1ubuntu1
    Versionstabel:
   *** 3.4.3-1ubuntu1 500
          500 http://ny-mirrors.evowise.com/ubuntu disco/main amd64 Packages
          100 /var/lib/dpkg/status
       3.3-1ubuntu7 500
          500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  (3) I obviously expected the URL to up to date.

  (4) I found that the URL was out of date.

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


From jsailor at jesnetplus.com  Mon Feb  3 16:06:01 2020
From: jsailor at jesnetplus.com (Jonathan Sailor)
Date: Mon, 03 Feb 2020 16:06:01 -0000
Subject: [Bug 1848856] Re: zfs on root fails with grub syntax error with
 multidisks pools
References: <157149486953.25166.791270331006920218.malonedeb@chaenomeles.canonical.com>
Message-ID: <158074596159.19296.15129988769913083486.malone@gac.canonical.com>

@jibel, any chance of an SRU for this?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848856

Title:
  zfs on root fails with grub syntax error with multidisks pools

Status in grub2 package in Ubuntu:
  Fix Released
Status in grubzfs-testsuite package in Ubuntu:
  Fix Released
Status in grub2 source package in Eoan:
  Triaged
Status in grubzfs-testsuite source package in Eoan:
  Triaged
Status in grub2 source package in Focal:
  Fix Released
Status in grubzfs-testsuite source package in Focal:
  Fix Released

Bug description:
  [Description]
  When a pool is created on several devices like cache and log on separate devices, mirror or raidz. When grub-probe queries the target to report the device attached to the boot directory, it reports all the devices that make the pool, one by line. The result is an error in 10_linux_zfs that generates an invalid grub configuration file. Only the case 1 pool = 1 device was considered

  [Test Case]
  1. Create a mirrored pool
  $ zpool create mirror /dev/Xda1 /dev/Xda2

  2. run update-grub

  Expected result:
  grub configuration is generated successfully.

  Actual result:
  The generated grub configuration file is incomplete and its syntax is invalid

  [Regression Potential]
  Low. The patch takes the first device returned by grub-probe which is the first device of data of the mirror. 

  [Original Description]
  At the end of the upgrade from 19.04 to 19.10, the post process of the update-grub reports:

  Syntax error at line 185
  Syntax errors are detected in generated GRUB config file.
  Ensure that there are no errors in /etc/default/grub
  and /etc/grub.d/* files or please file a bug report with
  /boot/grub/grub.cfg.new file attached.
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
  dpkg: error processing package linux-image-5.3.0-18-generic (--configure):
   installed linux-image-5.3.0-18-generic package post-installation script subprocess returned error exit status 1
  Errors were encountered while processing:
   friendly-recovery
   grub-efi-amd64
   grub-efi
   grub-efi-amd64-signed
   shim-signed
   linux-image-5.3.0-18-generic

  The system used https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04
  -Root-on-ZFS to add zfs on root to a 19.04 system.

  The syntax error in grub.cfg.new is an extra } on line 185.  However,
  comparing the grub.cfg.new to the previously generated grub.cfg under
  19.04, there is a significant quantity of configuration missing.

  Manually running update-grub generates the same error.
  /etc/default/grub is the only file changed from default installation
  to include zswap.  This file was not changed prior to upgrade.

  The error is reported during the processing of
  /etc/grub.d/10_linux_zfs which is dated October 11.  I attempted the
  upgrade on 10/18 and have done multiple updates to get the latest
  kernel and remove old kernels prior to the upgrade.  So, I believe the
  problem is with one of the upgrade modules.

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


From steve.langasek at canonical.com  Mon Feb  3 21:41:14 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Mon, 03 Feb 2020 21:41:14 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158076607461.26978.4121114350266428455.malone@soybean.canonical.com>

Hello mtemp, or anyone else affected,

Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.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 and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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 Eoan)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From steve.langasek at canonical.com  Mon Feb  3 21:53:11 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Mon, 03 Feb 2020 21:53:11 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158076679204.8770.11368214156715024890.malone@chaenomeles.canonical.com>

Hello mtemp, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.34 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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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 Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Tue Feb  4 05:31:58 2020
From: 1762391 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Tue, 04 Feb 2020 05:31:58 -0000
Subject: [Bug 1762391] Autopkgtest regression report (systemd/237-3ubuntu10.34)
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <20200204053158.D400B240194@snakefruit.canonical.com>

All autopkgtests for the newly accepted systemd (237-3ubuntu10.34) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

php7.2/7.2.24-0ubuntu0.18.04.2 (armhf)
openssh/1:7.6p1-4ubuntu0.3 (arm64, armhf, ppc64el, amd64, s390x, i386)
dovecot/1:2.2.33.2-1ubuntu4.5 (armhf)
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el)


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

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

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Tue Feb  4 05:48:10 2020
From: 1762391 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Tue, 04 Feb 2020 05:48:10 -0000
Subject: [Bug 1762391] Autopkgtest regression report (systemd/242-7ubuntu3.3)
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <20200204054810.EF598240712@snakefruit.canonical.com>

All autopkgtests for the newly accepted systemd (242-7ubuntu3.3) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:

samba/2:4.10.7+dfsg-0ubuntu2.4 (armhf)
netplan.io/0.98-0ubuntu1 (amd64, ppc64el)
gnome-desktop3/3.34.2-2ubuntu1~19.10.1 (armhf)
systemd/242-7ubuntu3.3 (ppc64el, arm64)
munin/2.0.49-3ubuntu1 (armhf)
bolt/0.8-4 (armhf)
umockdev/0.13.2-1 (armhf)
openssh/1:8.0p1-6build1 (amd64, ppc64el, i386, s390x, arm64, armhf)
linux-oem-osp1/5.0.0-1037.42 (amd64)
multipath-tools/unknown (armhf)
knot-resolver/3.2.1-3 (amd64, ppc64el)
lxc/3.0.4-0ubuntu1 (amd64, ppc64el, i386)


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

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

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1861985 at bugs.launchpad.net  Wed Feb  5 08:43:00 2020
From: 1861985 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 05 Feb 2020 08:43:00 -0000
Subject: [Bug 1861985] [NEW] Sync gexiv2 0.12.0-2 (main) from Debian unstable
 (main)
References: <158089217406.26940.13814686307869276484.malonedeb@soybean.canonical.com>
Message-ID: <158089218055.8684.11019519026605366739.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Rico Tzschichholz (ricotz):

Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Use python2 instead of python in the autopkg test.

Debian switched to use python3.

Changelog entries since current focal version 0.10.9-1ubuntu1:

gexiv2 (0.12.0-2) unstable; urgency=medium

  * Drop patch Use-exiv2-version-0.25.patch.
    Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
    can build against it. (Closes: #942519, #950169)
  * Update Standards-Version to 4.5.0.
    No changes necessary.

 -- Jason Crain <jason at inspiresomeone.us>  Sun, 02 Feb 2020 04:29:42
-0700

gexiv2 (0.12.0-1) unstable; urgency=medium

  * New upstream version 0.12.0
  * Update d/copyright
    * Add gexiv2 mailing list to Upstream-Contact.
  * Update d/rules
    * Remove dbgsym migration code since migration is complete.
    * No longer need to specify meson build system since autotools build was
      removed.
    * Renamed enable-gtk-doc option to gtk_doc.
  * Update d/control
    * Bump debhelper level to 12.
    * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
      file.
    * Update Standards-Version to 4.4.1 No changes necessary.
    * Add Rules-Requires-Root: no
  * Update symbols
  * Dynamically generate d/libgexiv2-2.symbols.
    Upstream removed the script which kept C++ symbols from being exported due
    to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
    Mark all C++ symbols as optional since these aren't part of the API.
  * Use 'python3' instead of 'python' in autopkgtest.
    Thanks to Matthias Klose (Closes: #943447)
  * Install /usr/share/vala/vapi/gexiv2.deps.
    This file tells vala about dependencies.
  * Add patch Use-exiv2-version-0.25.patch.
    This modifies gexiv2 to use exiv2 version 0.25, the version currently in
    Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
    which is only currently available in Debian experimental.

 -- Jason Crain <jason at inspiresomeone.us>  Fri, 01 Nov 2019 02:59:35
-0600

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

-- 
Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1861985
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1762391 at bugs.launchpad.net  Wed Feb  5 15:39:09 2020
From: 1762391 at bugs.launchpad.net (Dariusz Gadomski)
Date: Wed, 05 Feb 2020 15:39:09 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158091714943.20144.6634192435156395871.malone@wampee.canonical.com>

I have just verified bionic. With version 237-3ubuntu10.34 after
replaying test case from the description I see the groups from
/etc/security/group.conf (dialout, users) added:

ubuntu at bionic:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Wed Feb  5 15:46:59 2020
From: 1762391 at bugs.launchpad.net (Dariusz Gadomski)
Date: Wed, 05 Feb 2020 15:46:59 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158091761933.30510.4283240273543739706.malone@gac.canonical.com>

With identical setup and testcase for eoan I have managed to
successfully verify the patch with version 242-7ubuntu3.3:

ubuntu at eoan:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare
ubuntu at eoan:~$ 


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

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1862040 at bugs.launchpad.net  Wed Feb  5 17:32:53 2020
From: 1862040 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 05 Feb 2020 17:32:53 -0000
Subject: [Bug 1862040] [NEW] please remove ghostwriter [ppc64el s390x] from
 focal
References: <158092297268.8645.6195743342814122345.malonedeb@chaenomeles.canonical.com>
Message-ID: <158092397414.8594.1333847399587523258.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Juhani Numminen (jsonic):

A recent upload changed the build-dependencies  (Dependency wait:
Missing build dependencies: qtwebengine5-dev) so the package now can't
be built on ppc64el and s390x. Please remove those binaries so that the
new version can migrate from focal-proposed to focal. This was already
done in Debian, https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=947931.

There are no rdeps.
$ reverse-depends -r focal src:ghostwriter
No reverse dependencies found
$ reverse-depends -r focal -b src:ghostwriter
No reverse dependencies found

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

** Affects: ghostwriter (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: update-excuse
-- 
 please remove ghostwriter [ppc64el s390x] from focal
https://bugs.launchpad.net/bugs/1862040
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1862000 at bugs.launchpad.net  Wed Feb  5 17:34:49 2020
From: 1862000 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 05 Feb 2020 17:34:49 -0000
Subject: [Bug 1862000] [NEW] please remove minizinc-ide [ppc64el s390x] from
 focal
References: <158089864472.26139.4964242197704608007.malonedeb@soybean.canonical.com>
Message-ID: <158092408940.9041.16584972493333272092.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Juhani Numminen (jsonic):

A recent upload changed the build-dependencies so the package now can't
be built on ppc64el and s390x. Please remove those binaries so that the
new version can migrate from focal-proposed to focal. This was already
done in Debian, https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=948686.

There are no rdeps.
$ reverse-depends -r focal src:minizinc-ide
No reverse dependencies found
$ reverse-depends -r focal -b src:minizinc-ide
No reverse dependencies found

** Affects: minizinc-ide (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: minizinc-ide (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: update-excuse
-- 
please remove minizinc-ide [ppc64el s390x] from focal
https://bugs.launchpad.net/bugs/1862000
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1861985 at bugs.launchpad.net  Wed Feb  5 17:27:02 2020
From: 1861985 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Wed, 05 Feb 2020 17:27:02 -0000
Subject: [Bug 1861985] Re: Sync gexiv2 0.12.0-2 (main) from Debian unstable
 (main)
References: <158089217406.26940.13814686307869276484.malonedeb@soybean.canonical.com>
Message-ID: <158092362335.18780.2822324348661992406.launchpad@gac.canonical.com>

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861985

Title:
  Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

Status in gexiv2 package in Ubuntu:
  New

Bug description:
  Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Use python2 instead of python in the autopkg test.

  Debian switched to use python3.

  Changelog entries since current focal version 0.10.9-1ubuntu1:

  gexiv2 (0.12.0-2) unstable; urgency=medium

    * Drop patch Use-exiv2-version-0.25.patch.
      Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
      can build against it. (Closes: #942519, #950169)
    * Update Standards-Version to 4.5.0.
      No changes necessary.

   -- Jason Crain <jason at inspiresomeone.us>  Sun, 02 Feb 2020 04:29:42
  -0700

  gexiv2 (0.12.0-1) unstable; urgency=medium

    * New upstream version 0.12.0
    * Update d/copyright
      * Add gexiv2 mailing list to Upstream-Contact.
    * Update d/rules
      * Remove dbgsym migration code since migration is complete.
      * No longer need to specify meson build system since autotools build was
        removed.
      * Renamed enable-gtk-doc option to gtk_doc.
    * Update d/control
      * Bump debhelper level to 12.
      * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
        file.
      * Update Standards-Version to 4.4.1 No changes necessary.
      * Add Rules-Requires-Root: no
    * Update symbols
    * Dynamically generate d/libgexiv2-2.symbols.
      Upstream removed the script which kept C++ symbols from being exported due
      to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
      Mark all C++ symbols as optional since these aren't part of the API.
    * Use 'python3' instead of 'python' in autopkgtest.
      Thanks to Matthias Klose (Closes: #943447)
    * Install /usr/share/vala/vapi/gexiv2.deps.
      This file tells vala about dependencies.
    * Add patch Use-exiv2-version-0.25.patch.
      This modifies gexiv2 to use exiv2 version 0.25, the version currently in
      Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
      which is only currently available in Debian experimental.

   -- Jason Crain <jason at inspiresomeone.us>  Fri, 01 Nov 2019 02:59:35
  -0600

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


From corey.bryant at canonical.com  Wed Feb  5 19:40:19 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Wed, 05 Feb 2020 19:40:19 -0000
Subject: [Bug 1826114] Please test proposed package
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158093161931.26675.14449544629475621877.malone@soybean.canonical.com>

Hello Eduardo, or anyone else affected,

Accepted horizon into stein-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:stein-proposed
  sudo apt-get update

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, and change the tag
from verification-stein-needed to verification-stein-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-stein-failed. In either case, details of your
testing will help us make a better decision.

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

** Changed in: cloud-archive/stein
       Status: Triaged => Fix Committed

** Tags added: verification-stein-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Triaged
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1861985 at bugs.launchpad.net  Thu Feb  6 02:46:47 2020
From: 1861985 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 06 Feb 2020 02:46:47 -0000
Subject: [Bug 1861985] Re: Sync gexiv2 0.12.0-2 (main) from Debian unstable
 (main)
References: <158089217406.26940.13814686307869276484.malonedeb@soybean.canonical.com>
Message-ID: <158095720881.19181.16438496248749477146.launchpad@gac.canonical.com>

** Changed in: gexiv2 (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861985

Title:
  Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

Status in gexiv2 package in Ubuntu:
  New

Bug description:
  Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Use python2 instead of python in the autopkg test.

  Debian switched to use python3.

  Changelog entries since current focal version 0.10.9-1ubuntu1:

  gexiv2 (0.12.0-2) unstable; urgency=medium

    * Drop patch Use-exiv2-version-0.25.patch.
      Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
      can build against it. (Closes: #942519, #950169)
    * Update Standards-Version to 4.5.0.
      No changes necessary.

   -- Jason Crain <jason at inspiresomeone.us>  Sun, 02 Feb 2020 04:29:42
  -0700

  gexiv2 (0.12.0-1) unstable; urgency=medium

    * New upstream version 0.12.0
    * Update d/copyright
      * Add gexiv2 mailing list to Upstream-Contact.
    * Update d/rules
      * Remove dbgsym migration code since migration is complete.
      * No longer need to specify meson build system since autotools build was
        removed.
      * Renamed enable-gtk-doc option to gtk_doc.
    * Update d/control
      * Bump debhelper level to 12.
      * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
        file.
      * Update Standards-Version to 4.4.1 No changes necessary.
      * Add Rules-Requires-Root: no
    * Update symbols
    * Dynamically generate d/libgexiv2-2.symbols.
      Upstream removed the script which kept C++ symbols from being exported due
      to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
      Mark all C++ symbols as optional since these aren't part of the API.
    * Use 'python3' instead of 'python' in autopkgtest.
      Thanks to Matthias Klose (Closes: #943447)
    * Install /usr/share/vala/vapi/gexiv2.deps.
      This file tells vala about dependencies.
    * Add patch Use-exiv2-version-0.25.patch.
      This modifies gexiv2 to use exiv2 version 0.25, the version currently in
      Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
      which is only currently available in Debian experimental.

   -- Jason Crain <jason at inspiresomeone.us>  Fri, 01 Nov 2019 02:59:35
  -0600

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


From 1862040 at bugs.launchpad.net  Thu Feb  6 02:54:53 2020
From: 1862040 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 06 Feb 2020 02:54:53 -0000
Subject: [Bug 1862040] Re: please remove ghostwriter [ppc64el s390x] from focal
References: <158092297268.8645.6195743342814122345.malonedeb@chaenomeles.canonical.com>
Message-ID: <158095769460.18863.10363385445415411670.launchpad@gac.canonical.com>

** Changed in: ghostwriter (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862040

Title:
   please remove ghostwriter [ppc64el s390x] from focal

Status in ghostwriter package in Ubuntu:
  New
Status in ghostwriter package in Debian:
  Unknown

Bug description:
  A recent upload changed the build-dependencies  (Dependency wait:
  Missing build dependencies: qtwebengine5-dev) so the package now can't
  be built on ppc64el and s390x. Please remove those binaries so that
  the new version can migrate from focal-proposed to focal. This was
  already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=947931.

  There are no rdeps.
  $ reverse-depends -r focal src:ghostwriter
  No reverse dependencies found
  $ reverse-depends -r focal -b src:ghostwriter
  No reverse dependencies found

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


From 1862000 at bugs.launchpad.net  Thu Feb  6 02:55:32 2020
From: 1862000 at bugs.launchpad.net (Mathew Hodson)
Date: Thu, 06 Feb 2020 02:55:32 -0000
Subject: [Bug 1862000] Re: please remove minizinc-ide [ppc64el s390x] from
 focal
References: <158089864472.26139.4964242197704608007.malonedeb@soybean.canonical.com>
Message-ID: <158095773375.8849.3959766207444091359.launchpad@chaenomeles.canonical.com>

** Changed in: minizinc-ide (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862000

Title:
  please remove minizinc-ide [ppc64el s390x] from focal

Status in minizinc-ide package in Ubuntu:
  New
Status in minizinc-ide package in Debian:
  Unknown

Bug description:
  A recent upload changed the build-dependencies so the package now
  can't be built on ppc64el and s390x. Please remove those binaries so
  that the new version can migrate from focal-proposed to focal. This
  was already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=948686.

  There are no rdeps.
  $ reverse-depends -r focal src:minizinc-ide
  No reverse dependencies found
  $ reverse-depends -r focal -b src:minizinc-ide
  No reverse dependencies found

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


From mail2hemanth.n at gmail.com  Thu Feb  6 04:53:29 2020
From: mail2hemanth.n at gmail.com (Hemanth Nakkina)
Date: Thu, 06 Feb 2020 04:53:29 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158096480922.19827.15450099960626586513.malone@wampee.canonical.com>

Verified stein on bionic. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series bionic and release stein.

Version of package tested -
python3-django-horizon/bionic-proposed,now 3:15.1.1-0ubuntu1.1~cloud1

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Triaged
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1862000 at bugs.launchpad.net  Thu Feb  6 09:33:13 2020
From: 1862000 at bugs.launchpad.net (Bug Watch Updater)
Date: Thu, 06 Feb 2020 09:33:13 -0000
Subject: [Bug 1862000] Re: please remove minizinc-ide [ppc64el s390x] from
 focal
References: <158089864472.26139.4964242197704608007.malonedeb@soybean.canonical.com>
Message-ID: <158098159410.10913.9800076485885985821.launchpad@loganberry.canonical.com>

** Changed in: minizinc-ide (Debian)
       Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862000

Title:
  please remove minizinc-ide [ppc64el s390x] from focal

Status in minizinc-ide package in Ubuntu:
  New
Status in minizinc-ide package in Debian:
  Fix Released

Bug description:
  A recent upload changed the build-dependencies so the package now
  can't be built on ppc64el and s390x. Please remove those binaries so
  that the new version can migrate from focal-proposed to focal. This
  was already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=948686.

  There are no rdeps.
  $ reverse-depends -r focal src:minizinc-ide
  No reverse dependencies found
  $ reverse-depends -r focal -b src:minizinc-ide
  No reverse dependencies found

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


From 1388808 at bugs.launchpad.net  Mon Feb  3 09:20:48 2020
From: 1388808 at bugs.launchpad.net (Cvs-commit)
Date: Mon, 03 Feb 2020 09:20:48 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556277.10913.16450073105385792209.launchpad@loganberry.canonical.com>

The master branch has been updated by Mike Fabian
<mfabian at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4267522f5e0309f7606a8d1da5d436a166a719e2

commit 4267522f5e0309f7606a8d1da5d436a166a719e2
Author: Jwtiyar Nariman <jwtiyar at gmail.com>
Date:   Mon Jan 13 10:06:06 2020 +0100

    Add new locale: ckb_IQ (Kurdish/Sorani spoken in Iraq) [BZ #9809]

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Mon Feb  3 09:20:53 2020
From: 1388808 at bugs.launchpad.net (Cvs-commit)
Date: Mon, 03 Feb 2020 09:20:53 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556300.10913.8045916251333321061.launchpad@loganberry.canonical.com>

The master branch has been updated by Mike Fabian
<mfabian at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ae199e7d6423ed3bd0c8669381966ca4c58f4f49

commit ae199e7d6423ed3bd0c8669381966ca4c58f4f49
Author: Mike FABIAN <mfabian at redhat.com>
Date:   Mon Jan 13 10:12:07 2020 +0100

    Fix ckb_IQ [BZ #9809]
    
    Add ckb_IQ to SUPPORTED file.
    Add ckb_IQ.UTF-8.in collation test file.
    Mention new ckb_IQ locale in NEWS.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From jwtiyar at gmail.com  Wed Feb  5 17:59:30 2020
From: jwtiyar at gmail.com (Jwtiyar Nariman)
Date: Wed, 05 Feb 2020 17:59:30 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556306.10913.16961280014443518658.launchpad@loganberry.canonical.com>

Hey dear Mike
I have downloaded new glibc 2.31 release but couldn't find ckb_iq localedata there? it was not planned to be there?

best regards.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From jwtiyar at gmail.com  Wed Feb  5 20:00:52 2020
From: jwtiyar at gmail.com (Jwtiyar Nariman)
Date: Wed, 05 Feb 2020 20:00:52 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556312.10913.13408890875735156683.launchpad@loganberry.canonical.com>

Created attachment 12261
fixed typo in wednesday name in kurdish

Just a typo now fixed, replaced U+0624 with U+0627 in the name of
Wednesday  in kurdish.

Best Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From jwtiyar at gmail.com  Wed Feb  5 20:28:53 2020
From: jwtiyar at gmail.com (Jwtiyar Nariman)
Date: Wed, 05 Feb 2020 20:28:53 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556317.10913.16792918952853215480.launchpad@loganberry.canonical.com>

Created attachment 12262
Added reorder-end command which missing

Adding reorder-end because couldn't compile it with this error exist.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Thu Feb  6 00:20:19 2020
From: 1388808 at bugs.launchpad.net (Maiku-fabian)
Date: Thu, 06 Feb 2020 00:20:19 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556325.10913.5285901560351706883.launchpad@loganberry.canonical.com>

(In reply to Jwtiyar Nariman from comment #78)
> Hey dear Mike
> I have downloaded new glibc 2.31 release but couldn't find ckb_iq localedata
> there? it was not planned to be there?

Yes, of course, that’s what I wrote in


https://sourceware.org/bugzilla/show_bug.cgi?id=9809#c75

2.31 was already in code freeze, I could push this only *after* 2.31 was
released. Therefore, the target milesstone of this bug is set to 2.32.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Thu Feb  6 00:26:23 2020
From: 1388808 at bugs.launchpad.net (Maiku-fabian)
Date: Thu, 06 Feb 2020 00:26:23 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158098556331.10913.1395592570142635029.launchpad@loganberry.canonical.com>

(In reply to Jwtiyar Nariman from comment #80)
> Created attachment 12262 [details]
> Added reorder-end command which missing
> 
> Adding reorder-end because couldn't compile it with this error exist.

Not needed anymore, I rewrote the whole LC_COLLATE section, see

https://sourceware.org/bugzilla/show_bug.cgi?id=9809#c49

If you want to do further changes, please look at what is in current
git master:

https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=localedata/locales/ckb_IQ;hb=refs/heads/master

And then sent a *patch* not the complete new file.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1859627 at bugs.launchpad.net  Thu Feb  6 12:05:09 2020
From: 1859627 at bugs.launchpad.net (Bug Watch Updater)
Date: Thu, 06 Feb 2020 12:05:09 -0000
Subject: [Bug 1859627] Re: Firefox 72 regression - HTML5 games do not load
References: <157901118020.3421.14884327325588278772.malonedeb@soybean.canonical.com>
Message-ID: <158099071142.20881.18323953631473971498.launchpad@loganberry.canonical.com>

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1603843.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2019-12-13T21:12:31+00:00 Botond-2 wrote:

**Steps to reproduce**

In the latest Firefox nightly, load https://cl.ly/5bfb0a3df1ba.
I tested with `mozregression --launch 2019-12-13`, to be sure that it's not an addon or other configuration issue.

**Expected results**

The page loads a video viewer.

**Actual results**

The page loads blank.

The devtools console displays the following errors:

```
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. 5bfb0a3df1ba
PixiJS 4.8.2 - WebGL - http://www.pixijs.com/ app.js:33385:24
Error: WebGL warning: linkProgram: Programs with more than 16 samplers are disallowed on Mesa drivers to avoid crashing. app.js:29437:8
TypeError: Argument 1 of WebGLRenderingContext.getProgramParameter is not an object.
app.js:29509:30
Pixi.js Error: Could not initialize shader. app.js:29442:17
gl.VALIDATE_STATUS false app.js:29443:17
gl.getError() 0 app.js:29444:17
Pixi.js Warning: gl.getProgramInfoLog() Programs with more than 16 samplers are disallowed on Mesa drivers to avoid crashing. app.js:29449:21
Error: [$injector:modulerr] Failed to instantiate module viewer due to:
[$injector:nomod] Module 'viewer' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.4.8/$injector/nomod?p0=viewer
i/<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:380
ve/</</<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9978
t at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9451
ve/</<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:9763
h/<@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:18624
o at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:806
h at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:18473
et at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:20162
s at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7507
ae at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7815
oe at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:37:7063
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:43:28030
u at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:22325
fireWith at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:23137
ready at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:24933
a at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:964
EventListener.handleEvent*J.ready.promise at https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:25132
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:29:25231
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:209
@https://d1xpqvu40ore1n.cloudfront.net/d15afa7e/vendor.js:19:214

http://errors.angularjs.org/1.4.8/$injector/modulerr?p0=view…u40ore1n.cloudfront.net%2Fd15afa7e%2Fvendor.js%3A19%3A214%0A vendor.js:9279:11
Loading failed for the <script> with source “https://www.google-analytics.com/gtm/js?id=GTM-K2FZ8RB&cid=1977579554.1576271468”.
```

Disabling Enhanced Tracking Protection does not resolve the problem.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/0

------------------------------------------------------------------------
On 2019-12-13T21:24:51+00:00 B-emilio wrote:

It works for me fwiw, but this computer uses the nvidia driver (not
mesa) so I think this is just fallout from that linkProgram issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/1

------------------------------------------------------------------------
On 2019-12-13T21:26:54+00:00 B-emilio wrote:

It seems like this is because of bug 777028, so probably given it is
that old we should try to either remove the workaround of add some sort
of version detection.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/2

------------------------------------------------------------------------
On 2019-12-13T21:27:07+00:00 Botond-2 wrote:

Ah, indeed. I overlooked that error and focused in on the second one,
leading me to believe it was a content blocking or site issue.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/3

------------------------------------------------------------------------
On 2019-12-13T21:27:32+00:00 B-emilio wrote:

Does `gfx.work-around-driver-bugs=false` fix it for you?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/4

------------------------------------------------------------------------
On 2019-12-13T21:28:55+00:00 Botond-2 wrote:

(In reply to Emilio Cobos Álvarez (:emilio) from comment #4)
> Does `gfx.work-around-driver-bugs=false` fix it for you?

It does indeed!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/5

------------------------------------------------------------------------
On 2019-12-13T21:34:03+00:00 B-emilio wrote:

Created attachment 9115866
Bug 1603843 - Remove work-around for 7+-year-old Mesa bug. r=jgilbert

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/6

------------------------------------------------------------------------
On 2019-12-13T22:28:26+00:00 Pulsebot wrote:

Pushed by ealvarez at mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b5ffe1a199b5
Remove work-around for 7+-year-old Mesa bug. r=jgilbert

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/7

------------------------------------------------------------------------
On 2019-12-14T09:44:30+00:00 Dluca-9 wrote:

https://hg.mozilla.org/mozilla-central/rev/b5ffe1a199b5

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/8

------------------------------------------------------------------------
On 2019-12-28T01:08:18+00:00 Jgilbert wrote:

*** Bug 1601682 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/9

------------------------------------------------------------------------
On 2020-02-03T12:32:36+00:00 Cristian-fogel wrote:

Managed to reproduce the issue only on Linux - Ubuntu 19.04 distribution with 73.0a1(2019-12-13). For machines with Windows(10)/macOS(10.15) the loading appeared in order.
Verified with 73.0b12 and 74.0a1(20200203085242) on Ubuntu 19.04.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859627/comments/19


** Changed in: firefox
       Status: Unknown => Fix Released

** Changed in: firefox
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1859627

Title:
  Firefox 72 regression - HTML5 games do not load

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu the following URL:

  https://game-launcher-
  lux.isoftbet.com/255/904612?lang=en&cur=EUR&mode=0&user=fun

  * loads fine with Chrome
  * loads fine with Firefox 71
  * shows only a black page with Firefox 72

  However Firefox 72 on Windows and OSX loads correctly.

  All the HTML5 games from this provider are affected.

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


From corey.bryant at canonical.com  Thu Feb  6 13:35:28 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Thu, 06 Feb 2020 13:35:28 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158099612871.16990.4663058995932142318.malone@wampee.canonical.com>

Thanks @Hemanth for the quick testing.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Triaged
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From olivier.tilloy at canonical.com  Thu Feb  6 13:52:18 2020
From: olivier.tilloy at canonical.com (Olivier Tilloy)
Date: Thu, 06 Feb 2020 13:52:18 -0000
Subject: [Bug 1859627] Re: Firefox 72 regression - HTML5 games do not load
References: <157901118020.3421.14884327325588278772.malonedeb@soybean.canonical.com>
Message-ID: <158099713929.18863.13961893837335275746.malone@gac.canonical.com>

Firefox 73.0+build1-0ubuntu1 is now in focal.

** Changed in: firefox (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1859627

Title:
  Firefox 72 regression - HTML5 games do not load

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu the following URL:

  https://game-launcher-
  lux.isoftbet.com/255/904612?lang=en&cur=EUR&mode=0&user=fun

  * loads fine with Chrome
  * loads fine with Firefox 71
  * shows only a black page with Firefox 72

  However Firefox 72 on Windows and OSX loads correctly.

  All the HTML5 games from this provider are affected.

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


From launchpad at surgut.co.uk  Thu Feb  6 15:20:46 2020
From: launchpad at surgut.co.uk (Dimitri John Ledkov)
Date: Thu, 06 Feb 2020 15:20:46 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158100244618.30590.9865088370922347025.malone@gac.canonical.com>

This SRU needs to be reuploaded, due to security update that trumped
this in progress SRU.

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

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

** Tags removed: verification-done verification-done-bionic verification-done-eoan
** Tags added: verification-failed verification-failed-bionic verification-failed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From steve.langasek at canonical.com  Thu Feb  6 21:42:31 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Thu, 06 Feb 2020 21:42:31 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158102535217.19789.13631278313503119131.malone@wampee.canonical.com>

Hello mtemp, or anyone else affected,

Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.7
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 and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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 Eoan)
       Status: In Progress => Fix Committed

** Tags removed: verification-failed verification-failed-eoan
** Tags added: verification-needed verification-needed-eoan

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

** Tags removed: verification-failed-bionic
** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From steve.langasek at canonical.com  Thu Feb  6 21:46:34 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Thu, 06 Feb 2020 21:46:34 -0000
Subject: [Bug 1762391] Please test proposed package
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158102559460.8432.11196388128490263531.malone@chaenomeles.canonical.com>

Hello mtemp, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.39 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 and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. 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.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Fri Feb  7 04:59:41 2020
From: 1762391 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 07 Feb 2020 04:59:41 -0000
Subject: [Bug 1762391] Autopkgtest regression report (systemd/237-3ubuntu10.39)
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <20200207045941.65137240284@snakefruit.canonical.com>

All autopkgtests for the newly accepted systemd (237-3ubuntu10.39) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

php7.2/7.2.24-0ubuntu0.18.04.2 (armhf)
gvfs/1.36.1-0ubuntu1.3.3 (ppc64el)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
systemd/237-3ubuntu10.39 (i386)
netplan.io/0.98-0ubuntu1~18.04.1 (i386, amd64)


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

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

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Fri Feb  7 07:06:28 2020
From: 1762391 at bugs.launchpad.net (Ubuntu SRU Bot)
Date: Fri, 07 Feb 2020 07:06:28 -0000
Subject: [Bug 1762391] Autopkgtest regression report (systemd/242-7ubuntu3.7)
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <20200207070628.CAC262406C0@snakefruit.canonical.com>

All autopkgtests for the newly accepted systemd (242-7ubuntu3.7) for eoan have finished running.
The following regressions have been reported in tests triggered by the package:

remctl/3.15-1build2 (armhf)
systemd-bootchart/unknown (armhf)
netplan.io/0.98-0ubuntu1 (amd64)
systemd/242-7ubuntu3.7 (ppc64el, s390x)
sks/unknown (armhf)
munin/2.0.49-3ubuntu1 (i386)


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

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

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 12:24:43 2020
From: 1861481 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 07 Feb 2020 12:24:43 -0000
Subject: [Bug 1861481] [NEW] language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158107828462.26066.7376935535061522645.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Gunnar Hjalmarsson (gunnarhj):

Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE
and Xubuntu), if a user selects a language in syslinux other than those
with an included langpack, the session is then untranslated.

For example, if one boots Ubuntu MATE 20.04 and selects Greek in
syslinux, he ends up with LANGUAGE=en in the session.

The chain of events is:
LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
`locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

I believe the correct fix would be for language-options to list el_GR on
live CDs (to merge the output of locale -a in its output).

Thanks!

** Affects: accountsservice (Ubuntu)
     Importance: High
         Status: Confirmed

** Affects: lightdm (Ubuntu)
     Importance: Medium
     Assignee: Gunnar Hjalmarsson (gunnarhj)
         Status: In Progress


** Tags: patch rls-ff-notfixing
-- 
language-options causes live CD sessions to be untranslated
https://bugs.launchpad.net/bugs/1861481
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1861481 at bugs.launchpad.net  Fri Feb  7 12:35:00 2020
From: 1861481 at bugs.launchpad.net (Alkis Georgopoulos)
Date: Fri, 07 Feb 2020 12:35:00 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158107890080.8474.5117792411182072665.malone@chaenomeles.canonical.com>

Btw, lightdm doesn't set LANGUAGE at all in Debian; it only sets LANG,
like GDM, and everything works fine.

Gunnar, do you see any issues with just completely dropping your 04_language_handling.patch?
Or at least this line there:

+        session_set_env (session, "LANGUAGE", language);

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 12:41:12 2020
From: 1861481 at bugs.launchpad.net (Alkis Georgopoulos)
Date: Fri, 07 Feb 2020 12:41:12 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158107927243.19372.10617602201438425860.malone@wampee.canonical.com>

I commented before I saw the previous reply; I'll reply to that now.

The "grep cow" approach breaks the LTSP package and other software that uses a COW root.
To check for casper, please `grep -w boot=casper /proc/cmdline` or something casper-specific.

In schools, we sometimes have students of various nationalities. They're
not frequent enough to install whole langpacks for them, but they are
frequent enough to configure locales for them (locale-gen).

I do not see any reason to keep the Ubuntu-specific
04_language_handling.patch, when we know that it's causing issues and we
do not know its benefit. Of course it's your call. :)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 14:49:21 2020
From: 1861481 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Fri, 07 Feb 2020 14:49:21 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158108696111.8849.2251572284661692936.malone@chaenomeles.canonical.com>

On 2020-02-07 13:41, Alkis Georgopoulos wrote:
> The "grep cow" approach breaks the LTSP package and other software
> that uses a COW root.

Do those packages cause the file system /cow, listed by the df command,
to be mounted? If yes, I wouldn't mind to modify the debdiff. Please let
me know.

> To check for casper, please `grep -w boot=casper /proc/cmdline` or
> something casper-specific.

Thanks for the tip!

> In schools, we sometimes have students of various nationalities.
> They're not frequent enough to install whole langpacks for them, but
> they are frequent enough to configure locales for them (locale-gen).

It's unclear to me why it's more difficult to install language packs
than generating locales separately.

In any case, I would prefer to consider this aspect to be beyond the
scope of this bug report.

> Of course it's your call.

Yes. :)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 16:10:35 2020
From: 1861481 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 07 Feb 2020 16:10:35 -0000
Subject: [Bug 1861481] [NEW] language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158109183602.26139.9800304950434135218.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Gunnar Hjalmarsson (gunnarhj):

Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE
and Xubuntu), if a user selects a language in syslinux other than those
with an included langpack, the session is then untranslated.

For example, if one boots Ubuntu MATE 20.04 and selects Greek in
syslinux, he ends up with LANGUAGE=en in the session.

The chain of events is:
LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
`locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

I believe the correct fix would be for language-options to list el_GR on
live CDs (to merge the output of locale -a in its output).

Thanks!

** Affects: accountsservice (Ubuntu)
     Importance: High
         Status: Confirmed

** Affects: lightdm (Ubuntu)
     Importance: Medium
     Assignee: Gunnar Hjalmarsson (gunnarhj)
         Status: In Progress


** Tags: patch rls-ff-notfixing
-- 
language-options causes live CD sessions to be untranslated
https://bugs.launchpad.net/bugs/1861481
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From tjaalton at ubuntu.com  Fri Feb  7 16:05:35 2020
From: tjaalton at ubuntu.com (Timo Aaltonen)
Date: Fri, 07 Feb 2020 16:05:35 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158109153607.19258.12376174944608628762.malone@gac.canonical.com>

Hello Eduardo, or anyone else affected,

Accepted horizon into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/horizon/3:16.0.0-0ubuntu1.1 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 and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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: horizon (Ubuntu Eoan)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 16:07:51 2020
From: 1861481 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Fri, 07 Feb 2020 16:07:51 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158109167153.19142.15682705547732791803.malone@gac.canonical.com>

On 2020-02-07 16:41, Alkis Georgopoulos wrote:
> I checked with 20.04 and it appears that recent Ubuntu live CDs
> don't have boot=casper anymore; they do still have
> initrd=/casper/initrd;

I also saw that /proc/cmdline contains BOOT_IMAGE=/casper/..., so the
approach would probably have worked with a minor modification.

> but anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
> before).

Ok, good, then I keep the debdiff for now, in the hope that some sponsor
will approve and upload it soon.

> Thank you for your work in this.

Thank you for reporting it. The current behavior in live sessions of the
flavors is indeed unintentional and unnecessary.

** No longer affects: accountsservice (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From 1862040 at bugs.launchpad.net  Fri Feb  7 16:42:36 2020
From: 1862040 at bugs.launchpad.net (Bug Watch Updater)
Date: Fri, 07 Feb 2020 16:42:36 -0000
Subject: [Bug 1862040] Re: please remove ghostwriter [ppc64el s390x] from focal
References: <158092297268.8645.6195743342814122345.malonedeb@chaenomeles.canonical.com>
Message-ID: <158109375738.1023.10181471252304146041.launchpad@loganberry.canonical.com>

** Changed in: ghostwriter (Debian)
       Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862040

Title:
   please remove ghostwriter [ppc64el s390x] from focal

Status in ghostwriter package in Ubuntu:
  New
Status in ghostwriter package in Debian:
  Fix Released

Bug description:
  A recent upload changed the build-dependencies  (Dependency wait:
  Missing build dependencies: qtwebengine5-dev) so the package now can't
  be built on ppc64el and s390x. Please remove those binaries so that
  the new version can migrate from focal-proposed to focal. This was
  already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=947931.

  There are no rdeps.
  $ reverse-depends -r focal src:ghostwriter
  No reverse dependencies found
  $ reverse-depends -r focal -b src:ghostwriter
  No reverse dependencies found

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


From 1861481 at bugs.launchpad.net  Fri Feb  7 19:46:03 2020
From: 1861481 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Fri, 07 Feb 2020 19:46:03 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158110476370.19711.5890786374161198432.malone@wampee.canonical.com>

Related pull request: https://github.com/canonical/lightdm/pull/111

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From mitya57 at gmail.com  Sat Feb  8 19:47:33 2020
From: mitya57 at gmail.com (Dmitry Shachnev)
Date: Sat, 08 Feb 2020 19:47:33 -0000
Subject: [Bug 1860845] Re: Sync python-concurrent.futures 3.3.0-3 (universe)
 from Debian unstable (main)
References: <157994016259.5059.1256274147338832036.malonedeb@wampee.canonical.com>
Message-ID: <158119125355.19221.10756833757433238234.malone@gac.canonical.com>

This bug was fixed in the package python-concurrent.futures - 3.3.0-3
Sponsored for Hans Joachim Desserud (hjd)

---------------
python-concurrent.futures (3.3.0-3) unstable; urgency=medium

  * Reupload as source-only upload.

 -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 11:47:15 +0100

python-concurrent.futures (3.3.0-2) unstable; urgency=medium

  * Bump Standards-Version to 4.4.1.
  * Call python2 in the build and the autopkg test command.
  * d/copyright: Bump my copyright year.

 -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 08:07:33 +0100

** Changed in: python-concurrent.futures (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1860845

Title:
  Sync python-concurrent.futures 3.3.0-3 (universe) from Debian unstable
  (main)

Status in python-concurrent.futures package in Ubuntu:
  Fix Released

Bug description:
  Please sync python-concurrent.futures 3.3.0-3 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Call python2 in the build and the autopkg test command.

  The Debian package now call python2 as well.

  Changelog entries since current focal version 3.3.0-1ubuntu2:

  python-concurrent.futures (3.3.0-3) unstable; urgency=medium

    * Reupload as source-only upload.

   -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 11:47:15 +0100

  python-concurrent.futures (3.3.0-2) unstable; urgency=medium

    * Bump Standards-Version to 4.4.1.
    * Call python2 in the build and the autopkg test command.
    * d/copyright: Bump my copyright year.

   -- Ondřej Nový <onovy at debian.org>  Mon, 20 Jan 2020 08:07:33 +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-concurrent.futures/+bug/1860845/+subscriptions


From mitya57 at gmail.com  Sat Feb  8 19:52:08 2020
From: mitya57 at gmail.com (Dmitry Shachnev)
Date: Sat, 08 Feb 2020 19:52:08 -0000
Subject: [Bug 1861985] Re: Sync gexiv2 0.12.0-2 (main) from Debian unstable
 (main)
References: <158089217406.26940.13814686307869276484.malonedeb@soybean.canonical.com>
Message-ID: <158119152907.26751.8955748458364479180.malone@soybean.canonical.com>

Already synced to -proposed by Matthias Klose.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861985

Title:
  Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

Status in gexiv2 package in Ubuntu:
  Fix Committed

Bug description:
  Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Use python2 instead of python in the autopkg test.

  Debian switched to use python3.

  Changelog entries since current focal version 0.10.9-1ubuntu1:

  gexiv2 (0.12.0-2) unstable; urgency=medium

    * Drop patch Use-exiv2-version-0.25.patch.
      Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
      can build against it. (Closes: #942519, #950169)
    * Update Standards-Version to 4.5.0.
      No changes necessary.

   -- Jason Crain <jason at inspiresomeone.us>  Sun, 02 Feb 2020 04:29:42
  -0700

  gexiv2 (0.12.0-1) unstable; urgency=medium

    * New upstream version 0.12.0
    * Update d/copyright
      * Add gexiv2 mailing list to Upstream-Contact.
    * Update d/rules
      * Remove dbgsym migration code since migration is complete.
      * No longer need to specify meson build system since autotools build was
        removed.
      * Renamed enable-gtk-doc option to gtk_doc.
    * Update d/control
      * Bump debhelper level to 12.
      * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
        file.
      * Update Standards-Version to 4.4.1 No changes necessary.
      * Add Rules-Requires-Root: no
    * Update symbols
    * Dynamically generate d/libgexiv2-2.symbols.
      Upstream removed the script which kept C++ symbols from being exported due
      to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
      Mark all C++ symbols as optional since these aren't part of the API.
    * Use 'python3' instead of 'python' in autopkgtest.
      Thanks to Matthias Klose (Closes: #943447)
    * Install /usr/share/vala/vapi/gexiv2.deps.
      This file tells vala about dependencies.
    * Add patch Use-exiv2-version-0.25.patch.
      This modifies gexiv2 to use exiv2 version 0.25, the version currently in
      Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
      which is only currently available in Debian experimental.

   -- Jason Crain <jason at inspiresomeone.us>  Fri, 01 Nov 2019 02:59:35
  -0600

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


From 1862504 at bugs.launchpad.net  Sun Feb  9 09:30:24 2020
From: 1862504 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 09 Feb 2020 09:30:24 -0000
Subject: [Bug 1862504] [NEW] Sync ruby-sinatra 2.0.8.1-1 (universe) from
 Debian unstable (main)
References: <158124062160.18780.10391812099747501702.malonedeb@gac.canonical.com>
Message-ID: <158124062482.19941.18066799600926462646.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Hans Joachim Desserud (hjd):

Please sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.

The self-build-dependencies are dropped in Debian as well. The package
built successfully locally on Focal.

Changelog entries since current focal version 2.0.5-4ubuntu1:

ruby-sinatra (2.0.8.1-1) unstable; urgency=medium

  * Team upload.
  * New upstream version 2.0.8.1.
  * Bump debhelper compatibility level to 12.
  * Bump Standards-Version to 4.5.0 (no changes needed).
  * debian/compat: Drop obsolete compat file, rely on debhelper-compat.
  * debian/control: Drop BD on ruby-rack-protection and ruby-sinatra-contrib.
    (Closes: #921201)
  * debian/control: Add puma as BD.
  * debian/copyright: Use HTTPS in link to copyright format specs.
  * debian/patches: Refresh for new release.

  [ Utkarsh Gupta ]
  * Add salsa-ci.yml

 -- Georg Faerber <georg at debian.org>  Fri, 07 Feb 2020 11:23:28 +0000

** Affects: ruby-sinatra (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1862504
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1862504 at bugs.launchpad.net  Sun Feb  9 09:30:21 2020
From: 1862504 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sun, 09 Feb 2020 09:30:21 -0000
Subject: [Bug 1862504] [NEW] Sync ruby-sinatra 2.0.8.1-1 (universe) from
 Debian unstable (main)
Message-ID: <158124062160.18780.10391812099747501702.malonedeb@gac.canonical.com>

Public bug reported:

Please sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.
  * Drop self-build-dependency on ruby-rack-protection
    and ruby-sinatra-contrib.

The self-build-dependencies are dropped in Debian as well. The package
built successfully locally on Focal.

Changelog entries since current focal version 2.0.5-4ubuntu1:

ruby-sinatra (2.0.8.1-1) unstable; urgency=medium

  * Team upload.
  * New upstream version 2.0.8.1.
  * Bump debhelper compatibility level to 12.
  * Bump Standards-Version to 4.5.0 (no changes needed).
  * debian/compat: Drop obsolete compat file, rely on debhelper-compat.
  * debian/control: Drop BD on ruby-rack-protection and ruby-sinatra-contrib.
    (Closes: #921201)
  * debian/control: Add puma as BD.
  * debian/copyright: Use HTTPS in link to copyright format specs.
  * debian/patches: Refresh for new release.

  [ Utkarsh Gupta ]
  * Add salsa-ci.yml

 -- Georg Faerber <georg at debian.org>  Fri, 07 Feb 2020 11:23:28 +0000

** Affects: ruby-sinatra (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: focal upgrade-software-version

** Tags added: focal upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862504

Title:
  Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)

Status in ruby-sinatra package in Ubuntu:
  New

Bug description:
  Please sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.

  The self-build-dependencies are dropped in Debian as well. The package
  built successfully locally on Focal.

  Changelog entries since current focal version 2.0.5-4ubuntu1:

  ruby-sinatra (2.0.8.1-1) unstable; urgency=medium

    * Team upload.
    * New upstream version 2.0.8.1.
    * Bump debhelper compatibility level to 12.
    * Bump Standards-Version to 4.5.0 (no changes needed).
    * debian/compat: Drop obsolete compat file, rely on debhelper-compat.
    * debian/control: Drop BD on ruby-rack-protection and ruby-sinatra-contrib.
      (Closes: #921201)
    * debian/control: Add puma as BD.
    * debian/copyright: Use HTTPS in link to copyright format specs.
    * debian/patches: Refresh for new release.

    [ Utkarsh Gupta ]
    * Add salsa-ci.yml

   -- Georg Faerber <georg at debian.org>  Fri, 07 Feb 2020 11:23:28 +0000

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


From 1862505 at bugs.launchpad.net  Sun Feb  9 09:53:14 2020
From: 1862505 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 09 Feb 2020 09:53:14 -0000
Subject: [Bug 1862505] [NEW] alsa-lib-1.2.1.2: should install the
 alsa-ucm-conf and alsa-topology-conf to focal image by default
References: <158124195825.19555.9087533038007685280.malonedeb@gac.canonical.com>
Message-ID: <158124199441.19441.10919622652596040007.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Hui Wang (hui.wang):

Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
alsa-lib, when we install the alsa-lib/libasound2, they are installed
together with alsa-lib. But from 1.2.1 they are separated from the alsa-
lib, and in the focal, we choose the 1.2.1.2 version, we should install
the ucm and topology too, otherwise those machines need ucm and topology
will not work anymore, users have to install these two packages
manually.

Two packages we need to put into the focal image are:
alsa-ucm-conf 1.2.1.2-2
alsa-topology-conf 1.2.1-2

** Affects: alsa-lib (Ubuntu)
     Importance: Undecided
         Status: New

-- 
alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
https://bugs.launchpad.net/bugs/1862505
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From hui.wang at canonical.com  Sun Feb  9 09:52:38 2020
From: hui.wang at canonical.com (Hui Wang)
Date: Sun, 09 Feb 2020 09:52:38 -0000
Subject: [Bug 1862505] [NEW] alsa-lib-1.2.1.2: should install the
 alsa-ucm-conf and alsa-topology-conf to focal image by default
Message-ID: <158124195825.19555.9087533038007685280.malonedeb@gac.canonical.com>

Public bug reported:

Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
alsa-lib, when we install the alsa-lib/libasound2, they are installed
together with alsa-lib. But from 1.2.1 they are separated from the alsa-
lib, and in the focal, we choose the 1.2.1.2 version, we should install
the ucm and topology too, otherwise those machines need ucm and topology
will not work anymore, users have to install these two packages
manually.

Two packages we need to put into the focal image are:
alsa-ucm-conf 1.2.1.2-2
alsa-topology-conf 1.2.1-2

** Affects: alsa-lib (Ubuntu)
     Importance: High
         Status: New

** Changed in: alsa-lib (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

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


From hui.wang at canonical.com  Sun Feb  9 09:55:02 2020
From: hui.wang at canonical.com (Hui Wang)
Date: Sun, 09 Feb 2020 09:55:02 -0000
Subject: [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf
 and alsa-topology-conf to focal image by default
References: <158124195825.19555.9087533038007685280.malonedeb@gac.canonical.com>
Message-ID: <158124210276.8965.10699323485963700516.malone@chaenomeles.canonical.com>

registered sponsor team

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

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


From 1862546 at bugs.launchpad.net  Sun Feb  9 22:24:33 2020
From: 1862546 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 09 Feb 2020 22:24:33 -0000
Subject: [Bug 1862546] [NEW] Sync qalculate-gtk 3.3.0-1 (universe) from Debian
 experimental (main) - Multiple bugs,
 instabilities and superseded data combined in outdated package of qalculate
References: <158128395478.26544.12064963500309063178.malonedeb@soybean.canonical.com>
Message-ID: <158128707370.19403.10715454907415284096.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Juhani Numminen (jsonic):

Please sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental
(main)

Qalculate in the Ubuntu repositories is severely outdated. Compared to
2.8.2 in the repos which is more than 2 years old, 9 major releases have
been published (https://qalculate.github.io/news.html). These include
many bugfixes and improvements which makes it recommendable to update
the packages for the next Ubuntu release.

I personally experienced multiple crashes, bugs and outdated data in the
repository version. Not to mention missing features like the improved
unit conversions. I cannot list them in detail anymore because I always
install the newer qalculate packages (3.3) from debian experimental at
any computer I am working. The official Ubuntu version has become
unusable for me.

Qalculate is by far the best calculator I found for linux and I think
this package deserves some care.

Changelog entries since current focal version 2.8.2-1

qalculate-gtk (3.3.0-1) experimental; urgency=medium

  * New upstream version
    - refresh patches
    - update libqalculate Build-Depends version
  * Switch to debhelper 12
    - remove debian/compat
    - use debhelper-compat (= 12) in debian/control
  * Move to machine-readable debian/copyright file
  * Remove old transitional package qalculate
    - remove now useless debian/qalculate-gtk.install
  * debian/rules:
    - remove no longer needed override on dh_auto_test
    - remove --with-libgnome=no, no longer used upstream
  * refresh debian/gitlab-ci.yml

 -- Vincent Legout <vlegout at debian.org>  Wed, 31 Jul 2019 06:45:33 +0200

** Affects: qalculate-gtk (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: request update
-- 
Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main) - Multiple bugs, instabilities and superseded data combined in outdated package of qalculate
https://bugs.launchpad.net/bugs/1862546
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From mail2hemanth.n at gmail.com  Mon Feb 10 04:16:38 2020
From: mail2hemanth.n at gmail.com (Hemanth Nakkina)
Date: Mon, 10 Feb 2020 04:16:38 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158130819816.14921.5850407698778660788.malone@wampee.canonical.com>

Verified on ubuntu series eoan. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series eoan.

Version of package tested -
python3-django-horizon/eoan-proposed,now 3:16.0.0-0ubuntu1.1

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1762391 at bugs.launchpad.net  Mon Feb 10 10:19:53 2020
From: 1762391 at bugs.launchpad.net (Dariusz Gadomski)
Date: Mon, 10 Feb 2020 10:19:53 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158132999387.19060.16391356491568514302.malone@gac.canonical.com>

I have repeated verification for eoan (242-7ubuntu3.7) with identical
results.

ubuntu at eoan:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin lxd sambashare

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Mon Feb 10 10:21:15 2020
From: 1762391 at bugs.launchpad.net (Dariusz Gadomski)
Date: Mon, 10 Feb 2020 10:21:15 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158133007560.18863.2636446459583400247.malone@gac.canonical.com>

Similarly for bionic using version 237-3ubuntu10.39 verification was
also successsful:

ubuntu at bionic:~$ groups
ubuntu adm dialout cdrom sudo dip plugdev users lpadmin sambashare vboxsf

** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From corey.bryant at canonical.com  Mon Feb 10 13:55:27 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Mon, 10 Feb 2020 13:55:27 -0000
Subject: [Bug 1826114] Please test proposed package
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158134292739.19517.12691260833934475476.malone@gac.canonical.com>

Hello Eduardo, or anyone else affected,

Accepted horizon into train-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.

Please help us by testing this new package. To enable the -proposed
repository:

  sudo add-apt-repository cloud-archive:train-proposed
  sudo apt-get update

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, and change the tag
from verification-train-needed to verification-train-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-train-failed. In either case, details of your
testing will help us make a better decision.

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

** Changed in: cloud-archive/train
       Status: Triaged => Fix Committed

** Tags added: verification-train-needed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1862546 at bugs.launchpad.net  Mon Feb 10 17:21:17 2020
From: 1862546 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Mon, 10 Feb 2020 17:21:17 -0000
Subject: [Bug 1862546] Re: Sync qalculate-gtk 3.3.0-1 (universe) from Debian
 experimental (main) - Multiple bugs,
 instabilities and superseded data combined in outdated package of qalculate
References: <158128395478.26544.12064963500309063178.malonedeb@soybean.canonical.com>
Message-ID: <158135527793.19479.9277987276189083816.launchpad@gac.canonical.com>

** Tags removed: request update
** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862546

Title:
  Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main)
  - Multiple bugs, instabilities and superseded data combined in
  outdated package of qalculate

Status in qalculate-gtk package in Ubuntu:
  New

Bug description:
  Please sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental
  (main)

  Qalculate in the Ubuntu repositories is severely outdated. Compared to
  2.8.2 in the repos which is more than 2 years old, 9 major releases
  have been published (https://qalculate.github.io/news.html). These
  include many bugfixes and improvements which makes it recommendable to
  update the packages for the next Ubuntu release.

  I personally experienced multiple crashes, bugs and outdated data in
  the repository version. Not to mention missing features like the
  improved unit conversions. I cannot list them in detail anymore
  because I always install the newer qalculate packages (3.3) from
  debian experimental at any computer I am working. The official Ubuntu
  version has become unusable for me.

  Qalculate is by far the best calculator I found for linux and I think
  this package deserves some care.

  Changelog entries since current focal version 2.8.2-1

  qalculate-gtk (3.3.0-1) experimental; urgency=medium

    * New upstream version
      - refresh patches
      - update libqalculate Build-Depends version
    * Switch to debhelper 12
      - remove debian/compat
      - use debhelper-compat (= 12) in debian/control
    * Move to machine-readable debian/copyright file
    * Remove old transitional package qalculate
      - remove now useless debian/qalculate-gtk.install
    * debian/rules:
      - remove no longer needed override on dh_auto_test
      - remove --with-libgnome=no, no longer used upstream
    * refresh debian/gitlab-ci.yml

   -- Vincent Legout <vlegout at debian.org>  Wed, 31 Jul 2019 06:45:33
  +0200

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


From mail2hemanth.n at gmail.com  Tue Feb 11 02:40:40 2020
From: mail2hemanth.n at gmail.com (Hemanth Nakkina)
Date: Tue, 11 Feb 2020 02:40:40 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158138884025.26675.14346330700105588902.malone@soybean.canonical.com>

Verified train on bionic. Project and User pages on Horizon dashboard displayed the corresponding project/user information for the selected domain.
Test environment is built using stsstack-bundle with series bionic and release train.

Version of package tested -
python3-django-horizon/bionic-proposed,now 3:16.0.0-0ubuntu1.1~cloud0

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From mail2hemanth.n at gmail.com  Tue Feb 11 02:47:55 2020
From: mail2hemanth.n at gmail.com (Hemanth Nakkina)
Date: Tue, 11 Feb 2020 02:47:55 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158138927582.19479.2474762594926536118.launchpad@gac.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1862504 at bugs.launchpad.net  Tue Feb 11 05:24:48 2020
From: 1862504 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 11 Feb 2020 05:24:48 -0000
Subject: [Bug 1862504] Re: Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian
 unstable (main)
References: <158124062160.18780.10391812099747501702.malonedeb@gac.canonical.com>
Message-ID: <158139868910.9176.18225514623347901266.launchpad@chaenomeles.canonical.com>

** Changed in: ruby-sinatra (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862504

Title:
  Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)

Status in ruby-sinatra package in Ubuntu:
  New

Bug description:
  Please sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.

  The self-build-dependencies are dropped in Debian as well. The package
  built successfully locally on Focal.

  Changelog entries since current focal version 2.0.5-4ubuntu1:

  ruby-sinatra (2.0.8.1-1) unstable; urgency=medium

    * Team upload.
    * New upstream version 2.0.8.1.
    * Bump debhelper compatibility level to 12.
    * Bump Standards-Version to 4.5.0 (no changes needed).
    * debian/compat: Drop obsolete compat file, rely on debhelper-compat.
    * debian/control: Drop BD on ruby-rack-protection and ruby-sinatra-contrib.
      (Closes: #921201)
    * debian/control: Add puma as BD.
    * debian/copyright: Use HTTPS in link to copyright format specs.
    * debian/patches: Refresh for new release.

    [ Utkarsh Gupta ]
    * Add salsa-ci.yml

   -- Georg Faerber <georg at debian.org>  Fri, 07 Feb 2020 11:23:28 +0000

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


From 1862546 at bugs.launchpad.net  Tue Feb 11 05:28:03 2020
From: 1862546 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 11 Feb 2020 05:28:03 -0000
Subject: [Bug 1862546] Re: Sync qalculate-gtk 3.3.0-1 (universe) from Debian
 experimental (main) - Multiple bugs,
 instabilities and superseded data combined in outdated package of qalculate
References: <158128395478.26544.12064963500309063178.malonedeb@soybean.canonical.com>
Message-ID: <158139888503.8594.12128822066781263157.launchpad@chaenomeles.canonical.com>

** Changed in: qalculate-gtk (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862546

Title:
  Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main)
  - Multiple bugs, instabilities and superseded data combined in
  outdated package of qalculate

Status in qalculate-gtk package in Ubuntu:
  New

Bug description:
  Please sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental
  (main)

  Qalculate in the Ubuntu repositories is severely outdated. Compared to
  2.8.2 in the repos which is more than 2 years old, 9 major releases
  have been published (https://qalculate.github.io/news.html). These
  include many bugfixes and improvements which makes it recommendable to
  update the packages for the next Ubuntu release.

  I personally experienced multiple crashes, bugs and outdated data in
  the repository version. Not to mention missing features like the
  improved unit conversions. I cannot list them in detail anymore
  because I always install the newer qalculate packages (3.3) from
  debian experimental at any computer I am working. The official Ubuntu
  version has become unusable for me.

  Qalculate is by far the best calculator I found for linux and I think
  this package deserves some care.

  Changelog entries since current focal version 2.8.2-1

  qalculate-gtk (3.3.0-1) experimental; urgency=medium

    * New upstream version
      - refresh patches
      - update libqalculate Build-Depends version
    * Switch to debhelper 12
      - remove debian/compat
      - use debhelper-compat (= 12) in debian/control
    * Move to machine-readable debian/copyright file
    * Remove old transitional package qalculate
      - remove now useless debian/qalculate-gtk.install
    * debian/rules:
      - remove no longer needed override on dh_auto_test
      - remove --with-libgnome=no, no longer used upstream
    * refresh debian/gitlab-ci.yml

   -- Vincent Legout <vlegout at debian.org>  Wed, 31 Jul 2019 06:45:33
  +0200

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


From 1781597 at bugs.launchpad.net  Tue Feb 11 15:30:17 2020
From: 1781597 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 11 Feb 2020 15:30:17 -0000
Subject: [Bug 1781597] [NEW] [SRU] WoWLAN settings are not supported
References: <153148883225.32480.9487567832871649218.malonedeb@wampee.canonical.com>
Message-ID: <158143501808.14455.7701968448128903531.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Alfonso Sanchez-Beato (alfonsosanchezbeato):

[Impact]

WoWLAN lets us wake up the system by sending wake packets over the wifi
connection. This is something requested by some OEM projects, for bionic
server images.

NM 1.12 supports configuring this feature, so this can be achieved by
backporting that support to 1.10 (bionic version). These are the MPs for
cosmic and bionic:

https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

[Test Case]

First, the wifi card must support WoWLAN. This can be checked by running

$ iw phy

and searching for "WoWLAN support:" in the output. If it is supported,
with the patch applied a connection configured with wowlan can be
created with:

$ sudo nmcli d wifi connect <ssid> password <password>
$ sudo nmcli c modify <ssid> 802-11-wireless.wake-on-wlan 8
$ sudo nmcli c down <ssid>
$ sudo nmcli c up <ssid>

We can check with 'iw' that WoWLAN is active for the connection:

$ iw phy phy0 wowlan show
WoWLAN is enabled:
 * wake up on magic packet

In this case we have configured the connection to wake up the system
when a 'magic' packet is received. We can then suspend the system with

$ sudo systemctl suspend

And we should be able to wake the system from another device with the
command

$ sudo etherwake -i <wifi_iface> <destination_MAC_address>

[Regression Potential]

Although the patch is not especially small, it is a backport of changes
that have been merged upstream, with very little modifications to make
it compile in 1.10. It is also a rather isolated feature that should not
conflict with existing ones. The feature will be activated only if
configured from the command line, so the risk of regressions should be
small. Note also that the patch will be removed as soon as Ubuntu moves
to NM 1.12.

** Affects: network-manager (Ubuntu)
     Importance: Wishlist
         Status: Fix Released

** Affects: network-manager (Ubuntu Bionic)
     Importance: Wishlist
     Assignee: Sebastien Bacher (seb128)
         Status: Triaged

** Affects: network-manager (Ubuntu Cosmic)
     Importance: Wishlist
         Status: Fix Released


** Tags: verification-done-cosmic
-- 
[SRU] WoWLAN settings are not supported
https://bugs.launchpad.net/bugs/1781597
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From alfonso.sanchez-beato at canonical.com  Tue Feb 11 15:31:30 2020
From: alfonso.sanchez-beato at canonical.com (Alfonso Sanchez-Beato)
Date: Tue, 11 Feb 2020 15:31:30 -0000
Subject: [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
References: <153148883225.32480.9487567832871649218.malonedeb@wampee.canonical.com>
Message-ID: <158143509088.14802.11860689527789315899.malone@gac.canonical.com>

It looks like the VPN related SRU that was previous to this one was
reverted. Could we land this into bionic?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1781597

Title:
  [SRU] WoWLAN settings are not supported

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Triaged
Status in network-manager source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  WoWLAN lets us wake up the system by sending wake packets over the
  wifi connection. This is something requested by some OEM projects, for
  bionic server images.

  NM 1.12 supports configuring this feature, so this can be achieved by
  backporting that support to 1.10 (bionic version). These are the MPs
  for cosmic and bionic:

  https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468
  https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465

  [Test Case]

  First, the wifi card must support WoWLAN. This can be checked by
  running

  $ iw phy

  and searching for "WoWLAN support:" in the output. If it is supported,
  with the patch applied a connection configured with wowlan can be
  created with:

  $ sudo nmcli d wifi connect <ssid> password <password>
  $ sudo nmcli c modify <ssid> 802-11-wireless.wake-on-wlan 8
  $ sudo nmcli c down <ssid>
  $ sudo nmcli c up <ssid>

  We can check with 'iw' that WoWLAN is active for the connection:

  $ iw phy phy0 wowlan show
  WoWLAN is enabled:
   * wake up on magic packet

  In this case we have configured the connection to wake up the system
  when a 'magic' packet is received. We can then suspend the system with

  $ sudo systemctl suspend

  And we should be able to wake the system from another device with the
  command

  $ sudo etherwake -i <wifi_iface> <destination_MAC_address>

  [Regression Potential]

  Although the patch is not especially small, it is a backport of
  changes that have been merged upstream, with very little modifications
  to make it compile in 1.10. It is also a rather isolated feature that
  should not conflict with existing ones. The feature will be activated
  only if configured from the command line, so the risk of regressions
  should be small. Note also that the patch will be removed as soon as
  Ubuntu moves to NM 1.12.

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


From juhaninumminen0 at gmail.com  Tue Feb 11 17:22:47 2020
From: juhaninumminen0 at gmail.com (Juhani Numminen)
Date: Tue, 11 Feb 2020 17:22:47 -0000
Subject: [Bug 1862546] Re: Sync qalculate-gtk 3.3.0-1 (universe) from Debian
 experimental (main) - Multiple bugs,
 instabilities and superseded data combined in outdated package of qalculate
References: <158128395478.26544.12064963500309063178.malonedeb@soybean.canonical.com>
Message-ID: <158144176730.28848.17483846622560982943.malone@chaenomeles.canonical.com>

I did not notice this before, but qalculate 3.3.0-1 requires
libqalculate 3.3.0-1 which would start a library transition:
https://release.debian.org/transitions/html/auto-libqalculate.html

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862546

Title:
  Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main)
  - Multiple bugs, instabilities and superseded data combined in
  outdated package of qalculate

Status in qalculate-gtk package in Ubuntu:
  New

Bug description:
  Please sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental
  (main)

  Qalculate in the Ubuntu repositories is severely outdated. Compared to
  2.8.2 in the repos which is more than 2 years old, 9 major releases
  have been published (https://qalculate.github.io/news.html). These
  include many bugfixes and improvements which makes it recommendable to
  update the packages for the next Ubuntu release.

  I personally experienced multiple crashes, bugs and outdated data in
  the repository version. Not to mention missing features like the
  improved unit conversions. I cannot list them in detail anymore
  because I always install the newer qalculate packages (3.3) from
  debian experimental at any computer I am working. The official Ubuntu
  version has become unusable for me.

  Qalculate is by far the best calculator I found for linux and I think
  this package deserves some care.

  Changelog entries since current focal version 2.8.2-1

  qalculate-gtk (3.3.0-1) experimental; urgency=medium

    * New upstream version
      - refresh patches
      - update libqalculate Build-Depends version
    * Switch to debhelper 12
      - remove debian/compat
      - use debhelper-compat (= 12) in debian/control
    * Move to machine-readable debian/copyright file
    * Remove old transitional package qalculate
      - remove now useless debian/qalculate-gtk.install
    * debian/rules:
      - remove no longer needed override on dh_auto_test
      - remove --with-libgnome=no, no longer used upstream
    * refresh debian/gitlab-ci.yml

   -- Vincent Legout <vlegout at debian.org>  Wed, 31 Jul 2019 06:45:33
  +0200

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


From alberto.donato at canonical.com  Tue Feb 11 13:21:28 2020
From: alberto.donato at canonical.com (Alberto Donato)
Date: Tue, 11 Feb 2020 13:21:28 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:transitional-snap into
 ubuntu/+source/maas:ubuntu/devel
Message-ID: <158142728281.25279.11263162067260070041.launchpad@ackee.canonical.com>

Alberto Donato has proposed merging ~ack/ubuntu/+source/maas:transitional-snap into ubuntu/+source/maas:ubuntu/devel.

Commit message:
Transitional package to install and migrate to snap

Requested reviews:
  Ubuntu Sponsors Team (ubuntu-sponsors)

For more details, see:
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/378890

This branch drops MAAS source code from the snap, and provides a transitional package which installs the snap and migrates existing deb-based installs to it.
-- 
The attached diff has been truncated due to its size.
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:transitional-snap into ubuntu/+source/maas:ubuntu/devel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 524288 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-sponsors/attachments/20200211/06bf3a5d/attachment-0001.diff>

From julian.klode at canonical.com  Tue Feb 11 15:23:00 2020
From: julian.klode at canonical.com (Julian Andres Klode)
Date: Tue, 11 Feb 2020 15:23:00 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:transitional-snap into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158142728281.25279.11263162067260070041.launchpad@ackee.canonical.com>
Message-ID: <158143457965.18873.10448538844306431177.codereview@wampee.canonical.com>

I thinl the Breaks should be unversioned Conflicts for all packages that are not transitional packages (keeping the Replaces, though), and the remaininng Breaks+Replaces should be (<< 1:0.1~).

Conflicts are needed for update-manager to correctly replace the packages.
-- 
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/378890
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:transitional-snap into ubuntu/+source/maas:ubuntu/devel.


From cyrus.lien at canonical.com  Wed Feb 12 03:36:25 2020
From: cyrus.lien at canonical.com (Cyrus Lien)
Date: Wed, 12 Feb 2020 03:36:25 -0000
Subject: [Bug 1852691] Re: Disable touchscreen gesture 
References: <157379962715.22614.13579309380461920631.malonedeb@chaenomeles.canonical.com>
Message-ID: <158147858636.24383.14226359057743573395.launchpad@gac.canonical.com>

** Also affects: oem-priority
   Importance: Undecided
       Status: New

** Changed in: oem-priority
     Assignee: (unassigned) => Cyrus Lien (cyruslien)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
       Status: New => Confirmed

** Tags added: oem-priority originate-from-1814058 somerville

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1852691

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens.

  Config file that instructs driver to disable in-driver gestures for touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
  	Identifier "Wacom touchscreen gestures"
  	MatchDriver "wacom"
  	MatchIsTouchscreen "true"
  	Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger zoom/rotate and 3+ finger gestures) work as desired. Also check /var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead libinput driver.

  [Regression Potential]
  Low

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1852691/+subscriptions


From cyrus.lien at canonical.com  Wed Feb 12 03:49:47 2020
From: cyrus.lien at canonical.com (Cyrus Lien)
Date: Wed, 12 Feb 2020 03:49:47 -0000
Subject: [Bug 1852691] Re: Disable touchscreen gesture 
References: <157379962715.22614.13579309380461920631.malonedeb@chaenomeles.canonical.com>
Message-ID: <158147938793.24383.7014448491142421461.launchpad@gac.canonical.com>

** Also affects: oem-priority/bionic
   Importance: Undecided
       Status: New

** No longer affects: oem-priority/bionic

** Also affects: oem-priority/bionic
   Importance: Undecided
       Status: New

** No longer affects: oem-priority

** No longer affects: oem-priority/bionic

** Also affects: oem-priority
   Importance: Undecided
       Status: New

** Changed in: oem-priority
       Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
     Assignee: (unassigned) => Cyrus Lien (cyruslien)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1852691

Title:
  Disable touchscreen gesture

Status in OEM Priority Project:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  [Impact]
  Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens.

  Config file that instructs driver to disable in-driver gestures for touchscreens:
  # Prevent the Wacom driver from providing its own gestures for
  # touchscreen devices.
  #
  Section "InputClass"
  	Identifier "Wacom touchscreen gestures"
  	MatchDriver "wacom"
  	MatchIsTouchscreen "true"
  	Option "Gesture" "off"
  EndSection

  
  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom package
  2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger zoom/rotate and 3+ finger gestures) work as desired. Also check /var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead libinput driver.

  [Regression Potential]
  Low

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1852691/+subscriptions


From martin.babutzka at online.de  Wed Feb 12 10:58:00 2020
From: martin.babutzka at online.de (Martin Babutzka)
Date: Wed, 12 Feb 2020 10:58:00 -0000
Subject: [Bug 1862546] Re: Sync qalculate-gtk 3.3.0-1 (universe) from Debian
 experimental (main) - Multiple bugs,
 instabilities and superseded data combined in outdated package of qalculate
References: <158128395478.26544.12064963500309063178.malonedeb@soybean.canonical.com>
Message-ID: <158150508009.29590.14821291794491219720.malone@chaenomeles.canonical.com>

Yeah, surely an update of of the qalculate-gtk package requires an
update of some dependencies. I am just surprised how effortful all of
this sounds while a lot of other Ubuntu packages I know and use are just
updated with every release.

I think thats the point of major releases to get an up-to-date version
of the software packages (and not only security fixes). Controversial to
the (modified) bug description I would also look forward to an update to
an actual up-to-date version (latest version is 3.7). But I take what I
get... and if it is not updated I will continue installing Debian
packages.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862546

Title:
  Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main)
  - Multiple bugs, instabilities and superseded data combined in
  outdated package of qalculate

Status in qalculate-gtk package in Ubuntu:
  New

Bug description:
  Please sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental
  (main)

  Qalculate in the Ubuntu repositories is severely outdated. Compared to
  2.8.2 in the repos which is more than 2 years old, 9 major releases
  have been published (https://qalculate.github.io/news.html). These
  include many bugfixes and improvements which makes it recommendable to
  update the packages for the next Ubuntu release.

  I personally experienced multiple crashes, bugs and outdated data in
  the repository version. Not to mention missing features like the
  improved unit conversions. I cannot list them in detail anymore
  because I always install the newer qalculate packages (3.3) from
  debian experimental at any computer I am working. The official Ubuntu
  version has become unusable for me.

  Qalculate is by far the best calculator I found for linux and I think
  this package deserves some care.

  Changelog entries since current focal version 2.8.2-1

  qalculate-gtk (3.3.0-1) experimental; urgency=medium

    * New upstream version
      - refresh patches
      - update libqalculate Build-Depends version
    * Switch to debhelper 12
      - remove debian/compat
      - use debhelper-compat (= 12) in debian/control
    * Move to machine-readable debian/copyright file
    * Remove old transitional package qalculate
      - remove now useless debian/qalculate-gtk.install
    * debian/rules:
      - remove no longer needed override on dh_auto_test
      - remove --with-libgnome=no, no longer used upstream
    * refresh debian/gitlab-ci.yml

   -- Vincent Legout <vlegout at debian.org>  Wed, 31 Jul 2019 06:45:33
  +0200

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


From 1862926 at bugs.launchpad.net  Wed Feb 12 11:28:59 2020
From: 1862926 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 12 Feb 2020 11:28:59 -0000
Subject: [Bug 1862926] [NEW] Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158150693983.29344.8342177289773808820.launchpad@chaenomeles.canonical.com>

You have been subscribed to a public bug by Till Kamppeter (till-kamppeter):

In Focal we are still a bit old-fashioned regarding scanning. We are
still at the ancient SANE 1.0.27! That is really INSANE.

Current version is 1.0.29 and it contains a very important new feature
which will make hundreds (thousands?) of new scanners work with Ubuntu.
This new feature is Apple AirScan support as a client. I have introduced
a lot of nice printing stuff to support AirPrint, making lots of
printers (practically all modern network printers) working, and all the
multi-function devices under these (printer and scanner in one) do
AirScan, so all these scanner will work with SANE 1.0.29 (if yours does
not, it is a bug in SANE, please report).

The AirScan support is provided by the new "escl" backend. supporting
the eSCL protocol AirPrint is based on. The protocol uses HTTP and XML,
so this works out-of-the-box if your printer is connected to the
network, if it is connected via USB it work via IPP-over-USB using the
ippusbxd package.

Changes list from upstream:

- Backends
   + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
   + adds support for 23 new scanner models via existing backends
   + significantly changes genesys and pixma backends
   + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
   + fixes all compiler warnings on Debian 10 (#120)
   + fixes portability issues for uClibc-ng and MacOS builds
   + adds support to record and replay USB I/O traffic
   + adds timestamps to debug logs

debdiff attached.

** Affects: sane-backends (Ubuntu)
     Importance: High
         Status: New

-- 
Request for update: SANE 1.0.29
https://bugs.launchpad.net/bugs/1862926
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1311056 at bugs.launchpad.net  Wed Feb 12 15:25:05 2020
From: 1311056 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 12 Feb 2020 15:25:05 -0000
Subject: [Bug 1311056] [NEW] [SRU] apt-add-repository adds duplicate
 commented/disabled source lines
References: <20140422110006.18725.38464.malonedeb@chaenomeles.canonical.com>
Message-ID: <158152110611.14835.6677359729183870802.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Dave Jones (waveform):

Impact
======

Under most circumstances, the impact is minimal (a few extra redundant
comment lines in apt sources. However, if users are automating source
removal / addition on a machine (as in comment 11), there is the
potential to wind up with an excessively large (and thus slow to parse)
apt sources configuration.

Test packages for the supported releases are available from the
following PPA:

https://launchpad.net/~waveform/+archive/ubuntu/python-apt

Built from the source which can be found in the following branches:

https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/sru-dupe-ppa-xenial

https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/sru-dupe-ppa-bionic

https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/sru-dupe-ppa-eoan

Test Case
=========

* sudo add-apt-repository -y ppa:deadsnakes/ppa
* cat /etc/apt/sources.list.d/deadsnakes*.list
* Note the presence of one uncommented "deb" line, and one commented "deb-src" line
* sudo add-apt-repository -y ppa:deadsnakes/ppa
* cat /etc/apt/sources.list.d/deadsnakes*.list
* Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated
* sudo add-apt-repository ppa:waveform/python-apt
* sudo apt upgrade  # update python-apt to fixed version
* sudo add-apt-repository -y ppa:deadsnakes/ppa
* cat /etc/apt/sources.list.d/deadsnakes*.list
* Note there has been no further duplication of the commented "deb-src" line

Regression Potential
====================

Minimal; test cases have been added to cover the duplication case, and
to cover the enabling of sources (which was not covered by existing
tests, but was part of the code altered to fix the duplication case),
and insertion of sources at a position (again, not covered by existing
tests but modified as part of the fix). The test case has been used
successfully on all targeted releases (xenial, bionic, and eoan).

Original Description
====================

Trusty Tahr 14.04

0 root at osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
# deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
0 root at osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop
gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
0 root at osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
# deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
# deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
0 root at osprey:/etc/apt/sources.list.d#

That deb-src line should have stayed commented out, and not been
duplicated. (Commented deb lines should of course be uncommented, as
already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
apt/+bug/1042916 .)

** Affects: python-apt (Ubuntu)
     Importance: High
         Status: Fix Released

** Affects: python-apt (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: python-apt (Ubuntu Bionic)
     Importance: Undecided
         Status: New

** Affects: python-apt (Ubuntu Eoan)
     Importance: Undecided
         Status: New


** Tags: bot-comment canonical-bootstack id-5d65087107d6ae450d988462 patch
-- 
[SRU] apt-add-repository adds duplicate commented/disabled source lines
https://bugs.launchpad.net/bugs/1311056
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1862936 at bugs.launchpad.net  Wed Feb 12 16:21:59 2020
From: 1862936 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 12 Feb 2020 16:21:59 -0000
Subject: [Bug 1862936] [NEW] Error: Rotation feature not supported by the
 kernel tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158152451973.15520.8590046022473054832.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

$ dpkg -l | grep ltt
ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu Focal Fossa (development branch)
Release:        20.04
Codename:       focal

How to reproduce:

$ sudo lttng create foobar
Session foobar created.
Traces will be output to /root/lttng-traces/foobar-20200212-123955

$ sudo lttng enable-event --kernel sched_switch
Kernel event sched_switch created in channel channel0

$ sudo lttng start
Tracing started for session foobar

$ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
100000+0 records in
100000+0 records out
409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
100000+0 records in
100000+0 records out
409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

$ sudo lttng stop
Waiting for data availability.
Tracing stopped for session foobar

$ sudo lttng destroy
Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

** Affects: ltt-control (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: ltt-control (Ubuntu Focal)
     Importance: Undecided
         Status: New


** Tags: patch
-- 
Error: Rotation feature not supported by the kernel tracer.
https://bugs.launchpad.net/bugs/1862936
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1862936 at bugs.launchpad.net  Wed Feb 12 16:22:00 2020
From: 1862936 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Wed, 12 Feb 2020 16:22:00 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158152452049.14798.2031985070738364829.malone@soybean.canonical.com>

The attachment "ltt-control_2.11.1-1ubuntu1.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  New
Status in ltt-control source package in Focal:
  New

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1862926 at bugs.launchpad.net  Wed Feb 12 17:05:55 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Wed, 12 Feb 2020 17:05:55 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158152715594.14619.13276301847705617781.malone@soybean.canonical.com>

Also reported to Debian as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=951213

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  New

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1388808 at bugs.launchpad.net  Thu Feb 13 03:54:59 2020
From: 1388808 at bugs.launchpad.net (Bug Watch Updater)
Date: Thu, 13 Feb 2020 03:54:59 -0000
Subject: [Bug 1388808] Re: Request for new language packages for Kurdish
 Sorani (ckb)
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158156610092.2793.5279285903356521922.launchpad@loganberry.canonical.com>

** Changed in: glibc
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  Fix Released
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Tue Feb 11 09:16:54 2020
From: 1388808 at bugs.launchpad.net (Maiku-fabian)
Date: Tue, 11 Feb 2020 09:16:54 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158156610602.2793.16781658788557637533.launchpad@loganberry.canonical.com>

(In reply to Jwtiyar Nariman from comment #79)
> Created attachment 12261 [details]
> fixed typo in wednesday name in kurdish
> 
> Just a typo now fixed, replaced U+0624 with U+0627 in the name of Wednesday 
> in kurdish.
> 
> Best Regards.

$ git diff 
diff --git a/localedata/locales/ckb_IQ b/localedata/locales/ckb_IQ
index a18ff69cb7..238c381edf 100644
--- a/localedata/locales/ckb_IQ
+++ b/localedata/locales/ckb_IQ
@@ -124,7 +124,7 @@ abday "<U0634><U06D5><U0645>";/
 day "<U06CC><U06D5><U0643><U0634><U06D5><U0645><U0645><U06D5>";/
     "<U062F><U0648><U0648><U0634><U06D5><U0645><U0645><U06D5>";/
     "<U0633><U06CE><U0634><U06D5><U0645><U0645><U06D5>";/
-    "<U0686><U0648><U0624><U0631><U0634><U06D5><U0645><U0645><U06D5>";/
+    "<U0686><U0648><U0627><U0631><U0634><U06D5><U0645><U0645><U06D5>";/
     "<U067E><U06CE><U0646><U062C><U0634><U06D5><U0645><U0645><U06D5>";/
     "<U0647><U06D5><U06CC><U0646><U06CC>";/
     "<U0634><U06D5><U0645><U0645><U06D5>"
lines 1-13/13 (END)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  Fix Released
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Tue Feb 11 11:17:24 2020
From: 1388808 at bugs.launchpad.net (Cvs-commit)
Date: Tue, 11 Feb 2020 11:17:24 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158156610616.2793.12839079718947424545.launchpad@loganberry.canonical.com>

The master branch has been updated by Mike Fabian
<mfabian at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=eb948facd894e66429e2e170043b7d36fe445a8d

commit eb948facd894e66429e2e170043b7d36fe445a8d
Author: Mike FABIAN <mfabian at redhat.com>
Date:   Tue Feb 11 10:17:12 2020 +0100

    Fix typo in the name for Wednesday in Kurdish [BZ #9809]

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  Fix Released
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1388808 at bugs.launchpad.net  Tue Feb 11 11:17:59 2020
From: 1388808 at bugs.launchpad.net (Maiku-fabian)
Date: Tue, 11 Feb 2020 11:17:59 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158156610622.2793.12694580328237369107.launchpad@loganberry.canonical.com>

Fixed in current master.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  Fix Released
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From jwtiyar at gmail.com  Wed Feb 12 17:56:49 2020
From: jwtiyar at gmail.com (Jwtiyar Nariman)
Date: Wed, 12 Feb 2020 17:56:49 -0000
Subject: [Bug 1388808] 
References: <20141103122305.25448.11414.malonedeb@gac.canonical.com>
Message-ID: <158156610628.2793.5856962911851335522.launchpad@loganberry.canonical.com>

(In reply to Mike FABIAN from comment #85)
> Fixed in current master.

Thank you dear mike for everything, your help really appreciated.

Best Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1388808

Title:
  Request for new language packages for Kurdish Sorani (ckb)

Status in GLibC:
  Fix Released
Status in langpack-o-matic:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  Related Bug: 266975
  The Sorani dialect team wished to add its locale to the library so as to get finaly Kurdish-sorani version.
   Kurdish Sorani is a Right-to-Left script language like Arabic spoken mainly in Kurdistan region of Iran and Iraq.

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


From 1861985 at bugs.launchpad.net  Thu Feb 13 17:01:21 2020
From: 1861985 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Thu, 13 Feb 2020 17:01:21 -0000
Subject: [Bug 1861985] Re: Sync gexiv2 0.12.0-2 (main) from Debian unstable
 (main)
References: <158089217406.26940.13814686307869276484.malonedeb@soybean.canonical.com>
Message-ID: <158161328244.29423.5544401046412478510.malone@chaenomeles.canonical.com>

And now in the Ubuntu Focal archives
(https://bugs.launchpad.net/ubuntu/+source/gexiv2/0.12.0-2)

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861985

Title:
  Sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

Status in gexiv2 package in Ubuntu:
  Fix Released

Bug description:
  Please sync gexiv2 0.12.0-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Use python2 instead of python in the autopkg test.

  Debian switched to use python3.

  Changelog entries since current focal version 0.10.9-1ubuntu1:

  gexiv2 (0.12.0-2) unstable; urgency=medium

    * Drop patch Use-exiv2-version-0.25.patch.
      Exiv2 version 0.27 is now in Debian unstable. Drop this patch so gexiv2
      can build against it. (Closes: #942519, #950169)
    * Update Standards-Version to 4.5.0.
      No changes necessary.

   -- Jason Crain <jason at inspiresomeone.us>  Sun, 02 Feb 2020 04:29:42
  -0700

  gexiv2 (0.12.0-1) unstable; urgency=medium

    * New upstream version 0.12.0
    * Update d/copyright
      * Add gexiv2 mailing list to Upstream-Contact.
    * Update d/rules
      * Remove dbgsym migration code since migration is complete.
      * No longer need to specify meson build system since autotools build was
        removed.
      * Renamed enable-gtk-doc option to gtk_doc.
    * Update d/control
      * Bump debhelper level to 12.
      * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
        file.
      * Update Standards-Version to 4.4.1 No changes necessary.
      * Add Rules-Requires-Root: no
    * Update symbols
    * Dynamically generate d/libgexiv2-2.symbols.
      Upstream removed the script which kept C++ symbols from being exported due
      to regressions on OpenBSD (https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
      Mark all C++ symbols as optional since these aren't part of the API.
    * Use 'python3' instead of 'python' in autopkgtest.
      Thanks to Matthias Klose (Closes: #943447)
    * Install /usr/share/vala/vapi/gexiv2.deps.
      This file tells vala about dependencies.
    * Add patch Use-exiv2-version-0.25.patch.
      This modifies gexiv2 to use exiv2 version 0.25, the version currently in
      Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
      which is only currently available in Debian experimental.

   -- Jason Crain <jason at inspiresomeone.us>  Fri, 01 Nov 2019 02:59:35
  -0600

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


From 1862504 at bugs.launchpad.net  Sat Feb 15 08:52:24 2020
From: 1862504 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Sat, 15 Feb 2020 08:52:24 -0000
Subject: [Bug 1862504] Re: Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian
 unstable (main)
References: <158124062160.18780.10391812099747501702.malonedeb@gac.canonical.com>
Message-ID: <158175674441.24299.13561657245856435991.malone@gac.canonical.com>

Already synced.

** Changed in: ruby-sinatra (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862504

Title:
  Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)

Status in ruby-sinatra package in Ubuntu:
  Fix Released

Bug description:
  Please sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.
    * Drop self-build-dependency on ruby-rack-protection
      and ruby-sinatra-contrib.

  The self-build-dependencies are dropped in Debian as well. The package
  built successfully locally on Focal.

  Changelog entries since current focal version 2.0.5-4ubuntu1:

  ruby-sinatra (2.0.8.1-1) unstable; urgency=medium

    * Team upload.
    * New upstream version 2.0.8.1.
    * Bump debhelper compatibility level to 12.
    * Bump Standards-Version to 4.5.0 (no changes needed).
    * debian/compat: Drop obsolete compat file, rely on debhelper-compat.
    * debian/control: Drop BD on ruby-rack-protection and ruby-sinatra-contrib.
      (Closes: #921201)
    * debian/control: Add puma as BD.
    * debian/copyright: Use HTTPS in link to copyright format specs.
    * debian/patches: Refresh for new release.

    [ Utkarsh Gupta ]
    * Add salsa-ci.yml

   -- Georg Faerber <georg at debian.org>  Fri, 07 Feb 2020 11:23:28 +0000

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


From 1861481 at bugs.launchpad.net  Sun Feb 16 01:01:58 2020
From: 1861481 at bugs.launchpad.net (Martin Wimpress)
Date: Sun, 16 Feb 2020 01:01:58 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158181491995.15520.4844127670174013325.launchpad@soybean.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From 1862926 at bugs.launchpad.net  Sun Feb 16 08:14:03 2020
From: 1862926 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 16 Feb 2020 08:14:03 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158184084445.28809.17612111995447631066.malone@chaenomeles.canonical.com>

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

** Changed in: sane-backends (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From a33ypool3kbhd at t-online.de  Sun Feb 16 08:19:28 2020
From: a33ypool3kbhd at t-online.de (nmaxx)
Date: Sun, 16 Feb 2020 08:19:28 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158184116874.30733.353591163229937899.malone@wampee.canonical.com>

I agreee, this absolutely belongs in 20.04, and a SRU for 18.04 would
probably be warranted as well, assuming this is possible (not sure about
compatibility with clients built against 1.0.27).

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1862505 at bugs.launchpad.net  Sun Feb 16 20:52:38 2020
From: 1862505 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 16 Feb 2020 20:52:38 -0000
Subject: [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf
 and alsa-topology-conf to focal image by default
References: <158124195825.19555.9087533038007685280.malonedeb@gac.canonical.com>
Message-ID: <158188635895.28723.14450711899477529065.launchpad@chaenomeles.canonical.com>

** Tags added: packaging

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

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


From 1862936 at bugs.launchpad.net  Sun Feb 16 21:07:22 2020
From: 1862936 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 16 Feb 2020 21:07:22 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158188724425.15247.15133430280564753599.launchpad@soybean.canonical.com>

** Changed in: ltt-control (Ubuntu Focal)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  New
Status in ltt-control source package in Focal:
  New

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1862926 at bugs.launchpad.net  Sun Feb 16 21:01:56 2020
From: 1862926 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 16 Feb 2020 21:01:56 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158188691718.30858.2085821695734587266.launchpad@wampee.canonical.com>

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

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1311056 at bugs.launchpad.net  Sun Feb 16 21:14:41 2020
From: 1311056 at bugs.launchpad.net (Mathew Hodson)
Date: Sun, 16 Feb 2020 21:14:41 -0000
Subject: [Bug 1311056] Re: [SRU] apt-add-repository adds duplicate
 commented/disabled source lines
References: <20140422110006.18725.38464.malonedeb@chaenomeles.canonical.com>
Message-ID: <158188768380.30733.14347464988826097289.launchpad@wampee.canonical.com>

** Changed in: python-apt (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: python-apt (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu Bionic)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1311056

Title:
  [SRU] apt-add-repository adds duplicate commented/disabled source
  lines

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Eoan:
  New

Bug description:
  Impact
  ======

  Under most circumstances, the impact is minimal (a few extra redundant
  comment lines in apt sources. However, if users are automating source
  removal / addition on a machine (as in comment 11), there is the
  potential to wind up with an excessively large (and thus slow to
  parse) apt sources configuration.

  Test packages for the supported releases are available from the
  following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/python-apt

  Built from the source which can be found in the following branches:

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-xenial

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-bionic

  https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
  /python-apt/+ref/sru-dupe-ppa-eoan

  Test Case
  =========

  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the presence of one uncommented "deb" line, and one commented "deb-src" line
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated
  * sudo add-apt-repository ppa:waveform/python-apt
  * sudo apt upgrade  # update python-apt to fixed version
  * sudo add-apt-repository -y ppa:deadsnakes/ppa
  * cat /etc/apt/sources.list.d/deadsnakes*.list
  * Note there has been no further duplication of the commented "deb-src" line

  Regression Potential
  ====================

  Minimal; test cases have been added to cover the duplication case, and
  to cover the enabling of sources (which was not covered by existing
  tests, but was part of the code altered to fix the duplication case),
  and insertion of sources at a position (again, not covered by existing
  tests but modified as part of the fix). The test case has been used
  successfully on all targeted releases (xenial, bionic, and eoan).

  Original Description
  ====================

  Trusty Tahr 14.04

  0 root at osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root at osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:               imported: 1  (RSA: 1)
  OK
  0 root at osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root at osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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


From 1863528 at bugs.launchpad.net  Sun Feb 16 23:54:50 2020
From: 1863528 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sun, 16 Feb 2020 23:54:50 -0000
Subject: [Bug 1863528] [NEW] Sync matplotlib 3.1.2-2 (universe) from Debian
 unstable (main)
References: <158189728808.31087.4861820836825944724.malonedeb@wampee.canonical.com>
Message-ID: <158189729026.24684.4988241219622040489.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Amr Ibrahim (amribrahim1987):

Please sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Disabled the wxagg autopkg test, python3-wxgtk3.0 is removed.
  * Error out on failing builds.
The wxagg test is dropped.

Changelog entries since current focal version 3.1.2-1ubuntu2:

matplotlib (3.1.2-2) unstable; urgency=medium

  * debian/tests/{control, wxagg}
    - drop wxagg test; Closes: #950799

 -- Sandro Tosi <morph at debian.org>  Wed, 12 Feb 2020 21:55:19 -0500

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

-- 
Sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1863528
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1826114 at bugs.launchpad.net  Mon Feb 17 09:20:53 2020
From: 1826114 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 17 Feb 2020 09:20:53 -0000
Subject: [Bug 1826114] Update Released
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158193125355.30187.6314786842922551704.malone@wampee.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Committed
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1762391 at bugs.launchpad.net  Mon Feb 17 09:25:35 2020
From: 1762391 at bugs.launchpad.net (=?utf-8?q?=C5=81ukasz_Zemczak?=)
Date: Mon, 17 Feb 2020 09:25:35 -0000
Subject: [Bug 1762391] Update Released
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158193153511.15569.6866993945431637789.malone@soybean.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1826114 at bugs.launchpad.net  Mon Feb 17 09:30:54 2020
From: 1826114 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 17 Feb 2020 09:30:54 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158193189574.22448.13168197464553258921.malone@ackee.canonical.com>

This bug was fixed in the package horizon - 3:16.0.0-0ubuntu1.1

---------------
horizon (3:16.0.0-0ubuntu1.1) eoan; urgency=medium

  [ Corey Bryant ]
  * d/gbp.conf: Create stable/train branch.

  [ Hemanth Nakkina ]
  * Fix users/projects list when domain context is changed (LP: #1826114)
    - d/p/fix-user-list-for-different-domain.patch.
  * GUI hangs on creation of project in User creation form (LP: #1826114)
    - d/p/gui-hangs-on-project-creation.patch.

 -- Hemanth Nakkina <hemanth.nakkina at canonical.com>  Tue, 07 Jan 2020
12:02:44 +0530

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Committed
Status in Ubuntu Cloud Archive train series:
  Fix Committed
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Released
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1762391 at bugs.launchpad.net  Mon Feb 17 09:35:40 2020
From: 1762391 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 17 Feb 2020 09:35:40 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158193214434.22452.6667524119178953604.malone@ackee.canonical.com>

This bug was fixed in the package systemd - 242-7ubuntu3.7

---------------
systemd (242-7ubuntu3.7) eoan; urgency=medium

  [ Dariusz Gadomski ]
  * d/p/lp1762391/0001-Call-getgroups-to-know-size-of-supplementary-groups-.patch,
    d/p/lp1762391/0002-user-util-tweak-to-in_gid.patch,
    d/p/lp1762391/0003-user-util-Add-helper-functions-for-gid-lists-operati.patch,
    d/p/lp1762391/0004-execute-Restore-call-to-pam_setcred.patch,
    d/p/lp1762391/0005-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch,
    d/p/lp1762391/0006-test-Add-tests-for-gid-list-ops.patch,
    d/p/lp1762391/0007-execute-add-const-to-array-parameters-where-possible.patch,
    d/p/lp1762391/0008-execute-allow-pam_setcred-to-fail-ignore-errors.patch:
    - Restore call to pam_setcred (LP: #1762391)

  * d/p/lp1846232/0001-network-honor-MTUBytes-setting.patch,
    d/p/lp1846232/0002-network-bump-MTU-bytes-only-when-MTUByte-is-not-set.patch:
    - do not always bump MTU with additional 4bytes (LP: #1846232)
  * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
    - set ipv6 mtu at correct time (LP: #1671951)
  * d/p/lp1845909/0001-network-rename-linux_configure_after_setting_mtu-to-linux.patch,
    d/p/lp1845909/0002-network-add-link-setting_genmode-flag.patch,
    d/p/lp1845909/0003-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch,
    d/p/lp1845909/0004-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch,
    d/p/lp1845909/0005-network-drop-IPv6LL-address-when-LinkLocalAddressing.patch:
    - drop foreign config and raise interface after setting genmode
      (LP: #1845909)
  * d/t/storage: without scsi_debug, skip test (LP: #1847816)

 -- Dan Streetman <ddstreet at canonical.com>  Thu, 06 Feb 2020 09:45:57
-0500

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1762391 at bugs.launchpad.net  Mon Feb 17 10:07:54 2020
From: 1762391 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 17 Feb 2020 10:07:54 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158193407862.22448.944647830365270115.malone@ackee.canonical.com>

This bug was fixed in the package systemd - 237-3ubuntu10.39

---------------
systemd (237-3ubuntu10.39) bionic; urgency=medium

  [ Dariusz Gadomski ]
  * d/p/lp1762391/0001-Call-getgroups-to-know-size-of-supplementary-groups-.patch,
    d/p/lp1762391/0002-user-util-tweak-to-in_gid.patch,
    d/p/lp1762391/0003-user-util-Add-helper-functions-for-gid-lists-operati.patch,
    d/p/lp1762391/0004-execute-Restore-call-to-pam_setcred.patch,
    d/p/lp1762391/0005-execute-Detect-groups-added-by-PAM-and-merge-them-wi.patch,
    d/p/lp1762391/0006-test-Add-tests-for-gid-list-ops.patch,
    d/p/lp1762391/0007-execute-add-const-to-array-parameters-where-possible.patch,
    d/p/lp1762391/0008-execute-allow-pam_setcred-to-fail-ignore-errors.patch:
    - Restore call to pam_setcred (LP: #1762391)

  [ Ioanna Alifieraki ]
  * d/p/lp1860548/0001-Revert-Replace-use-of-snprintf-with-xsprintf.patch,
    d/p/lp1860548/0002-job-truncate-unit-description.patch:
    - use snprintf instead of xsprintf (LP: #1860548)

  [ Dan Streetman ]
  * d/p/lp1833193-network-update-address-when-static-address-was-alrea.patch:
    - Update lft when static addr was cfg by dhcp (LP: #1833193)
  * d/p/lp1849261/0001-core-when-we-can-t-enqueue-OnFailure-job-show-full-e.patch,
    d/p/lp1849261/0002-core-don-t-trigger-OnFailure-deps-when-a-unit-is-goi.patch:
    - Only trigger OnFailure= if Restart= is not in effect (LP: #1849261)
  * d/p/lp1671951-network-set-ipv6-mtu-after-link-up-or-device-mtu-cha.patch:
    - set ipv6 mtu at correct time (LP: #1671951)
  * d/p/lp1845909/0001-networkd-honour-LinkLocalAddressing.patch,
    d/p/lp1845909/0002-networkd-fix-link_up-12505.patch,
    d/p/lp1845909/0003-network-do-not-send-ipv6-token-to-kernel.patch,
    d/p/lp1845909/0004-network-rename-linux_configure_after_setting_mtu-to-linux.patch,
    d/p/lp1845909/0005-network-add-link-setting_genmode-flag.patch,
    d/p/lp1845909/0006-network-if-ipv6ll-is-disabled-enumerate-tentative-ipv6-ad.patch,
    d/p/lp1845909/0007-network-drop-foreign-config-after-addr_gen_mode-has-been-.patch,
    d/p/lp1845909/0008-network-drop-IPv6LL-address-when-LinkLocalAddressing.patch:
    - if LinkLocalAddressing=no prevent creation of ipv6ll (LP: #1845909)
  * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch:
    - enable ipv6 when needed (LP: #1859862)
  * d/p/lp1836695-networkd-Add-back-static-routes-after-DHCPv4-lease-e.patch:
    - (re)add static routes after getting dhcp4 addr (LP: #1836695)
  * d/t/storage:
    - fix buggy test (LP: #1831459)
    - without scsi_debug, skip test (LP: #1847816)

 -- Dan Streetman <ddstreet at canonical.com>  Thu, 06 Feb 2020 10:00:49
-0500

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1861481 at bugs.launchpad.net  Mon Feb 17 11:02:01 2020
From: 1861481 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Mon, 17 Feb 2020 11:02:01 -0000
Subject: [Bug 1861481] Re: language-options causes live CD sessions to be
 untranslated
References: <158045930546.20144.11411485442504660059.malonedeb@wampee.canonical.com>
Message-ID: <158193732184.28809.11438234493917220188.malone@chaenomeles.canonical.com>

I tested the live session with today's daily build of Ubuntu MATE and
can confirm that LANGUAGE is no longer set. Thus translated strings in
universe packages are always displayed in the selected language.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861481

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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


From mjeanson at gmail.com  Mon Feb 17 17:14:00 2020
From: mjeanson at gmail.com (Michael Jeanson)
Date: Mon, 17 Feb 2020 17:14:00 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158195964010.30821.3995153476006076279.malone@wampee.canonical.com>

This is fixed in 2.11.2 which was synced in focal.

https://launchpad.net/ubuntu/+source/ltt-control/2.11.2-1

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  New
Status in ltt-control source package in Focal:
  New

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1863528 at bugs.launchpad.net  Mon Feb 17 17:47:13 2020
From: 1863528 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Mon, 17 Feb 2020 17:47:13 -0000
Subject: [Bug 1863528] Re: Sync matplotlib 3.1.2-2 (universe) from Debian
 unstable (main)
References: <158189728808.31087.4861820836825944724.malonedeb@wampee.canonical.com>
Message-ID: <158196163408.24554.17601318963092040018.launchpad@gac.canonical.com>

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863528

Title:
  Sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

Status in matplotlib package in Ubuntu:
  New

Bug description:
  Please sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Disabled the wxagg autopkg test, python3-wxgtk3.0 is removed.
    * Error out on failing builds.
  The wxagg test is dropped.

  Changelog entries since current focal version 3.1.2-1ubuntu2:

  matplotlib (3.1.2-2) unstable; urgency=medium

    * debian/tests/{control, wxagg}
      - drop wxagg test; Closes: #950799

   -- Sandro Tosi <morph at debian.org>  Wed, 12 Feb 2020 21:55:19 -0500

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


From 1863609 at bugs.launchpad.net  Mon Feb 17 21:15:20 2020
From: 1863609 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Mon, 17 Feb 2020 21:15:20 -0000
Subject: [Bug 1863609] [NEW]  [SRU] Update to vala 0.40.19 in bionic 
References: <158194336745.14972.1692101375000515098.malonedeb@soybean.canonical.com>
Message-ID: <158197412087.15247.13008724073057388073.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Rico Tzschichholz (ricotz):

The 0.40.x series is maintained as LTS release and will receive further
bug fix releases in the future. See https://wiki.gnome.org/Projects/Vala

Previous 0.40.17 SRU https://bugs.launchpad.net/bugs/1803136

Falls under the standing GNOME SRU execption
https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

Upstream changes since 0.40.17:

Vala 0.40.19
============
 * Various improvements and bug fixes:
   - codegen:
    + Fix precondition in creation method of structs
    + Don't set implemenation of interface property to its own [#891]
    + Use result value of assignment rather than its computation [#895]
    + Cast instance parameter in member-initializer for base-properties [#899]
    + Skip StructRegisterFunction for boolean/integer/floating types [#901]
    + Handle different type-symbols in visit_base_access() [#901]
   - vala:
    + VoidType is actually compatible with itself [#878]
    + Keep formal_target_type on transform of method-call/object-creation [#835]
    + Add a basic parameter check for [Print] methods
    + Don't ignore inner errors in Block and acknowledge them further
    + Don't report further errors if MemberInitializer.check() failed
    + Improve error message for unsupported inner types and declarations
    + Don't allow "va_list" as return-type or type of fields [#884]
    + Check before accessing "name" of parent_symbol which might be null
    + Allow to override base interface properties explicitly
    + Fix base-access check for compact classes
    + Improve detection of recursive struct declarations [#902]
    + Inline allocated arrays require length or initializer [#903]
    + Don't ignore errors in Parameter and acknowledge them further
  - parser: Implicit "main" method of main-block is public and static
  - genie: Fix parser's inner state when a struct is declared after a class
  - girparser: Apply explicitly given ctype metadata attributes on callables
  - testrunner: Invalid tests and therefore expected failures must return 1

 * Bindings:
  - glib-2.0: Add to_string() for GLib.PollFd and GLib.Pid
  - gtk+-3.0: Update to 3.24.13+3822ac74

Vala 0.40.18
============
 * Various improvements and bug fixes:
  - codegen:
    + Use G_TYPE_INSTANCE_GET_INTERFACE to get vtable for base-access
    + Fix setting of generic-type properties for gobject chain up [#654702]
    + Make type-parameter properties readable [#190]
    + Fix vfunc signature of delegate-typed property in interface
    + Fix support of dynamic DBus methods
  - vala:
    + Warn when passing arrays to typeof(), except for "string[]" [#868]
    + Don't falsely resolve binary-expression to bool [#869]
    + Do not allow += for arrays with fixed length
    + Array with fixed length don't require explicit instantiation [#720]
    + Infer array length of inline allocated arrays for fields [#644046]
    + Do not allow to .resize() on arrays with fixed length
    + Do not allow to change .length of arrays with fixed length
    + Improve error message for arrays as type arguments
    + Improve error reporting for invalid interface prerequisites [#437]
    + Write value of constants/enums in fast-vapi if constant only [#461]
    + Don't require constant initializer in fast-vapi [#461]
    + Restore DestroysInstance behaviour for non-compact classes [#873]
    + Report error for async creation expression without yield
  - parser: `owned` is not allowed on Constants
  - girparser: Detect and replace "-" in parameter names
  - girwriter: Add readable="0"/private="1" attribute to type-specific fields
  - gidl:
    + Calculate size correctly, avoid use-after-free
    + Avoid use of uninitialized "markup" warning
    + Ignore flags like -mfpmath=sse, -msse or -msse2
  - valadoc:
    + libvaladoc: Fix parameter and property ownership declarations
    + Fix ownership declarations of Constants
  - pkg-config:
    + vala: Add missing gmodule-2.0 to Requires.private of pkg-config file
    + libvaladoc: Move gmodule-2.0 to Requires.private of pkg-config file

 * Bindings:
  - glib-2.0: Guard against passing null source to GLib.Memory.copy()
  - gtk+-3.0: Skip _MountOperationHandler* symbols
  - libusb-1.0: Don't depend on glib-2.0
  - libusb-1.0: Remove unused private "malloc" binding
  - linux: Add memfd_create(2)
  - posix: Bind some essential memory allocation functions

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

-- 
 [SRU] Update to vala 0.40.19 in bionic 
https://bugs.launchpad.net/bugs/1863609
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From corey.bryant at canonical.com  Tue Feb 18 13:29:48 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Tue, 18 Feb 2020 13:29:48 -0000
Subject: [Bug 1852599] Re: Cannot delete TLS Terminated listener if container
 has been deleted in barbican
References: <157374528757.6370.13569343319335325172.malonedeb@gac.canonical.com>
Message-ID: <158203258824.25031.15020041497889975858.malone@gac.canonical.com>

This is fix released via:
https://bugs.launchpad.net/cloud-archive/+bug/1858933
https://bugs.launchpad.net/cloud-archive/+bug/1858934

** Changed in: octavia (Ubuntu Eoan)
       Status: Triaged => Fix Released

** Changed in: cloud-archive/train
       Status: Triaged => Fix Released

** Changed in: cloud-archive/stein
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1852599

Title:
  Cannot delete TLS Terminated listener if container has been deleted in
  barbican

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in octavia:
  Fix Released
Status in octavia package in Ubuntu:
  Fix Released
Status in octavia source package in Disco:
  Won't Fix
Status in octavia source package in Eoan:
  Fix Released
Status in octavia source package in Focal:
  Fix Released

Bug description:
  [Impact]
  octavia lb's listener can't be delete when there is no secret container which is already deleted.

  
  [Test Case]

  1. deploy and setup octavia env
  2. run below script
  - https://pastebin.ubuntu.com/p/xPWKnPqFhw/
  3. check if there is listener-1 is there or not ( in this case, there is )

  [Regression]

  This fix needs restarting octavia services. so downtime will be there
  shortly.

  [Others]

  After patching with https://review.opendev.org/#/c/691693/,

  I Was able to see the same error , but listener is actually deleted.

  
  [Original Description]

  There seems to be a fault condition in amphora builds that can lead to
  not being able to delete a failed loadbalancer/listener.

  If the barbican container for a tls terminated endpoint listener is
  deleted before the listener/amphora is deleted, the query to update to
  the listener's tls certificates fails during the delete_pools flow.

  It exhibits the following in the client:

  DELETE call to None for https://octavia.mysite:9876/v2.0/lbaas/listeners/4f46a6a3-a756-41b2-9148-c060bf28e621 used request id req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf
  Request returned failure status: 500
  Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 29, in wrapper
      response = func(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 204, in listener_delete
      response = self.delete(url)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 185, in delete
      return self._request('DELETE', url, **params)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 141, in _request
      return session.request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/osc_lib/session.py", line 40, in request
      resp = super(TimingSession, self).request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/keystoneauth1/session.py", line 737, in request
      raise exceptions.from_response(resp, method, url)
  keystoneauth1.exceptions.http.InternalServerError: Internal Server Error (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand
      result = cmd.run(parsed_args)
    File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run
      return super(Command, self).run(parsed_args)
    File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run
      return_code = self.take_action(parsed_args) or 0
    File "/usr/lib/python3/dist-packages/octaviaclient/osc/v2/listener.py", line 152, in take_action
      listener_id=listener_id)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 38, in wrapper
      request_id=e.request_id)
  octaviaclient.api.v2.octavia.OctaviaClientException: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  clean_up DeleteListener: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 29, in wrapper
      response = func(*args, **kwargs)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 204, in listener_delete
      response = self.delete(url)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 185, in delete
      return self._request('DELETE', url, **params)
    File "/usr/lib/python3/dist-packages/osc_lib/api/api.py", line 141, in _request
      return session.request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/osc_lib/session.py", line 40, in request
      resp = super(TimingSession, self).request(url, method, **kwargs)
    File "/usr/lib/python3/dist-packages/keystoneauth1/session.py", line 737, in request
      raise exceptions.from_response(resp, method, url)
  keystoneauth1.exceptions.http.InternalServerError: Internal Server Error (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 134, in run
      ret_val = super(OpenStackShell, self).run(argv)
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 279, in run
      result = self.run_subcommand(remainder)
    File "/usr/lib/python3/dist-packages/osc_lib/shell.py", line 169, in run_subcommand
      ret_value = super(OpenStackShell, self).run_subcommand(argv)
    File "/usr/lib/python3/dist-packages/cliff/app.py", line 400, in run_subcommand
      result = cmd.run(parsed_args)
    File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 41, in run
      return super(Command, self).run(parsed_args)
    File "/usr/lib/python3/dist-packages/cliff/command.py", line 184, in run
      return_code = self.take_action(parsed_args) or 0
    File "/usr/lib/python3/dist-packages/octaviaclient/osc/v2/listener.py", line 152, in take_action
      listener_id=listener_id)
    File "/usr/lib/python3/dist-packages/octaviaclient/api/v2/octavia.py", line 38, in wrapper
      request_id=e.request_id)
  octaviaclient.api.v2.octavia.OctaviaClientException: Not Found: Not Found. Sorry but your container is in another castle. (HTTP 500) (Request-ID: req-8146cc8c-334a-4155-9fa6-489d4cf1ecbf)

  The server side log shows:

  2019-11-05 14:41:48.288 2020577 WARNING octavia.controller.worker.controller_worker [req-046fe879-63c2-4804-9732-9985faf380e6 - ef8b2568c694461499c074c641a57a14 - - -] Task 'octavia.controller.worker.tasks.amphora_driver_tasks.ListenersUpdate' (1e77205e-486a-432b-b236-8e806c3c2b7e) transitioned into state 'FAILURE' from state 'RUNNING'
  5 predecessors (most recent first):
    Atom 'octavia.controller.worker.tasks.model_tasks.DeleteModelObject' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'object': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': None}
    |__Atom 'octavia.controller.worker.tasks.database_tasks.CountPoolChildrenForQuota' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': {'HM': 1, 'member': 3}}
       |__Atom 'octavia.controller.worker.tasks.database_tasks.MarkPoolPendingDeleteInDB' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>}, 'provides': None}
          |__Atom 'octavia.controller.worker.tasks.lifecycle_tasks.PoolToErrorOnRevertTask' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'pool': <octavia.common.data_models.Pool object at 0x7fd217b21978>, 'listeners': [<octavia.common.data_models.Listener object at 0x7fd217b7f400>], 'loadbalancer': <octavia.common.data_models.LoadBalancer object at 0x7fd216dc6550>}, 'provides': None}
             |__Flow 'octavia-delete-pool-flow': barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker Traceback (most recent call last):
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican.py", line 114, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return pkcs12.PKCS12Cert(cert_secret.payload)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 193, in payload
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._fetch_payload()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 261, in _fetch_payload
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     if not self.payload_content_type and not self.content_types:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 184, in payload_content_type
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     if not self._payload_content_type and self.content_types:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 34, in wrapper
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._fill_lazy_properties()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/secrets.py", line 414, in _fill_lazy_properties
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     result = self._api.get(self._secret_ref)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 70, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return super(_HTTPClient, self).get(*args, **kwargs).json()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 375, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return self.request(url, 'GET', **kwargs)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 63, in request
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._check_status_code(resp)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 107, in _check_status_code
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     status
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker During handling of the above exception, another exception occurred:
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker Traceback (most recent call last):
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/taskflow/engines/action_engine/executor.py", line 53, in _execute_task
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     result = task.execute(**arguments)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/controller/worker/tasks/amphora_driver_tasks.py", line 78, in execute
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.amphora_driver.update(listener, loadbalancer.vip)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 162, in update
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     certs = self._process_tls_certificates(listener)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/amphorae/drivers/haproxy/rest_api_driver.py", line 284, in _process_tls_certificates
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.cert_manager, listener)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/common/tls_utils/cert_parser.py", line 353, in load_certificates_data
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     check_only=True))
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican.py", line 122, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     check_only=check_only, service_name=service_name
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican_legacy.py", line 160, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     LOG.error('Error getting cert %s: %s', cert_ref, str(e))
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self.force_reraise()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     six.reraise(self.type_, self.value, self.tb)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     raise value
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/octavia/certificates/manager/barbican_legacy.py", line 138, in get_cert
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     container_ref=cert_ref
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/v1/containers.py", line 540, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     response = self._api.get(container_ref)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 70, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return super(_HTTPClient, self).get(*args, **kwargs).json()
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/keystoneauth1/adapter.py", line 375, in get
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     return self.request(url, 'GET', **kwargs)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 63, in request
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     self._check_status_code(resp)
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker   File "/usr/lib/python3/dist-packages/barbicanclient/client.py", line 107, in _check_status_code
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker     status
  2019-11-05 14:41:48.288 2020577 ERROR octavia.controller.worker.controller_worker barbicanclient.exceptions.HTTPClientError: Not Found: Not Found. Sorry but your container is in another castle.

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


From corey.bryant at canonical.com  Tue Feb 18 13:44:54 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Tue, 18 Feb 2020 13:44:54 -0000
Subject: [Bug 1826114] Update Released
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158203349463.15140.4459960455109871576.malone@soybean.canonical.com>

The verification of the Stable Release Update for horizon has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Released
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From corey.bryant at canonical.com  Tue Feb 18 13:44:57 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Tue, 18 Feb 2020 13:44:57 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158203349785.30257.16465065048412429684.malone@wampee.canonical.com>

This bug was fixed in the package horizon - 3:16.0.0-0ubuntu1.1~cloud0
---------------

 horizon (3:16.0.0-0ubuntu1.1~cloud0) bionic-train; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 horizon (3:16.0.0-0ubuntu1.1) eoan; urgency=medium
 .
   [ Corey Bryant ]
   * d/gbp.conf: Create stable/train branch.
 .
   [ Hemanth Nakkina ]
   * Fix users/projects list when domain context is changed (LP: #1826114)
     - d/p/fix-user-list-for-different-domain.patch.
   * GUI hangs on creation of project in User creation form (LP: #1826114)
     - d/p/gui-hangs-on-project-creation.patch.


** Changed in: cloud-archive/train
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Released
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From corey.bryant at canonical.com  Tue Feb 18 13:48:27 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Tue, 18 Feb 2020 13:48:27 -0000
Subject: [Bug 1826114] Update Released
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158203370716.29590.948196347261255780.malone@chaenomeles.canonical.com>

The verification of the Stable Release Update for horizon has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Released
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From corey.bryant at canonical.com  Tue Feb 18 13:48:28 2020
From: corey.bryant at canonical.com (Corey Bryant)
Date: Tue, 18 Feb 2020 13:48:28 -0000
Subject: [Bug 1826114] Re: Errors creating users and projects
References: <155608694554.6733.14259175844005204847.malonedeb@chaenomeles.canonical.com>
Message-ID: <158203370836.14835.6866775475755322726.malone@soybean.canonical.com>

This bug was fixed in the package horizon - 3:15.1.1-0ubuntu1.1~cloud1
---------------

 horizon (3:15.1.1-0ubuntu1.1~cloud1) bionic-stein; urgency=medium
 .
   * Fix users/projects list when domain context is changed (LP: #1826114)
     - d/p/fix-user-list-for-different-domain.patch.
   * GUI hangs on creation of project in User creation form (LP: #1826114)
     - d/p/gui-hangs-on-project-creation.patch.


** Changed in: cloud-archive/stein
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1826114

Title:
  Errors creating users and projects

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Fix Released
Status in horizon source package in Disco:
  Won't Fix
Status in horizon source package in Eoan:
  Fix Released
Status in horizon source package in Focal:
  Fix Released

Bug description:
  After a fresh install of OpenStack Stein using Juju Charms I'm getting
  errors and items not appearing when creating new users and projects.
  Here are several tests I made:

  When creating ONLY a new user in a domain different than admin_domain,
  the user creates successfully but is not shown in the user list on the
  GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating ONLY a project in a domain different than admin_domain,
  the project creates successfully but is not shown in the user list on
  the GUI even after a refresh/logout. Using the CLI shows that it was
  created successfully.

  When creating a user in a domain different than admin_domain, the
  project list in the form is empty.

  When creating a user AND a project in any domain (using the "+" icon
  in the user creation form), after creating the project the GIU hangs
  on a "Working..." spinning wheel and the following error appears on
  the web console:

  Uncaught SyntaxError: Unexpected token < in JSON at position 53
      at JSON.parse (<anonymous>)
      at Function.jQuery.parseJSON (439e79e74c16.js:567)
      at Function.jQuery.parseJSON (439e79e74c16.js:720)
      at processServerSuccess (c1b8ea0c3a19.js:80)
      at Object.success (c1b8ea0c3a19.js:84)
      at fire (439e79e74c16.js:210)
      at Object.fireWith [as resolveWith] (439e79e74c16.js:216)
      at done (439e79e74c16.js:626)
      at XMLHttpRequest.callback (439e79e74c16.js:653)

  After a refresh, the project is created but not the user.

  When creating a new user and a project separately in admin_domain
  everything works OK. After that I can see both and assign the project
  to the user.

  In all the pages I load from Horizon I get the following warning on
  the web console:

  439e79e74c16.js:700 JQMIGRATE: $(html) HTML strings must start with '<' character
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653
  439e79e74c16.js:700 console.trace
  migrateWarn @ 439e79e74c16.js:700
  jQuery.fn.init @ 439e79e74c16.js:714
  jQuery @ 439e79e74c16.js:15
  success @ c1b8ea0c3a19.js:204
  fire @ 439e79e74c16.js:210
  fireWith @ 439e79e74c16.js:216
  done @ 439e79e74c16.js:626
  callback @ 439e79e74c16.js:653

  
  ==========================================================================

  [Impact]

  New users and projects created in domain other than admin_domain are not
  displayed in dashboard. 
  Creation of project from User creation form hangs and never returns

  This patch fixes both the issues mentioned above

  [Test Case]

  Tests involved 3 cases
  - Creation of Project in different domain context
  - Creation of User in different domain context
  - Creation of Project in Create User form

  1. Reproducing the issue

  1a. Login to horizon as admin user
  1b. Go to page Identity->Domains and select "SetDomainContext" button for domain other than default or admin

  1c. Go to page Identity->Projects
  1d. Click on Create Project, enter new project details and click on Finish
  1e. The page gets refreshed but the new project is not displayed

  1f. Go to page Identity->Users
  1g. Click on Create User, enter new user details and click on Create User button in the form
  1h. The page gets refreshed but the new user is not displayed

  1i. Go to page Identity->Users
  1j. Click on Create User and enter new user details
  1k. Click on + symbol under Primary project in the form to create New project. Spinning wheel rotates forever.

  2. Install the package with fixed code

  3. Confirm bug have been fixed

  3a. Repeat steps 1a-1d. New project should be displayed in the table
  3b. Repeat steps 1f-1h. New user should be displayed in the table
  3c. Repeat steps 1i-1k, Project creation form should be opened
  3d. Add new project details and click on Create Project button in the form. Project should be displayed in User creation form.
  3e. Click on Create User button in Create user form
  3f. Users page should be refreshed and new user will be displayed
  3g. Go to Identity->Projects and new project created during user creation should be displayed

  [Regression Potential]

  Upstream CI passed for all the releases including the backported versions.
  Installation of new package will restart apache service and hence there will be downtime of horizon service for few milliseconds.

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


From 1776447 at bugs.launchpad.net  Tue Feb 18 14:47:28 2020
From: 1776447 at bugs.launchpad.net (Martin Wimpress)
Date: Tue, 18 Feb 2020 14:47:28 -0000
Subject: [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
References: <152879513924.25566.9444725611812079535.malonedeb@soybean.canonical.com>
Message-ID: <158203724908.24383.5835488895604770593.launchpad@gac.canonical.com>

** Changed in: xorg-server (Ubuntu)
     Assignee: (unassigned) => Timo Aaltonen (tjaalton)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
      Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

  ---- Original Bug Report Follows ----

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved at xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:
  dmi.product.family: Mini PC
  dmi.product.name: S I
  dmi.product.version: Default string
  dmi.sys.vendor: AZW
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  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/xorg-server/+bug/1776447/+subscriptions


From seb128 at ubuntu.com  Tue Feb 18 14:50:51 2020
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Tue, 18 Feb 2020 14:50:51 -0000
Subject: [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
References: <152879513924.25566.9444725611812079535.malonedeb@soybean.canonical.com>
Message-ID: <158203745189.28968.13350521231316117808.malone@chaenomeles.canonical.com>

Tagging rls-ff-notfxing, the bug is not important enough to be rls
tracked. Still it's in the sponsoring queue and hopefully gets fixed
before focal is out

** Tags removed: champagne
** Tags added: rls-ff-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
      Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

  ---- Original Bug Report Follows ----

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved at xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:
  dmi.product.family: Mini PC
  dmi.product.name: S I
  dmi.product.version: Default string
  dmi.sys.vendor: AZW
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  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/xorg-server/+bug/1776447/+subscriptions


From ddstreet at canonical.com  Tue Feb 18 15:14:03 2020
From: ddstreet at canonical.com (Dan Streetman)
Date: Tue, 18 Feb 2020 15:14:03 -0000
Subject: [Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
References: <152327372166.9603.13162907490865392858.malonedeb@soybean.canonical.com>
Message-ID: <158203884371.30733.1840055701016121341.malone@wampee.canonical.com>

upstream systemd issue is https://github.com/systemd/systemd/issues/11198
As launchpad was failing to sync the status of the upstream issue, I just marked it manually as fix released.

** Changed in: systemd
   Importance: Unknown => Undecided

** Changed in: systemd
 Remote watch: github.com/systemd/systemd/issues #11198 => None

** Changed in: systemd
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1762391

Title:
  pam_group.so is not evaluated by gnome-terminal

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

Bug description:
  [Impact]

  pam_setcred call was missing in systemd making its implementation of the PAM protocol incomplete. It could manifest in different ways, but one particularly problematic for enterprise environments was the fact that
  processes were never getting group membership they were expected to get via pam_group module.

  [Test Case]

   * Add a /etc/security/group.conf entry, e.g.
     *;*;*;Al0000-2400;dialout,users
   * Add pam_group to your PAM stack, e.g. /etc/pam.d/common-auth
   * Login to the system and launch gnome-terminal (it will be launched via gnome-terminal-server launched by systemd --user + dbus).

  Expected result:
  Logged in user is a member of 'dialout' and 'users' groups.

  Actual result:
  no group membership gained from pam_group.

  [Regression Potential]

   * It introduces a new PAM warning message in some scenarios (e.g. for
  systemd DynamicUser=1 units) for users that can't authenticate
  (pam_setcred fails in such case).

   * In certain systems user group membership may be extended by
  pam_group.

  [Other Info]
  Original bug description:

  We are using Ubuntu in a university network with lots of ldap users.
  To automatically map ldap users/groups to local groups we are using
  pam_group.so. This has worked for years.

  With the upgrade from Xenial to Bionic /etc/security/group.conf is not
  evaluated anymore by gnome-terminal as it runs as systemd --user.
  Xterm, ssh, su, and tty* however do work as expected. Only the default
  gnome-terminal behaves different.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851243
  and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756458 this
  might not be a bug, but a feature.

  Nevertheless this behavior is very unexpected when upgrading from
  Xenial to Bionic and therefore should at least added to the changelog.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 13:17:52 2018
  InstallationDate: Installed on 2018-03-29 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


From 1858857 at bugs.launchpad.net  Wed Feb 19 08:21:43 2020
From: 1858857 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 19 Feb 2020 08:21:43 -0000
Subject: [Bug 1858857] [NEW] gnome-calendar: Hits assert when timezone set to
 Etc/UTC
References: <157851405407.2981.5387672217752004766.malonedeb@soybean.canonical.com>
Message-ID: <158210050480.14619.10240108671861471163.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]

When the system timezone is set to Etc/UTC, most notably in the 20.04
Live CD environment, gnome-calendar fails to start, as it hits an
assert.

ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
Aborted (core dumped)

This is reproducible in focal with: gnome-calendar 3.34.2-1build1
This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1

More seriously, this bug is triggered when a user presses the Super key
in the Live CD test environment and searches for an application, as dbus
will attempt to start the gnome-calendar service, and gnome-calendar
will crash due to this bug.

[Test Case]

Change system timezone to Etc/UTC and attempt to launch gnome-calendar:

ubuntu at ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
ubuntu at ubuntu:/var/log$ timedatectl
               Local time: Tue 2020-02-18 02:49:21 UTC
           Universal time: Tue 2020-02-18 02:49:21 UTC
                 RTC time: Tue 2020-02-18 02:49:22
                Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
ubuntu at ubuntu:/var/log$ gnome-calendar
**
ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
Aborted (core dumped)

[Regression Potential]

The risk of regression is low due to the assert being removed and
replaced with a default to UTC time if the previous timezone pointer is
NULL. This is also only going to the focal development release, where
any impact to real users will be low.

[Other Information]

There is an upstream issue open:

https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485

** Affects: gnome-calendar (Ubuntu)
     Importance: Medium
     Assignee: Matthew Ruffell (mruffell)
         Status: Fix Committed

** Affects: gnome-calendar (Ubuntu Focal)
     Importance: Medium
     Assignee: Matthew Ruffell (mruffell)
         Status: Fix Committed


** Tags: amd64 apport-crash champagne focal patch
-- 
gnome-calendar: Hits assert when timezone set to Etc/UTC
https://bugs.launchpad.net/bugs/1858857
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1858857 at bugs.launchpad.net  Wed Feb 19 08:21:45 2020
From: 1858857 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Wed, 19 Feb 2020 08:21:45 -0000
Subject: [Bug 1858857] Re: gnome-calendar: Hits assert when timezone set to
 Etc/UTC
References: <157851405407.2981.5387672217752004766.malonedeb@soybean.canonical.com>
Message-ID: <158210050559.29232.4291696539065368358.malone@chaenomeles.canonical.com>

The attachment "gnome-calendar debdiff for focal" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1858857

Title:
  gnome-calendar: Hits assert when timezone set to Etc/UTC

Status in gnome-calendar package in Ubuntu:
  Fix Committed
Status in gnome-calendar source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  When the system timezone is set to Etc/UTC, most notably in the 20.04
  Live CD environment, gnome-calendar fails to start, as it hits an
  assert.

  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  This is reproducible in focal with: gnome-calendar 3.34.2-1build1
  This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1

  More seriously, this bug is triggered when a user presses the Super
  key in the Live CD test environment and searches for an application,
  as dbus will attempt to start the gnome-calendar service, and gnome-
  calendar will crash due to this bug.

  [Test Case]

  Change system timezone to Etc/UTC and attempt to launch gnome-
  calendar:

  ubuntu at ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
  ubuntu at ubuntu:/var/log$ timedatectl
                 Local time: Tue 2020-02-18 02:49:21 UTC
             Universal time: Tue 2020-02-18 02:49:21 UTC
                   RTC time: Tue 2020-02-18 02:49:22
                  Time zone: Etc/UTC (UTC, +0000)
  System clock synchronized: yes
                NTP service: active
            RTC in local TZ: no
  ubuntu at ubuntu:/var/log$ gnome-calendar
  **
  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  [Regression Potential]

  The risk of regression is low due to the assert being removed and
  replaced with a default to UTC time if the previous timezone pointer
  is NULL. This is also only going to the focal development release,
  where any impact to real users will be low.

  [Other Information]

  There is an upstream issue open:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485

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


From 1858857 at bugs.launchpad.net  Wed Feb 19 10:13:30 2020
From: 1858857 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 19 Feb 2020 10:13:30 -0000
Subject: [Bug 1858857] Re: gnome-calendar: Hits assert when timezone set to
 Etc/UTC
References: <157851405407.2981.5387672217752004766.malonedeb@soybean.canonical.com>
Message-ID: <158210721218.22449.14256897321434495941.malone@ackee.canonical.com>

This bug was fixed in the package gnome-calendar - 3.34.2-1ubuntu1

---------------
gnome-calendar (3.34.2-1ubuntu1) focal; urgency=medium

  * d/p/fall-back-to-UTC-when-timezone-is-unrecognized.patch:
    - Fix a crash where the "Etc/UTC" timezone from Live CD
      is not recongised by libical. (LP: #1858857)

 -- Matthew Ruffell <matthew.ruffell at canonical.com>  Wed, 19 Feb 2020
13:09:39 +1300

** Changed in: gnome-calendar (Ubuntu Focal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1858857

Title:
  gnome-calendar: Hits assert when timezone set to Etc/UTC

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Focal:
  Fix Released

Bug description:
  [Impact]

  When the system timezone is set to Etc/UTC, most notably in the 20.04
  Live CD environment, gnome-calendar fails to start, as it hits an
  assert.

  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  This is reproducible in focal with: gnome-calendar 3.34.2-1build1
  This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1

  More seriously, this bug is triggered when a user presses the Super
  key in the Live CD test environment and searches for an application,
  as dbus will attempt to start the gnome-calendar service, and gnome-
  calendar will crash due to this bug.

  [Test Case]

  Change system timezone to Etc/UTC and attempt to launch gnome-
  calendar:

  ubuntu at ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
  ubuntu at ubuntu:/var/log$ timedatectl
                 Local time: Tue 2020-02-18 02:49:21 UTC
             Universal time: Tue 2020-02-18 02:49:21 UTC
                   RTC time: Tue 2020-02-18 02:49:22
                  Time zone: Etc/UTC (UTC, +0000)
  System clock synchronized: yes
                NTP service: active
            RTC in local TZ: no
  ubuntu at ubuntu:/var/log$ gnome-calendar
  **
  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  [Regression Potential]

  The risk of regression is low due to the assert being removed and
  replaced with a default to UTC time if the previous timezone pointer
  is NULL. This is also only going to the focal development release,
  where any impact to real users will be low.

  [Other Information]

  There is an upstream issue open:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485

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


From mitya57 at gmail.com  Wed Feb 19 14:13:17 2020
From: mitya57 at gmail.com (Dmitry Shachnev)
Date: Wed, 19 Feb 2020 14:13:17 -0000
Subject: [Bug 1863528] Re: Sync matplotlib 3.1.2-2 (universe) from Debian
 unstable (main)
References: <158189728808.31087.4861820836825944724.malonedeb@wampee.canonical.com>
Message-ID: <158212159714.24684.4145174716663929144.malone@gac.canonical.com>

The "Error out on failing builds" part is not applied in Debian. Have
you verified that the package builds fine on Ubuntu?

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863528

Title:
  Sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

Status in matplotlib package in Ubuntu:
  Incomplete

Bug description:
  Please sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Disabled the wxagg autopkg test, python3-wxgtk3.0 is removed.
    * Error out on failing builds.
  The wxagg test is dropped.

  Changelog entries since current focal version 3.1.2-1ubuntu2:

  matplotlib (3.1.2-2) unstable; urgency=medium

    * debian/tests/{control, wxagg}
      - drop wxagg test; Closes: #950799

   -- Sandro Tosi <morph at debian.org>  Wed, 12 Feb 2020 21:55:19 -0500

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


From 1858857 at bugs.launchpad.net  Wed Feb 19 14:42:12 2020
From: 1858857 at bugs.launchpad.net (Christopher Leslie-John Peters)
Date: Wed, 19 Feb 2020 14:42:12 -0000
Subject: [Bug 1858857] Re: gnome-calendar: Hits assert when timezone set
 to Etc/UTC
References: <157851405407.2981.5387672217752004766.malonedeb@soybean.canonical.com>
 <158210721218.22449.14256897321434495941.malone@ackee.canonical.com>
Message-ID: <CAAS4=mw0f-5e7oyEqG63xr0b=moBQpLPEw26_F4EbSxZRSDEPg@mail.gmail.com>

This is all fascinating. Thank fo updates.

You are all super stars ! Enamoring 😳

Sincerely.

Christopher Leslie-John Peters

On Wed, Feb 19, 2020, 5:22 AM Launchpad Bug Tracker <
1858857 at bugs.launchpad.net> wrote:

> This bug was fixed in the package gnome-calendar - 3.34.2-1ubuntu1
>
> ---------------
> gnome-calendar (3.34.2-1ubuntu1) focal; urgency=medium
>
>   * d/p/fall-back-to-UTC-when-timezone-is-unrecognized.patch:
>     - Fix a crash where the "Etc/UTC" timezone from Live CD
>       is not recongised by libical. (LP: #1858857)
>
>  -- Matthew Ruffell <matthew.ruffell at canonical.com>  Wed, 19 Feb 2020
> 13:09:39 +1300
>
> ** Changed in: gnome-calendar (Ubuntu Focal)
>        Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1858857
>
> Title:
>   gnome-calendar: Hits assert when timezone set to Etc/UTC
>
> Status in gnome-calendar package in Ubuntu:
>   Fix Released
> Status in gnome-calendar source package in Focal:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   When the system timezone is set to Etc/UTC, most notably in the 20.04
>   Live CD environment, gnome-calendar fails to start, as it hits an
>   assert.
>
>
> ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone:
> assertion failed: (ical_tz != NULL)
>   Bail out!
> ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone:
> assertion failed: (ical_tz != NULL)
>   Aborted (core dumped)
>
>   This is reproducible in focal with: gnome-calendar 3.34.2-1build1
>   This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1
>
>   More seriously, this bug is triggered when a user presses the Super
>   key in the Live CD test environment and searches for an application,
>   as dbus will attempt to start the gnome-calendar service, and gnome-
>   calendar will crash due to this bug.
>
>   [Test Case]
>
>   Change system timezone to Etc/UTC and attempt to launch gnome-
>   calendar:
>
>   ubuntu at ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
>   ubuntu at ubuntu:/var/log$ timedatectl
>                  Local time: Tue 2020-02-18 02:49:21 UTC
>              Universal time: Tue 2020-02-18 02:49:21 UTC
>                    RTC time: Tue 2020-02-18 02:49:22
>                   Time zone: Etc/UTC (UTC, +0000)
>   System clock synchronized: yes
>                 NTP service: active
>             RTC in local TZ: no
>   ubuntu at ubuntu:/var/log$ gnome-calendar
>   **
>
> ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone:
> assertion failed: (ical_tz != NULL)
>   Bail out!
> ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone:
> assertion failed: (ical_tz != NULL)
>   Aborted (core dumped)
>
>   [Regression Potential]
>
>   The risk of regression is low due to the assert being removed and
>   replaced with a default to UTC time if the previous timezone pointer
>   is NULL. This is also only going to the focal development release,
>   where any impact to real users will be low.
>
>   [Other Information]
>
>   There is an upstream issue open:
>
>   https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1858857/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1858857

Title:
  gnome-calendar: Hits assert when timezone set to Etc/UTC

Status in gnome-calendar package in Ubuntu:
  Fix Released
Status in gnome-calendar source package in Focal:
  Fix Released

Bug description:
  [Impact]

  When the system timezone is set to Etc/UTC, most notably in the 20.04
  Live CD environment, gnome-calendar fails to start, as it hits an
  assert.

  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  This is reproducible in focal with: gnome-calendar 3.34.2-1build1
  This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1

  More seriously, this bug is triggered when a user presses the Super
  key in the Live CD test environment and searches for an application,
  as dbus will attempt to start the gnome-calendar service, and gnome-
  calendar will crash due to this bug.

  [Test Case]

  Change system timezone to Etc/UTC and attempt to launch gnome-
  calendar:

  ubuntu at ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
  ubuntu at ubuntu:/var/log$ timedatectl
                 Local time: Tue 2020-02-18 02:49:21 UTC
             Universal time: Tue 2020-02-18 02:49:21 UTC
                   RTC time: Tue 2020-02-18 02:49:22
                  Time zone: Etc/UTC (UTC, +0000)
  System clock synchronized: yes
                NTP service: active
            RTC in local TZ: no
  ubuntu at ubuntu:/var/log$ gnome-calendar
  **
  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Bail out! ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  [Regression Potential]

  The risk of regression is low due to the assert being removed and
  replaced with a default to UTC time if the previous timezone pointer
  is NULL. This is also only going to the focal development release,
  where any impact to real users will be low.

  [Other Information]

  There is an upstream issue open:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485

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


From teward at thomas-ward.net  Wed Feb 19 16:29:35 2020
From: teward at thomas-ward.net (Thomas Ward)
Date: Wed, 19 Feb 2020 16:29:35 -0000
Subject: [Bug 1863528] Re: Sync matplotlib 3.1.2-2 (universe) from Debian
 unstable (main)
References: <158189728808.31087.4861820836825944724.malonedeb@wampee.canonical.com>
Message-ID: <158212977535.29054.4788556322650785605.malone@chaenomeles.canonical.com>

Builds successfully on s390x, ppc64el, armhf, and arm64.

FTBFS in amd64.

https://launchpad.net/~teward/+archive/ubuntu/build-
tests/+builds?build_text=matplotlib&build_state=all

https://launchpadlibrarian.net/465694005/buildlog_ubuntu-focal-
amd64.matplotlib_3.1.2-2~ppa1_BUILDING.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863528

Title:
  Sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

Status in matplotlib package in Ubuntu:
  Incomplete

Bug description:
  Please sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Disabled the wxagg autopkg test, python3-wxgtk3.0 is removed.
    * Error out on failing builds.
  The wxagg test is dropped.

  Changelog entries since current focal version 3.1.2-1ubuntu2:

  matplotlib (3.1.2-2) unstable; urgency=medium

    * debian/tests/{control, wxagg}
      - drop wxagg test; Closes: #950799

   -- Sandro Tosi <morph at debian.org>  Wed, 12 Feb 2020 21:55:19 -0500

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


From mitya57 at gmail.com  Wed Feb 19 17:51:22 2020
From: mitya57 at gmail.com (Dmitry Shachnev)
Date: Wed, 19 Feb 2020 17:51:22 -0000
Subject: [Bug 1863528] Re: Sync matplotlib 3.1.2-2 (universe) from Debian
 unstable (main)
References: <158189728808.31087.4861820836825944724.malonedeb@wampee.canonical.com>
Message-ID: <158213468209.14724.213732777782614859.malone@soybean.canonical.com>

So we can't sync it as is.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863528

Title:
  Sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

Status in matplotlib package in Ubuntu:
  Won't Fix

Bug description:
  Please sync matplotlib 3.1.2-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Disabled the wxagg autopkg test, python3-wxgtk3.0 is removed.
    * Error out on failing builds.
  The wxagg test is dropped.

  Changelog entries since current focal version 3.1.2-1ubuntu2:

  matplotlib (3.1.2-2) unstable; urgency=medium

    * debian/tests/{control, wxagg}
      - drop wxagg test; Closes: #950799

   -- Sandro Tosi <morph at debian.org>  Wed, 12 Feb 2020 21:55:19 -0500

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


From 1854563 at bugs.launchpad.net  Thu Feb 20 09:09:31 2020
From: 1854563 at bugs.launchpad.net (Amr Ibrahim)
Date: Thu, 20 Feb 2020 09:09:31 -0000
Subject: [Bug 1854563] Re: Sync materia-gtk-theme 20190315-1 (universe) from
 Debian unstable (main)
References: <157510811257.31064.14015076822460317307.malonedeb@wampee.canonical.com>
Message-ID: <158218977220.29344.4991996842481530709.launchpad@chaenomeles.canonical.com>

** Changed in: materia-gtk-theme (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854563

Title:
  Sync materia-gtk-theme 20190315-1 (universe) from Debian unstable
  (main)

Status in materia-gtk-theme package in Ubuntu:
  Fix Released

Bug description:
  Please sync materia-gtk-theme 20190315-1 (universe) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    [ Erich Eickmeyer ]
    * Fix Ubiquity theming issue (LP: #1822134)
      - Previous change did not fix issue
    * Fix Ubiquity theming issue (LP: #1822134)

  The Ubuntu change is now upstream.

  Changelog entries since current focal version 20190201-1ubuntu2:

  materia-gtk-theme (20190315-1) unstable; urgency=medium

    * New upstream version 20190315

   -- Sagar Ippalpalli <i.vikram15 at gmail.com>  Sun, 07 Apr 2019 20:33:24
  +0530

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/materia-gtk-theme/+bug/1854563/+subscriptions


From robert.ancell at canonical.com  Fri Feb 21 04:10:11 2020
From: robert.ancell at canonical.com (Robert Ancell)
Date: Fri, 21 Feb 2020 04:10:11 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158225821132.24299.3773911670355154541.malone@gac.canonical.com>

The changes to the symbol files had changed the package name from
'libsane' to 'libsane1', so I reverted that and uploaded the rest,
thanks Till!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From robert.ancell at canonical.com  Fri Feb 21 04:10:51 2020
From: robert.ancell at canonical.com (Robert Ancell)
Date: Fri, 21 Feb 2020 04:10:51 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158225825143.29344.7480803459883421290.malone@chaenomeles.canonical.com>

There wasn't a bug link in the changelog, so this bug wont be
automatically closed.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1794478 at bugs.launchpad.net  Fri Feb 21 08:28:16 2020
From: 1794478 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Fri, 21 Feb 2020 08:28:16 -0000
Subject: [Bug 1794478] [NEW] Automatic ipv4 not assigned to bond interface is
 manual ipv6 is assigned to it
References: <153795476448.25111.10599931296514318283.malonedeb@gac.canonical.com>
Message-ID: <158227369726.14724.4474741296555644527.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Seyeong Kim (xtrusia):

[Impact]

In case creating bond interface, IPv4 address is not automatically
assigned when IPv6 has manual setting.

[Test Case]

1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
2. ipv6 manual, ipv4 auto
##################################
sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
sudo nmcli con mod bond0 ipv4.method auto;
sudo nmcli con add type bond-slave ifname ens34 master bond0;
sudo nmcli con add type bond-slave ifname ens35 master bond0;
sudo nmcli con mod bond0 +bond.options mii=100

sleep 5

sudo nmcli con up bond-slave-ens34
sudo nmcli con up bond-slave-ens35
sudo nmcli con up bond0;

sleep 5;
sudo nmcli c s bond0
##################################
3. ipv6 auto, ipv4 auto
##################################
sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
sudo nmcli con mod bond0 ipv6.method auto;
sudo nmcli con mod bond0 ipv4.method auto;
sudo nmcli con add type bond-slave ifname ens34 master bond0;
sudo nmcli con add type bond-slave ifname ens35 master bond0;
sudo nmcli con mod bond0 +bond.options mii=100

sleep 5

sudo nmcli con up bond-slave-ens34
sudo nmcli con up bond-slave-ens35
sudo nmcli con up bond0;

sleep 5

sudo nmcli c s bond0
##################################

when run #3, it is working, but with #2, it is not working.

[Potential Regression]

Actually nothing special. fix just remove if statement. but it needs
Network Manager restarted.

[Other informations]

After upstream fix, it is working fine with #2 and #3 above.

* Upstream bug and fix:

https://bugzilla.redhat.com/show_bug.cgi?id=1575944
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

* Only affecting Bionic:

$ git describe --contains f03ae35
1.10.8~2

$ rmadison network-manager
==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
    network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
    network-manager | 1.22.4-1ubuntu2     | focal

[Original description]

---Problem Description---
Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.

---uname output---
Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux

Machine Type = s390x

---Debugger---
A debugger is not configured

---Steps to Reproduce---
 When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface

This issue will not happen in below cases:
1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
2)with ipv4 automatic and ipv6 automatic configuration for bond interface
3)with ipv4 automatic and ipv6 disabled configuration for bond interface

Configuration:
Bond interface, ipv4 automatic mode and ipv6 automatic mode

root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
[connection]
id=test_bond
uuid=63e54542-5135-47ac-a954-b861c3937be2
type=bond
interface-name=test_bond
permissions=
timestamp=1537944121

[ethernet]
mac-address-blacklist=

[bond]
downdelay=0
fail_over_mac=none
miimon=100
mode=active-backup
num_grat_arp=0
primary_reselect=always
updelay=0

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

>From /var/log/syslog, we can see ip got assigned:

Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
    inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
       valid_lft 353sec preferred_lft 353sec
    inet6 fe80::ff:feb3:b522/64 scope link
       valid_lft forever preferred_lft forever

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Bond interface, ipv4 automatic mode and ipv6 manual mode

root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
[connection]
id=test_bond
uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
type=bond
interface-name=test_bond
permissions=
timestamp=1537943300

[ethernet]
mac-address-blacklist=

[bond]
downdelay=0
fail_over_mac=none
miimon=100
mode=active-backup
num_grat_arp=0
primary_reselect=always
updelay=0

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
address1=fe81::32a5:bc5f:287f:8db8/64
dns-search=
method=manual

No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
    inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

==> Correct LP-Package need to be assigned...!

** Affects: ubuntu-z-systems
     Importance: Undecided
     Assignee: Canonical Foundations Team (canonical-foundations)
         Status: Fix Released

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: network-manager (Ubuntu Bionic)
     Importance: High
     Assignee: Seyeong Kim (xtrusia)
         Status: Confirmed


** Tags: architecture-s39064 bugnameltc-171765 severity-high sts targetmilestone-inin1804 verification-done verification-done-bionic
-- 
Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
https://bugs.launchpad.net/bugs/1794478
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From bugproxy at us.ibm.com  Fri Feb 21 08:28:39 2020
From: bugproxy at us.ibm.com (bugproxy)
Date: Fri, 21 Feb 2020 08:28:39 -0000
Subject: [Bug 1794478] lp1794478_bionic.debdiff
References: <153795476448.25111.10599931296514318283.malonedeb@gac.canonical.com>
Message-ID: <158227371930.15569.12510198748022603046.malone@soybean.canonical.com>

Default Comment by Bridge

** Attachment added: "lp1794478_bionic.debdiff"
   https://bugs.launchpad.net/bugs/1794478/+attachment/5330008/+files/lp1794478_bionic.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
  2. ipv6 manual, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##################################
  3. ipv6 auto, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##################################

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
      network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
      network-manager | 1.22.4-1ubuntu2     | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
         valid_lft 353sec preferred_lft 353sec
      inet6 fe80::ff:feb3:b522/64 scope link
         valid_lft forever preferred_lft forever

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
         valid_lft forever preferred_lft forever

  ==> Correct LP-Package need to be assigned...!

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


From seyeong.kim at canonical.com  Fri Feb 21 08:37:00 2020
From: seyeong.kim at canonical.com (Seyeong Kim)
Date: Fri, 21 Feb 2020 08:37:00 -0000
Subject: [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is
 manual ipv6 is assigned to it
References: <153795476448.25111.10599931296514318283.malonedeb@gac.canonical.com>
Message-ID: <158227422095.31124.8703791769560907988.malone@wampee.canonical.com>

why bugproxy keep attaching old debdiff I've changed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
  2. ipv6 manual, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##################################
  3. ipv6 auto, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##################################

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
      network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
      network-manager | 1.22.4-1ubuntu2     | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
         valid_lft 353sec preferred_lft 353sec
      inet6 fe80::ff:feb3:b522/64 scope link
         valid_lft forever preferred_lft forever

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
         valid_lft forever preferred_lft forever

  ==> Correct LP-Package need to be assigned...!

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


From 1862926 at bugs.launchpad.net  Fri Feb 21 09:58:25 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Fri, 21 Feb 2020 09:58:25 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158227910604.24756.5698151947517490845.malone@gac.canonical.com>

1.0.29-0ubuntu1 does FTBFS, -0ubuntu2 with added Build-Depends: on the
way.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1862926 at bugs.launchpad.net  Fri Feb 21 10:20:54 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Fri, 21 Feb 2020 10:20:54 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158228045465.29100.1770689927339029514.malone@chaenomeles.canonical.com>

The attached debdiff adds the missing Build-Depends for fixing the FTBFS
and getting all backends built.

** Patch added: "sane-backends_1.0.29-0ubuntu1_1.0.29-0ubuntu2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862926/+attachment/5330030/+files/sane-backends_1.0.29-0ubuntu1_1.0.29-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From steve.langasek at canonical.com  Fri Feb 21 19:33:12 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 21 Feb 2020 19:33:12 -0000
Subject: [Bug 1862040] Re: please remove ghostwriter [ppc64el s390x] from focal
References: <158092297268.8645.6195743342814122345.malonedeb@chaenomeles.canonical.com>
Message-ID: <158231359312.30932.6947694192204001089.malone@wampee.canonical.com>

Removing packages from focal:
	ghostwriter 1.7.4-2 in focal ppc64el
	ghostwriter 1.7.4-2 in focal s390x
Comment: ANAIS
2 packages successfully removed.


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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862040

Title:
   please remove ghostwriter [ppc64el s390x] from focal

Status in ghostwriter package in Ubuntu:
  Fix Released
Status in ghostwriter package in Debian:
  Fix Released

Bug description:
  A recent upload changed the build-dependencies  (Dependency wait:
  Missing build dependencies: qtwebengine5-dev) so the package now can't
  be built on ppc64el and s390x. Please remove those binaries so that
  the new version can migrate from focal-proposed to focal. This was
  already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=947931.

  There are no rdeps.
  $ reverse-depends -r focal src:ghostwriter
  No reverse dependencies found
  $ reverse-depends -r focal -b src:ghostwriter
  No reverse dependencies found

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


From steve.langasek at canonical.com  Fri Feb 21 19:32:01 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Fri, 21 Feb 2020 19:32:01 -0000
Subject: [Bug 1862000] Re: please remove minizinc-ide [ppc64el s390x] from
 focal
References: <158089864472.26139.4964242197704608007.malonedeb@soybean.canonical.com>
Message-ID: <158231352270.15103.3102093648273353392.malone@soybean.canonical.com>

$ remove-package -b -a ppc64el -a s390x -m ANAIS -y minizinc-ide
Removing packages from focal:
	minizinc-ide 2.1.7-1 in focal ppc64el
	minizinc-ide 2.1.7-1 in focal s390x
Comment: ANAIS
2 packages successfully removed.


** Changed in: minizinc-ide (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862000

Title:
  please remove minizinc-ide [ppc64el s390x] from focal

Status in minizinc-ide package in Ubuntu:
  Fix Released
Status in minizinc-ide package in Debian:
  Fix Released

Bug description:
  A recent upload changed the build-dependencies so the package now
  can't be built on ppc64el and s390x. Please remove those binaries so
  that the new version can migrate from focal-proposed to focal. This
  was already done in Debian, https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=948686.

  There are no rdeps.
  $ reverse-depends -r focal src:minizinc-ide
  No reverse dependencies found
  $ reverse-depends -r focal -b src:minizinc-ide
  No reverse dependencies found

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


From 1863609 at bugs.launchpad.net  Sat Feb 22 05:01:44 2020
From: 1863609 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 05:01:44 -0000
Subject: [Bug 1863609] Re:  [SRU] Update to vala 0.40.19 in bionic 
References: <158194336745.14972.1692101375000515098.malonedeb@soybean.canonical.com>
Message-ID: <158234770529.14759.8749433455298097469.launchpad@soybean.canonical.com>

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

** Tags added: upgrade-software-version

** Also affects: vala (Ubuntu Bionic)
   Importance: Undecided
       Status: New

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863609

Title:
   [SRU] Update to vala 0.40.19 in bionic

Status in vala package in Ubuntu:
  Fix Released
Status in vala source package in Bionic:
  New

Bug description:
  The 0.40.x series is maintained as LTS release and will receive
  further bug fix releases in the future. See
  https://wiki.gnome.org/Projects/Vala

  Previous 0.40.17 SRU https://bugs.launchpad.net/bugs/1803136

  Falls under the standing GNOME SRU execption
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

  Upstream changes since 0.40.17:

  Vala 0.40.19
  ============
   * Various improvements and bug fixes:
     - codegen:
      + Fix precondition in creation method of structs
      + Don't set implemenation of interface property to its own [#891]
      + Use result value of assignment rather than its computation [#895]
      + Cast instance parameter in member-initializer for base-properties [#899]
      + Skip StructRegisterFunction for boolean/integer/floating types [#901]
      + Handle different type-symbols in visit_base_access() [#901]
     - vala:
      + VoidType is actually compatible with itself [#878]
      + Keep formal_target_type on transform of method-call/object-creation [#835]
      + Add a basic parameter check for [Print] methods
      + Don't ignore inner errors in Block and acknowledge them further
      + Don't report further errors if MemberInitializer.check() failed
      + Improve error message for unsupported inner types and declarations
      + Don't allow "va_list" as return-type or type of fields [#884]
      + Check before accessing "name" of parent_symbol which might be null
      + Allow to override base interface properties explicitly
      + Fix base-access check for compact classes
      + Improve detection of recursive struct declarations [#902]
      + Inline allocated arrays require length or initializer [#903]
      + Don't ignore errors in Parameter and acknowledge them further
    - parser: Implicit "main" method of main-block is public and static
    - genie: Fix parser's inner state when a struct is declared after a class
    - girparser: Apply explicitly given ctype metadata attributes on callables
    - testrunner: Invalid tests and therefore expected failures must return 1

   * Bindings:
    - glib-2.0: Add to_string() for GLib.PollFd and GLib.Pid
    - gtk+-3.0: Update to 3.24.13+3822ac74

  Vala 0.40.18
  ============
   * Various improvements and bug fixes:
    - codegen:
      + Use G_TYPE_INSTANCE_GET_INTERFACE to get vtable for base-access
      + Fix setting of generic-type properties for gobject chain up [#654702]
      + Make type-parameter properties readable [#190]
      + Fix vfunc signature of delegate-typed property in interface
      + Fix support of dynamic DBus methods
    - vala:
      + Warn when passing arrays to typeof(), except for "string[]" [#868]
      + Don't falsely resolve binary-expression to bool [#869]
      + Do not allow += for arrays with fixed length
      + Array with fixed length don't require explicit instantiation [#720]
      + Infer array length of inline allocated arrays for fields [#644046]
      + Do not allow to .resize() on arrays with fixed length
      + Do not allow to change .length of arrays with fixed length
      + Improve error message for arrays as type arguments
      + Improve error reporting for invalid interface prerequisites [#437]
      + Write value of constants/enums in fast-vapi if constant only [#461]
      + Don't require constant initializer in fast-vapi [#461]
      + Restore DestroysInstance behaviour for non-compact classes [#873]
      + Report error for async creation expression without yield
    - parser: `owned` is not allowed on Constants
    - girparser: Detect and replace "-" in parameter names
    - girwriter: Add readable="0"/private="1" attribute to type-specific fields
    - gidl:
      + Calculate size correctly, avoid use-after-free
      + Avoid use of uninitialized "markup" warning
      + Ignore flags like -mfpmath=sse, -msse or -msse2
    - valadoc:
      + libvaladoc: Fix parameter and property ownership declarations
      + Fix ownership declarations of Constants
    - pkg-config:
      + vala: Add missing gmodule-2.0 to Requires.private of pkg-config file
      + libvaladoc: Move gmodule-2.0 to Requires.private of pkg-config file

   * Bindings:
    - glib-2.0: Guard against passing null source to GLib.Memory.copy()
    - gtk+-3.0: Skip _MountOperationHandler* symbols
    - libusb-1.0: Don't depend on glib-2.0
    - libusb-1.0: Remove unused private "malloc" binding
    - linux: Add memfd_create(2)
    - posix: Bind some essential memory allocation functions

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


From 1862936 at bugs.launchpad.net  Sat Feb 22 05:13:20 2020
From: 1862936 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 05:13:20 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158234840097.15472.15216140890732878870.malone@soybean.canonical.com>

ltt-control (2.11.1-2) unstable; urgency=medium

  * [3aeb42e] Fix session rotation with kernel domain (Closes: #951206)

 -- Michael Jeanson <mjeanson at debian.org>  Wed, 12 Feb 2020 10:58:54
-0500

** Changed in: ltt-control (Ubuntu Focal)
       Status: New => Fix Released

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Focal:
  Fix Released
Status in ltt-control package in Debian:
  Unknown

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1862936 at bugs.launchpad.net  Sat Feb 22 05:20:12 2020
From: 1862936 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 05:20:12 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158234881351.29190.9593092260941590241.launchpad@chaenomeles.canonical.com>

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Focal:
  Fix Released
Status in ltt-control package in Debian:
  Unknown

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1862936 at bugs.launchpad.net  Sat Feb 22 05:39:21 2020
From: 1862936 at bugs.launchpad.net (Bug Watch Updater)
Date: Sat, 22 Feb 2020 05:39:21 -0000
Subject: [Bug 1862936] Re: Error: Rotation feature not supported by the kernel
 tracer.
References: <158151127480.29232.843019065801435990.malonedeb@chaenomeles.canonical.com>
Message-ID: <158234996302.29607.7287142394322844942.launchpad@loganberry.canonical.com>

** Changed in: ltt-control (Debian)
       Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862936

Title:
  Error: Rotation feature not supported by the kernel tracer.

Status in ltt-control package in Ubuntu:
  Fix Released
Status in ltt-control source package in Focal:
  Fix Released
Status in ltt-control package in Debian:
  Fix Released

Bug description:
  $ dpkg -l | grep ltt
  ii  liblttng-ctl0:amd64                  2.11.1-1                            amd64        LTTng control and utility library
  ii  liblttng-ust-ctl4:amd64              2.11.0-1                            amd64        LTTng 2.0 Userspace Tracer (trace control library)
  ii  lttng-modules-dkms                   2.10.8-1ubuntu2                     all          Linux Trace Toolkit (LTTng) kernel modules (DKMS)
  ii  lttng-tools                          2.11.1-1                            amd64        LTTng control and utility programs

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu Focal Fossa (development branch)
  Release:        20.04
  Codename:       focal

  How to reproduce:

  $ sudo lttng create foobar
  Session foobar created.
  Traces will be output to /root/lttng-traces/foobar-20200212-123955

  $ sudo lttng enable-event --kernel sched_switch
  Kernel event sched_switch created in channel channel0

  $ sudo lttng start
  Tracing started for session foobar

  $ dd if=/dev/zero bs=4096 count=100000 | cat | cat | cat | dd bs=4096 > /dev/null
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664467 s, 616 MB/s
  100000+0 records in
  100000+0 records out
  409600000 bytes (410 MB, 391 MiB) copied, 0.664758 s, 616 MB/s

  $ sudo lttng stop
  Waiting for data availability.
  Tracing stopped for session foobar

  $ sudo lttng destroy
  Error: Rotation feature not supported by the kernel tracer. during the destruction of session "foobar"

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


From 1794478 at bugs.launchpad.net  Sat Feb 22 05:44:14 2020
From: 1794478 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 05:44:14 -0000
Subject: [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is
 manual ipv6 is assigned to it
References: <153795476448.25111.10599931296514318283.malonedeb@gac.canonical.com>
Message-ID: <158235025641.31006.16864246456182496150.launchpad@wampee.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
  2. ipv6 manual, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##################################
  3. ipv6 auto, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##################################

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
      network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
      network-manager | 1.22.4-1ubuntu2     | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
         valid_lft 353sec preferred_lft 353sec
      inet6 fe80::ff:feb3:b522/64 scope link
         valid_lft forever preferred_lft forever

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
         valid_lft forever preferred_lft forever

  ==> Correct LP-Package need to be assigned...!

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


From 1776447 at bugs.launchpad.net  Sat Feb 22 05:51:48 2020
From: 1776447 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 05:51:48 -0000
Subject: [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
References: <152879513924.25566.9444725611812079535.malonedeb@soybean.canonical.com>
Message-ID: <158235071012.30106.8182187775163161936.launchpad@wampee.canonical.com>

** Tags removed: fixed-upstream
** Tags added: patch-accepted-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
      Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

  ---- Original Bug Report Follows ----

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved at xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:
  dmi.product.family: Mini PC
  dmi.product.name: S I
  dmi.product.version: Default string
  dmi.sys.vendor: AZW
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  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/xorg-server/+bug/1776447/+subscriptions


From 1776447 at bugs.launchpad.net  Sat Feb 22 06:06:12 2020
From: 1776447 at bugs.launchpad.net (Mathew Hodson)
Date: Sat, 22 Feb 2020 06:06:12 -0000
Subject: [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression
References: <152879513924.25566.9444725611812079535.malonedeb@soybean.canonical.com>
Message-ID: <158235157253.24083.6643133344714893475.launchpad@gac.canonical.com>

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item&px=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
      Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

  ---- Original Bug Report Follows ----

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved at xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr00.12:bd12/18/2017:svnAZW:pnSI:pvrDefaultstring:rvnIP3Tech:rnAB1:rvrDefaultstring:cvnDefaultstring:ct35:cvrDefaultstring:
  dmi.product.family: Mini PC
  dmi.product.name: S I
  dmi.product.version: Default string
  dmi.sys.vendor: AZW
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  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/xorg-server/+bug/1776447/+subscriptions


From 1864252 at bugs.launchpad.net  Sat Feb 22 07:24:52 2020
From: 1864252 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 22 Feb 2020 07:24:52 -0000
Subject: [Bug 1864252] [NEW] preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158235629256.24807.6887792270200415363.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Robert C Jennings (rcj):

[Impact]

Images built with pre-seeded snaps contain insufficient assertion data
causing boot to fail.

The snaps for seeding are downloaded with a custom snap tool for an
earlier cohort API (now deprecated).  The assertions that it pulls are
incomplete.  We could update that list and move to the new API but at
this time the snap-tool provides no value compared to use of the snap
CLI (cohort support has moved to the cli as well).  The development
overhead of maintaining snap-tool in livecd-rootfs are not warranted.

This patch removes the bespoke snap-tool and relies on the snap CLI
instead.

[Test Case]

 * Produce images that include preseeded snaps (in
/var/lib/snapd/seed/*)

 * Boot the resulting image and ensure that the snapd.seeded unit is
successful and the snaps (from the correct channels) show up in 'snap
list'

[Regression Potential]

 * The interface for these two tools is consistent and the output should
be the same.  There's always a chance that snap-tool had quirks which a
move to the snap CLI uncovers, where the result would be different snaps
seeded from before the change. An example would be channel differences
before and after this change. I haven't seen issues in my testing and I
do think it's unlikely, mostly I'm suspicious of SRUs that don't list
any regression potentials.

[Other Info]

* The attached MP for Xenial is simpler as it never had snap-tool.  The
Xenial MP is a minor change to give us parity between releases for use
of the snap cohort key during download.

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
     Assignee: Robert C Jennings (rcj)
         Status: New

-- 
preseeded snap installs fail in images
https://bugs.launchpad.net/bugs/1864252
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1864252 at bugs.launchpad.net  Sat Feb 22 11:50:36 2020
From: 1864252 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 22 Feb 2020 11:50:36 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158237223701.30858.7433323963291823566.malone@wampee.canonical.com>

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

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The attached MP for Xenial is simpler as it never had snap-tool.
  The Xenial MP is a minor change to give us parity between releases for
  use of the snap cohort key during download.

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


From 1864290 at bugs.launchpad.net  Sat Feb 22 12:01:56 2020
From: 1864290 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Sat, 22 Feb 2020 12:01:56 -0000
Subject: [Bug 1864290] [NEW] FTBFS on python2 removal
References: <158237256760.15247.4588406611716473506.malonedeb@soybean.canonical.com>
Message-ID: <158237291702.24647.3255581893668368789.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Mitsuya Shibata (cosmos-door):

mozc cannot build current focal because /usr/bin/python is removed.

https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1

INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc
ninja: Entering directory `out_linux/Release'
[1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc 
cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
/bin/sh: 1: python: not found

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

-- 
FTBFS on python2 removal
https://bugs.launchpad.net/bugs/1864290
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From mty.shibata at gmail.com  Sat Feb 22 12:01:07 2020
From: mty.shibata at gmail.com (Mitsuya Shibata)
Date: Sat, 22 Feb 2020 12:01:07 -0000
Subject: [Bug 1864290] Re: FTBFS on python2 removal
References: <158237256760.15247.4588406611716473506.malonedeb@soybean.canonical.com>
Message-ID: <158237286744.25031.13851574648566658041.malone@gac.canonical.com>

Upstream of mozc package doesn't prepare to support python3 yet.
I attach patch which just use "/usr/bin/python2" instead of "/usr/bin/python" on build package.

Could you sponsor it?

** Patch added: "workaround_python2_removal.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1864290/+attachment/5330275/+files/workaround_python2_removal.debdiff

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864290

Title:
  FTBFS on python2 removal

Status in mozc package in Ubuntu:
  In Progress

Bug description:
  mozc cannot build current focal because /usr/bin/python is removed.

  https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1

  INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc
  ninja: Entering directory `out_linux/Release'
  [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc 
  cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  /bin/sh: 1: python: not found

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


From robert.ancell at canonical.com  Sun Feb 23 20:22:03 2020
From: robert.ancell at canonical.com (Robert Ancell)
Date: Sun, 23 Feb 2020 20:22:03 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158248932346.24223.5165799696325601017.malone@gac.canonical.com>

I uploaded 1.0.29-0ubuntu2 to focal

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From iain at orangesquash.org.uk  Mon Feb 24 09:15:32 2020
From: iain at orangesquash.org.uk (Iain Lane)
Date: Mon, 24 Feb 2020 09:15:32 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158253573228.24857.2413872887152590146.malone@gac.canonical.com>

After the dropping of snap-tool, Ubuntu desktop ISOs are failing to
build:

error: cannot validate seed:
- cannot use snap "gnome-3-28-1804": base "core18" is missing
- cannot use snap "gnome-calculator": base "core18" is missing
- cannot use snap "gnome-characters": base "core18" is missing
- cannot use snap "gnome-logs": base "core18" is missing
- cannot use snap "gtk-common-themes": base "core18" is missing

https://launchpadlibrarian.net/466333748/buildlog_ubuntu_focal_amd64_ubuntu_BUILDING.txt.gz

Ah, OK:

$ ./snap-tool info gnome-logs | egrep '^base:'
$ base:      core18
$ snap info gnome-logs | egrep '^base:'
$ 

but there is:

$ snap info --verbose gnome-logs | egrep '^base:'
$ base:    core18

so I think we just need to add --verbose.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The attached MP for Xenial is simpler as it never had snap-tool.
  The Xenial MP is a minor change to give us parity between releases for
  use of the snap cohort key during download.

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


From kleber.souza at canonical.com  Mon Feb 24 09:54:48 2020
From: kleber.souza at canonical.com (Kleber Sacilotto de Souza)
Date: Mon, 24 Feb 2020 09:54:48 -0000
Subject: [Bug 1837886] Re: kpatch 0.5.0-0ubuntu2 ADT test failure with linux
 5.3.0-0.1
References: <156405991404.18485.18350487893200706506.malonedeb@gac.canonical.com>
Message-ID: <158253808833.24118.12405523348823955691.malone@gac.canonical.com>

This issue also affects Eoan.

** Also affects: kpatch (Ubuntu Eoan)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1837886

Title:
  kpatch 0.5.0-0ubuntu2 ADT test failure with linux 5.3.0-0.1

Status in kpatch package in Ubuntu:
  New
Status in kpatch source package in Bionic:
  New
Status in kpatch source package in Eoan:
  New

Bug description:
  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/k/kpatch/20190724_125410_41a25@/log.gz

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


From iain at orangesquash.org.uk  Mon Feb 24 11:24:25 2020
From: iain at orangesquash.org.uk (Iain Lane)
Date: Mon, 24 Feb 2020 11:24:25 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158254346573.28653.897424232831327453.malone@chaenomeles.canonical.com>

> so I think we just need to add --verbose.

(I've done that in focal now. Will trigger a rebuild if & when this
migrates out.)

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The attached MP for Xenial is simpler as it never had snap-tool.
  The Xenial MP is a minor change to give us parity between releases for
  use of the snap cohort key during download.

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


From 1862926 at bugs.launchpad.net  Mon Feb 24 11:52:42 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Mon, 24 Feb 2020 11:52:42 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158254516303.15520.12036990912171024776.malone@soybean.canonical.com>

Thank you for the second upload, it fixed the general FTBFS but some
architectures still show problems:


i386 (the only remaining 32-bit architecture?):

The genesys backend fails the unit tests due to a problem with floating
point arithmetics on 32/64-bit. There are bug reports upstream, but all
unsolved:

https://gitlab.com/sane-project/backends/issues/241
https://gitlab.com/sane-project/backends/issues/157


ppc64el:

Fails on symbol table generation:

dh_makeshlibs -- -v1.0.29 -Pdebian/libsane -plibsane
dpkg-gensymbols: warning: new libraries appeared in the symbols file: libsane-ricoh2.so.1 libsane-escl.so.1
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
dpkg-gensymbols: warning: debian/libsane/DEBIAN/symbols doesn't match completely debian/libsane.symbols.ppc64el

Do we really need to generate symbol tables for each scanner driver? No
one develops against the drivers, only against the main library.

To fix, one simply needs to copy the patch from the buildlog and apply
it.

And why do we need these scanner drivers on server-only architectures?


s390x:

Bog known and fixed upstream:

https://gitlab.com/sane-project/backends/-/merge_requests/329



So the biggest problem is the i386, as upstream has no solution for that, perhaps skip this one test (genesys backend) i386-only.


** Bug watch added: gitlab.com/sane-project/backends/issues #241
   https://gitlab.com/sane-project/backends/issues/241

** Bug watch added: gitlab.com/sane-project/backends/issues #157
   https://gitlab.com/sane-project/backends/issues/157

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1862926 at bugs.launchpad.net  Mon Feb 24 12:03:15 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Mon, 24 Feb 2020 12:03:15 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158254579517.24807.7027984837982996711.malone@gac.canonical.com>

Already when I started updating SANE to 1.0.29 I had a look into Rolf
Bensch's PPA

https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git/+packages

and overtaken some of his work, especially I copied the symbols files.
But his package is not built for ppc64el and s390x (probably because no
one needs scanner drivers on these server-only architectures?). Probably
therefore ppc64el fails with the symbol table.

The s390x problem Rolf also did not hit due to his selection of
architectures.

The i386 problem is known to Rolf and this has made him skipping the
unit tests altogether:

https://gitlab.com/sane-project/backends/issues/157#note_270664146

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From eric.desrochers at canonical.com  Mon Feb 24 13:07:08 2020
From: eric.desrochers at canonical.com (Eric Desrochers)
Date: Mon, 24 Feb 2020 13:07:08 -0000
Subject: [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is
 manual ipv6 is assigned to it
References: <153795476448.25111.10599931296514318283.malonedeb@gac.canonical.com>
Message-ID: <158254962807.29007.4904564187866110591.malone@chaenomeles.canonical.com>

@xtrusia,

Is this ready for sponsorship ?

I'll have a look when ready.

- Eric

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1794478

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  [Impact]

  In case creating bond interface, IPv4 address is not automatically
  assigned when IPv6 has manual setting.

  [Test Case]

  1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description.
  2. ipv6 manual, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5;
  sudo nmcli c s bond0
  ##################################
  3. ipv6 auto, ipv4 auto
  ##################################
  sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup;
  sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0";
  sudo nmcli con mod bond0 ipv6.method auto;
  sudo nmcli con mod bond0 ipv4.method auto;
  sudo nmcli con add type bond-slave ifname ens34 master bond0;
  sudo nmcli con add type bond-slave ifname ens35 master bond0;
  sudo nmcli con mod bond0 +bond.options mii=100

  sleep 5

  sudo nmcli con up bond-slave-ens34
  sudo nmcli con up bond-slave-ens35
  sudo nmcli con up bond0;

  sleep 5

  sudo nmcli c s bond0
  ##################################

  when run #3, it is working, but with #2, it is not working.

  [Potential Regression]

  Actually nothing special. fix just remove if statement. but it needs
  Network Manager restarted.

  [Other informations]

  After upstream fix, it is working fine with #2 and #3 above.

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
      network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
      network-manager | 1.22.4-1ubuntu2     | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond
         valid_lft 353sec preferred_lft 353sec
      inet6 fe80::ff:feb3:b522/64 scope link
         valid_lft forever preferred_lft forever

  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root at NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog
  root at NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
      link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
      inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
         valid_lft forever preferred_lft forever

  ==> Correct LP-Package need to be assigned...!

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


From 1864252 at bugs.launchpad.net  Mon Feb 24 19:35:07 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Mon, 24 Feb 2020 19:35:07 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158257290745.14879.1023943300127413098.malone@soybean.canonical.com>

Thank laney, I've fixed up the SRUs

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The attached MP for Xenial is simpler as it never had snap-tool.
  The Xenial MP is a minor change to give us parity between releases for
  use of the snap cohort key during download.

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


From 1864252 at bugs.launchpad.net  Mon Feb 24 22:19:16 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Mon, 24 Feb 2020 22:19:16 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158258275808.24756.9498208222197571442.launchpad@gac.canonical.com>

** Description changed:

  [Impact]
  
  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.
  
  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.
  
  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.
  
  [Test Case]
  
   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)
  
   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'
  
  [Regression Potential]
  
   * The interface for these two tools is consistent and the output should
  be the same.  There's always a chance that snap-tool had quirks which a
  move to the snap CLI uncovers, where the result would be different snaps
  seeded from before the change. An example would be channel differences
  before and after this change. I haven't seen issues in my testing and I
  do think it's unlikely, mostly I'm suspicious of SRUs that don't list
  any regression potentials.
  
  [Other Info]
  
- * The attached MP for Xenial is simpler as it never had snap-tool.  The
- Xenial MP is a minor change to give us parity between releases for use
- of the snap cohort key during download.
+ * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
+ * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From brian at ubuntu.com  Tue Feb 25 01:22:27 2020
From: brian at ubuntu.com (Brian Murray)
Date: Tue, 25 Feb 2020 01:22:27 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158259374824.18997.1803861810295766590.launchpad@chaenomeles.canonical.com>

** Also affects: livecd-rootfs (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: livecd-rootfs (Ubuntu Xenial)
       Status: New => In Progress

** Changed in: livecd-rootfs (Ubuntu Xenial)
     Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: New => Confirmed

** Changed in: livecd-rootfs (Ubuntu Eoan)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1862926 at bugs.launchpad.net  Tue Feb 25 04:33:33 2020
From: 1862926 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 25 Feb 2020 04:33:33 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158260521331.21937.14192821279961805687.launchpad@chaenomeles.canonical.com>

** Bug watch removed: gitlab.com/sane-project/backends/issues #157
   https://gitlab.com/sane-project/backends/issues/157

** Bug watch removed: gitlab.com/sane-project/backends/issues #241
   https://gitlab.com/sane-project/backends/issues/241

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1864290 at bugs.launchpad.net  Tue Feb 25 04:40:39 2020
From: 1864290 at bugs.launchpad.net (Mathew Hodson)
Date: Tue, 25 Feb 2020 04:40:39 -0000
Subject: [Bug 1864290] Re: FTBFS on python2 removal
References: <158237256760.15247.4588406611716473506.malonedeb@soybean.canonical.com>
Message-ID: <158260564040.16379.10174176988025773957.launchpad@wampee.canonical.com>

** Tags added: ftbfs

** Changed in: mozc (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864290

Title:
  FTBFS on python2 removal

Status in mozc package in Ubuntu:
  In Progress

Bug description:
  mozc cannot build current focal because /usr/bin/python is removed.

  https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1

  INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc
  ninja: Entering directory `out_linux/Release'
  [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc 
  cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  /bin/sh: 1: python: not found

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


From 1864290 at bugs.launchpad.net  Tue Feb 25 08:43:13 2020
From: 1864290 at bugs.launchpad.net (Gunnar Hjalmarsson)
Date: Tue, 25 Feb 2020 08:43:13 -0000
Subject: [Bug 1864290] Re: FTBFS on python2 removal
References: <158237256760.15247.4588406611716473506.malonedeb@soybean.canonical.com>
Message-ID: <158262019329.14831.14798279421057614644.malone@soybean.canonical.com>

Thanks for the fix! Sponsored to focal.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864290

Title:
  FTBFS on python2 removal

Status in mozc package in Ubuntu:
  Fix Committed

Bug description:
  mozc cannot build current focal because /usr/bin/python is removed.

  https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1

  INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc
  ninja: Entering directory `out_linux/Release'
  [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc 
  cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  /bin/sh: 1: python: not found

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


From 1864290 at bugs.launchpad.net  Tue Feb 25 10:47:16 2020
From: 1864290 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 25 Feb 2020 10:47:16 -0000
Subject: [Bug 1864290] Re: FTBFS on python2 removal
References: <158237256760.15247.4588406611716473506.malonedeb@soybean.canonical.com>
Message-ID: <158262763839.28382.9902450098661571921.malone@ackee.canonical.com>

This bug was fixed in the package mozc - 2.23.2815.102+dfsg-8ubuntu1

---------------
mozc (2.23.2815.102+dfsg-8ubuntu1) focal; urgency=medium

  * Add d/patches/workaround_python2.patch
    Use "python2" explicitly in gyp scripts to workaround for focal
    (LP: #1864290).

 -- Mitsuya Shibata <mty.shibata at gmail.com>  Sat, 22 Feb 2020 18:01:18
+0900

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864290

Title:
  FTBFS on python2 removal

Status in mozc package in Ubuntu:
  Fix Released

Bug description:
  mozc cannot build current focal because /usr/bin/python is removed.

  https://launchpad.net/ubuntu/+source/mozc/2.23.2815.102+dfsg-8build1

  INFO: Running: ninja -v -C out_linux/Release ibus_mozc mozc_emacs_helper mozc_server mozc_renderer fcitx-mozc uim-mozc
  ninja: Entering directory `out_linux/Release'
  [1/629] cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  FAILED: gen/proto_out/usage_stats/usage_stats.pb.h gen/proto_out/usage_stats/usage_stats.pb.cc 
  cd ../../usage_stats; python ../build_tools/protoc_wrapper.py "--project_root=.." "--protoc_command=protoc" "--proto=usage_stats.proto" "--cpp_out=../out_linux/Release/gen/proto_out"
  /bin/sh: 1: python: not found

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


From 1864643 at bugs.launchpad.net  Tue Feb 25 11:55:47 2020
From: 1864643 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Tue, 25 Feb 2020 11:55:47 -0000
Subject: [Bug 1864643] [NEW] Sync gr-osmosdr 0.2.0-2 (universe) from Debian
 unstable (main)
References: <158263174478.16013.3146596872310814103.malonedeb@soybean.canonical.com>
Message-ID: <158263174751.16144.4536443964204904327.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Clayton Smith (argilo):

Please sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Actually look for boost components and link against them in CMake.

0.2.0-2 already includes the appropriate find_package for Boost,
so this patch should no longer be necessary.

Changelog entries since current focal version 0.1.5-1ubuntu2:

gr-osmosdr (0.2.0-2) unstable; urgency=medium

  * Upload to unstable
  * Upstream refactored from wx to Qt (Closes: #885943)

 -- A. Maitland Bottoms <bottoms at debian.org>  Fri, 21 Feb 2020 18:19:42
-0500

gr-osmosdr (0.2.0-1) experimental; urgency=medium

  * New upstream tag
  * update watch file
  * upload to experimental for soversion bump

 -- A. Maitland Bottoms <bottoms at debian.org>  Wed, 19 Feb 2020 19:14:57
-0500

** Affects: gr-osmosdr (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1864643
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From seb128 at ubuntu.com  Tue Feb 25 14:25:17 2020
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Tue, 25 Feb 2020 14:25:17 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158264071800.12624.10564248617451804349.malone@gac.canonical.com>

The build got fixed now
https://launchpad.net/ubuntu/+source/sane-backends/1.0.29-0ubuntu5
the remaining blocked is an arm64 autopkgtest issue which isn't new to this update

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1862926 at bugs.launchpad.net  Tue Feb 25 16:45:47 2020
From: 1862926 at bugs.launchpad.net (Till Kamppeter)
Date: Tue, 25 Feb 2020 16:45:47 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158264914749.13322.4598810873028586397.malone@gac.canonical.com>

Seb, thanks for the info about the package being fixed.
locutusofborg, thanks for fixing and uploading.

** Changed in: sane-backends (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From rolf at bensch-online.de  Tue Feb 25 18:51:51 2020
From: rolf at bensch-online.de (Rolf Bensch)
Date: Tue, 25 Feb 2020 18:51:51 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158265671150.13040.10374915429530521342.malone@gac.canonical.com>

Till, in my ppa the symbol files are not up to date. I just removed
outdated entries, but not added new ones.

However, libpng-dev is included to the build by other dependecies. I see
that adding this package to control file makes this dependency more
transparent and I'll add it into my ppa.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1864643 at bugs.launchpad.net  Tue Feb 25 19:11:50 2020
From: 1864643 at bugs.launchpad.net (Hans Joachim Desserud)
Date: Tue, 25 Feb 2020 19:11:50 -0000
Subject: [Bug 1864643] Re: Sync gr-osmosdr 0.2.0-2 (universe) from Debian
 unstable (main)
References: <158263174478.16013.3146596872310814103.malonedeb@soybean.canonical.com>
Message-ID: <158265791149.14778.4658000423720186829.launchpad@wampee.canonical.com>

** Tags added: upgrade-software-version

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864643

Title:
  Sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

Status in gr-osmosdr package in Ubuntu:
  New

Bug description:
  Please sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Actually look for boost components and link against them in CMake.

  0.2.0-2 already includes the appropriate find_package for Boost,
  so this patch should no longer be necessary.

  Changelog entries since current focal version 0.1.5-1ubuntu2:

  gr-osmosdr (0.2.0-2) unstable; urgency=medium

    * Upload to unstable
    * Upstream refactored from wx to Qt (Closes: #885943)

   -- A. Maitland Bottoms <bottoms at debian.org>  Fri, 21 Feb 2020
  18:19:42 -0500

  gr-osmosdr (0.2.0-1) experimental; urgency=medium

    * New upstream tag
    * update watch file
    * upload to experimental for soversion bump

   -- A. Maitland Bottoms <bottoms at debian.org>  Wed, 19 Feb 2020
  19:14:57 -0500

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


From 1864252 at bugs.launchpad.net  Tue Feb 25 22:17:35 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Tue, 25 Feb 2020 22:17:35 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158266905558.14995.5377312358368389231.launchpad@soybean.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/379858

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864643 at bugs.launchpad.net  Wed Feb 26 01:35:17 2020
From: 1864643 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 26 Feb 2020 01:35:17 -0000
Subject: [Bug 1864643] Re: Sync gr-osmosdr 0.2.0-2 (universe) from Debian
 unstable (main)
References: <158263174478.16013.3146596872310814103.malonedeb@soybean.canonical.com>
Message-ID: <158268091782.14146.5394430586561721655.launchpad@wampee.canonical.com>

** Changed in: gr-osmosdr (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864643

Title:
  Sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

Status in gr-osmosdr package in Ubuntu:
  New

Bug description:
  Please sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Actually look for boost components and link against them in CMake.

  0.2.0-2 already includes the appropriate find_package for Boost,
  so this patch should no longer be necessary.

  Changelog entries since current focal version 0.1.5-1ubuntu2:

  gr-osmosdr (0.2.0-2) unstable; urgency=medium

    * Upload to unstable
    * Upstream refactored from wx to Qt (Closes: #885943)

   -- A. Maitland Bottoms <bottoms at debian.org>  Fri, 21 Feb 2020
  18:19:42 -0500

  gr-osmosdr (0.2.0-1) experimental; urgency=medium

    * New upstream tag
    * update watch file
    * upload to experimental for soversion bump

   -- A. Maitland Bottoms <bottoms at debian.org>  Wed, 19 Feb 2020
  19:14:57 -0500

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


From 1864252 at bugs.launchpad.net  Wed Feb 26 01:47:55 2020
From: 1864252 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 26 Feb 2020 01:47:55 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158268167660.18796.4965531338728136877.launchpad@chaenomeles.canonical.com>

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => High

** Changed in: livecd-rootfs (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: livecd-rootfs (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: livecd-rootfs (Ubuntu Eoan)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1837886 at bugs.launchpad.net  Wed Feb 26 01:46:28 2020
From: 1837886 at bugs.launchpad.net (Mathew Hodson)
Date: Wed, 26 Feb 2020 01:46:28 -0000
Subject: [Bug 1837886] Re: kpatch 0.5.0-0ubuntu2 ADT test failure with linux
 5.3.0-0.1
References: <156405991404.18485.18350487893200706506.malonedeb@gac.canonical.com>
Message-ID: <158268158967.13991.10409667195389405345.launchpad@wampee.canonical.com>

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1837886

Title:
  kpatch 0.5.0-0ubuntu2 ADT test failure with linux 5.3.0-0.1

Status in kpatch package in Ubuntu:
  New
Status in kpatch source package in Bionic:
  New
Status in kpatch source package in Eoan:
  New

Bug description:
  Testing failed on:
      amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-bootstrap/eoan/amd64/k/kpatch/20190724_125410_41a25@/log.gz

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


From 1864252 at bugs.launchpad.net  Wed Feb 26 02:28:40 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Wed, 26 Feb 2020 02:28:40 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158268412030.14048.11386483877820528596.launchpad@wampee.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/379863

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864252 at bugs.launchpad.net  Wed Feb 26 03:15:53 2020
From: 1864252 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 26 Feb 2020 03:15:53 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158268695445.21915.8393290112731874091.launchpad@ackee.canonical.com>

** Merge proposal unlinked:
   https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/379691

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864824 at bugs.launchpad.net  Wed Feb 26 10:11:32 2020
From: 1864824 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 26 Feb 2020 10:11:32 -0000
Subject: [Bug 1864824] [NEW] BlueZ 5.53 release
References: <158271116779.14250.3631803704679599614.malonedeb@gac.canonical.com>
Message-ID: <158271189296.13372.8753820776470414040.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Daniel van Vugt (vanvugt):

Release BlueZ 5.53 to focal.

** Affects: bluez (Ubuntu)
     Importance: Undecided
     Assignee: Daniel van Vugt (vanvugt)
         Status: In Progress


** Tags: champagne focal
-- 
BlueZ 5.53 release
https://bugs.launchpad.net/bugs/1864824
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From seb128 at ubuntu.com  Wed Feb 26 11:10:37 2020
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Wed, 26 Feb 2020 11:10:37 -0000
Subject: [Bug 1864824] Re: BlueZ 5.53 release
References: <158271116779.14250.3631803704679599614.malonedeb@gac.canonical.com>
Message-ID: <158271543838.15043.16429123503436312027.launchpad@soybean.canonical.com>

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864824

Title:
  BlueZ 5.53 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.53 to focal.

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


From 1864861 at bugs.launchpad.net  Wed Feb 26 14:41:00 2020
From: 1864861 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 26 Feb 2020 14:41:00 -0000
Subject: [Bug 1864861] [NEW] Sync ruby-defaults 1:2.7~0 (main) from Debian
 experimental (main)
References: <158272805527.19592.5579831107736158881.malonedeb@chaenomeles.canonical.com>
Message-ID: <158272806092.14778.14316702435826285616.launchpad@wampee.canonical.com>

You have been subscribed to a public bug by Lucas Kanashiro (lucaskanashiro):

Please sync ruby-defaults 1:2.7~0 (main) from Debian experimental (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Make autopkgtests cross-test-friendly.

The delta was applied in Debian version 1:2.5.7.1.

This sync will allow us to start the Ruby 2.7 transition since the version
1:2.7~0 supports only Ruby 2.7 (Ruby 2.5 support was dropped).

It builds fine in Focal and the autopkgtest passes.

Changelog entries since current focal version 1:2.5.2ubuntu1:

ruby-defaults (1:2.7~0) experimental; urgency=medium

  [ Antonio Terceiro ]
  * Make Ruby 2.7 the default and drop Ruby 2.5
  * debian/tests/control: add test-name pkg-config test
  * debian/tests/ruby-all-dev: remove deprecated usage of global must_match
  * Remove ruby.postinst, not really needed nowadays

 -- Antonio Terceiro <terceiro at debian.org>  Tue, 25 Feb 2020 16:20:01
-0300

ruby-defaults (1:2.5.7.1) unstable; urgency=medium

  * d/t/control: Make autopkgtests cross-test-friendly
  * d/t/smoke-test: use $AUTOPKGTEST_TMP instead of the deprecated $ADTTMP
  * Declare compliance with Debian Policy 4.5.0
  * Bump debhelper compaitiblity level to 12

 -- Lucas Kanashiro <kanashiro at debian.org>  Thu, 20 Feb 2020 16:11:01
-0300

ruby-defaults (1:2.5.7) unstable; urgency=medium

  * Upload to unstable.
    + Both interpreters, 2.5 and 2.7, are enabled.

 -- Lucas Kanashiro <kanashiro at debian.org>  Mon, 17 Feb 2020 19:34:01
-0300

ruby-defaults (1:2.5.7~0) experimental; urgency=medium

  * Enable building against ruby2.7
  * Add myself to Uploaders

 -- Lucas Kanashiro <kanashiro at debian.org>  Wed, 27 Nov 2019 18:27:44
-0300

** Affects: ruby-defaults (Ubuntu)
     Importance: Wishlist
         Status: New

-- 
Sync ruby-defaults 1:2.7~0 (main) from Debian experimental (main)
https://bugs.launchpad.net/bugs/1864861
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From rafaeldtinoco at ubuntu.com  Wed Feb 26 15:00:48 2020
From: rafaeldtinoco at ubuntu.com (Rafael David Tinoco)
Date: Wed, 26 Feb 2020 15:00:48 -0000
Subject: [Bug 1864861] Re: Sync ruby-defaults 1:2.7~0 (main) from Debian
 experimental (main)
References: <158272805527.19592.5579831107736158881.malonedeb@chaenomeles.canonical.com>
Message-ID: <158272924814.13750.771543880207418895.malone@gac.canonical.com>

This bug was fixed in the package ruby-defaults - 1:2.7~0
Sponsored for Lucas Kanashiro (lucaskanashiro)

---------------
ruby-defaults (1:2.7~0) experimental; urgency=medium

  [ Antonio Terceiro ]
  * Make Ruby 2.7 the default and drop Ruby 2.5
  * debian/tests/control: add test-name pkg-config test
  * debian/tests/ruby-all-dev: remove deprecated usage of global must_match
  * Remove ruby.postinst, not really needed nowadays

 -- Antonio Terceiro <terceiro at debian.org>  Tue, 25 Feb 2020 16:20:01
-0300

ruby-defaults (1:2.5.7.1) unstable; urgency=medium

  * d/t/control: Make autopkgtests cross-test-friendly
  * d/t/smoke-test: use $AUTOPKGTEST_TMP instead of the deprecated $ADTTMP
  * Declare compliance with Debian Policy 4.5.0
  * Bump debhelper compaitiblity level to 12

 -- Lucas Kanashiro <kanashiro at debian.org>  Thu, 20 Feb 2020 16:11:01
-0300

ruby-defaults (1:2.5.7) unstable; urgency=medium

  * Upload to unstable.
    + Both interpreters, 2.5 and 2.7, are enabled.

 -- Lucas Kanashiro <kanashiro at debian.org>  Mon, 17 Feb 2020 19:34:01
-0300

ruby-defaults (1:2.5.7~0) experimental; urgency=medium

  * Enable building against ruby2.7
  * Add myself to Uploaders

 -- Lucas Kanashiro <kanashiro at debian.org>  Wed, 27 Nov 2019 18:27:44
-0300

** Changed in: ruby-defaults (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864861

Title:
  Sync ruby-defaults 1:2.7~0 (main) from Debian experimental (main)

Status in ruby-defaults package in Ubuntu:
  Fix Released

Bug description:
  Please sync ruby-defaults 1:2.7~0 (main) from Debian experimental
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Make autopkgtests cross-test-friendly.

  The delta was applied in Debian version 1:2.5.7.1.

  This sync will allow us to start the Ruby 2.7 transition since the version
  1:2.7~0 supports only Ruby 2.7 (Ruby 2.5 support was dropped).

  It builds fine in Focal and the autopkgtest passes.

  Changelog entries since current focal version 1:2.5.2ubuntu1:

  ruby-defaults (1:2.7~0) experimental; urgency=medium

    [ Antonio Terceiro ]
    * Make Ruby 2.7 the default and drop Ruby 2.5
    * debian/tests/control: add test-name pkg-config test
    * debian/tests/ruby-all-dev: remove deprecated usage of global must_match
    * Remove ruby.postinst, not really needed nowadays

   -- Antonio Terceiro <terceiro at debian.org>  Tue, 25 Feb 2020 16:20:01
  -0300

  ruby-defaults (1:2.5.7.1) unstable; urgency=medium

    * d/t/control: Make autopkgtests cross-test-friendly
    * d/t/smoke-test: use $AUTOPKGTEST_TMP instead of the deprecated $ADTTMP
    * Declare compliance with Debian Policy 4.5.0
    * Bump debhelper compaitiblity level to 12

   -- Lucas Kanashiro <kanashiro at debian.org>  Thu, 20 Feb 2020 16:11:01
  -0300

  ruby-defaults (1:2.5.7) unstable; urgency=medium

    * Upload to unstable.
      + Both interpreters, 2.5 and 2.7, are enabled.

   -- Lucas Kanashiro <kanashiro at debian.org>  Mon, 17 Feb 2020 19:34:01
  -0300

  ruby-defaults (1:2.5.7~0) experimental; urgency=medium

    * Enable building against ruby2.7
    * Add myself to Uploaders

   -- Lucas Kanashiro <kanashiro at debian.org>  Wed, 27 Nov 2019 18:27:44
  -0300

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


From corradoventu at gmail.com  Wed Feb 26 18:20:29 2020
From: corradoventu at gmail.com (corrado venturini)
Date: Wed, 26 Feb 2020 18:20:29 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158274122912.13901.9612795135295907127.malone@gac.canonical.com>

On my Ubuntu 20.04 installed from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
doing update+upgrade the upgrade process hang with message
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864919 at bugs.launchpad.net  Wed Feb 26 20:23:15 2020
From: 1864919 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Wed, 26 Feb 2020 20:23:15 -0000
Subject: [Bug 1864919] [NEW] Sync lttng-modules 2.11.2-1 (universe) from
 Debian unstable (main)
References: <158274859291.19546.5429923140187231459.malonedeb@chaenomeles.canonical.com>
Message-ID: <158274859586.14311.10672967382579799075.launchpad@soybean.canonical.com>

You have been subscribed to a public bug by Michael Jeanson (mjeanson):

Please sync lttng-modules 2.11.2-1 (universe) from Debian unstable
(main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Fix dkms build with Linux 5.1/5.2 (LP: #1830048)
    - debian/patches/0006-Fix-mm-create-the-new-vm_fault_t-type-v5.1.patch
    - debian/patches/0007-Fix-rcu-Remove-wrapper-definitions-for-obsolete-RCU..patch
    - debian/patches/0008-Fix-pipe-stop-using-can_merge-v5.1.patch
    - debian/patches/0009-Fix-Revert-KVM-MMU-show-mmu_valid_gen.-v5.1.patch
    - debian/patches/0010-Fix-Remove-start-and-number-from-syscall_get_argumen.patch
    - debian/patches/0011-fix-timer-trace-Improve-timer-tracing-v5.2.patch
    - debian/patches/0012-fix-mm-vmscan-drop-may_writepage-and-classzone_idx-f.patch
    - debian/patches/0013-fix-mm-vmscan-simplify-trace_reclaim_flags-and-trace.patch
    - debian/patches/0014-fix-mm-move-recent_rotated-pages-calculation-to-shri.patch
    - debian/patches/0015-fix-random-only-read-from-dev-random-after-its-pool-.patch


All the ubuntu patches are backports from upstream which are included in the 2.11.2
release.


Changelog entries since current focal version 2.10.8-1ubuntu2:

lttng-modules (2.11.2-1) unstable; urgency=medium

  * [2bebc7c] New upstream version 2.11.2

 -- Michael Jeanson <mjeanson at debian.org>  Wed, 26 Feb 2020 11:12:39
-0500

lttng-modules (2.11.1-1) unstable; urgency=medium

  * [097ed28] New upstream version 2.11.1

 -- Michael Jeanson <mjeanson at debian.org>  Wed, 29 Jan 2020 11:40:35
-0500

lttng-modules (2.11.0-2) unstable; urgency=medium

  * [a196266] Add new probes to dkms config

 -- Michael Jeanson <mjeanson at debian.org>  Mon, 21 Oct 2019 17:18:34
-0400

lttng-modules (2.11.0-1) unstable; urgency=medium

  * [79326af] New upstream version 2.11.0
  * [a732214] Bump debhelper to 11
  * [b0627db] Set Rules-Requires-Root to no
  * [3da3e09] Bump standards version to 4.4.1
  * [1513156] Update d/copyright

 -- Michael Jeanson <mjeanson at debian.org>  Thu, 17 Oct 2019 15:49:22
-0400

lttng-modules (2.10.11-1) unstable; urgency=medium

  * [64ea811] New upstream version 2.10.11

 -- Michael Jeanson <mjeanson at debian.org>  Thu, 12 Sep 2019 11:17:02
-0400

lttng-modules (2.10.10-1) unstable; urgency=medium

  * [c753cf3] Disable Salsa CI autopkgtest test
  * [113af65] New upstream version 2.10.10

 -- Michael Jeanson <mjeanson at debian.org>  Fri, 12 Jul 2019 14:21:09
-0400

lttng-modules (2.10.9-2) unstable; urgency=medium

  * [f6ae7c6] Don't remove README from sources (Closes: #924896)

 -- Michael Jeanson <mjeanson at debian.org>  Mon, 18 Mar 2019 13:02:40
-0400

lttng-modules (2.10.9-1) unstable; urgency=medium

  * [000a3f0] Add Salsa CI configuration
  * [190ff29] dkms autopkgtest requires machine isolation
  * [a220fec] New upstream version 2.10.9
  * [f4fb560] Bump debhelper compat to 10
  * [60010d9] Bump standards version to 4.3.0
  * [77dbb46] Add upstream metadata file
  * [7a30331] Exclude doc files from usr/src

 -- Michael Jeanson <mjeanson at debian.org>  Tue, 12 Mar 2019 15:36:16
-0400

** Affects: lttng-modules (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Sync lttng-modules 2.11.2-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/1864919
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From steve.langasek at canonical.com  Wed Feb 26 20:20:45 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Wed, 26 Feb 2020 20:20:45 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
 <158274122912.13901.9612795135295907127.malone@gac.canonical.com>
Message-ID: <20200226202045.GA16573@homer.dodds.net>

On Wed, Feb 26, 2020 at 06:20:29PM -0000, corrado venturini wrote:
> On my Ubuntu 20.04 installed from Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
> doing update+upgrade the upgrade process hang with message
> snapd.failure.service is a disabled or a static unit, not starting it.
> snapd.snap-repair.service is a disabled or a static unit, not starting it.

That does not sound like it's related to this bug, but if it is, the remedy
would be for you to reinstall from a later image that has the fixed
preseeding behavior, or to manually fix the state of your snap installs.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864252 at bugs.launchpad.net  Wed Feb 26 20:23:34 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Wed, 26 Feb 2020 20:23:34 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158274861604.14098.17464587914406551343.launchpad@wampee.canonical.com>

** Changed in: livecd-rootfs (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From apw at canonical.com  Wed Feb 26 22:24:45 2020
From: apw at canonical.com (Andy Whitcroft)
Date: Wed, 26 Feb 2020 22:24:45 -0000
Subject: [Bug 1864919] Re: Sync lttng-modules 2.11.2-1 (universe) from Debian
 unstable (main)
References: <158274859291.19546.5429923140187231459.malonedeb@chaenomeles.canonical.com>
Message-ID: <158275588618.15194.5826538413046152509.launchpad@soybean.canonical.com>

** Changed in: lttng-modules (Ubuntu)
       Status: New => Fix Committed

** Changed in: lttng-modules (Ubuntu)
     Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: lttng-modules (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864919

Title:
  Sync lttng-modules 2.11.2-1 (universe) from Debian unstable (main)

Status in lttng-modules package in Ubuntu:
  Fix Released

Bug description:
  Please sync lttng-modules 2.11.2-1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Fix dkms build with Linux 5.1/5.2 (LP: #1830048)
      - debian/patches/0006-Fix-mm-create-the-new-vm_fault_t-type-v5.1.patch
      - debian/patches/0007-Fix-rcu-Remove-wrapper-definitions-for-obsolete-RCU..patch
      - debian/patches/0008-Fix-pipe-stop-using-can_merge-v5.1.patch
      - debian/patches/0009-Fix-Revert-KVM-MMU-show-mmu_valid_gen.-v5.1.patch
      - debian/patches/0010-Fix-Remove-start-and-number-from-syscall_get_argumen.patch
      - debian/patches/0011-fix-timer-trace-Improve-timer-tracing-v5.2.patch
      - debian/patches/0012-fix-mm-vmscan-drop-may_writepage-and-classzone_idx-f.patch
      - debian/patches/0013-fix-mm-vmscan-simplify-trace_reclaim_flags-and-trace.patch
      - debian/patches/0014-fix-mm-move-recent_rotated-pages-calculation-to-shri.patch
      - debian/patches/0015-fix-random-only-read-from-dev-random-after-its-pool-.patch

  
  All the ubuntu patches are backports from upstream which are included in the 2.11.2
  release.

  
  Changelog entries since current focal version 2.10.8-1ubuntu2:

  lttng-modules (2.11.2-1) unstable; urgency=medium

    * [2bebc7c] New upstream version 2.11.2

   -- Michael Jeanson <mjeanson at debian.org>  Wed, 26 Feb 2020 11:12:39
  -0500

  lttng-modules (2.11.1-1) unstable; urgency=medium

    * [097ed28] New upstream version 2.11.1

   -- Michael Jeanson <mjeanson at debian.org>  Wed, 29 Jan 2020 11:40:35
  -0500

  lttng-modules (2.11.0-2) unstable; urgency=medium

    * [a196266] Add new probes to dkms config

   -- Michael Jeanson <mjeanson at debian.org>  Mon, 21 Oct 2019 17:18:34
  -0400

  lttng-modules (2.11.0-1) unstable; urgency=medium

    * [79326af] New upstream version 2.11.0
    * [a732214] Bump debhelper to 11
    * [b0627db] Set Rules-Requires-Root to no
    * [3da3e09] Bump standards version to 4.4.1
    * [1513156] Update d/copyright

   -- Michael Jeanson <mjeanson at debian.org>  Thu, 17 Oct 2019 15:49:22
  -0400

  lttng-modules (2.10.11-1) unstable; urgency=medium

    * [64ea811] New upstream version 2.10.11

   -- Michael Jeanson <mjeanson at debian.org>  Thu, 12 Sep 2019 11:17:02
  -0400

  lttng-modules (2.10.10-1) unstable; urgency=medium

    * [c753cf3] Disable Salsa CI autopkgtest test
    * [113af65] New upstream version 2.10.10

   -- Michael Jeanson <mjeanson at debian.org>  Fri, 12 Jul 2019 14:21:09
  -0400

  lttng-modules (2.10.9-2) unstable; urgency=medium

    * [f6ae7c6] Don't remove README from sources (Closes: #924896)

   -- Michael Jeanson <mjeanson at debian.org>  Mon, 18 Mar 2019 13:02:40
  -0400

  lttng-modules (2.10.9-1) unstable; urgency=medium

    * [000a3f0] Add Salsa CI configuration
    * [190ff29] dkms autopkgtest requires machine isolation
    * [a220fec] New upstream version 2.10.9
    * [f4fb560] Bump debhelper compat to 10
    * [60010d9] Bump standards version to 4.3.0
    * [77dbb46] Add upstream metadata file
    * [7a30331] Exclude doc files from usr/src

   -- Michael Jeanson <mjeanson at debian.org>  Tue, 12 Mar 2019 15:36:16
  -0400

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


From 1864965 at bugs.launchpad.net  Thu Feb 27 12:26:07 2020
From: 1864965 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 27 Feb 2020 12:26:07 -0000
Subject: [Bug 1864965] [NEW] Add Intel RAID/RST detection with NVMe devices
References: <158278738697.14634.8487362183856735923.malonedeb@wampee.canonical.com>
Message-ID: <158280636793.14154.10404307740827846850.launchpad@gac.canonical.com>

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]

The disk-detect.sh supports to detect if Intel RAID/RST mode is
activated as NVMe devices are remapped to PCI bus. Based on this,
ubiquity installer can take advantage of detection and handle such a
case with improved user experience.

[Test Case]

There are several ways to test this case, but one of them will be
integration test:

In ubiquity, hw-detect will be sourced, and then import disk-detect.sh to call remapped_nvme_probe(). Then use the following command to get debconf value:
$ echo "get disk-detect/activate_remapped_nvme" | sudo debconf-communicate
0 True

[Regression Potential]

Some case will be different, especially the system doesn't have AHCI
when RAID mode was set in BIOS, so that PCI attribute "remapped_nvme" is
gone.

[Other Info]

To upstream to debian sid is another WIP item.

** Affects: hw-detect (Ubuntu)
     Importance: Undecided
     Assignee: Woodrow Shen (woodrow-shen)
         Status: New


** Tags: patch
-- 
Add Intel RAID/RST detection with NVMe devices
https://bugs.launchpad.net/bugs/1864965
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.


From 1864965 at bugs.launchpad.net  Thu Feb 27 12:26:08 2020
From: 1864965 at bugs.launchpad.net (Ubuntu Foundations Team Bug Bot)
Date: Thu, 27 Feb 2020 12:26:08 -0000
Subject: [Bug 1864965] Re: Add Intel RAID/RST detection with NVMe devices
References: <158278738697.14634.8487362183856735923.malonedeb@wampee.canonical.com>
Message-ID: <158280636819.13750.15779157266101401001.malone@gac.canonical.com>

The attachment "hw-detect_1.117ubuntu8.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864965

Title:
  Add Intel RAID/RST detection with NVMe devices

Status in hw-detect package in Ubuntu:
  New

Bug description:
  [Impact]

  The disk-detect.sh supports to detect if Intel RAID/RST mode is
  activated as NVMe devices are remapped to PCI bus. Based on this,
  ubiquity installer can take advantage of detection and handle such a
  case with improved user experience.

  [Test Case]

  There are several ways to test this case, but one of them will be
  integration test:

  In ubiquity, hw-detect will be sourced, and then import disk-detect.sh to call remapped_nvme_probe(). Then use the following command to get debconf value:
  $ echo "get disk-detect/activate_remapped_nvme" | sudo debconf-communicate
  0 True

  [Regression Potential]

  Some case will be different, especially the system doesn't have AHCI
  when RAID mode was set in BIOS, so that PCI attribute "remapped_nvme"
  is gone.

  [Other Info]

  To upstream to debian sid is another WIP item.

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


From 1848286 at bugs.launchpad.net  Thu Feb 27 12:49:11 2020
From: 1848286 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 27 Feb 2020 12:49:11 -0000
Subject: [Bug 1848286] Fix included in openstack/ceilometer 11.1.0
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <158280775137.14202.11497109349837017193.malone@gac.canonical.com>

This issue was fixed in the openstack/ceilometer 11.1.0 release.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

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


From 1848286 at bugs.launchpad.net  Thu Feb 27 12:49:41 2020
From: 1848286 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 27 Feb 2020 12:49:41 -0000
Subject: [Bug 1848286] Fix included in openstack/ceilometer 12.1.0
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <158280778165.19302.3900932900645870139.malone@chaenomeles.canonical.com>

This issue was fixed in the openstack/ceilometer 12.1.0 release.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

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


From 1848286 at bugs.launchpad.net  Thu Feb 27 12:50:09 2020
From: 1848286 at bugs.launchpad.net (OpenStack Infra)
Date: Thu, 27 Feb 2020 12:50:09 -0000
Subject: [Bug 1848286] Fix included in openstack/ceilometer 13.1.0
References: <157120349517.9264.9907033696688366629.malonedeb@soybean.canonical.com>
Message-ID: <158280780967.14778.3119728709352807814.malone@wampee.canonical.com>

This issue was fixed in the openstack/ceilometer 13.1.0 release.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848286

Title:
  octavia is not reporting metrics like lbaasv2

Status in Ceilometer:
  Fix Released
Status in OpenStack Octavia Charm:
  Triaged
Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive queens series:
  Triaged
Status in Ubuntu Cloud Archive rocky series:
  Fix Released
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in Ubuntu Cloud Archive train series:
  Fix Released
Status in ceilometer package in Ubuntu:
  Fix Released
Status in ceilometer source package in Bionic:
  Triaged
Status in ceilometer source package in Disco:
  Fix Released
Status in ceilometer source package in Eoan:
  Fix Released
Status in ceilometer source package in Focal:
  Fix Released

Bug description:
  [Environment]

  Stein OpenStack
  Ubuntu Bionic

  [Description]

  From my understanding the current Octavia API should be backwards
  compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
  should suffice to gather the following meters:

  meters:

  - network.services.lb.outgoing.bytes
  - network.services.lb.incoming.bytes
  - network.services.lb.pool
  - network.services.lb.listener
  - network.services.lb.member
  - network.services.lb.health_monitor
  - network.services.lb.loadbalancer
  - network.services.lb.total.connections
  - network.services.lb.active.connections

  However, the following warning is noticed when restarted the
  ceilometer services.

  2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi
  3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] metric network.services.lb.loadbalancer is not handled by Gnocchi

  In fact, by checking at the gnocchi metric list (https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
  metrics/resources haven't been created.

  The reason is that for a gnocchi resource to exist, ceilometer has to create the resource type explicitly.
  This action is commanded by the ceilometer gnocchi client [2] and it uses the file /usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
  for the resource definitions, which doesn't includes the lbaasv2 directives.

  [Test case]

  1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
  2) check that lb meters aren't being gathered

  $ gnocchi metric list|grep loadbalancer | wc -l
  0
  3) install the patched version
  4) configure all pollsters
  $  juju config ceilometer enable-all-pollsters=true
  5) sudo systemctl restart ceilometer*
  6) sudo ceilometer-upgrade
  7) Check that lb metrics are being gathered

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep loadbalancer | wc -l
  72

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae7040

  [Regression Potential]

  There is no regression potential identified on this patch as it uses
  the new metrics upgrade path and it doesn't
  enables any new metrics if the lbaasv2 pollster isn't configured.

  [Proposed solution]

  Enable the resources on /usr/lib/python3/dist packages/ceilometer/publisher/data/gnocchi_resources.yaml
  and modify the gnocchi client provider. I am able to gather the metrics for the octavia load balancers.

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric list|grep network.services
  | 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | network.services.lb.active.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | network.services.lb.loadbalancer | loadbalancer | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
  | 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | network.services.lb.total.connections | connection | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | network.services.lb.health_monitor | health_monitor | 3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
  | 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
  | bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | network.services.lb.active.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
  | eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | network.services.lb.total.connections | connection | 82d129f3-64a5-40d6-a72b-7ae704046176 |
  | ef04f494-884a-4097-ba58-74845f5fbf19 | ceilometer-low | network.services.lb.pool | pool | 6c4a5a4f-0455-42e6-8bf4-ed9c24e2c06c |

  ubuntu at niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi measures show ef04f494-884a-4097-ba58-74845f5fbf19
  +---------------------------+-------------+-------+
  | timestamp | granularity | value |
  +---------------------------+-------------+-------+
  | 2019-11-07T18:30:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:35:00+00:00 | 300.0 | 1.0 |
  | 2019-11-07T18:40:00+00:00 | 300.0 | 1.0 |
  +---------------------------+-------------+-------+

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


From seb128 at ubuntu.com  Thu Feb 27 13:38:45 2020
From: seb128 at ubuntu.com (Sebastien Bacher)
Date: Thu, 27 Feb 2020 13:38:45 -0000
Subject: [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf
 and alsa-topology-conf to focal image by default
References: <158124195825.19555.9087533038007685280.malonedeb@gac.canonical.com>
Message-ID: <158281072545.14194.9695273090708150870.malone@wampee.canonical.com>

Hey Hui, some comments about the report

- you subscribed ubuntu-sponsors but there is no debdiff to sponsor
there?

- alsa-lib in focal has libasound2-data Recommends 'Recommends: alsa-
ucm-conf, alsa-topology-conf'

- to be installed by default the recommends need to be in main, that's
bug #1862776

I guess the bug here can be closed?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862505

Title:
  alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-
  conf to focal image by default

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Before the alsa-lib-1.2.1 the ucm and topology conf files are in the
  alsa-lib, when we install the alsa-lib/libasound2, they are installed
  together with alsa-lib. But from 1.2.1 they are separated from the
  alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should
  install the ucm and topology too, otherwise those machines need ucm
  and topology will not work anymore, users have to install these two
  packages manually.

  Two packages we need to put into the focal image are:
  alsa-ucm-conf 1.2.1.2-2
  alsa-topology-conf 1.2.1-2

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


From 1864252 at bugs.launchpad.net  Thu Feb 27 14:23:42 2020
From: 1864252 at bugs.launchpad.net (Launchpad Bug Tracker)
Date: Thu, 27 Feb 2020 14:23:42 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158281342841.21918.6518042476918789043.launchpad@ackee.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/379968

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From alberto.donato at canonical.com  Tue Feb 25 11:24:23 2020
From: alberto.donato at canonical.com (Alberto Donato)
Date: Tue, 25 Feb 2020 11:24:23 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:snap-default-version into
 ubuntu/+source/maas:ubuntu/devel
Message-ID: <158262986187.16860.8401392482075091157.launchpad@ackee.canonical.com>

Alberto Donato has proposed merging ~ack/ubuntu/+source/maas:snap-default-version into ubuntu/+source/maas:ubuntu/devel.

Commit message:
set default snap track version  to 2.7/stable if snapd doesn't support default tracks

Requested reviews:
  Ubuntu Sponsors Team (ubuntu-sponsors)

For more details, see:
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379801
-- 
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:snap-default-version into ubuntu/+source/maas:ubuntu/devel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 1557 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-sponsors/attachments/20200225/a9be5fbe/attachment-0001.diff>

From adam.collard at canonical.com  Tue Feb 25 11:27:41 2020
From: adam.collard at canonical.com (Adam Collard)
Date: Tue, 25 Feb 2020 11:27:41 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:snap-default-version into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158262986187.16860.8401392482075091157.launchpad@ackee.canonical.com>
Message-ID: <158263006121.21440.767110194652274093.codereview@chaenomeles.canonical.com>



Diff comments:

> diff --git a/debian/maas.preinst b/debian/maas.preinst
> index 15da5cd..fb77981 100755
> --- a/debian/maas.preinst
> +++ b/debian/maas.preinst
> @@ -14,6 +15,16 @@ get_snap_mode() {
>      cat "$SNAP_COMMON/snap_mode" 2>/dev/null || true
>  }
>  
> +snapd_has_track_support() {

s/track/default_track/

> +    local version
> +    version=$(snap version | awk '$1 == "snapd" { print $2; }')
> +    local major="${version%%.*}"
> +    local rest="${version#*.}"
> +    local minor="${rest%%.*}"
> +
> +    [ "$major" -ge 2 ] && [ "$minor" -ge 44 ]
> +}
> +
>  check_connectivity() {
>      local count=0
>      while true; do


-- 
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379801
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:snap-default-version into ubuntu/+source/maas:ubuntu/devel.


From alberto.donato at canonical.com  Wed Feb 26 13:44:24 2020
From: alberto.donato at canonical.com (Alberto Donato)
Date: Wed, 26 Feb 2020 13:44:24 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:fix-description into
 ubuntu/+source/maas:ubuntu/devel
Message-ID: <158272466272.11105.17212738631991986753.launchpad@ackee.canonical.com>

Alberto Donato has proposed merging ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.

Commit message:
fix package long description to match as transitional package

Requested reviews:
  Ubuntu Sponsors Team (ubuntu-sponsors)

For more details, see:
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379892
-- 
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: review-diff.txt
Type: text/x-diff
Size: 1694 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-sponsors/attachments/20200226/2a12be0d/attachment-0001.diff>

From andreas at canonical.com  Thu Feb 27 12:48:08 2020
From: andreas at canonical.com (Andreas Hasenack)
Date: Thu, 27 Feb 2020 12:48:08 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:fix-description into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158272466272.11105.17212738631991986753.launchpad@ackee.canonical.com>
Message-ID: <158280768762.13945.12410068180372489236.codereview@wampee.canonical.com>

Review: Approve

+1
-- 
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379892
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.


From andreas at canonical.com  Thu Feb 27 12:52:54 2020
From: andreas at canonical.com (Andreas Hasenack)
Date: Thu, 27 Feb 2020 12:52:54 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:fix-description into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158272466272.11105.17212738631991986753.launchpad@ackee.canonical.com>
Message-ID: <158280797399.14449.4039016822743655326.codereview@soybean.canonical.com>

Sponsoring 14daa6d5fc4e98104718d3655ea489cf643f48f5
$ git push pkg upload/1%0.4
Enumerating objects: 14, done.
Counting objects: 100% (14/14), done.
Delta compression using up to 4 threads
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 1.16 KiB | 74.00 KiB/s, done.
Total 10 (delta 5), reused 0 (delta 0)
To ssh://git.launchpad.net/~usd-import-team/ubuntu/+source/maas
 * [new tag]           upload/1%0.4 -> upload/1%0.4

$ dput ubuntu ../maas_0.4_source.changes
Checking signature on .changes
gpg: ../maas_0.4_source.changes: Valid signature from AC983EB5BF6BCBA9
Checking signature on .dsc
gpg: ../maas_0.4.dsc: Valid signature from AC983EB5BF6BCBA9
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading maas_0.4.dsc: done.
  Uploading maas_0.4.tar.xz: done.
  Uploading maas_0.4_source.buildinfo: done.
  Uploading maas_0.4_source.changes: done.
Successfully uploaded packages.

-- 
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379892
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.


From andreas at canonical.com  Thu Feb 27 12:53:35 2020
From: andreas at canonical.com (Andreas Hasenack)
Date: Thu, 27 Feb 2020 12:53:35 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:fix-description into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158272466272.11105.17212738631991986753.launchpad@ackee.canonical.com>
Message-ID: <158280801450.21628.128005491841056744.launchpad@ackee.canonical.com>

The proposal to merge ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel has been updated.

    Status: Needs review => Approved

For more details, see:
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379892
-- 
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.


From noreply at launchpad.net  Thu Feb 27 13:02:51 2020
From: noreply at launchpad.net (noreply at launchpad.net)
Date: Thu, 27 Feb 2020 13:02:51 -0000
Subject: [Merge] ~ack/ubuntu/+source/maas:fix-description into
 ubuntu/+source/maas:ubuntu/devel
In-Reply-To: <158272466272.11105.17212738631991986753.launchpad@ackee.canonical.com>
Message-ID: <158280857083.21628.11521913523789613721.launchpad@ackee.canonical.com>

The proposal to merge ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel has been updated.

    Status: Approved => Merged

For more details, see:
https://code.launchpad.net/~ack/ubuntu/+source/maas/+git/maas/+merge/379892
-- 
Your team Ubuntu Sponsors Team is requested to review the proposed merge of ~ack/ubuntu/+source/maas:fix-description into ubuntu/+source/maas:ubuntu/devel.


From steve.langasek at canonical.com  Thu Feb 27 20:22:36 2020
From: steve.langasek at canonical.com (Steve Langasek)
Date: Thu, 27 Feb 2020 20:22:36 -0000
Subject: [Bug 1864252] Proposed package upload rejected
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158283495648.13276.160077394944580206.malone@gac.canonical.com>

An upload of livecd-rootfs to eoan-proposed has been rejected from the
upload queue for the following reason: "needs another bugfix".

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From 1864252 at bugs.launchpad.net  Fri Feb 28 16:57:55 2020
From: 1864252 at bugs.launchpad.net (Robert C Jennings)
Date: Fri, 28 Feb 2020 16:57:55 -0000
Subject: [Bug 1864252] Re: preseeded snap installs fail in images
References: <158232038891.28618.1753208284227465491.malonedeb@chaenomeles.canonical.com>
Message-ID: <158290907572.12686.16928186987885828929.launchpad@wampee.canonical.com>

** Merge proposal linked:
   https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/380036

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864252

Title:
  preseeded snap installs fail in images

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  In Progress
Status in livecd-rootfs source package in Bionic:
  Confirmed
Status in livecd-rootfs source package in Eoan:
  Confirmed

Bug description:
  [Impact]

  Images built with pre-seeded snaps contain insufficient assertion data
  causing boot to fail.

  The snaps for seeding are downloaded with a custom snap tool for an
  earlier cohort API (now deprecated).  The assertions that it pulls are
  incomplete.  We could update that list and move to the new API but at
  this time the snap-tool provides no value compared to use of the snap
  CLI (cohort support has moved to the cli as well).  The development
  overhead of maintaining snap-tool in livecd-rootfs are not warranted.

  This patch removes the bespoke snap-tool and relies on the snap CLI
  instead.

  [Test Case]

   * Produce images that include preseeded snaps (in
  /var/lib/snapd/seed/*)

   * Boot the resulting image and ensure that the snapd.seeded unit is
  successful and the snaps (from the correct channels) show up in 'snap
  list'

  [Regression Potential]

   * The interface for these two tools is consistent and the output
  should be the same.  There's always a chance that snap-tool had quirks
  which a move to the snap CLI uncovers, where the result would be
  different snaps seeded from before the change. An example would be
  channel differences before and after this change. I haven't seen
  issues in my testing and I do think it's unlikely, mostly I'm
  suspicious of SRUs that don't list any regression potentials.

  [Other Info]

  * The snap-tool that is being removed is used only in livecd-rootfs through live-build/functions.   The replacement with the upstream snap cli is equivalent the 'info' and 'download' commands that are used.  The snap-tool code is using deprecated APIs which do not provide the data needed for pre-seeding.
  * The attached MP for Xenial is simpler as it never had snap-tool.  The Xenial MP is a minor change to give us parity between releases for use of the snap cohort key during download.

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


From loganrosen at gmail.com  Sat Feb 29 05:44:42 2020
From: loganrosen at gmail.com (Logan Rosen)
Date: Sat, 29 Feb 2020 05:44:42 -0000
Subject: [Bug 1864643] Re: Sync gr-osmosdr 0.2.0-2 (universe) from Debian
 unstable (main)
References: <158263174478.16013.3146596872310814103.malonedeb@soybean.canonical.com>
Message-ID: <158295508284.7072.9702092108772352964.malone@chaenomeles.canonical.com>

Synced. Thanks!

** Changed in: gr-osmosdr (Ubuntu)
     Assignee: (unassigned) => Logan Rosen (logan)

** Changed in: gr-osmosdr (Ubuntu)
       Status: New => In Progress

** Changed in: gr-osmosdr (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1864643

Title:
  Sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

Status in gr-osmosdr package in Ubuntu:
  Fix Released

Bug description:
  Please sync gr-osmosdr 0.2.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Actually look for boost components and link against them in CMake.

  0.2.0-2 already includes the appropriate find_package for Boost,
  so this patch should no longer be necessary.

  Changelog entries since current focal version 0.1.5-1ubuntu2:

  gr-osmosdr (0.2.0-2) unstable; urgency=medium

    * Upload to unstable
    * Upstream refactored from wx to Qt (Closes: #885943)

   -- A. Maitland Bottoms <bottoms at debian.org>  Fri, 21 Feb 2020
  18:19:42 -0500

  gr-osmosdr (0.2.0-1) experimental; urgency=medium

    * New upstream tag
    * update watch file
    * upload to experimental for soversion bump

   -- A. Maitland Bottoms <bottoms at debian.org>  Wed, 19 Feb 2020
  19:14:57 -0500

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


From loganrosen at gmail.com  Sat Feb 29 05:47:19 2020
From: loganrosen at gmail.com (Logan Rosen)
Date: Sat, 29 Feb 2020 05:47:19 -0000
Subject: [Bug 1854555] Re: Sync lwt 4.3.0-2 (universe) from Debian unstable
 (main)
References: <157510141574.31064.3046553856640334817.malonedeb@wampee.canonical.com>
Message-ID: <158295523967.12073.16042447995210423106.malone@wampee.canonical.com>

We're in sync with Debian now. Closing this out.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1854555

Title:
  Sync lwt 4.3.0-2 (universe) from Debian unstable (main)

Status in lwt package in Ubuntu:
  Fix Released

Bug description:
  Please sync lwt 4.3.0-2 (universe) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Upload back in sync with Debian
    * Upload back in sync with Debian
    * Re-enable glib bindings, needed for zeroinstall-injector

  Looks like the changes were reverted again, effectively empty delta.

  Changelog entries since current focal version 2.7.1-7ubuntu2:

  lwt (4.3.0-2) unstable; urgency=medium

    * Comment out page_size test, which does not pass on all
  architectures

   -- Stéphane Glondu <glondu at debian.org>  Mon, 11 Nov 2019 11:20:36
  +0100

  lwt (4.3.0-1) unstable; urgency=medium

    * New upstream release
      - SSL bindings have been moved to a different package, drop binary
        packages liblwt-ssl-ocaml{,-dev}
      - drop liblwt-ocaml-doc which has been empty for a while

   -- Stéphane Glondu <glondu at debian.org>  Fri, 08 Nov 2019 16:34:06
  +0100

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


From a33ypool3kbhd at t-online.de  Sat Feb 29 11:47:05 2020
From: a33ypool3kbhd at t-online.de (nmaxx)
Date: Sat, 29 Feb 2020 11:47:05 -0000
Subject: [Bug 1862926] Re: Request for update: SANE 1.0.29
References: <158150690273.29381.8059242321717047107.malonedeb@chaenomeles.canonical.com>
Message-ID: <158297682583.7072.7716440220835234914.malone@chaenomeles.canonical.com>

That you so much for updating SANE to 1.0.29 - I think scanning in
Ubuntu is in a *much* better place now, including futureproofing via the
AirPrint device support. :)

Can't wait for the 20.04 release...

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862926

Title:
  Request for update: SANE 1.0.29

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Unknown

Bug description:
  In Focal we are still a bit old-fashioned regarding scanning. We are
  still at the ancient SANE 1.0.27! That is really INSANE.

  Current version is 1.0.29 and it contains a very important new feature
  which will make hundreds (thousands?) of new scanners work with
  Ubuntu. This new feature is Apple AirScan support as a client. I have
  introduced a lot of nice printing stuff to support AirPrint, making
  lots of printers (practically all modern network printers) working,
  and all the multi-function devices under these (printer and scanner in
  one) do AirScan, so all these scanner will work with SANE 1.0.29 (if
  yours does not, it is a bug in SANE, please report).

  The AirScan support is provided by the new "escl" backend. supporting
  the eSCL protocol AirPrint is based on. The protocol uses HTTP and
  XML, so this works out-of-the-box if your printer is connected to the
  network, if it is connected via USB it work via IPP-over-USB using the
  ippusbxd package.

  Changes list from upstream:

  - Backends
     + adds an escl backend (theoretically supporting all AirPrint devices with a scan unit
     + adds support for 23 new scanner models via existing backends
     + significantly changes genesys and pixma backends
     + fixes bugs in canon_dr, fujitsu, hp3900, mustek_usb2, plustek and xerox_mfp backends
     + fixes all compiler warnings on Debian 10 (#120)
     + fixes portability issues for uClibc-ng and MacOS builds
     + adds support to record and replay USB I/O traffic
     + adds timestamps to debug logs

  debdiff attached.

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


From 1818724 at bugs.launchpad.net  Sat Feb 29 17:35:01 2020
From: 1818724 at bugs.launchpad.net (Amr Ibrahim)
Date: Sat, 29 Feb 2020 17:35:01 -0000
Subject: [Bug 1818724] Re: Sync pdfchain 1:0.4.4.2-1 (universe) from Debian
 testing (main)
References: <155182009298.29074.7972310177326384773.malonedeb@chaenomeles.canonical.com>
Message-ID: <158299770159.7438.10267367268668091836.malone@chaenomeles.canonical.com>

This is still not synced.

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

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1818724

Title:
  Sync pdfchain 1:0.4.4.2-1 (universe) from Debian testing (main)

Status in pdfchain package in Ubuntu:
  New

Bug description:
  Please sync pdfchain 1:0.4.4.2-1 (universe) from Debian testing (main)

  All changelog entries:

  pdfchain (1:0.4.4.2-1) unstable; urgency=medium

    * New upstream version.
    * Bump Standards-Version to 3.9.8
      - remove debian/menu.
    * debian/copyright: Update years and fix format.
    * Add patch to fix spelling/grammar mistakes found by lintian.
    * debian/watch: Detect x.y.z releases properly.
    * debian/rules: Use hardening=+all.
    * debian/control: Use https:// links for Vcs-* and Homepage fields.

   -- Johann Felix Soden <johfel at debian.org>  Sat, 31 Dec 2016 16:19:18
  +0100

  pdfchain (1:0.4.4-1) unstable; urgency=medium

    * New upstream version.
    * Depend on pdftk >= 2.00.
    * debian/control: Vcs-Git shortened and Vcs-Browser fixed.
    * Bump Standards-Version to 3.9.5.
    * debian/copyright: Update years
    * Update fix_desktop_file patch.

   -- Johann Felix Soden <johfel at debian.org>  Sat, 21 Jun 2014 19:50:42
  +0200

  pdfchain (1:0.4.0-1) unstable; urgency=low

    * New upstream version.
    * Depend on pdftk >= 1.45.
    * Switch to debhelper compat v9.
    * debian/copyright: Update years and authors. Drop obsolete entries.
    * Bump Standards-Version to 3.9.4.
    * Use anonscm.debian.org for VCS-* fields.
    * Drop no longer necessary fix_build_system and fix_concatenate_bug patch
      and update fix_desktop_file patch and let it add keywords.
    * Do not install unneeded/empty documentation files.
    * debian/control: drop DM-Upload-Allowed flag.

   -- Johann Felix Soden <johfel at debian.org>  Mon, 01 Jul 2013 00:10:45
  +0200

  pdfchain (1:0.3.3-2) unstable; urgency=low

    * Use correct pdftk call for concatenating pdf files in all cases.
      (Closes: #696079)
    * debian/control: Change my e-mail address.

   -- Johann Felix Soden <johfel at debian.org>  Sun, 16 Dec 2012 16:37:21
  +0100

  pdfchain (1:0.3.3-1) unstable; urgency=low

    * New upstream version with new version numbering scheme
      - Increase epoch.
      - Adapt debian/watch.
    * Support dpkg-buildflags.
    * Depend on pdftk >= 1.44.
    * Build-depend on libgtkmm-3.0-dev.
    * Switch to debhelper compat v8.
    * Bump Standards-Version to 3.9.2.
    * Drop no longer necessary do_not_restrict_to_ascii patch and update
      fix_build_system and fix_desktop_file patch.
    * Update debian/copyright to latest DEP5 format.

   -- Johann Felix Soden <johfel at gmx.de>  Tue, 27 Dec 2011 14:19:23
  +0100

  pdfchain (0.123-2) unstable; urgency=low

    * Allow calling pdftk with non-ascii characters.
    * Depend on at least pdftk-1.41+dfsg for non-ascii support.
    * Add VCS fields to debian/control.
    * Convert package to the 3.0 (quilt) source format.
     - add debian/source/format
     - remove debian/README.source
     - debian/control: remove quilt from Build-Depends
     - debian/rules: do not use quilt dh add-on anymore

   -- Johann Felix Soden <johfel at gmx.de>  Tue, 24 Nov 2009 20:22:49
  +0100

  pdfchain (0.123-1) unstable; urgency=low

    * Initial release (Closes: #539866)

   -- Johann Felix Soden <johfel at gmx.de>  Tue, 18 Aug 2009 13:46:25
  +0200

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


